> Killing just the X session (client) holding the lock is unacceptable
because killing a user's apps or shell is worse than the bug itself.
I wholeheartedly disagree. shutdown the computer altogether would be
less bad than granting access when the user expects otherwise..
--
You received this bu
Either that and even if it doesn't work, can't we get a hack that kills
the entire X session in the event the lock is unsuccessful? Or call a
user-defined script? Those would be more useful than removing the
feature altogether.
--
You received this bug notification because you are a member of Ubu
Agreed that this is a massive security flaw.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579
Title:
screen doesn't lock when panel menu is open
To manage notificati
Thanks Pedro.
I've just tried the rhythmbox package that's currently in precise. It
doesn't seem to have rhythmbox-client in it yet. Do you know when it
will be there?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubunt
Not sure when we'll see the fixed package come out in oneiric but until
then, one solution is to pin rhythmbox back to the natty version:
To do so, create the file /etc/apt/preferences.d/rhythmbox-pin
containing:
Package: rhythmbox
Pin: release n=natty
Pin-Priority: 1001
Then copy /etc/apt/sourc
