Bug 453441

Summary:	Close buttons on maximized windows don't get mouse input
Product:	[Plasma] kwin	Reporter:	Noah Davis <noahadvs>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	top left corner different cursor slightly to the right usual cursor

Description Noah Davis 2022-05-05 21:02:23 UTC

SUMMARY
When a window is maximized, the close button can't be hovered or clicked.

My titlebar button layout is [❎🔽🔼 Title ⏫(icon)].

I have no idea how this happened or how to reproduce it, I'm just writing this report so it's not forgotten.

OBSERVED RESULT
The close button is unresponsive to mouse input

EXPECTED RESULT
The close button should respond to mouse input

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220503
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 30.8 GiB of RAM
Graphics Processor: AMD RENOIR
Manufacturer: Eluktronics
Product Name: THINN-15

Comment 1 Noah Davis 2022-05-06 02:33:20 UTC

I am thinking this bug might actually be some kind of invisible window. All mouse input is blocked in a small area of the top left and the mouse cursor changes appearance up there.

Comment 2 Noah Davis 2022-05-06 02:34:20 UTC

Created attachment 148596 [details]
top left corner different cursor

Comment 3 Noah Davis 2022-05-06 02:34:51 UTC

Created attachment 148597 [details]
slightly to the right usual cursor

Comment 4 Noah Davis 2022-05-06 05:42:27 UTC

I figured out the cause. Somehow, the discord app puts an invisible floating systray item in the top left. I have no idea how this is even possible.

Comment 5 Nate Graham 2022-05-06 13:39:28 UTC

Yeah, it's Bug 433079.

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