Bug 455414

Summary: Color chooser dialog doesn't work under Wayland
Product: [Applications] systemsettings Reporter: thebluequasar
Component: kcm_colorsAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, jpwhiting, mwoehlke.floss, yerrey
Priority: NOR    
Version: 5.25.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Color chooser not working under Wayland

Description thebluequasar 2022-06-16 14:26:16 UTC
Created attachment 149801 [details]
Color chooser not working under Wayland

SUMMARY
Color chooser dialog doesn't work under Wayland
It's also the same for KColorChooser  app, both:  1-cannot pick up any color, 2-can't detect the position of mouse cursor while outside its window. See the screen recording.

STEPS TO REPRODUCE
1.  Log in to a Plasma Wayland session, open system settings app and go to colors section under appearance sub-menu (Optionally, you can use KColorChooser app since they behave exactly the same in this regard)
2. Choose custom color in the accent color options, and try to pick up any color, preferably outside its own window
3. No color will be chosen based on where you've clicked, and the position of the mouse cursor  won't work when the mouse cursor isn't over the Color chooser dialog window (or KColorChooser main window).

OBSERVED RESULT
Color chooser dialog doesn't work under Wayland

EXPECTED RESULT
Color chooser dialog should work as it does under Xorg, picking up colors from anywhere on the screen

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon User – 5.25
KDE Plasma Version: 5.25
KDE Frameworks Version: 5.95
Qt Version: 5.15.4
Kernel: 5.13.0-51 generic (64bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
A screen recording is attached.
Comment 1 Yerrey Dev 2022-06-16 17:26:21 UTC
This is a "feature" of Wayland of itself I believe. To quote a smarter person "By design, Wayland doesn't allow clients to see the contents of another client". If that's the case here, the fix is not trivial.
Comment 2 Patrick Silva 2022-06-16 21:00:54 UTC

*** This bug has been marked as a duplicate of bug 415927 ***