Bug 461414 - [wayland] Panel doesn't register primary (left) mouse clicks with window behavior setting "activate and raise"
Summary: [wayland] Panel doesn't register primary (left) mouse clicks with window beha...
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.26.2
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-11-04 12:07 UTC by Gabriel
Modified: 2024-04-27 00:19 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
gabriel: Wayland+
gabriel: X11-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel 2022-11-04 12:07:05 UTC
SUMMARY
When clicking anywhere on the panel in Wayland session, nothing gets registered. Secondary and tertiary (right/middle) clicks do however work fine, as well as hover. The problem persists in edit mode too. No other part of the desktop seems to have trouble picking up on clicks though…

STEPS TO REPRODUCE
1. Click panel in Wayland session

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
Whatever you clicked on will perform its action (e.g. open the launcher, run application or open system tray)

SOFTWARE
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Nvidia driver version: 515.65.01
Graphics Platform: Wayland

ADDITIONAL INFORMATION
It's hard to show something not registering on a screen recording, so no attachment. Just imagine clicking on stuff in the panel and nothing happening. :^)
Comment 1 Gabriel 2022-12-03 15:11:05 UTC
I found the cause of the issue: I use the window behavior setting Window Actions > Inactive Inner Window Actions > Left click: "Activate and raise". This is so that I don't inadvertently cause an action when I just want to bring the window forward.

On Wayland this however means that the panel doesn't read clicks, because it will never truly be raised. I would not expect this setting to affect the panel anyways, but now I know it's the cause. Do with that what you will. :^)
Comment 2 Nate Graham 2022-12-05 18:30:00 UTC
Can confirm, thanks for the investigation!
Comment 3 Justin 2023-06-25 13:46:39 UTC
(In reply to Gabriel from comment #1)
> I found the cause of the issue: I use the window behavior setting Window
> Actions > Inactive Inner Window Actions > Left click: "Activate and raise".
> This is so that I don't inadvertently cause an action when I just want to
> bring the window forward.
> 
> On Wayland this however means that the panel doesn't read clicks, because it
> will never truly be raised. I would not expect this setting to affect the
> panel anyways, but now I know it's the cause. Do with that what you will. :^)

I can confirm your finding also.
Comment 4 Michael Breno 2023-12-26 23:46:29 UTC
(In reply to Gabriel from comment #1)
> I found the cause of the issue: I use the window behavior setting Window
> Actions > Inactive Inner Window Actions > Left click: "Activate and raise".
> This is so that I don't inadvertently cause an action when I just want to
> bring the window forward.
> 
> On Wayland this however means that the panel doesn't read clicks, because it
> will never truly be raised. I would not expect this setting to affect the
> panel anyways, but now I know it's the cause. Do with that what you will. :^)

I can confirm it too.

Same happens with right-click if I set "Activate and rise" to it

Arch Linux 6.6.8
Plasma 5.27.10
Comment 5 Marco Rebhan 2024-03-05 13:09:05 UTC
This seems to be fixed with Plasma 6.
Comment 6 Marco Rebhan 2024-03-05 13:19:37 UTC
(In reply to Marco Rebhan from comment #5)
> This seems to be fixed with Plasma 6.

Well, almost. Panel's context menus seem to have focus state, they need to be clicked twice to use the menu entry.
Comment 7 Patrik Spiess 2024-04-26 16:36:44 UTC
Can confirm this, too. I would really like to use "Activate and raise" behavior for left click again. Fixing this would be greatly appreciated.
Comment 8 Justin 2024-04-27 00:19:14 UTC
Yes, it would be good to see a fix. This bug stops me from switching to Wayland.