After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 473902 - applying screen lock to gnome desktop causes desktop hang
applying screen lock to gnome desktop causes desktop hang
Status: RESOLVED INCOMPLETE
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.19.x
Other All
: Normal critical
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-05 13:14 UTC by Wendell MacKenzie
Modified: 2009-01-19 15:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Wendell MacKenzie 2007-09-05 13:14:06 UTC
Please describe the problem:
click on the lock on the taskbar and you cannot get the unlock dialog back up.

worked on version 2.19.6.1, broken in OpenSUSE 10.3 BETA3 version:

2.19.7.2

Steps to reproduce:
1. fire up gnome desktop
2. click on lock icon on taskbar
3. move cursor screen goes black no unlock dialog - have to reboot


Actual results:
should receive unlock dialog

Expected results:
as above

Does this happen every time?
yep

Other information:
Comment 1 Eetu Huisman 2007-09-28 18:20:17 UTC
I think I'm suffering from the same problem on Ubuntu Gutsy Beta. If it is in fact the same (and chances are that even if it isn't), you don't have to reboot. Simply switch to another virtual terminal with Ctrl+Alt+F1, log in there, kill gnome-screensaver-dialog and gnome-screensaver and switch back to the VT where X is running (usually VT 7, Ctrl+F7).
Comment 2 Eetu Huisman 2007-09-29 14:18:23 UTC
Oops, that last Ctrl+F7 should of course be Alt+F7.
Comment 3 Eetu Huisman 2007-10-18 15:01:21 UTC
Does anyone have any ideas on how to debug this? I'm still suffering from the issue.
Comment 4 William Jon McCann 2007-11-09 22:40:21 UTC
http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-d50bc17e7d6f3a51c4715f02c657195e80e26c2c

Can you try running the "test-passwd" tool that is included in the gnome-screensaver sources and post the output here?

Thanks.
Comment 5 Eetu Huisman 2007-11-10 08:03:16 UTC
test-passwd: 

** (test-passwd:26372): WARNING **: Unable to establish service gnome-screensaver: Critical error - immediate abort

Incorrect

This repeats over and over again while the hard drive starts to spin.

gnome-screensaver --no-daemon --debug:

