GNOME Bugzilla – Bug 618925
gnome-screensaver crashed with SIGSEGV in gs_manager_set_active()
Last modified: 2014-08-20 20:23:46 UTC
gnome-screensaver crashes when locking on X servers which don't support XRANDR or XF86VM gamma fade
+ Trace 221957
It could really do with a check around the fade_setup calls so that this virtual function is not called when the fade_type is FADE_TYPE_NONE
Created attachment 161269 [details] [review] 0001-Don-t-crash-on-systems-that-don-t-support-XF86VM-or-.patch
Makes sense. Thanks for the patch!
Created attachment 165286 [details] [review] Adds the fade type checking to reset and finalize This doesn't appear to be quite complete. It fixes gs_fade_start, but not gs_fade_reset or gs_fade_finalize. I've attached a patch to fix those. This makes test-fade in the src directory complete successfully on systems that don't support either of the fade methods. (e.g. NX servers.) (I originally fixed this by just checking the pointers weren't null before calling them, but then found this bug, so rewrote it in the same way.)
Ah, I fixed the call in gs_fade_reset some months ago in Ubuntu, but forgot to attach the updated patch here (http://bazaar.launchpad.net/~ubuntu-desktop/gnome-screensaver/ubuntu/annotate/77/debian/patches/15_dont_crash_on_no_fade.patch), sorry about that. I guess users never noticed it crashes in gs_fade_finalize, as that's only called normally when shutting down
Part of the patch is not in git master, so re-opening
The screen lock is now implemented directly in gnome-shell, not in gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x). If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected. If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.