Bug 312292 - Lock dialog is not removed after unlocking
Summary: Lock dialog is not removed after unlocking
Status: RESOLVED DUPLICATE of bug 306186
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 4.9.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-28 07:11 UTC by Lastique
Modified: 2012-12-28 07:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
The screenshot demonstrating the problem. (204.53 KB, image/png)
2012-12-28 07:12 UTC, Lastique
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lastique 2012-12-28 07:11:19 UTC
When the screen is unlocked the lock dialog is sometimes left present on top of the desktop. The desktop is accessible but the lock window cannot be interacted with (i.e. it doesn't respond to mouse clicks and cannot be selected with window selection through Alt+Tab). The dialog cannot be removed. Locking and unlocking again doesn't help; the lock window is still visible afterwards.

I've attached a screenshot which was taken by selecting to screenshot only a window under the cursor and clicking on the lock dialog. As you can see, the underlying browser window has been shot instead while the lock dialog still being visible in front of it.

Reproducible: Sometimes

Steps to Reproduce:
1. Lock the screen.
2. In my case the computer was idle for the night so the display was turned off. This might not be necessary to reproduce the problem.
3. Unlock the screen by typing the password.

Actual Results:  
The desktop appears but the lock dialog is still visible and cannot be removed.

Expected Results:  
The lock dialog should not be shown after unlocking.

I'm using Kubuntu 12.04 with KDE 4.9.4 and AMD Catalyst drivers on MacBook Pro. I have an external monitor attached to the laptop.
Comment 1 Lastique 2012-12-28 07:12:11 UTC
Created attachment 76047 [details]
The screenshot demonstrating the problem.
Comment 2 Martin Flöser 2012-12-28 07:18:04 UTC

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