https://bugs.documentfoundation.org/show_bug.cgi?id=157214
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #11 from Michael Weghorn <[email protected]> --- (In reply to Rafael Lima from comment #10) > Yeah, I can confirm that it does not crash when I comment out these two > environment variables. I didn't know this trick, thanks for pointing it out. Thanks for confirming. > This bug is actually a pain when building and testing LO on my second > machine, where I run Wayland on Plasma 5.27... at least by commenting these > lines, I can get around this issue. It is indeed. Other workarounds are using a different VCL plugin (e.g. SAL_USE_VCLPLUGIN=qt6 ) or forcing the use of the X11/xcb QT platform plugin instead of the native Wayland one ( QT_QPA_PLATFORM=xcb ). > I agree that this is an upstream bug. But isn't Plasma 5.27 an LTS? So maybe > it should be a good idea to report this issue upstream. Without analyzing further, I'd rather expect this to be a Qt issue. The KDE community still has a "patch collection" for Qt 5, but since the issue doesn't cause any user-visible issues in a "normal" setup, my assumption is that the most likely way to actually get a fix would be to analyze in more detail and either identify what commit fixed this for Qt 6 and suggest a backport, or come up with a fix oneself. I wouldn't feel able to create a proper bug report without spending more time. And while this is indeed annoying when using Wayland, my personal focus is more on qt6 than kf5/qt5 when it comes to non-critical things. > I haven't built LO using Plasma 6 yet... so I can't tell whether the problem > is there too. I have only tested the PPA version of LO under Plasma 6, but > using the kf5 backend, since qt6 isn't being shipped yet in the PPA. Do you see the issue with kf5 with that PPA? (My initial assumption would be no, as I'd expect that to be a release build, where the environment variables causing the crash shouldn't be set.) -- You are receiving this mail because: You are the assignee for the bug.
