I am not certain whether this is a bug or mis-configuration (or possibly both).
Since upgrading my desktop computer to Ubuntu 24.04, I have very poor and somewhat weird performance in OnlyOffice Desktop Editors only when working in a Wayland session. That is, everything seems fine when running in an X windows session. The problems I see under Wayland are primarily:
The part of the window containing the document occasionally becomes transparent, showing whatever is under the editor window. The surrounding controls, menu bar etc remain in place and visible.
Inserting text is very “laggy”, to the point of being almost impossible to use. What I mean by this is that text appears a couple of seconds after being typed, which becomes a huge problem when for example trying to correct a spelling mistake.
Here is my configuration:
OnlyOffice version 8.0.1.31 (deb) installed using apt
Ubuntu 24.04 LTS, fresh install on new M2SSD, updated as updates offered
GNOME version 46
Kernel 6.8.0-35-generic
AMD Ryzen 7 3800X 32GB memory 1TB M2SSD
NVIDIA GeForce RTX 3060, Samsung 5120 X 1440 120Hz monitor 100% scale fractional scaling off
NVIDIA driver version 535 (proprietary, tested) recommended
It may be worth mentioning that I ran into two Wayland - NVIDIA driver issues when I moved from Ubuntu 23.10 to 24.04:
You are most welcome, Nikolas. I have some more info to add that I hope is useful to you.
I just tried a similar experiment on my laptop, which is an i7-8750H running Ubuntu - Wayland 24.04 with an Intel® UHD Graphics 630 (CFL GT2).
I can see no odd behaviour whatsoever on this platform - no weird laggy jumping on the last two characters typed, no flashing of the screen between tab selections, no transparent events.
I recorded it if you want to see it.
So I guess this points to something odd in the NVidia 3060 / NVidia driver / Wayland / whatever else combination on the desktop machine.
Please let me know if there’s anything you would like me to test further. And thanks for looking into this.
(seems like there’s always another reason to wait for the next round for Wayland… I use some QT-based software that’s also unhappy on Wayland).
@Bonzini
Thank you for the info, I believe this will help our team.
As soon as we have additional information or any questions, I will get back to you.
@Nikolas just to let you know, there has been some work on the NVidia drivers 535 and 550 and so today I tried using the 550 version in Wayland on my desktop machine. OnlyOffice still shows the odd behaviour in this configuration. Also, I note in the Launchpad conversation that Daniel van Vugt from Canonical mentions that Chrome also has problems under Wayland using NVidia drivers 535 or 550. I conclude for the time being that I will continue with X11 rather than Wayland on my desktop machine.
Please let me know if there’s anything you’d like me to try at my end. Thank you!
We haven’t been able to reproduce the issue on our side, but we would really appreciate it if you could record a new video demonstrating the problem, including the driver versions you’re currently using.
It would also be helpful if the video shows that you’re running Wayland.
Thank you so much for helping us improve our product!
Thanks for looking into this. I am away from the problematic computer until late on 05 October. I’ve left myself a calendar reminder to make the video immediately thereafter.