Bug 508151

Summary:	Moving a window using the titlebar raises the window when configured to only activate
Product:	[Plasma] kwin	Reporter:	Chris Moore <chris>
Component:	core	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	CONFIRMED ---
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	6.3.4
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Chris Moore 2025-08-12 08:43:01 UTC

SUMMARY

I have the following section in my kwinrc:

[MouseBindings]
CommandActiveTitlebar1=Nothing
CommandInactiveTitlebar1=Activate
CommandTitlebarWheel=Raise/Lower
CommandWindow1=Activate and pass click

If I click the titlebar of a window behind another one, it is not raised. However, if I drag the window at all by the titlebar, it is raised above the frontmost window.

STEPS TO REPRODUCE
1. use the kwinrc config above
2. open two windows overlapping
3. click on the window behind by the titlebar and move it

OBSERVED RESULT

The window is raised

EXPECTED RESULT

The window moves behind the frontmost window and is not raised

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 25.04
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION
I'm running the wayland session

Comment 1 Bug Janitor Service 2025-08-12 09:33:38 UTC

Thank you for the bug report!

However Plasma 6.3.4 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.4, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.

Comment 2 Chris Moore 2025-08-12 09:42:38 UTC

Sorry, I should have been specific that I also see this bug in the current version on arch

Comment 3 Nate Graham 2025-08-12 15:56:42 UTC

Can confirm.