[gs_debug_init] gs-debug.c:106 (09:59:15):	 Debugging enabled
[main] gnome-screensaver.c:87 (09:59:15):	 initializing gnome-screensaver 2.20.0
[init_session_id] gs-listener-dbus.c:2051 (09:59:15):	 Got session-id: /org/freedesktop/ConsoleKit/Session1
[gs_fade_init] gs-fade.c:683 (09:59:15):	 Fade type: 2
[gamma_info_init] gs-fade.c:356 (09:59:15):	 Initialized gamma ramp fade
[initialize_server_extensions] gs-watcher-x11.c:903 (09:59:15):	 Not using server's MIT-SCREEN-SAVER extension.
[gs_watcher_set_active] gs-watcher-x11.c:731 (09:59:15):	 turning watcher: ON
[_gs_watcher_set_active_internal] gs-watcher-x11.c:718 (09:59:15):	 Starting idle watcher
[listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (09:59:15):	 obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.37
[listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (09:59:15):	 obj_path=(null) interface=(null) method=(null) destination=:1.37
[listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (09:59:15):	 obj_path=(null) interface=(null) method=(null) destination=:1.37
[listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (09:59:15):	 obj_path=(null) interface=(null) method=(null) destination=:1.37
[listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (09:59:15):	 obj_path=(null) interface=(null) method=(null) destination=:1.37
[_gs_watcher_notice_window_created] gs-watcher-x11.c:568 (09:59:20):	 Window created: noticing activity on 0xE054C4
[notice_events_inner] gs-watcher-x11.c:358 (09:59:20):	 Adding events for 0xE054C4
[listener_service_deleted] gs-listener-dbus.c:1043 (09:59:20):	 DBUS service deleted: 
[gs_grab_grab_root] gs-grab-x11.c:481 (09:59:20):	 Grabbing the root window
[gs_grab_get_keyboard] gs-grab-x11.c:166 (09:59:20):	 Grabbing keyboard widget=55
[gs_grab_get_mouse] gs-grab-x11.c:193 (09:59:20):	 Grabbing mouse widget=55
[gs_manager_create_window] gs-manager.c:1375 (09:59:20):	 Creating 1 windows for screen 0
[gs_manager_activate] gs-manager.c:1495 (09:59:20):	 fading out
[fade_done_cb] gs-manager.c:1456 (09:59:21):	 fade completed, showing windows
[get_best_visual_for_screen] gs-window-x11.c:500 (09:59:21):	 Found best GL visual for screen 0: 0x25
[window_map_cb] gs-manager.c:1214 (09:59:21):	 Handling window map event
[gs_window_clear] gs-window-x11.c:276 (09:59:21):	 Clearing window
[clear_all_children] gs-window-x11.c:251 (09:59:21):	 Clearing all child windows
[window_show_cb] gs-manager.c:1263 (09:59:21):	 Handling window show
[gs_job_set_command] gs-job.c:193 (09:59:21):	 Setting command for job: 't3d -root'
[gs_watcher_set_active] gs-watcher-x11.c:731 (09:59:21):	 turning watcher: OFF
[_gs_watcher_set_active_internal] gs-watcher-x11.c:714 (09:59:21):	 Stopping idle watcher
[gs_listener_update_console_kit_idle] gs-listener-dbus.c:296 (09:59:21):	 Updating ConsoleKit idle status: 1
[gs_listener_send_signal_active_changed] gs-listener-dbus.c:260 (09:59:21):	 Sending the ActiveChanged(TRUE) signal on the session bus
[listener_service_deleted] gs-listener-dbus.c:1043 (09:59:21):	 DBUS service deleted: 
[gs_manager_set_lock_active] gs-manager.c:414 (09:59:21):	 Setting lock active: 1
[gs_manager_set_lock_active] gs-manager.c:414 (09:59:21):	 Setting lock active: 1
[gs_listener_set_active] gs-listener-dbus.c:516 (09:59:21):	 Trying to set active state when already: active
[gs_manager_set_lock_active] gs-manager.c:414 (09:59:21):	 Setting lock active: 1
[gs_monitor_lock_screen] gs-monitor.c:227 (09:59:21):	 Unable to lock the screen
[listener_service_deleted] gs-listener-dbus.c:1043 (09:59:21):	 DBUS service deleted: :1.35
[listener_service_deleted] gs-listener-dbus.c:1043 (09:59:21):	 DBUS service deleted: :1.34
[gs_window_xevent] gs-window-x11.c:679 (09:59:21):	 not raising our windows
[window_map_event_cb] gs-manager.c:1201 (09:59:21):	 Handling window map_event event
[manager_maybe_grab_window] gs-manager.c:1155 (09:59:21):	 Moving grab to 0x80b0020
[xorg_lock_smasher_set_active] gs-grab-x11.c:126 (09:59:21):	 Disabling the x.org grab smasher
[xorg_lock_smasher_set_active] gs-grab-x11.c:146 (09:59:21):	 XF86MiscSetGrabKeysState(off) returned MiscExtGrabStateSuccess

[gs_grab_move_keyboard] gs-grab-x11.c:331 (09:59:21):	 Moving keyboard grab from 55 to 2A00024
[gs_grab_move_keyboard] gs-grab-x11.c:338 (09:59:21):	 *** doing X server grab
[gs_grab_release_keyboard] gs-grab-x11.c:219 (09:59:21):	 Ungrabbing keyboard
[gs_grab_get_keyboard] gs-grab-x11.c:166 (09:59:21):	 Grabbing keyboard widget=2A00024
[gs_grab_move_keyboard] gs-grab-x11.c:360 (09:59:21):	 *** releasing X server grab
[gs_grab_move_mouse] gs-grab-x11.c:276 (09:59:21):	 Moving pointer grab from 55 to 2A00024
[gs_grab_move_mouse] gs-grab-x11.c:283 (09:59:21):	 *** doing X server grab
[gs_grab_release_mouse] gs-grab-x11.c:237 (09:59:21):	 Ungrabbing pointer
[gs_grab_get_mouse] gs-grab-x11.c:193 (09:59:21):	 Grabbing mouse widget=2A00024
[gs_grab_move_mouse] gs-grab-x11.c:306 (09:59:21):	 *** releasing X server grab
[manager_maybe_start_job_for_window] gs-manager.c:206 (09:59:21):	 Starting job for window
[gs_job_start] gs-job.c:431 (09:59:21):	 starting job
[nice_process] gs-job.c:234 (09:59:21):	 Setting child process priority to: 10
[gs_window_xevent] gs-window-x11.c:679 (09:59:21):	 not raising our windows
[window_map_event_cb] gs-manager.c:1201 (09:59:21):	 Handling window map_event event
[manager_maybe_grab_window] gs-manager.c:1155 (09:59:21):	 Moving grab to 0x80b0020
[xorg_lock_smasher_set_active] gs-grab-x11.c:126 (09:59:21):	 Disabling the x.org grab smasher
[xorg_lock_smasher_set_active] gs-grab-x11.c:146 (09:59:21):	 XF86MiscSetGrabKeysState(off) returned MiscExtGrabStateAlready

[gs_grab_move_keyboard] gs-grab-x11.c:324 (09:59:21):	 Window 2A00024 is already grabbed, skipping
[gs_grab_move_mouse] gs-grab-x11.c:264 (09:59:21):	 Window 2A00024 is already grabbed, skipping
[manager_maybe_start_job_for_window] gs-manager.c:212 (09:59:21):	 Not starting job because job is running
[unfade_idle] gs-manager.c:1182 (09:59:22):	 resetting fade
[gs_fade_reset] gs-fade.c:639 (09:59:22):	 Resetting fade
[find_window_at_pointer] gs-manager.c:1131 (09:59:23):	 Requesting unlock for screen 0
[gs_window_request_unlock] gs-window-x11.c:1473 (09:59:23):	 Requesting unlock
[window_dialog_up_cb] gs-manager.c:1040 (09:59:23):	 Handling dialog up
[gs_grab_get_keyboard] gs-grab-x11.c:166 (09:59:23):	 Grabbing keyboard widget=2A00024
[gs_grab_get_mouse] gs-grab-x11.c:193 (09:59:23):	 Grabbing mouse widget=2A00024
[gs_grab_release_mouse] gs-grab-x11.c:237 (09:59:23):	 Ungrabbing pointer
[window_dialog_up_cb] gs-manager.c:1063 (09:59:23):	 Suspending jobs
[gs_job_suspend] gs-job.c:508 (09:59:23):	 suspending job
[popup_dialog_idle] gs-window-x11.c:1421 (09:59:23):	 Popping up dialog
[gs_window_clear] gs-window-x11.c:276 (09:59:23):	 Clearing window
[clear_all_children] gs-window-x11.c:251 (09:59:23):	 Clearing all child windows
[gs_window_raise] gs-window-x11.c:627 (09:59:23):	 Raising screensaver window
[gs_window_raise] gs-window-x11.c:627 (09:59:23):	 Raising screensaver window
[gs_window_raise] gs-window-x11.c:627 (09:59:23):	 Raising screensaver window
[gs_window_xevent] gs-window-x11.c:698 (09:59:23):	 not raising our windows
[gs_window_xevent] gs-window-x11.c:698 (09:59:23):	 not raising our windows
[gs_window_raise] gs-window-x11.c:627 (09:59:23):	 Raising screensaver window
[gs_manager_request_unlock] gs-manager.c:1586 (09:59:23):	 Request unlock but dialog is already up
[error_watch] gs-window-x11.c:850 (09:59:23):	 command error output: [gs_debug_init] gs-debug.c:106 (09:59:23):	 Debugging enabled

[error_watch] gs-window-x11.c:850 (09:59:23):	 command error output: 

[error_watch] gs-window-x11.c:850 (09:59:23):	 command error output: ** (gnome-screensaver-dialog:26476): WARNING **: Unable to establish service gnome-screensaver: Critical error - immediate abort

[error_watch] gs-window-x11.c:850 (09:59:23):	 command error output: 

[error_watch] gs-window-x11.c:850 (09:59:23):	 command error output: [do_auth_check] gnome-screensaver-dialog.c:293 (09:59:23):	 Verify user returned: FALSE

[lock_command_watch] gs-window-x11.c:1323 (09:59:23):	 command output: NOTICE=AUTH FAILED
Comment 6 Eetu Huisman 2007-11-25 15:18:03 UTC
I found the cause of my problems. While running Ubuntu 7.04 I had added the line @include common-pamkeyring to /etc/pam.d/gnome-screensaver to enable automatic WPA authentication when restoring from hibernate. When I upgraded to 7.10, common-pamkeyring was no longer available, which caused gnome-screensaver-dialog to fail. The following messages are from /var/log/auth.log:

Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM _pam_load_conf_file: unable to open /etc/pam.d/common-pamkeyring
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM unable to dlopen(<*unknown module path*>)
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM [error: <*unknown module path*>: cannot open shared object file: No such file or directory]
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM adding faulty module: <*unknown module path*>
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM error loading (null)
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM _pam_init_handlers: error reading /etc/pam.d/gnome-screensaver
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM _pam_init_handlers: [Kriittinen virhe - välitön keskeytys]
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM error reading PAM configuration file
Nov 25 16:37:16 kannettava gnome-screensaver-dialog: PAM pam_start: failed to initialize handlers

Now, I'm not sure whether the original reporter actually suffered from the same issue or not, but my problems are gone. I guess there is a real bug hidden in there (it should fail more gracefully when confronting a missing pam module), so maybe I should file another bug about that.
Comment 7 Christoph Wurm 2009-01-19 15:54:29 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!