Bug 216970 - kbluelock messes up desktop if plasmoids on locked screen
Summary: kbluelock messes up desktop if plasmoids on locked screen
Status: RESOLVED DUPLICATE of bug 266829
Alias: None
Product: kde-bluetooth
Classification: Miscellaneous
Component: kbluelock (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Mattia Merzi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-01 19:11 UTC by suppandi G
Modified: 2011-04-11 19:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description suppandi G 2009-12-01 19:11:44 UTC 
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

kbluelock from kdebluetooth4-0.4.RC1+svn-40.10 locks and unlocks the desktop fine if there are no widgets on the locked screen.

But if there are widgets, after unlock, a translucent layer remains on the desktop with the widgets. This layer seems to capture all mouse input, but the keyboard inputs are going to windows behind this layer.

The only way to get out is to lock the screen again and unlock using the traditional way.
Comment 1 Lamarque V. Souza 2011-04-11 19:53:40 UTC 
Since kbluetooth is unmaintained (http://bugs.kde.org/270702) I am marking this bug as duplicate of the Bluedevil bluelock request feature.

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