| Summary: | Chrome shows a line between chrome and content when using Wayland and 150% scale | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andrew Udvare <audvare> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | minor | CC: | john.kizer, nate |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| URL: | https://issues.chromium.org/issues/40900734 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot showing behaviour | ||
I have been able to reproduce this on another machine with the same packages installed. It is a laptop with a 4K display I normally run at 175% scale but with 150% scale set the same thing happens. Upgraded to 6.3.3 and there is no difference. Hi - this has been reported as a Chromium bug: https://issues.chromium.org/issues/40900734 Thanks! |
Created attachment 179317 [details] Screenshot showing behaviour SUMMARY An ugly transparent line shows between the chrome (top bar) and the content in Chrome only when Ozone platform hint is set to Auto or Wayland and only when using scale of 150%. STEPS TO REPRODUCE 1. Run Chrome Beta 135.0.7049.3 or better 2. Set Ozone platform hint to 'Auto' or 'Wayland' in chrome://flags/#ozone-platform-hint 3. Restart Chrome. OBSERVED RESULT Transparent line shows. EXPECTED RESULT Transparent line should not show. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 1 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-gentoo-limelight (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i9-11900K @ 3.50GHz Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090 ADDITIONAL INFORMATION Started after update to 6.3.2. Chrome was likely updated but since it only happens with 150% scale I think it is KDE's bug. Workaround for now is to set Ozone platform hint to Default which makes it use XWayland.