Blurry appearance on Wayland - switch from XWayland to native Wayland

[spoorun]

Running 6.1.0.90, on Manjaro KDE with Wayland With fractional scaling at 2x on HiDPI screen

[ShockwaveNN]

Hi there, currently out team have only HiDPI screen at our disposal, connected to Kubuntu 20.04 I've tried to run wayland here - but I got only black screen, and I don't think I have free time to figure out the reason of this

So could you try to setup non-wayland session on same pc+monitor combo to be sure that your problem is 100% in wayland

And on side note - could you descrbie your monitor resolution and DPI

[spoorun]

Hi there, currently out team have only HiDPI screen at our disposal, connected to Kubuntu 20.04 I've tried to run wayland here - but I got only black screen, and I don't think I have free time to figure out the reason of this

So could you try to setup non-wayland session on same pc+monitor combo to be sure that your problem is 100% in wayland

And on side note - could you descrbie your monitor resolution and DPI

Apologies for late reply..

My laptop monitor: 3840 x 2400 resolution 15.6" laptop screen 290 ppi

I can confirm that the issue occurs on another PC running Wayland and does not occur on my laptop or PC when not running Wayland. Exactly the same device and setup but without Wayland it's sharp and clear.

It may not be relevant, but I've had the same issue with blurry text when running Chrome and Chrome-based apps (and again, only on Wayland).

I worked-around it by launching them with: Exec=google-chrome-beta --enable-features=UseOzonePlatform --ozone-platform=wayland

[ShockwaveNN]

It may not be relevant, but I've had the same issue with blurry text when running Chrome and Chrome-based apps (and again, only on Wayland).

Hmm, this may be a case, since we're using chrome as base of our DesktopEditors, so the root problem may be on Chrome size, maybe already some known bug in chrome issue tracker

[spoorun]

It may not be relevant, but I've had the same issue with blurry text when running Chrome and Chrome-based apps (and again, only on Wayland).

Hmm, this may be a case, since we're using chrome as base of our DesktopEditors, so the root problem may be on Chrome size, maybe already some known bug in chrome issue tracker

So, Electron 12 is currently in beta and due for release next month, which will support Ozone Platform and Wayland. But whether it will require a commandline switch, as Chrome currently does is not currently obvious ( --enable-features=UseOzonePlatform --ozone-platform=wayland)

So I guess it's a waiting game for Chrome/Chromium/Electron support.

In the meantime, is there a way that HiDPI Wayland users like me can set that commandline switch to start DesktopEditors?

[ShockwaveNN]

Electron 12 is currently in beta and due for release next month

Yeah, please note that we are not using Electron, we using cef directly

In the meantime, is there a way that HiDPI Wayland users like me can set that commandline switch to start DesktopEditors?

Sorry I'm not aware of such and since I've got troubles running Wayland on my computer - currently I've no time to figure out it

[major-mayer]

I can confirm this issue also using Onlyoffice on Manjaro in combination with Wayland.

I know that native Wayland support has just landed on Chromium, so maybe it just takes a while until they also merge it into the CEF, but maybe it's already possible right now... You can see the same behavior on other apps like Spotify which also use the CEF. They are not using Wayland directly but instead rely on the presence of XWayland which is something like an X server within Wayland. And X does not have fractional scaling capabilities, that's where the blur comes from.

However, I am waiting hard on this feature, because it would make working with Onlyoffice on Linux systems which use Wayland as their display manager much more comfortable :smiley: Fedora for example is using Wayland by default for multiple years, even Ubuntu tried it out once IIRC.

BTW: In general I would say the Wayland support is better on Gnome in comparison to KDE, probably because they started implementing Wayland earlier.

Edit: There seem to exist some sort of Wayland support in CEF since 2019, but only for view mode (dunno what this means exactly, but i guess you cannot create some sort of top level windows):

Better wayland support is currently waiting for some PRs (here and here)to be approved, however the work has not continued since 2020, if i see that correctly.

[iMonZ]

Anything new on this issue?

[ShockwaveNN]

@iMonZ Sorry, I don't think so, mainly because part of issues related to CEF (chromium embedded framework) and update is quite tedious task for us

[spoorun]

Is this the snag point that needs fixing with CEF-Embedded?

https://bitbucket.org/chromiumembedded/cef/issues/2804/ozone-wayland-x11-support

[ShockwaveNN]

needs fixing with CEF-Embedded?

