On Thu, 18 Jun 2015 21:19:20 +0400 George Hertz <george...@gmail.com> wrote:
> I've just upgraded to 3.16 on unstable, but restarted the system right 
> after the update finished.
> 
> No problems unlocking.

Yeah, the problem only occurs with a gnome-shell which is already
running during the upgrade.

However, the problem also occurs when only locking the session after the
upgrade has completed.

One possible workaround after the upgrade is

        killall -HUP gnome-shell gnome-settings-daemon

Sending SIGHUP to gnome-shell only is enough to be able to unlock the
session, but gnome-settings-daemon also needs to be restarted, or some
things such as keyboard shortcuts don't work properly in the new
gnome-shell.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to