Summary: | kwin doesn't handle Chrome CSD on Wayland properly | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Neal Gompa <ngompa13> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | bugseforuns, jgrulich, kde, rdieter |
Priority: | NOR | ||
Version First Reported In: | 5.22.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot of Chrome on Wayland with CSD + SSD showing up |
Erk, I messed up the summary. I meant to write: SUMMARY When running Chrome as a Wayland app on KDE Plasma, Chrome tries to use CSDs, which works properly on GNOME, but on KDE Plasma with kwin, it renders the CSDs *and* the SSD titlebar. It looks bizarre and kind of broken (which you can see in the attached screenshot. Can you provide the output of running it with WAYLAND_DEBUG=1 ? Yesterday I saw the same bug with chromium 92.0.4515.159-1 on Arch Linux. looks a chromium bug fixed yesterday https://bugs.chromium.org/p/chromium/issues/detail?id=1138724 |
Created attachment 140806 [details] Screenshot of Chrome on Wayland with CSD + SSD showing up SUMMARY When running Chrome as a Wayland app on KDE Plasma, Chrome tries to use CSDs STEPS TO REPRODUCE 1. Install google-chrome-stable-92.0.4515.131-1.x86_64 2. Run Google Chrome with Wayland: "google-chrome-stable -enable-features=UseOzonePlatform -ozone-platform=wayland" OBSERVED RESULT Chrome shows up with both SSD (titlebar) and CSD (merged controls + browser tabs). EXPECTED RESULT Chrome shows up with only CSD (merged controls + browser tabs). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This has been an issue since Chrome 90 + Plasma 5.21.