4 ms·
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 pipelin
by BoysenberryPi 6y ago
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.
- mondoshawan 6y agoOn my ASUS PN50 APU, Steam works fine in wayland, even in big picture mode. Input, however, is another (sad) story.
- fullstop 6y agoI 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.
- whatshisface 6y ago>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.
- fullstop 6y agoI'm pretty sure that it's a bug in Chrome / Chromium since other applications are just fine even when Chrome is being dog slow.
- roel_v 6y agoIf every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
- whatshisface 6y agoChrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.
- fullstop 6y agoIf every other application / process is running fine, but not Chrome, then how is it a Wayland 'bug'?
- jyxent 6y agohttps://bugs.chromium.org/p/chromium/issues/detail?id=1121782 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.
- kaba0 6y agoChrome 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.
- skratlo 6y agoThis should help you: chromium --enable-features=UseOzonePlatform --ozone-platform=wayland & disown & exit You can also adjust your .desktop Chrome launcher to use these flags
- BoysenberryPi 6y agoThis is good info. I'll spin up a VM running Sway or something and give it another go and see what roadblocks I hit.
- dleslie 6y agoBasically all GTK2 apps won't work.
- floatboth 6y agoThey won't be native but of course they just work via xwayland
- bionade24 6y agoswaywm (Wayland) runs Krita and Steam just fine. Don't use Godot, so can't tell anything about it.
- ywei3410 6y agoEmacs and Steam seem to work for me - I've been using it with XWayland for around a year now.
- rvolosatovs 6y agoGodot and Steam work perfectly fine on Wayland.
- vetinari 6y ago> Steam just doesn't work. Steam works fine. What exactly doesn't work for you?