Desktopeditors: Linux binaries crashes on startup

Run the binaries here on Linux with any wayland compositor

Hi, any advice on simplest way to setup system with Wayland?

I believe you can run sway (a light wayland compositor) inside Xorg, and it'll run wayland nested inside Xorg.
I don't have Xorg set up on my system, so I'm not entirely sure of the finer details, but IIRC, just running sway from a terminal should work.

As an alternative, I do believe that recent Ubuntu/Fedora releases let you pick wayland from the login screen.

I've failed to find the build scripts for these binaries, but if you can point me to them, I can try and pinpoint what's wrong there. I have an impression that the Qt build is missing wayland support for some reason

I believe you can run sway (a light wayland compositor) inside Xorg, and it'll run wayland nested inside Xorg.

Ok, we'll try it. @XDmitryK please try to run DesktopEditors on Ubuntu with wayland server, I think this instruction is enough

I've failed to find the build scripts for these binaries

All build instuction at https://github.com/ONLYOFFICE/build_tools repo

@WhyNotHugo
I launched the desktop on Ubuntu 20.04 with WayLand (deb package)
What installation method did you use?
And also our need information about your OS

I installed via an ArchLinux User Package which basically downloads upstream binaries.

Maybe it's running via XWayland. Can you try either:

• Running via a terminal after running unset DISPLAY, or
• Running via a terminal setting QT_QPA_PLATFORM=wayland?

That should force it to use Wayland, at which point you might see the error I'm mentioning. (Also, if you enable desktop scaling to something like 1.5x, you'll probably notice the version running via Xorg scales very blurry. This is due to an Xorg limitation).

@WhyNotHugo
Unfortunately on Ubuntu this is not repeated
Can you send us an image of your system in a VM file?

I'd like to confirm that this issue is still present in the latest versions (6.0.0. and 5.6.4). I am running Arch Linux and Sway, and I have tried both the version from the AUR (updated today) and the latest AppImage.

The binaries work on XWayland (QT_QPA_PLATFORM=xcb) but this causes the editor to become blurry on displays with scaling enabled as mentioned before.

Same issue here. Sway on arch linux. However, so far QT_QPA_PLATFORM=xcb seems to fix it.

Using QT_QPA_PLATFORM=xcb forces the application to run via XWayland, which has it's own set of issues. I'd rather just run the application natively.

@XDmitryK Can you try using the latest fedora image? It has a nice GUI to switch to use Wayland instead of Xorg.

However, did the application run okay for you after running unset DISPLAY? That should not be possible, since it should not be able to communicate with Xorg if this variable is unset.

Version v6.1.0 is out, still not compiled with wayland support

I am using the latest version Manjaro (it's a rolling release) and installed the "onlyoffice-desktopeditors" from the official package repository and it's working just fine under Wayland.
I guess it's using XWayland tho, because everything is blurred on my 4K display with fractional scaling enabled.
On the FullHD Monitor which is not using fractional scaling it's looking good.

So if it's possible to build the Qt application (it's not using electron right?) with native Wayland support, i would be very happy to test it :heart:

I guess it's using XWayland tho, because everything is blurred on my 4K display with fractional scaling enabled.

I'd guess it's using XWayland too. You can confirm this by running xeyes, and moving the cursor around on top of onlyoffice. If the eyes track the cursor, then the application is using xwayland.

If you're using sway, you can also confirm by inspecting the output of swaymsg -t get_tree.

Uhh nice tool, didn't know about this yet.
And yes as you expected, the eyes track the cursor over the whole onlyoffice window which does not happen on native GTK3 apps or things like Thunderbird and Firefox(-Wayland)

It'd be great if they could update to the latest version of QT in order to natively support Wayland protocol...

Anything new here @ShockwaveNN @XDmitryK ?
Would be really nice if this could be fixed at some point.
Wayland support of most Qt apps is pretty solid nowadays, so I wonder why this couldn't get archived for onlyoffice too.

If you really need it, I can configure you a vm with a Wayland session pre-set, but it shouldn't be too hard to reproduce this on your own.

Just start your already working Ubuntu Gnome Desktop with session type Wayland (you can choose this with the bottom right gear icon if you are using GDM (depending on your theme)) and execute onlyoffice with the parameter --platform wayland.
Et voilà Onlyoffice doesn't start anymore, because somehow it isn't compiled with Qt's Wayland support (that's where I can't help either unfortunately).

@major-mayer
I confim this bug is reproduced. i posted this in our local bugtracker.(bug 49179)

Thanks you for the confirmation 👍

I guess that adding '-qt-wayland' to qt_params in build_tools/automate.py may resolve this issue.