Bug 159392 - Crash: after selecting a floating table and clicking 'file' in menubar (mergedlo!SfxPoolItem::CloneSetWhich+0x25:)
Summary: Crash: after selecting a floating table and clicking 'file' in menubar (merge...
Status: RESOLVED DUPLICATE of bug 159386
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.8.0.0 alpha0+ Master
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks:
 
Reported: 2024-01-26 19:13 UTC by Telesto
Modified: 2024-01-27 07:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2024-01-26 19:13:09 UTC
Description:
Crash: after selecting a floating table and clicking 'file' in menubar

Steps to Reproduce:
1. Open attachment 191950 [details] (bug 159195)
2. Hoover over the top of the table (black arrow appears)
3. left Click to select
4. Left click on 'File' in the menubar


Actual Results:
Crash

Expected Results:
No crash


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 566bb271b8fe5882f24fef230e06c2af4ea12b33
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 threaded
Comment 1 m_a_riosv 2024-01-26 23:14:46 UTC
Reproducible
Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 566bb271b8fe5882f24fef230e06c2af4ea12b33
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

Regression from
Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community
Build ID: cafcc50570f9edaaebe74d2152bae5df1cc2edfe
CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Comment 2 Telesto 2024-01-27 07:37:16 UTC

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