Solved Wayland Support

jumpsq

HORRAAAAAY!
This snapshot is really delivering! WOW.

Any ideas of how to remove this bar? This was not there before.

A Former User

@delx Thanks for letting us know! It's a little buggy under kiwmi but seems to work quite well under sway.

@jumpsq I guess it's created by your compositor -- either Vivaldi doesn't register its CSD or the compositor ignores it.

jumpsq

@potmeklecbohdan sure, may be sway.

Regression: I notice quite a difference when scrolling (even after turning off "smooth scrolling", it still does not stop when I stop). ~~And now I have to think about what to use instead of xdotool~~ for my libinput-gestures (e.g. closing tabs with trackpad gesture; my trackpad is not really good for mouse gestures, sadly), but this rather excites me
ydotool seems to mostly do just fine, although I feel it may be a little less responsive.

Big Improvement: I feel that working with multiple windows (Ctrl+N, Ctrl+Shift+N) is quite a bit smoother than when using xwayland.

A Former User

@jumpsq said in Wayland Support:

sure, may be sway

Oh, I didn't look at your signature. Try toggling the native window setting; maybe it's made for CSD-only compositors (i.e. doesn't ask whether SSDs are also supported) & when you've set it to use native window (I guess you have), it just renders something.

You could then disable the buttons &c with custom CSS.

Edit: I’ve tried toggling native window & now I can tell for sure that the ugly bar is what Chromium makes when you ask for SSD.

jumpsq

@potmeklecbohdan: Yes, it was in the settings. Silly me forgot to search there...

Big Improvement: I feel that working with multiple windows (Ctrl+N, Ctrl+Shift+N) is quite a bit smoother than when using xwayland.

There seems to be an issue with chromium on wayland in general, so possibly these flags may be helpful for others experiencing performance drawbacks since some time:
vivaldi-snapshot --enable-features=UseOzonePlatform --ozone-platform=wayland --use-cmd-decoder=validating --use-gl=desktop

jumpsq

I had a lot of crashes more recently, which I relate to notificaitons (as crashes always happened when I received 3+ new feed entries or mails at once). Setting the notificaiton type to System notifications in the Vivaldi settings and installing mako seems to solve this issue.

Some additional advice:
You can check if it's working by running notify-send test.
You may also want to set mako to anchor=bottom-right in ~/.config/mako/config (see man 5 mako for more settings, such as semi-transparent notifications or a default timeout).

SleeplessSloth

Using Ozone + wayland works somewhat but there are lots of issues, including chromium titlebar that's impossible to hide, and broken context menus. I'd use it via Xwayland if I could but fractional scaling makes all Xwayland apps blurry as hell (at least on sway) and there doesn't seem to be a way to disable scaling just for Xwayland apps. On X I used to just increasing the font size without any scaling but that doesn't work on Wayland. Oh well

luetage

@guigirl In the meantime Ubuntu will switch to Wayland in its upcoming release. But yeah, I would never use Nvidia on Linux, no matter the display protocol.

jumpsq

More recently (last two-three snapshots), I noticed very weird behaviour (tabs barely loading any more and the interface responding super slow, as if the windows were using exclusive resources or something) when using more than one window.

vivaldi-snapshot --enable-features=UseOzonePlatform --ozone-platform=wayland --use-cmd-decoder=validating --use-gl=egl

anyone here made similar experiences?

A Former User

@jumpsq I don’t seem to have that issue.

A Former User

@guigirl But don’t you want native window? I thought you used it. Or do you call native window that weird bluish thing created by Chromium?

that black-purple bar is native window

that bluish bar is not native window

(borrowed your screenshot)

guigirl

From https://pointieststick.com/2021/12/17/this-week-in-kde-kind-of-everything/

In the Plasma Wayland session, various Chromium-based web browsers now show their windows properly (Vlad Zahorodnii, Plasma 5.24)

The bug's details.

jumpsq

Hum ... also the latest version of wlroots and sway seem to be broken.
It has been fixed in chromium on 5 January already, so I hope that this requires nothing more than just another chromium update, although I'm not certain.

Reported as VB-86221, just in case. Either don't update for now or use xwayland instead.

A Former User

@jumpsq or give up trying to use chromium & wayland together . (though it’s true that this particular bug was quite common, by far not chromium-only, but most other programs have already had bugfix releases.)

luetage

@jumpsq I don’t think Vivaldi has worked on Wayland support at all. So Wayland support would be a feature request and your current way to run natively on Wayland is 100% Chromium and could stop working or disappear in any future update.

guigirl

I'm confident this news will be tremendously exciting to all Vivaldifarians here , & so, fyi...

Firefox Nightly is now fully Wayland-compliant even with its standard launcher, ie, no longer needs the modified launcher command. I can verify that it works just peachy now natively as a full-W app [not Xwayland] in KDE Wayland.

Yep, i just knew you'd all be thrilled.

jumpsq

~~Hum ... also the latest version of wlroots and sway seem to be broken.~~

Fixed.

DoctorG

@jumpsq said in Wayland Support:

~~Hum ... also the latest version of wlroots and sway seem to be broken.~~

Fixed.

Whoa! Nice
I will test tomorrow.

Hubro

@jumpsq Fantastic! I was just visiting the forum for this news Guess I just have to wait for the next update.

guigirl

In KDE Plasma 5.23.5 atm... mouse scroll control.

X11 sessions:

Spoiler

Wayland sessions:

Spoiler

This [latter] enhanced scroll control nicely solves the problem noticed & posted by @Pathduck several months ago. Now, finally, in Vivaldi [launched as vivaldi-snapshot --enable-features=UseOzonePlatform --ozone-platform=wayland] manually scrolling pages by rolling the wheel by finger becomes efficient. Otoh, in X11 sessions it remains markedly inferior to Firefox.