Bug 506313

Summary:	When the action that prompted the authentication doesn't have an immediate visual effect, the background dim doesn't go away after authenticating
Product:	[Plasma] kwin	Reporter:	Nikola Arlotti <aksamitna.egzystencja>
Component:	effects-various	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	drf, jgrulich, jreznik, nate
Priority:	NOR
Version First Reported In:	6.4.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nikola Arlotti 2025-06-28 14:05:54 UTC

STEPS TO REPRODUCE
1. create a script that calls any command through pkexec, such as "pkexec echo 'hello!'"
2. run the script

OBSERVED RESULT
After entering the password, the dialog disappears but the background stays dim until I click my mouse somewhere or until the next visual change on screen gets triggered. Keyboard presses do not dismiss the dim effect unless they trigger a visual change (e.g. the Meta key launching the program menu).

EXPECTED RESULT
The background returns to normal as soon as the authentication dialog disappears

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Fedora 42 KDE Edition, Wayland
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Scenarios in which I experienced this in real usage:

On a slow computer when an app requires authentication through policykit-agent to even launch (for example gparted) there are several seconds of delay between the authentication window disappearing and the next visual change on screen (gparted launching), during which the screen stays dim, which is jarring.

Another example is when some background process calls for a drive being mounted, which spawns a policykit-agent window "out of nowhere" that then disappears "into nowhere", and so no immediate visual change (such as the file manager showing the drive contents) happens.

Comment 1 Nate Graham 2025-08-13 17:32:05 UTC

I can't reproduce this issue on current git master. It could be a graphical glitch. What kind of GPU does the affected system have?

Comment 2 Bug Janitor Service 2025-08-28 03:47:42 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Nikola Arlotti 2025-08-30 20:36:57 UTC

AMD integrated graphics (Radeon 320SP), I'm able to reproduce the bug both on the latest stable version provided by Fedora 42 and the latest release available from kde-builder.

Comment 4 Nikola Arlotti 2025-08-30 20:45:16 UTC

Checked on another laptop with an AMD GPU there, it is present too on:

Linux: Fedora 41 KDE Edition, Wayland
KDE Plasma version: 6.4.4
KDE Frameworks version: 6.17.0
Qt version: 6.8.3
GPU: AMD Radeon 780M

Comment 5 Bug Janitor Service 2025-09-14 03:48:06 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2025-09-29 03:46:27 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.