I tried to build 7.1.2.2 from source on my non-wayland linux system. As it happens, the build includes non-optional dependency on wayland in its binaries. After build completion, I tried to run soffice, and my Xorg blanked the screen and after several mode changes (visible by display's status popups) stopped responding at all. (Same problem exists on my system with AppImage of 7.1.2.2 as downloaded from libreoffice.org). Expected result: build that doesn't hardwire wayland requirements, which is the root of the problem, by my guess. Part of ' ldd -r libvclplug_gtk3lo.so |sort ' output: libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007eff4b2f3000) libwayland-cursor.so.0 => /usr/lib64/libwayland-cursor.so.0 (0x00007eff4b2e9000) libwayland-egl.so.1 => /usr/lib64/libwayland-egl.so.1 (0x00007eff4b2e4000)
Almost same thing happens with qt5 vcl plugin. Only the Xorg screen doesn't blank (splash screen and empty soffice frame are showing) and you can switch away to text console. However, there's no dependency on wayland in qt5 plugin. My configure options this time were: ./configure \ --with-jdk-home=/usr/lib64/jdk-16 \ --without-junit \ --disable-debug \ \ --enable-qt5 \ --disable-gtk3 \
Even gen plugin has this issue (??!!). And in all three cases once Xorg is screwed up, you can't bring it back to workable state, going to non-graphical runlevel and back to graphical doesn't help.
I build LO 7.1 and current master on Ubuntu 18.04 x86-64 and I do not have any problem to run LO in my Xorg session. Please could you attach your autogen options. Generally these options are provided in a file named autogen.input That said, you could ask for help on the developer irc channel. Status has been set to NEEDINFO, please set it back to UNCONFIRMED once requested information has been provided. Best regards. JBF
I don't have such file anywhere in the source tree. I'm using libreoffice-7.1.2.2.tar.xz source archive as downloaded from libreoffice.org. But I have to remind I've had such problems earlier already, only with the AppImage 7.* variant (as downloaded from libreoffice.org).
[Automated Action] NeedInfo-To-Unconfirmed
You should ask for help on the developers irc channel #libreoffice-dev. Best regards. JBF
@ Yuri: any news about this issue ? Status has been set to NEEDINFO, please set it back to UNCONFIRMED once requested information has been provided. Best regards. JBF
Basic Still Appimage (as taken today from libreoffice.org) still has the issue.
Which Linux distribution do you use?
Dear Yury, 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 Yury, 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