6 ms·

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 Kr

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.

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 ago
  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.
  - roel_v 6y ago
    If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
    - whatshisface 6y ago
      Chrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.
    - fullstop 6y ago
      If every other application / process is running fine, but not Chrome, then how is it a Wayland 'bug'?
    - jyxent 6y ago
      https://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 ago
      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.
skratlo 6y ago
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
BoysenberryPi 6y ago
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.

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 ago
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.
- roel_v 6y ago
  If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
  - whatshisface 6y ago
    Chrome has separate code for dealing with each compositor. The bug would be in the code that deals with Wayland specifically.
  - fullstop 6y ago
    If every other application / process is running fine, but not Chrome, then how is it a Wayland 'bug'?
  - jyxent 6y ago
    https://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 ago
    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.

skratlo 6y ago

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

BoysenberryPi 6y ago

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.