Bug 513924 - Window buttons can't be released without action with Aurorae themes
Summary: Window buttons can't be released without action with Aurorae themes
Status: RESOLVED DUPLICATE of bug 512389
Alias: None
Product: kwin
Classification: Plasma
Component: aurorae (other bugs)
Version First Reported In: 6.5.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-28 19:54 UTC by letsdiskuss
Modified: 2026-01-07 16:15 UTC (History)
2 users (show)

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


Attachments
button pressed, released outside (17.59 KB, video/mp4)
2026-01-06 20:53 UTC, letsdiskuss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description letsdiskuss 2025-12-28 19:54:53 UTC
SUMMARY


STEPS TO REPRODUCE
1. Press the "close window" button and keep it pressed
2. Move cursor away from the button
3. Release the mouse button

OBSERVED RESULT
The window closes

EXPECTED RESULT
The window should not get closed because the mouse button was released outside the window button

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
The correct behavior works for the button inside the applications, only the window buttons display this behavior.
Comment 1 Nate Graham 2026-01-05 21:08:51 UTC
Assuming you're talking about the close button in the titlebar, I can't reproduce the issue. Please attach a screen recording that shows it happening. Thanks!
Comment 2 letsdiskuss 2026-01-06 02:36:10 UTC
Yes I'm talking about that.
Screen recording doesn't work on Plasma for me. I'll try to explain better.
1. Open any window (e.g. Dolphin)
2. Press the X button to close the window with the mouse but do not release it, keep it pressed
3. Move the cursor outside of the window (e.g. on the desktop)
4. Release the mouse button
The window gets closed, but it should not
Comment 3 Nate Graham 2026-01-06 17:07:58 UTC
Doesn't happen here. Please attach a screen recording that shows it happening. Thanks!
Comment 4 letsdiskuss 2026-01-06 18:55:05 UTC
An error occurred while attempting to record the screen.
Screen recording is not available on X11
Comment 5 Nate Graham 2026-01-06 18:55:40 UTC
Then use an X11-compatible screen recorder.

Also, does this happen on Wayland?
Comment 6 letsdiskuss 2026-01-06 18:58:46 UTC
I never tried on Wayland, how do I find a compatible screen recorder?
Comment 7 Nate Graham 2026-01-06 19:09:54 UTC
Same way you find any app. Use your process there to find another screen recorder app. Personally I use Discover for this.

VokoScreen, Peek, and SimpleScreenRecorder are some X11-compatible screen recording app I've used in the past.
Comment 8 letsdiskuss 2026-01-06 20:53:07 UTC
Created attachment 188278 [details]
button pressed, released outside
Comment 9 Nate Graham 2026-01-06 21:50:36 UTC
Thanks.

Does the issue reproduce on X11 in a new clean user account with no customization?
Comment 10 letsdiskuss 2026-01-06 22:46:50 UTC
Actually no, I didn't think of trying with a fresh user, but I went through the settings menu over and over and found nothing related. Is this a setting that can be changed?
Comment 11 Nate Graham 2026-01-06 22:48:42 UTC
You can create a new user account in System Settings > Users.
Comment 12 letsdiskuss 2026-01-07 00:12:48 UTC
I rephrase, I did create a new user, the issue is not present. I previously searched if it was a setting doing this and found nothing. Do I have to change some settings?
Comment 13 Nate Graham 2026-01-07 15:10:58 UTC
Yes, it sounds like some customization in your normal user account is the cause. I specifically noticed the use of a custom window decoration theme, which has the capability to introduce this bug.

Let us know if you ever find the exact component that causes it!
Comment 14 letsdiskuss 2026-01-07 16:12:46 UTC
Yes, using any window decoration theme except Breeze causes this issue. I guess it still counts as a bug since it's not unique to any theme in particular.
Comment 15 Nate Graham 2026-01-07 16:15:23 UTC

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