5 ms·
If every other compositor/desktop system/whatever it is, is running fine, but not with Wayland, then how is it a Chrome 'bug'?
by 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 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.