Created attachment 188747 [details] Try to open the attached document with LO 24.2.0.0 alpha0. Open the attached file in LO 24.2.0.0 alpha0. LO tries to load the document and crashes. Have reset the user profile, also downloaded the next daily build - doesn't help. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: eef0c5d4d45ba35acfb6d8f7551fe565ca4badaa CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded (Master from 2023-08-03) Could load the document without any problem with LO 7.4.7.2 on the same machine.
No reproduced with: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: eef0c5d4d45ba35acfb6d8f7551fe565ca4badaa CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded However, I can't start LO with the kf5 or qt5 VCLs at all. In the console: /opt/libreofficedev24.2/program/soffice.bin: symbol lookup error: /opt/libreofficedev24.2/program/libvclplug_qt5lo.so: undefined symbol: _ZNK7QWidget6screenEv, version Qt_5 I could use those VCLs at eff5a3fe98ca5d1d28c4f5386c4af8a3be8f5703, so might be something in this range: https://git.libreoffice.org/core/+log/eff5a3fe98ca5d1d28c4f5386c4af8a3be8f5703..eef0c5d4d45ba35acfb6d8f7551fe565ca4badaa Khaled, there was qt5 VCL-related changes in 444e246535a7cf56b94143823845ec4bd2628236, could that be it?
(In reply to Stéphane Guillou (stragu) from comment #1) > Khaled, there was qt5 VCL-related changes in > 444e246535a7cf56b94143823845ec4bd2628236, could that be it? It does not crash for me with or without Qt.
On pc Debian x86-64 with master sources updated today (f7ff0468616d3ed8ded78598649a32bcb4e1ef1a), I don't reproduce this gen, gtk3, kf5 or qt5 renderings. (I used German/Germany locale and UI) Robert: do you think you can retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace)
Created attachment 188750 [details] Backtrace - LO crashed while loading attached file in KDE This isn't a special behavior of KDE. It will crash also with SAL_USE_VCLPLUGIN=gen ./soffice Note: I have only installed the main packages, not help and no special languages package.
(In reply to Stéphane Guillou (stragu) from comment #1) > However, I can't start LO with the kf5 or qt5 VCLs at all. > > In the console: > > /opt/libreofficedev24.2/program/soffice.bin: symbol lookup error: > /opt/libreofficedev24.2/program/libvclplug_qt5lo.so: undefined symbol: > _ZNK7QWidget6screenEv, version Qt_5 On what distro is that and what Qt 5 version does it provide? Could be related to our baseline bump to AlmaLinux 8, which has Qt 5.15.3, so e.g. `QtFrame::screen` will now be compiled for the for Qt >= 5.14 path: https://git.libreoffice.org/core/+/refs/heads/master/vcl/qt5/QtFrame.cxx#341 (The baseline defines the minimum requirements for both, building and running, so running with older library versions is unsupported.)
(In reply to Robert Großkopf from comment #4) > This isn't a special behavior of KDE. It will crash also with > SAL_USE_VCLPLUGIN=gen ./soffice Acknowledged, we are seeing different issues. (In reply to Michael Weghorn from comment #5) > On what distro is that and what Qt 5 version does it provide? Could be > related to our baseline bump to AlmaLinux 8, which has Qt 5.15.3, so e.g. > `QtFrame::screen` will now be compiled for the for Qt >= 5.14 path: > https://git.libreoffice.org/core/+/refs/heads/master/vcl/qt5/QtFrame.cxx#341 > > (The baseline defines the minimum requirements for both, building and > running, so running with older library versions is unsupported.) Ubuntu 20.04 with qt5-default at 5.12.8+dfsg-0ubuntu2.1
(In reply to Stéphane Guillou (stragu) from comment #6) > Ubuntu 20.04 with qt5-default at 5.12.8+dfsg-0ubuntu2.1 That's indeed too old then, maybe time to upgrade? :) Alternatively, either building qtbase from source or installing via the Qt online installer (https://www.qt.io/download - don't know whether it still supports Qt 5 as well still, though) might be an option.
(In reply to Robert Großkopf from comment #4) > Created attachment 188750 [details] > Backtrace - LO crashed while loading attached file in KDE > > This isn't a special behavior of KDE. It will crash also with > SAL_USE_VCLPLUGIN=gen ./soffice > > Note: I have only installed the main packages, not help and no special > languages package. Could you try again but this time, each time you got "??" or something like this, just type "c" (without quotes) until having something else than "??" then you'll get the "real" backtrace.
(In reply to Julien Nabet from comment #8) > > Could you try again but this time, each time you got "??" or something like > this, just type "c" (without quotes) until having something else than "??" > then you'll get the "real" backtrace. Don't know how to type anything there. I start in Konsole with ./soffice --backtrace Then I try to open the document. After some seconds LO crashes and Konsole will have written content to gdbtrace.log.
Uninstalled master from 2023-08-03 Installed this version I downloaded 2023-07-28 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 24d0a62bd75b9a895c419aa165da648ab18f134d CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Could open the document with this version.
(In reply to Robert Großkopf from comment #9) > (In reply to Julien Nabet from comment #8) > > > > Could you try again but this time, each time you got "??" or something like > > this, just type "c" (without quotes) until having something else than "??" > > then you'll get the "real" backtrace. > > Don't know how to type anything there. I start in Konsole with > ./soffice --backtrace > Then I try to open the document. > After some seconds LO crashes and Konsole will have written content to > gdbtrace.log. You're right, you need to use the old to retrieve the backtrace. 1) Open a first Konsole and launch LO (don't open the document for the moment) 2) Open a second Konsole and type this: gdb --pid=$(pidof soffice.bin) => it takes some seconds then it'll stop with a prompt 3) type "c" 4) Open the first Konsole with LO, open the document => on the second Konsole, gdb should stop at a moment with "??" 5) type "c" until you see something else than "??" 6) type "bt" I know it's far more complicated but it's due to the interaction of Java with gdb. I just know there's some config lacking but I don't know more.
Have downloaded no this version: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 2b0b4ddc8bd8fdd4cd689300620fe4621d7533b7 CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded 2023-08-04 Could open the document with this version without any crash. Seems there has been something going wrong with version from 2023-08-03 and 2023-08-02. Will close this bug as WORKSFORME.