Description: Hello This has been going on for a few weeks, but I haven't had time to debug properly. I tagged it as version 6.4.4.2 as I'm keeping up with the updates, but it's started a while ago and I didn't keep notes. Behavior: Opening LibreOffice as a user crashes within ~2 seconds of startup, but opening as root succeeds. Nothing I've tried to debug and fix worked. Some things I've tried: 1. Fonts, updating cache, removing Debian packages, installing packages, and nothing. I focused on this because I did install fonts in the time frame that somewhat corresponds to when this behavior started, and because what Google shows as the top search results about related keywords come back with. Nothing I did with the fonts worked, although these two commands: $ fc-cache -fv $ sudo fc-cache -fv produce many lines saying "skipping, looped directory detected". I've reached what I know about debugging/cleaning up fonts on Linux, so I'm giving up despite not being confident I've completed this line of thought. 2. A backtrace is not very helpful, but it's beyond what I know what to do with anyway. The following is a trace for the CLI command: $ libreoffice --calc --backtrace ``` warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after fork from child process 627090] [New Thread 0x7f4d48124700 (LWP 627095)] [Thread 0x7f4d48124700 (LWP 627095) exited] [Inferior 1 (process 627082) exited with code 01] /usr/lib/libreoffice/program/gdbtrace:9: Error in sourced command file: No stack. ``` 3. Disabling OpenGL doesn't stop the crashes. Instructions I followed: https://wiki.documentfoundation.org/OpenGL#How_to_enable.2Fdisable_OpenGL 4. MANY iterations of deleting the user profile directory (it gets re-created at next startup, and the program crashes) and purging the LibreOffice package using apt and re-installing. 5. Manually setting the language didn't do anything: $ libreoffice --calc --language=en I'd love help to fix this, and happy to share debug outputs if you show me how to produce them. Thanks! Steps to Reproduce: 1. Try to open LibreOffice as a user, using the KDE menu or CLI, and it will crash. For example on the CLI: libreoffice --calc Actual Results: LibreOffice shows up in the task bar, but then immediately crashes and is no longer shown. Expected Results: LibreOffice opens. Reproducible: Always User Profile Reset: Yes Additional Info: $ libreoffice --version LibreOffice 6.4.4.2 40(Build:2)
After I filed the bug report, I noticed the LO 7.0 RC2 link at the top. Trying that, the same crash happens but sudo works. However, the gdb trace has a new warning "Corrupted shared library list"; trace in full: ``` warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after fork from child process 630394] warning: Corrupted shared library list: 0x71d590 != 0x70e130 [New Thread 0x7fffe3200700 (LWP 630399)] [New Thread 0x7fffe1b3c700 (LWP 630400)] [New Thread 0x7fffe0e3f700 (LWP 630401)] [Thread 0x7fffe0e3f700 (LWP 630401) exited] [Thread 0x7fffe3200700 (LWP 630399) exited] [Thread 0x7fffe1b3c700 (LWP 630400) exited] [Inferior 1 (process 630389) exited with code 01] /opt/libreoffice7.0/program/gdbtrace:9: Error in sourced command file: No stack. ``` Thanks.
Did you install LO from Debian repos or from website? Which Debian version do you use? (stable, testing, sid) In a term/console, could you try this: - export SAL_USE_VCLPLUGIN=gen - soffice --writer about, bt, here are some information: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Thanks for the reply. My OS is Kubuntu 20.04. LO installed from distro packages. The export SAL_USE_VCLPLUGIN=gen suggestion did not enable it to start correctly. I will look at the backtrace link you shared. What specifically should I be looking for?
(In reply to Pierre from comment #3) > Thanks for the reply. > > My OS is Kubuntu 20.04. LO installed from distro packages. Ok thought you had downloaded packages from website at a moment. > ... > > I will look at the backtrace link you shared. What specifically should I be > looking for? Don't bother, re reading the bugtracker I just noticed you had already did this, there was no stacktrace. I must recognize I'm stuck and can't help here. => uncc myself
(In reply to Pierre from comment #0) > 4. MANY iterations of deleting the user profile directory (it gets > re-created at next startup, and the program crashes) and purging the > LibreOffice package using apt and re-installing. That's what i was going to suggest. I've been using Ubuntu 20.04 since early development and haven't seen this. Are you still having the problem now? Or should we just close this as unreproducible except in your instance?
(In reply to Justin L from comment #5) > (In reply to Pierre from comment #0) > > 4. MANY iterations of deleting the user profile directory (it gets > > re-created at next startup, and the program crashes) and purging the > > LibreOffice package using apt and re-installing. > > That's what i was going to suggest. I've been using Ubuntu 20.04 since early > development and haven't seen this. Are you still having the problem now? > Or should we just close this as unreproducible except in your instance? Hello Pierre, Please, provide the information requested.
I've found myself in a similar situation as Pierre. I tried removing some of the non-English fonts installed in Kubuntu 21.04 by default, cleared the font cache, and rebooted, and now LibreOffice crashes immediately on startup. Running with sudo works, however. Here is the result of a backtrace (with safe mode enabled): warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Detaching after fork from child process 7712] warning: Corrupted shared library list: 0x55ff6c6fbe40 != 0x55ff6c6f7330 [New Thread 0x7f1ee11ae640 (LWP 7729)] [New Thread 0x7f1ee09a8640 (LWP 7730)] [Thread 0x7f1ee11ae640 (LWP 7729) exited] [Thread 0x7f1ee253a000 (LWP 7708) exited] [Inferior 1 (process 7708) exited with code 01] /usr/lib/libreoffice/program/gdbtrace:9: Error in sourced command file: No stack. Version is LibreOffice 7.1.4.2 10(Build:2) installed from Ubuntu repos. I will try reinstalling the fonts I removed and will update if that fixes the issue.
After some testing, I opened a new bug report. My problem was related to removing the Lohit font family, maybe this bug is related. https://bugs.documentfoundation.org/show_bug.cgi?id=143271
Dear Pierre, 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
Dear Pierre, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp