I've flagged v. 6.4.0.1 rc albeit I'm running 6.4.01. The problem persists in several LO versions going some second levels back (6.x. ...)- x is the "level". What I do: I just start LO and let the initial picture rest, aftaer some time LO crashes ... I use; Debian Linux rln 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux I run Linux on both Intel and AMD both in 64-bit versions. /René
Could you give a try to https://wiki.documentfoundation.org/QA/FirstSteps ? Also, how did you install 6.4.0?
Well, As stated I have the same reaction on 2 (two) different platforms. Therefore I am somewhat reluctant to try your suggestion, as both platforms have been re-installaed recently. I'm sorry, but somewhat lazy. /René
PS. I installed from http://downloadarchive.documentfoundation.org/libreoffice/old/?C=N;O=D
Well, I'm a nice guy, I think. I tried the actions suggested in the link you sent. But to no avail. The LO still crashes when open and just left alone. On both platforms!
(In reply to René Lagoni Neukirch from comment #4) > PS. > I installed from > http://downloadarchive.documentfoundation.org/libreoffice/old/?C=N;O=D LO Linux packages on TDF are more for package maintainers. Indeed, you must deal with dependencies requirements. So unless you want to deal with them, you should stick to the repositories of your distribution. Anyway, you can try to provide a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace).
Created attachment 156789 [details] Backtrace log THX for your patient guidance ... Here is the requested dump, the gdb log attached to this comment: rln@rln:~$ libreoffice6.4 --backtrace GNU gdb (Debian 8.2.1-2+b3) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /opt/libreoffice6.4/program/soffice.bin...(no debugging symbols found)...done. log will be saved as gdbtrace.log, this will take some time, patience...
It seems related to KDE part, could you try this: - launch term/console - export SAL_USE_VCLPLUGIN=gen - soffice Also, you didn't respond about how you installed LO 6.4.0
I download 3 packages (the LO itself and the language- and help-packs) from the link: http://downloadarchive.documentfoundation.org/libreoffice/old/?C=N;O=D Next I unpack to a USB stick (to install on both my platforms). Then I install like this: cd /media/rln/RLN\ DEAS/LibreOffice_6.4.0.1_Linux_x86-64_deb/DEBS/ && sudo dpkg -i *.deb and this also goes for the language pack and the help pack. There are no warnings what so ever, it just installs smoothly. As for the KDE test, this I also did with the --backtrace option - just in case: 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 2078] [New Thread 0x7fffe8e5f700 (LWP 2080)] [New Thread 0x7fffe3fff700 (LWP 2081)] [Thread 0x7fffe8e5f700 (LWP 2080) exited] [New Thread 0x7fffe8e5f700 (LWP 2082)] [New Thread 0x7fffd7e4d700 (LWP 2083)] [Thread 0x7fffe8e5f700 (LWP 2082) exited] [New Thread 0x7fffe8e5f700 (LWP 2084)] [Thread 0x7fffe8e5f700 (LWP 2084) exited] [New Thread 0x7fffe8e5f700 (LWP 2085)] [Thread 0x7fffe8e5f700 (LWP 2085) exited] [New Thread 0x7fffe8e5f700 (LWP 2086)] [Thread 0x7fffe8e5f700 (LWP 2086) exited] [Thread 0x7fffe3fff700 (LWP 2081) exited] [Thread 0x7fffd7e4d700 (LWP 2083) exited] [Inferior 1 (process 2074) exited with code 0121] /opt/libreoffice6.4/program/gdbtrace:9: Error in sourced command file: No stack.
(In reply to René Lagoni Neukirch from comment #9) > I download 3 packages (the LO itself and the language- and help-packs) from > the link: > http://downloadarchive.documentfoundation.org/libreoffice/old/?C=N;O=D > Oups, you had already responded on comment 5 > ... > As for the KDE test, this I also did with the --backtrace option - just in > case: > ... From my previous comment "You can try: - launch term/console - export SAL_USE_VCLPLUGIN=gen - soffice " However, as I indicated in comment 6: " LO Linux packages on TDF are more for package maintainers. Indeed, you must deal with dependencies requirements. So unless you want to deal with them, you should stick to the repositories of your distribution. " So just my personal opinion but I'd put NOTABUG
Just one extra observation: I "backtracked" installation of previous versions. I.e. I re-installed them. The 6.4.y.z and the 6.3.y.z and 6.2.y.z crash when opened and left alone. BUT the 6.1.y.z does NOT. All versions are downloaded and installed as informed earlier...
[Automated Action] NeedInfo-To-Unconfirmed
put back to NEEDINFO since there's no feedback concerning gen rendering test.
(In reply to René Lagoni Neukirch from comment #9) Have you read comment 9 in full? The "KDE" backtrace below stems from a run with the environment set to SAL_USE_VCLPLUGIN=gen > I download 3 packages (the LO itself and the language- and help-packs) from > the link: > http://downloadarchive.documentfoundation.org/libreoffice/old/?C=N;O=D > > Next I unpack to a USB stick (to install on both my platforms). > > Then I install like this: > > cd /media/rln/RLN\ DEAS/LibreOffice_6.4.0.1_Linux_x86-64_deb/DEBS/ && sudo > dpkg -i *.deb > > and this also goes for the language pack and the help pack. > > There are no warnings what so ever, it just installs smoothly. > > As for the KDE test, this I also did with the --backtrace option - just in > case: > > 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 2078] > [New Thread 0x7fffe8e5f700 (LWP 2080)] > [New Thread 0x7fffe3fff700 (LWP 2081)] > [Thread 0x7fffe8e5f700 (LWP 2080) exited] > [New Thread 0x7fffe8e5f700 (LWP 2082)] > [New Thread 0x7fffd7e4d700 (LWP 2083)] > [Thread 0x7fffe8e5f700 (LWP 2082) exited] > [New Thread 0x7fffe8e5f700 (LWP 2084)] > [Thread 0x7fffe8e5f700 (LWP 2084) exited] > [New Thread 0x7fffe8e5f700 (LWP 2085)] > [Thread 0x7fffe8e5f700 (LWP 2085) exited] > [New Thread 0x7fffe8e5f700 (LWP 2086)] > [Thread 0x7fffe8e5f700 (LWP 2086) exited] > [Thread 0x7fffe3fff700 (LWP 2081) exited] > [Thread 0x7fffd7e4d700 (LWP 2083) exited] > [Inferior 1 (process 2074) exited with code 0121] > /opt/libreoffice6.4/program/gdbtrace:9: Error in sourced command file: > No stack.
(In reply to René Lagoni Neukirch from comment #14) > (In reply to René Lagoni Neukirch from comment #9) > > Have you read comment 9 in full? > > The "KDE" backtrace below stems from a run with the environment set to > SAL_USE_VCLPLUGIN=gen > ... That's weird. Ok then. Thank you for your feedback. So I don't have more questions => UNCONFIRMED I'm stuck and I can't help here => uncc myself
(In reply to René Lagoni Neukirch from comment #7) > Reading symbols from /opt/libreoffice6.4/program/soffice.bin...(no debugging > symbols found)...done. No debugging symbols found, so the backtrace is not useful, unfortunately. You can use the Linux build ending with "-dbg" here: https://dev-builds.libreoffice.org/daily/master/current.html https://wiki.documentfoundation.org/Installing_in_parallel/Linux
Thank you for reporting the bug. I can confirm that the bug is not present in 6.4.6.2. It could be something buggy in your PC settings or too many applications running at the same time that your computer cant handle it?
Hi René Lagoni Neukirch, Could you please try to reproduce it with the latest version 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.
(In reply to Xisco Faulí from comment #18) > Hi René Lagoni Neukirch, > Could you please try to reproduce it with the latest version 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. Well, I have both the Fresh (7.1 Alpha1) and the 7.0.3-version running without crashes. I think there were more LO people involved at the time of my reporting, and the the error was simply caused by the then default to run with JAVA. This default doesn't seem to be the case anymore.
(In reply to René Lagoni Neukirch from comment #19) > (In reply to Xisco Faulí from comment #18) > > Hi René Lagoni Neukirch, > > Could you please try to reproduce it with the latest version 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. > > Well, I have both the Fresh (7.1 Alpha1) and the 7.0.3-version running > without crashes. > I think there were more LO people involved at the time of my reporting, and > the the error was simply caused by the then default to run with JAVA. > > This default doesn't seem to be the case anymore. Thanks for retesting. Closing as RESOLVED WORKSFORME