Description: Application crashes and enters recovery mode when "Insert > Special Character" is selected through the main menu. Crash appears to occur before dialog is shown. Version: 6.2.1.2 Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Linux Mint "Cinnamon" 19.1 Steps to Reproduce: 1. Open document in Writer 2. Select "Insert > Special Character" 3. CRASH Actual Results: Application crashes and enters recovery mode when "Insert > Special Character" is selected through the main menu. Crash appears to occur before dialog is shown. Expected Results: Show the dialog for special characters. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.1.2 Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: e74de110d16c95414fac7541c8fe6541d4597113 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Does it happen with a blank document? Could you please try to reproduce it with the version 6.2.2.2 of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Thanks for the feedback, Xisco. We tried a full update to 6.2.2; unfortunatly, the problem remains / is identical to the one faced in the previously installed edition. For now, the workaround is to use the system character applet instead. Administrator, NDAS
which version of gtk3 do you use ? Does it crash if you launch LibreOffice with SAL_USE_VCLPLUGIN=gen ?
"which version of gtk3 do you use ? Does it crash if you launch LibreOffice with SAL_USE_VCLPLUGIN=gen ?" Hi Xisco, The standard OS thoughout NDAS is [currently] Linux Mint 19. Please briefly explain how to run this test. Administrator, NDAS
(In reply to Administrator, NDAS from comment #4) > "which version of gtk3 do you use ? Does it crash if you launch LibreOffice > with SAL_USE_VCLPLUGIN=gen ?" > > Hi Xisco, > > The standard OS thoughout NDAS is [currently] Linux Mint 19. Please briefly > explain how to run this test. > > Administrator, NDAS Go to the console and execute 'SAL_USE_VCLPLUGIN=gen soffice'
Dear Administrator, NDAS, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Hey, I experience this bug as well. I already tried to debug with gdb: Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0x00007f0fbd88fe3c in rtl_uString_assign () from /usr/lib/libreoffice/program/libuno_sal.so.3 If I start with 'SAL_USE_VCLPLUGIN=gen' it also crashes: [New Thread 0x7fd2a673d700 (LWP 2783)] [New Thread 0x7fd2a59a9700 (LWP 2784)] [New Thread 0x7fd2d87fc700 (LWP 2785)] [Thread 0x7fd2a673d700 (LWP 2783) exited] Thread 1 "soffice.bin" received signal SIGABRT, Aborted. 0x00007fd3281ed7bb in raise () from /lib/x86_64-linux-gnu/libc.so.6 My about LibreOffice: Version: 6.3.2.2 Build-ID: 1:6.3.2-1~bpo10+1 CPU-Threads: 4; BS: Linux 4.19; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded I'm on Debian buster (x64) and installed LO from backports.
it shouldn't be the same. you're using KDE5 while the original report is for GTK3. @bugs.documentfoundation-sammy@balkonien.org, did you try with a clean profile ?
Thanks for your suggestion. Actually the input of special characters work with a clean profile. Should I mark the bug as resolved now? And do you have an idea about how to get this working with my real profile?
Okay. Actually it works now. I just clered my cache. Thanks for the help. I mark this issue as resolved now.