Solved Wayland Support

@luetage I also was/am unsure wrt its V application, but thought i'd post anyway as others presumably would just like a general sense of dev trajectory.

Slightly OT, but from other articles i've read this week, it really seems more & more that the X project is functionally dead, with previous major backers like Red Hat moving dev effort from X to W, & nobody else stepping up so far to take on the ongoing X development & support burden. Hence, IMO, downstream devs including V, are probably gonna be backed into a corner unless they start proactively moving themselves along with W as well.

Steffie

Salient for X:
https://www.phoronix.com/scan.php?page=news_item&px=Ajax-On-The-X-Server

WhyNotHugo

The lack of Wayland support is what's keeping me from adopting Vivaldi.

Aside from the security issues of using XWayland, it also does not support scaling, so if you have a HiDPI screen (which is pretty common in 2020), Vivaldi will render extremely blurry (since it's rendered low-res and then the bitmap streched).

This is a hard dealbreaker, not only due to blurriness and ugliness, but also text it extremely hard to read.

A Former User

@WhyNotHugo Please upvote the first post in this thread, the number of votes is usually what matters when looking for most wanted features (though not at all always this fact matters when the devs choose what to do next).

delx

Hurrah! The latest 2020-11-19 Vivaldi desktop snapshot is based on Chromium 87, which has Wayland support!

I'm using it right now and it looks beautiful.

Just start it from the command line and add these arguments:

--enable-features=UseOzonePlatform --ozone-platform=wayland

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?