You are not logged in.
Starting about two weeks ago, I haven't been able to unlock my screen after the screensaver kicks in. When I move the mouse, the desktop background image flashes for a split second, the mouse cursor is visible, and then the screensaver resumes: the prompt to unlock the screen never appears. The only way to get back to the desktop is to kill gnome-screensaver. I've tried re-installing it, and all of it's dependancies (with the exception of libgl as it conflicts with the nvidia package). As I expected, no luck there, but I didn't know what else to do...
Here's the output of "gnome-screensaver --no-daemon --debug"
I don't know if this helps, but here's some interesting output from LD_DEBUG=libs gnome-screensaver:
7559: /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
7559: /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: gtk_module_display_init (fatal)
.....
7559: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
.....
7559: /usr/lib/gio/modules/libgvfsdbus.so: error: symbol lookup error: undefined symbol: g_module_check_init (fatal)
7559: /usr/lib/gio/modules/libgvfsdbus.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
I hope that doesn't steer anyone in the wrong direction; I just learned about LD_DEBUG last night so I don't know if it's of any help.
Any help will be appreciated.
Offline
The crashes are most likely a bug in gtk 2.20.1. There's a -2 release of this package that should fix the issues you're seeing related to crashes.
Offline
My gtk2 was already up to date (gtk2 2.20.1-2). I tried removing it, re-installing it, and then running ldconfig, but the issue is still present.
Offline
*bump* same here
Offline
I also am now having this same problem.
Offline