[policykit-kde-agent-1] [Bug 506313] New: When the action that prompted the authentication doesn't have an immediate visual effect, the background dim doesn't go away after authenticating

[Nikola Arlotti]

https://bugs.kde.org/show_bug.cgi?id=506313

            Bug ID: 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
    Classification: Plasma
           Product: policykit-kde-agent-1
      Version First 6.4.0
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: aksamitna.egzystencja at gmail.com
                CC: drf at kde.org, jgrulich at redhat.com, jreznik at redhat.com
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.