Description: LibreOffice crashes while inspecting a file containing a custom shape. Steps to Reproduce: Using gtk3 UI: 1. Open the sample attachment 163404 [details] or create a new write file and add an arbitrary custom shape like a rectangle 2. Open "UNO Object Inspector" from "Tools > Development Tools" Menu 3. Find the only shape in "Shapes" part under "Object" section 4. Click on "Properties" 6. Select "@0" and press * on keyboard Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 1ec5a1300632a5455416b6cbb090d8c48353d939 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Note: If you are not using gtk3 UI, you should open and close several branches to encounter the crash. By pressing * LO tries to open every branch. I encountered a crash with X11 UI: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 1ec5a1300632a5455416b6cbb090d8c48353d939 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded The same happens with gtk4 UI: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 1ec5a1300632a5455416b6cbb090d8c48353d939 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk4 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
For me on gtk3 it hangs while spewing these warnings endlessly: (soffice:58068): Gtk-WARNING **: 15:36:00.259: ../gtk/gtk/gtktreestore.c:1046: Invalid column number 5 added to iter (remember to end your list of columns with a -1) On Windows nothing bad happens. On Linux kf5 & gen I get a crash, but only after clicking the document canvas (the property expands fine before that). Arch Linux 64-bit Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 4b41880be6894aaa2d2392554e858631278ba320 CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 13 August 2021
it looks like a dupe of bug 143640
*** This bug has been marked as a duplicate of bug 143640 ***