Do you have a pointer to an explanation of this “inherent issue” and why it’s impossible to solve?
What I don’t understand, in particular, is _why_ GTK menus need to grab the mouse and keyboard in the first place. (But if this is an absolute requirement, surely the GTK developers can work with the X developers to come up with a new type of grab that’s cancelable by global shortcut keys and by the screensaver.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Confirmed Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “gnome-screensaver” source package in Precise: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
