https://bugs.documentfoundation.org/show_bug.cgi?id=152911
--- Comment #75 from [email protected] --- (In reply to ppaanncchhoo507 from comment #74) > (In reply to Michael Weghorn from comment #52) > > (In reply to danileon95 from comment #51) > > > This bug makes LibreOffice **unusable** on a Wayland session. I'm on a > > > high-end system with a Ryzen 5800X and an RTX 4070Ti Super, on the latest > > > driver, and trying to scroll through a 20-something page document is > > > unusable, and I'm not being hyperbolic, the program just cannot be used > > > like > > > this. > > > > > > I won't pretend to know why this issue is taking so long to fix, but I do > > > have a question. Why not disable Wayland support by default if it's a > > > known > > > fact that it's broken? Then re-enable it once it's not broken? > > > > The experience seems to differ, depending on unknown factors. For example, > > in my setup (s. below for system details), there is a clearly noticeable > > (and annoying) lag on Wayland as compared to X11, but LO is still usable. > > > > Forcing LO to run on XWayland would be quite a "radical" step, and not what > > other users may be expecting. (I suppose that while Plasma Wayland has > > matured a lot over the last years, choosing to run Plasma X11 is still what > > some do whose primary goal is to avoid odd Wayland-specific issues. Others > > explicitly want Wayland and might not be happy about it silently "not being > > used" by some apps.) > > > > One aspect is also that disabling Qt's wayland QPA plugin by default would > > also mean that LO no longer gets used/tested with it - meaning that other > > potential issues are presumably not reported and fixed either. > > > > So in my opinion, forcing to run on X11 would require very strong reasons. > > (As I said, the experience I get in my setup isn't that bad, maybe would be > > useful to know more exactly what is causing the difference). > > > > I think one could also argue that the qt6/kf6 VCL plugin shouldn't be used > > by default at all, but the gtk3 one instead (which can be forced by using > > SAL_USE_VCLPLUGIN=gtk3), because it's the most mature one on Linux. > > > > Of course, any help to further analyze and fix the issue are more than > > welcome. After all, LO is an open source project that welcomes > > contributions: > > https://www.libreoffice.org/community/get-involved/ > > > > > I'm currently resorting to launching LibreOffice from the terminal every > > > time so I can pass the QT_QPA_PLATFORM=xcb envar ONLY to LibreOffice, but > > > I > > > don't think that's a reasonable solution. LibreOffice should default to > > > X11 > > > until the Wayland backend isn't broken. > > > > If you don't want to manually set the environment variable every time, one > > approach could be to modify the LibreOffice shell wrapper and set the > > environment variable there. > > Or, as mentioned above, set SAL_USE_VCLPLUGIN=gtk3 in your ~/.bashrc or > > similar. > > > > Operating System: Debian GNU/Linux 12 > > KDE Plasma Version: 6.3.0 > > KDE Frameworks Version: 6.10.0 > > Qt Version: 6.7.2 > > Kernel Version: 6.12.12-amd64 (64-bit) > > Graphics Platform: Wayland > > Processors: 32 × 13th Gen Intel® Core™ i9-13900HX > > Memory: 62.5 GiB of RAM > > Graphics Processor 1: Intel® Graphics > > Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU > > Manufacturer: TUXEDO > > Product Name: TUXEDO Gemini Gen2 > > > > Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community > > Build ID: 8710a20fabcb8892d8f1f2ae917101028db61e39 > > CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: qt6 > > (cairo+wayland) > > Locale: en-GB (en_GB.UTF-8); UI: en-US > > Calc: threaded > > From my testing it seems to happen only on RPM-based distros. Not sure if > others can reproduce. nevermind, on the latest 25.2 update to libreoffice it happens on ubuntu now. I will need to run this with a debugger.... -- You are receiving this mail because: You are the assignee for the bug.