I'm not 100% this issue is fixed in current stable releaser of CEF, but we use not very actual version and there is a lot of hard work updating it so I truly cannot say

[WhyNotHugo]

This is partially related to #382.

• XWayland itself does not fully support scaling, so results will always be somewhat blurry (it's just an upscaled surface).
• Native wayland support has been discussed in #382, and it likely the best way to get it to render properly.

[parrenin]

I confirm this issue still exists in OO 7.0 under KDE/wayland 5.24.3. The problem is that under KDE, xwayland does not support scaling. The issue is reported here: https://bugs.kde.org/show_bug.cgi?id=449993 And there is a merge request here: https://invent.kde.org/plasma/kwin/-/merge_requests/1959 Another way for OO to fix this issue would be to release a wayland-enabled version.

[ShockwaveNN]

would be to release a wayland-enabled version.

I have no proper talk with our developers still, but judging by this issue https://bitbucket.org/chromiumembedded/cef/issues/2804/ozone-wayland-x11-support

We simply cannot release wayland-enabled version until this issue fixed (not counting any more issues we can find after that fix) Correct me if I wrong, but we definitely using CEF and not planning to change that in the future

[ghost]

The problem it's they use Xwayland, so it's an X server linked to wayland it's why it's blurry, if they had supported wayland nativly it's will not pose the problem, libreoffice has the same problem, and when they have fixed to work on native wayland poof problem gone.

[major-mayer]

Yeah, but that's nothing really new at this point...

Libreoffice supports Wayland both with their Qt and Gtk based backend by the way.

[ghost]

Yeah, but that's nothing really new at this point...

Libreoffice supports Wayland both with their Qt and Gtk based backend by the way.

i know but since onlyoffice is clearly better to handle word file (break less file), i hope to see native soon on it.

[WhyNotHugo]

Since CEF seems to be the blocker, probably using something like Tauri could be a good approach, but that's a lot of work.

[arjpar]

Any update on this issue? According to this issue (linked in a comment above) it seems like CEF can run on Wayland now with some extra work, and there are some missing features. Not sure how much that pertains to OnlyOffice though. Maybe someone more experienced can chime in.

[ShockwaveNN]

@arjpar Sorry, currently there is no updates on this issue on ONLYOFFICE side

[spoorun]

A year later, and Wayland is largely adopted across the board in Linux distros - any updates? Thanks

[LuckySpecialist]

Bug 63841 was issued for this problem.

[Smartich0ke]

Has there been any progress on this? Issue 63841 does not seem to exist.

[PumpkinXD]

tried Arch wiki's(and fcitx wiki's) tricks and OO still not running on wayland native

uh... did they blocked something?

[parrenin]

Any news on this issue? I was wondering if there is any plan to update CEF in OnlyOffice next major version.

[Greatz08]

any updates on this issue ? @LuckySpecialist

[LuckySpecialist]

@HakaishinShwet, sorry, there is no movement towards fixing this problem yet. It has a low priority for developers.

[parrenin]

It is unfortunate that this issue has a low priority. QHD displays are more and more common on laptops, and the only way to deal with them comfortably is with fractional scaling. But fractional scaling on Gnome leads to a blurry OnlyOffice.

[repsac-by]

If you use GNOME and Archlinux, you can install mutter-xwayland-scaling and configure it as described in the pinned post. This will resolve the issue immediately for all applications using XWayland, including ONLYOFFICE.

[parrenin]

@repsac-by, thanks for the hint. Unfortunately, I do not use Arch Linux so I cannot use this package. But there is good news, Gnome is considering some better Xwayland scaling: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3567 Maybe this will help us before OnlyOffice supports Wayland natively.

[Smartich0ke]

I have tried Gnome's new xwayland scaling feature. It's an experimental feature that can be enabled in Gnome 47. It's no longer blurry, but onlyoffice seems to use a slightly larger gui scale than normal. Other apps work really well with it though.

I really wish this would get fixed soon, as wayland is becoming default on more and more distros and no wayland support in 2024 is kinda worrying.

[Nvixbl]

Majority of the users have HiDPI displays as they have been out for almost a decade and most distros are starting to drop X11 and have Wayland only by default.

Those distros are used by many linux beginners who won't know what X11 and Wayland nor will they try to find a fix for this issue, their first impression of the app will be its blurry UI that causes headaches making them never consider this app again and switch to Libreoffice that has native Wayland support.

I hope the developers re-asses the priority of this issue as it's making the app barely usable for many of us.