This bug was filed from the crash reporting server and is br-0074bc14-59d0-4454-8b4a-f2ec922ef7e2. ========================================= I downloaded the latest 6.2.5 RPM distribution (64bit) from the Libreoffice repository to a generic, up-to-date CentOS 7 install, extracted the tar.gz and from within the RPM directory, installed it like this: yum localinstall *rpm This seemed to proceed smoothly and yum did not report any errors or missing dependencies. Next, I tried to open LibreOffice, first from the created icon in my KDE menu, but that crashed (the splash screen shows up for a second and then disappears and nothing else opens). Next, I tried to execute scalc, swriter, and soffice directly from /opt/libreoffice6.2/program/soffice, but that had the same effect. I tried to find out if there were any missing dynamic libs, like this: ldd ./soffice.bin | grep found which should show any missing libs, but nothing is missing. Any other suggestion? The interesting thing is, when I installed 6.1.x I don't have any problem, but I do get a notice that the previous time I opened the program it crashed. I sent the crash report, which you can find here: The crash report was successfully uploaded. You can soon find the report at: crashreport.libreoffice.org/stats/crash_details/0074bc14-59d0-4454-8b4a-f2ec922ef7e2 Thanks!
@Jan-marek, is this related to bug 126272 ? @demeler, what happens if you execute 'SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/soffice' from command line ?
(In reply to Xisco Faulí from comment #1) > @Jan-marek, is this related to bug 126272 ? > > @demeler, what happens if you execute 'SAL_USE_VCLPLUGIN=gen > /opt/libreoffice6.2/program/soffice' from command line ? Might be. But since there is no backtrace, it's hard to tell. But Qt4 libraries are loaded according to the raw dump. @demeler Please test a daily build from https://dev-builds.libreoffice.org/daily/libreoffice-6-2/Linux-rpm_deb-x86_64@86-TDF/ with date "2019-07-11" or later (More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds) There were some potential fixes merged, which might help.
And please provide the About Libreoffice information, if you still have an older version running. I've set the bug status to NEEDINFO. Please reset to UNCONFIRMED when you add a reply.
(In reply to Jan-Marek Glogowski from comment #2) > (In reply to Xisco Faulí from comment #1) > > @Jan-marek, is this related to bug 126272 ? > > > > @demeler, what happens if you execute 'SAL_USE_VCLPLUGIN=gen > > /opt/libreoffice6.2/program/soffice' from command line ? > > Might be. But since there is no backtrace, it's hard to tell. But Qt4 > libraries are loaded according to the raw dump. > > @demeler Please test a daily build from > https://dev-builds.libreoffice.org/daily/libreoffice-6-2/Linux-rpm_deb- > x86_64@86-TDF/ with date "2019-07-11" or later (More information about daily > builds can be found at: > https://wiki.documentfoundation.org/Testing_Daily_Builds) > > There were some potential fixes merged, which might help. Yes, when I use this command, LibreOffice starts normally for 6.2.5!
(In reply to demeler from comment #4) > (In reply to Jan-Marek Glogowski from comment #2) > > (In reply to Xisco Faulí from comment #1) > > > @Jan-marek, is this related to bug 126272 ? > > > > > > @demeler, what happens if you execute 'SAL_USE_VCLPLUGIN=gen > > > /opt/libreoffice6.2/program/soffice' from command line ? > > > > Might be. But since there is no backtrace, it's hard to tell. But Qt4 > > libraries are loaded according to the raw dump. > > > > @demeler Please test a daily build from > > https://dev-builds.libreoffice.org/daily/libreoffice-6-2/Linux-rpm_deb- > > x86_64@86-TDF/ with date "2019-07-11" or later (More information about daily > > builds can be found at: > > https://wiki.documentfoundation.org/Testing_Daily_Builds) > > > > There were some potential fixes merged, which might help. > > Yes, when I use this command, LibreOffice starts normally for 6.2.5! Version: 6.2.5.2 Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: x11; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Quoting from your mail (please just use bugzilla, as nobody else can follow mail replies): > xiscofauli@libreoffice.org identified the issue - this works: > > 'SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/soffice' > > Do you still want me to use the latest build? That would be great. Xiscos command is just a workaround, so LO uses the x11 / gen backend to handle stuff. No more theming, native file pickers, Desktop settings lookup, etc. > If this is related to Qt, I do have a custom Qt *5* installation on my > CentOS 7 box. Not sure if this could interfere. Would be interesting to know, if your Qt version is >= 5.9. If not it's a good indicator, that this is the same problem then bug 126272. (In reply to demeler from comment #5) > Version: 6.2.5.2 > Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 > CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: x11; > Locale: en-US (en_US.UTF-8); UI-Language: en-US > Calc: threaded No - that is from Xiscos command :-) I was interested in the same from your previous working version (6.2.3 I assume). As you can see it says "VCL: x11". I expect your previous version says "VCL: kde4". And I expect the current daily build to say "VCL: kde5" and not crash. If you are interested in more background info you can read bug 126272, which has some larger analysis of the potential origins of the crashes. Nobody knows yet why LO is crashing, but I implemented some possible fixes. (In reply to demeler from comment #0) > I tried to find out if there were any missing dynamic libs, like this: > > ldd ./soffice.bin | grep found > > which should show any missing libs, but nothing is missing. Yup - this is just the main program. But depending on the detected environment LO loads different VCL plugins (libvclplug_*lo.so), which are linked to the libraries of your DE, like gtk3, kde4, kde5 or just x11 (gen).
(In reply to Jan-Marek Glogowski from comment #6) > Quoting from your mail (please just use bugzilla, as nobody else can follow > mail replies): > > > xiscofauli@libreoffice.org identified the issue - this works: > > > > 'SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/soffice' > > > > Do you still want me to use the latest build? > > That would be great. I tried this file: libreoffice-6-2~2019-07-11_09.35.49_LibreOfficeDev_6.2.6.0.0_Linux_x86-64_rpm.tar.gz from the current directory. After installing it with 'yum localinstall *rpm' I could not find 'soffice' in this distribution. Is there another file I should have downloaded for the rpm-based distribution? > Xiscos command is just a workaround, so LO uses the x11 / gen backend to > handle stuff. No more theming, native file pickers, Desktop settings lookup, > etc. > > > If this is related to Qt, I do have a custom Qt *5* installation on my > > CentOS 7 box. Not sure if this could interfere. > > Would be interesting to know, if your Qt version is >= 5.9. If not it's a > good indicator, that this is the same problem then bug 126272. My Qt version is 5.11.1 > > (In reply to demeler from comment #5) > > Version: 6.2.5.2 > > Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 > > CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: x11; > > Locale: en-US (en_US.UTF-8); UI-Language: en-US > > Calc: threaded > > No - that is from Xiscos command :-) > > I was interested in the same from your previous working version (6.2.3 I > assume). As you can see it says "VCL: x11". I expect your previous version > says "VCL: kde4". You are right! I was able to run 6.1, here is the "About" statement: Version: 6.1.6.3 Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: kde4; Locale: en-US (en_US.UTF-8); Calc: group threaded > And I expect the current daily build to say "VCL: kde5" and not crash. If > you are interested in more background info you can read bug 126272, which > has some larger analysis of the potential origins of the crashes. Nobody > knows yet why LO is crashing, but I implemented some possible fixes. > > (In reply to demeler from comment #0) > > I tried to find out if there were any missing dynamic libs, like this: > > > > ldd ./soffice.bin | grep found > > > > which should show any missing libs, but nothing is missing. > > Yup - this is just the main program. But depending on the detected > environment LO loads different VCL plugins (libvclplug_*lo.so), which are > linked to the libraries of your DE, like gtk3, kde4, kde5 or just x11 (gen). At this point it would be helpful to get a link to the latest build RPM tar.gz archive *file* that I can download and test again. Thanks!
(In reply to demeler from comment #7) > (In reply to Jan-Marek Glogowski from comment #6) > > Quoting from your mail (please just use bugzilla, as nobody else can follow > > mail replies): > > > > > xiscofauli@libreoffice.org identified the issue - this works: > > > > > > 'SAL_USE_VCLPLUGIN=gen /opt/libreoffice6.2/program/soffice' > > > > > > Do you still want me to use the latest build? > > > > That would be great. > > I tried this file: > libreoffice-6-2~2019-07-11_09.35.49_LibreOfficeDev_6.2.6.0.0_Linux_x86- > 64_rpm.tar.gz > from the current directory. After installing it with 'yum localinstall *rpm' > I could not find 'soffice' in this distribution. Is there another file I > should have downloaded for the rpm-based distribution? > > > > Xiscos command is just a workaround, so LO uses the x11 / gen backend to > > handle stuff. No more theming, native file pickers, Desktop settings lookup, > > etc. > > > > > If this is related to Qt, I do have a custom Qt *5* installation on my > > > CentOS 7 box. Not sure if this could interfere. > > > > Would be interesting to know, if your Qt version is >= 5.9. If not it's a > > good indicator, that this is the same problem then bug 126272. > > My Qt version is 5.11.1 > > > > > > (In reply to demeler from comment #5) > > > Version: 6.2.5.2 > > > Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 > > > CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: x11; > > > Locale: en-US (en_US.UTF-8); UI-Language: en-US > > > Calc: threaded > > > > No - that is from Xiscos command :-) > > > > I was interested in the same from your previous working version (6.2.3 I > > assume). As you can see it says "VCL: x11". I expect your previous version > > says "VCL: kde4". > > You are right! > > I was able to run 6.1, here is the "About" statement: > Version: 6.1.6.3 > Build ID: 5896ab1714085361c45cf540f76f60673dd96a72 > CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: kde4; > Locale: en-US (en_US.UTF-8); Calc: group threaded > > > And I expect the current daily build to say "VCL: kde5" and not crash. If > > you are interested in more background info you can read bug 126272, which > > has some larger analysis of the potential origins of the crashes. Nobody > > knows yet why LO is crashing, but I implemented some possible fixes. > > > > (In reply to demeler from comment #0) > > > I tried to find out if there were any missing dynamic libs, like this: > > > > > > ldd ./soffice.bin | grep found > > > > > > which should show any missing libs, but nothing is missing. > > > > Yup - this is just the main program. But depending on the detected > > environment LO loads different VCL plugins (libvclplug_*lo.so), which are > > linked to the libraries of your DE, like gtk3, kde4, kde5 or just x11 (gen). > > At this point it would be helpful to get a link to the latest build RPM > tar.gz archive *file* that I can download and test again. > > Thanks! Folks... Apologies, I had checked the wrong directory. The file I downloaded has everything I need. I verified it works! So the recent changes to the development version take care of the problem :) Here is the "About" info from the development version: Version: 6.2.6.0.0+ Build ID: 45cf5d55221b92e395948cb2e36d6ae6f056b1a3 CPU threads: 6; OS: Linux 3.10; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-2, Time: 2019-07-11_09:35:49 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: CL It is not showing kde5 since I doubt CentOS 7 is already switched to kde5, so it is still kde4. Thank you all!
i guess we can close this as a duplicate of bug 126272 *** This bug has been marked as a duplicate of bug 126272 ***
(In reply to Xisco Faulí from comment #9) > i guess we can close this as a duplicate of bug 126272 > > *** This bug has been marked as a duplicate of bug 126272 *** It's still not sure that this is the same setup. But it's fixed, so I don't care much, if it's really a dup.
*** Bug 126782 has been marked as a duplicate of this bug. ***
*** Bug 125966 has been marked as a duplicate of this bug. ***