Bug 441108 - kwin doesn't handle Chrome CSD on Wayland properly
Summary: kwin doesn't handle Chrome CSD on Wayland properly
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.22.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-18 02:23 UTC by Neal Gompa
Modified: 2021-08-18 14:54 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of Chrome on Wayland with CSD + SSD showing up (70.41 KB, image/png)
2021-08-18 02:23 UTC, Neal Gompa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Neal Gompa 2021-08-18 02:23:51 UTC
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.
Comment 1 Neal Gompa 2021-08-18 02:33:57 UTC
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.
Comment 2 David Redondo 2021-08-18 06:49:26 UTC
Can you provide the output of running it with WAYLAND_DEBUG=1 ?
Comment 3 Patrick Silva 2021-08-18 13:57:08 UTC
Yesterday I saw the same bug with chromium 92.0.4515.159-1 on Arch Linux.
Comment 4 Patrick Silva 2021-08-18 14:12:10 UTC
looks a chromium bug fixed yesterday

https://bugs.chromium.org/p/chromium/issues/detail?id=1138724