https://bugs.kde.org/show_bug.cgi?id=370526
Martin Gräßlin changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=370526
adarma...@gmail.com changed:
What|Removed |Added
Severity|major |minor
--- Comment #5 from adarma...@gmail.
https://bugs.kde.org/show_bug.cgi?id=370526
--- Comment #4 from Martin Gräßlin ---
(In reply to adarmalik from comment #3)
> So it might be that virtualbox grabs the keys and the screenlocker can't
> grab them so it doesn't start?
yes that makes sense. If an application grabs the keyboard (or po
https://bugs.kde.org/show_bug.cgi?id=370526
--- Comment #3 from adarma...@gmail.com ---
Hi Martin,
I don't see any inhibition in the applet.
I have found something that might be related:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1124282
https://bugs.launchpad.net/ubuntu/+
https://bugs.kde.org/show_bug.cgi?id=370526
--- Comment #2 from Martin Gräßlin ---
you should see that in the "Battery and Brightness" applet whether there is an
inhibition in place.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370526
--- Comment #1 from Martin Gräßlin ---
I assume it's a feature of virtualbox and it inhibits the lock screen
--
You are receiving this mail because:
You are watching all bug changes.
