Bug 306941 - Extra login window remains after screensaver unlocked
Summary: Extra login window remains after screensaver unlocked
Status: RESOLVED DUPLICATE of bug 306186
Alias: None
Product: plasma4
Classification: Unmaintained
Component: screensaver overlay (show other bugs)
Version: 4.9.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-17 16:02 UTC by Leon Maurer
Modified: 2012-11-16 01:28 UTC (History)
2 users (show)

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


Attachments
The extra login window is visible in the center of the left half of the screen. (808.11 KB, image/jpeg)
2012-09-17 16:04 UTC, Leon Maurer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leon Maurer 2012-09-17 16:02:20 UTC
Sometimes when I unlock the screensaver, an extra unlock window remains visible. See attachment (the extra login window is in the middle of the left half of the screen).

This extra login window floats above most other windows, which makes it a real nuisance.

Reproducible: Sometimes
Comment 1 Leon Maurer 2012-09-17 16:04:43 UTC
Created attachment 73980 [details]
The extra login window is visible in the center of the left half of the screen.
Comment 2 Leon Maurer 2012-09-17 16:07:33 UTC
I should add that I don't remember this happening before I installed KDE 4.9.0.
Comment 3 Michael K. 2012-11-15 21:39:44 UTC
I can confirm, exactly the same thing happens on my laptop quite often. Any idea how to remedy this without logging out/restarting X?
Fedora 17, KDE 4.9.2.
Comment 4 Michael K. 2012-11-15 21:41:56 UTC
(In reply to comment #2)
> I should add that I don't remember this happening before I installed KDE
> 4.9.0.

I have the same suspicion, although I'm not sure when did it start to happen exactly.
Comment 5 Leon Maurer 2012-11-15 22:38:19 UTC
> any idea how to remedy this without logging out/restarting 
Run 'kwin --replace'.
Comment 6 Jekyll Wu 2012-11-16 01:28:23 UTC

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