Hacker News Reader

Comment by BoysenberryPi | Hacker News Reader

No problem, the biggest ones I tried were Godot, Krita, and Steam. Godot does not run on Wayland although support seems to be planned somewhere down the pipeline. Krita "runs" on Wayland but a lot of the features do not work nor does pen support last time I checked. Steam just doesn't work.

Edit: A commenter on this thread mentioned Emacs. I have not tried that as I have recently switched to Emacs but if that is true then that would also be a big one for me.

View on HN

I have a Linux PC that my kids mostly use, running Wayland sessions. It definitely works with Steam and Krita, although I admit that I do not know if all of Krita's features work. They have played Portal 2, Minecraft, and a few "windows-only" games with Proton.

My biggest gripe is that if you have more than one window of Chrome open it gets VERY slow. Multiple tabs are good, multiple windows are not.

>Multiple tabs are good, multiple windows are not.

"It's a perfect compositor, as long as it is not expected to composite." ;)

Personally I need the ability to open a remote window on my desktop, fingers crossed that someone will add that.

I'm pretty sure that it's a bug in Chrome / Chromium since other applications are just fine even when Chrome is being dog slow.

If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?

Chrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.

If every other application / process is running fine, but not Chrome, then how is it a Wayland 'bug'?

https://bugs.chromium.org/p/chromium/issues/detail?id=112178...

Chrome regressed on Wayland after changing the default rendering path on Linux. The slowness seems to be a problem in getting proper vsync, and there are multiple cases where it was/is causing issues.

Chrome doesn’t even run on wayland, unless compiled specifically on a new enough branch so OP talks about the version running inside XWayland. It can possibly be a bug in the specific compositor’s xwayland implementation or even in chrome. Also, your special ability to try out every compositors must be really useful.

This should help you:

chromium --enable-features=UseOzonePlatform --ozone-platform=wayland & disown & exit

You can also adjust your .desktop Chrome launcher to use these flags

This is good info. I'll spin up a VM running Sway or something and give it another go and see what roadblocks I hit.

On my ASUS PN50 APU, Steam works fine in wayland, even in big picture mode. Input, however, is another (sad) story.

Godot and Steam work perfectly fine on Wayland.

Emacs and Steam seem to work for me - I've been using it with XWayland for around a year now.

> Steam just doesn't work.

Steam works fine. What exactly doesn't work for you?

swaywm (Wayland) runs Krita and Steam just fine. Don't use Godot, so can't tell anything about it.

Basically all GTK2 apps won't work.

They won't be native but of course they just work via xwayland

Reply on news.ycombinator.com