Bug 139146 - Crash pasting content inside table in impress, Windows only?
Summary: Crash pasting content inside table in impress, Windows only?
Status: RESOLVED DUPLICATE of bug 139074
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace, regression
Depends on:
Blocks:
 
Reported: 2020-12-22 08:26 UTC by Telesto
Modified: 2021-01-04 18:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screencast (334.13 KB, video/mp4)
2020-12-22 08:27 UTC, Telesto
Details
WinDbg ST crash on paste into Impress Table cell (12.58 KB, text/plain)
2020-12-22 19:15 UTC, V Stuart Foote
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-12-22 08:26:58 UTC
Description:
Crash cutting content inside table in impress

Steps to Reproduce:
1. Open Impress
2. Insert -> table -> OK
3. enter table cell
4. Type D
5. Select D
6. Cut
7. Paste different cell

Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.0.alpha0+ (x64)
Build ID: 315c7570c4a72f4c834086082825533b1e50d1bf
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-12-22 08:27:37 UTC
Created attachment 168403 [details]
Screencast
Comment 2 V Stuart Foote 2020-12-22 19:15:03 UTC
The crash is not on the Cut occur with the Paste, the same as bug 139074

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 4041c68ea59181f1c4774c356809066d2051db41
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 3 V Stuart Foote 2020-12-22 19:15:57 UTC
Created attachment 168428 [details]
WinDbg ST crash on paste into Impress Table cell
Comment 4 V Stuart Foote 2020-12-22 19:54:41 UTC

*** This bug has been marked as a duplicate of bug 139074 ***