I'm tired of this anti-Wayland horseshit

Re:I'm tired of this anti-Wayland horseshit by fullstop on Tuesday February 02, 2021 @10:41AM (#26002245)

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.

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by whatshisface on Tuesday February 02, 2021 @10:52AM (#26002417)

>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.

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by fullstop on Tuesday February 02, 2021 @10:53AM (#26002433)

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.

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by roel_v on Tuesday February 02, 2021 @11:06AM (#26002637)

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

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by jyxent on Tuesday February 02, 2021 @01:05PM (#26004345)

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.

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by whatshisface on Tuesday February 02, 2021 @11:13AM (#26002743)

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

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by kaba0 on Tuesday February 02, 2021 @03:07PM (#26005900)

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.

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by fullstop on Tuesday February 02, 2021 @11:13AM (#26002750)

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

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by skratlo on Tuesday February 02, 2021 @01:21PM (#26004564)

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

[ Parent | on HN ]

Re:I'm tired of this anti-Wayland horseshit by BoysenberryPi on Tuesday February 02, 2021 @01:35PM (#26004734)

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.

[ Parent | on HN ]