Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Hi all, I just wanted to mention that, after a few exchanges with the GNOME developers on the upstream bug report [0], I have managed to solve this problem for me by adding the following setting to the [daemon] section of /etc/gdm/gdm.conf: UserAuthDir=/tmp Can the rest of you try this and see if it makes any difference? Thanks, Vasilis [0] http://bugzilla.gnome.org/show_bug.cgi?id=527443 -- Vasilis Vasaitis A man is well or woe as he thinks himself so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457777: [gnome-screensaver] does not display login-dialog,, locking out user
Just wanted to mention, that I am experiencing the same problem: Sometimes when moving the mouse while the screensaver is running, the hack just freezes and no login dialog is displayed. I then log in through the network with ssh -Y ... and can then open the gnome-system-monitor remotely which tells me that the status of the screensaver hack is stopped. I can then click on continue, the hack resumes, and moving the mouse once more finally gives me the login dialog. (Alternatively I can just kill the frozen screensaver-hack and also get the login dialog.) The graphics driver is intel, by the way. Another work-around when no network and/or second computer is present: Press alt-ctrl-F1 to jump to the console and kill the frozen screensaver-hack (not gnome-screensaver itself!), if you know which one is running - or find out using top. Afterwards you can jump back to gnome by pressing alt-F7 and (hopefully) you'll have the login window. cheers, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Hi, I'm experiencing this bug too, so I thought I'd come here and report it. In my case however, the cause is quite obvious: my home directory is on AFS, and the bug manifests when my AFS tickets have expired. I would imagine that gnome-screensaver tries to access one or more files inside my home directory before presenting the unlock dialog, and fails. I'll report this directly upstream too. Thanks, Vasilis -- Vasilis Vasaitis A man is well or woe as he thinks himself so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Dear everybody, Am Mittwoch, den 09.04.2008, 00:54 +0200 schrieb Sven Arvidsson: Thanks for the log and answering my questions. Thanks for looking into this. I couldn't find anything suspicious in the log, but I will forward it upstream to be sure. Thanks. Before I do so, the symptoms described reminds me of bug 420339. Do you have more than one video output? If so, does xrandr -q falsely detect it as connected? (Bug 420339 should be fixed, but you never know...). My graphics card $ lspci | grep nVidia 01:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX 5600] (rev a1) has a DVI-connector to which the monitor is connected to and a VGA-connector with nothing connected to. $ xrandr -q Screen 0: minimum 640 x 400, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 60.0*75.0 1280x960 60.0 1280x800 60.0 1152x864 75.0 1280x768 60.0 1024x768 75.0 70.0 60.0 832x62475.0 800x60075.0 72.0 60.0 56.0 640x48075.0 73.0 67.0 60.0 720x40070.0 Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
also my infos: My external VGA connector is not in use and alos has been never used. moria:/home/tobi#lspci | grep Graph 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) moria:/home/tobi# xrandr -q Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1280x800 59.9*+ 60.0 1280x768 60.0 1024x768 60.0 800x60060.3 640x48059.9 TV disconnected (normal left inverted right x axis y axis) signature.asc Description: This is a digitally signed message part
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
I just missed the hint for #420339 to include in the prevoius mail. There is a difference in my case: The screensaver works as usual, showing its animations but suddendly it wilkl just freeze. Mostly, The animation will stop and then the bug is occuring. Also seen, that the screen is blank (black) when the bug appears (backlight working) . But this could be some power saving as well. signature.asc Description: This is a digitally signed message part
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Hi, Thanks for the log and answering my questions. I couldn't find anything suspicious in the log, but I will forward it upstream to be sure. Before I do so, the symptoms described reminds me of bug 420339. Do you have more than one video output? If so, does xrandr -q falsely detect it as connected? (Bug 420339 should be fixed, but you never know...). -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
I'm not currently at that machine, but I neigther used compiz nor I have a special PAM setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
On Sun, 2008-04-06 at 15:26 +0200, Paul Menzel wrote: $ gnome-screensaver-command --exit $ gnome-screensaver --no-daemon --debug Ctrl + a, c $ gnome-screensaver-command -a See no login-dialog, move mouse, enter some keys and then login under tty? do $ screen -dr Maybe one differnece: That won't work on my machine, as once the bug wents of, I cannot switch to a tty (Ctr+Alt+Fn seems to be captured.) Mmm. I use UTF-8. -- Could Ctr+Alt+Fn translate to an UTF char and be captured because of that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Dear Sven, thank you for your quick reply. Am Samstag, den 05.04.2008, 16:35 +0200 schrieb Sven Arvidsson: The gnome-screensaver FAQ have a few suggestions when it comes to bugs; http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-d50bc17e7d6f3a51c4715f02c657195e80e26c2c You could perhaps try to run g-s in verbose mode from a terminal first, and later try getting a backtrace if nothing interesting shows up. Here you go. I used screen the following way. $ screen in terminal and do $ gnome-screensaver-command --exit $ gnome-screensaver --no-daemon --debug Ctrl + a, c $ gnome-screensaver-command -a See no login-dialog, move mouse, enter some keys and then login under tty? do $ screen -dr and then $ gnome-screensaver-command -d # I think, one can skip this. $ gnome-screensaver-command --exit This is what I got. $ gnome-screensaver --no-daemon --debug [gs_debug_init] gs-debug.c:106 (15:19:23): Debugging enabled [main] gnome-screensaver.c:87 (15:19:23):initializing gnome-screensaver 2.22.0 [query_session_id] gs-listener-dbus.c:2033 (15:19:23): org.freedesktop.DBus.Error.ServiceUnknown raised: The name org.freedesktop.ConsoleKit was not provided by any .service files [init_session_id] gs-listener-dbus.c:2051 (15:19:23):Got session-id: (null) [gs_fade_init] gs-fade.c:679 (15:19:23): Fade type: 2 [gamma_info_init] gs-fade.c:352 (15:19:23): Initialized gamma ramp fade [initialize_server_extensions] gs-watcher-x11.c:903 (15:19:23): Not using server's MIT-SCREEN-SAVER extension. [gs_watcher_set_active] gs-watcher-x11.c:731 (15:19:23): turning watcher: ON [_gs_watcher_set_active_internal] gs-watcher-x11.c:718 (15:19:23): Starting idle watcher [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (15:19:23): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.37 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (15:19:23): obj_path=(null) interface=(null) method=(null) destination=:1.37 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (15:19:23): obj_path=(null) interface=(null) method=(null) destination=:1.37 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (15:19:23): obj_path=(null) interface=(null) method=(null) destination=:1.37 [listener_dbus_handle_system_message] gs-listener-dbus.c:1481 (15:19:23): obj_path=(null) interface=(null) method=(null) destination=:1.37 [listener_service_deleted] gs-listener-dbus.c:1043 (15:19:26): DBUS service deleted: [gs_grab_grab_root] gs-grab-x11.c:481 (15:19:26):Grabbing the root window [gs_grab_get_keyboard] gs-grab-x11.c:166 (15:19:26): Grabbing keyboard widget=66 [gs_grab_get_mouse] gs-grab-x11.c:193 (15:19:26):Grabbing mouse widget=66 [gs_manager_create_window] gs-manager.c:1370 (15:19:26): Creating 1 windows for screen 0 [gs_manager_activate] gs-manager.c:1490 (15:19:26): fading out [fade_done_cb] gs-manager.c:1451 (15:19:27): fade completed, showing windows [get_best_visual_for_screen] gs-window-x11.c:500 (15:19:27): Found best GL visual for screen 0: 0x24 [window_map_cb] gs-manager.c:1209 (15:19:27):Handling window map event [gs_window_clear] gs-window-x11.c:276 (15:19:27):Clearing window [clear_all_children] gs-window-x11.c:251 (15:19:27): Clearing all child windows [window_show_cb] gs-manager.c:1258 (15:19:27): Handling window show [gs_job_set_command] gs-job.c:193 (15:19:27):Setting command for job: 'NULL' [gs_watcher_set_active] gs-watcher-x11.c:731 (15:19:27): turning watcher: OFF [_gs_watcher_set_active_internal] gs-watcher-x11.c:714 (15:19:27): Stopping idle watcher [gs_listener_send_signal_active_changed] gs-listener-dbus.c:260 (15:19:27): Sending the ActiveChanged(TRUE) signal on the session bus [gs_manager_set_lock_active] gs-manager.c:409 (15:19:27):Setting lock active: 1 [gs_window_xevent] gs-window-x11.c:679 (15:19:27): not raising our windows [window_map_event_cb] gs-manager.c:1196 (15:19:27): Handling window map_event event [manager_maybe_grab_window] gs-manager.c:1150 (15:19:27):Moving grab to 0x80b9048 [xorg_lock_smasher_set_active] gs-grab-x11.c:126 (15:19:27): Disabling the x.org grab smasher [xorg_lock_smasher_set_active] gs-grab-x11.c:146 (15:19:27): XF86MiscSetGrabKeysState(off) returned MiscExtGrabStateSuccess [gs_grab_move_keyboard] gs-grab-x11.c:331 (15:19:27):Moving keyboard grab from 66 to 2200021 [gs_grab_move_keyboard] gs-grab-x11.c:338 (15:19:27):*** doing X server grab [gs_grab_release_keyboard] gs-grab-x11.c:219 (15:19:27): Ungrabbing keyboard [gs_grab_get_keyboard] gs-grab-x11.c:166 (15:19:27): Grabbing keyboard widget=2200021 [gs_grab_move_keyboard] gs-grab-x11.c:360 (15:19:27):*** releasing X server grab
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
Package: gnome-screensaver Version: 2.22.0-1+b1 --- Please enter the report below this line. --- Dear DDs, I also encounter this bug. It is a freshly installed sid system and each time (three all in all), the dialog to enter the password is not displayed. I can see the mouse cursor only when moving the mouse, when I stop moving the mouse it vanishes. As a work-around I did System -- Preferences -- Screensaver -- Disable checkbox and when I get hit by this bug I do on tty1 killall gnome-screensaver. Please tell me, what other informations you need. And in my opinion the severity should be set to important. Thanks a lot Paul --- System information. --- Architecture: i386 Kernel: Linux 2.6.24-1-686 Debian Release: lenny/sid 500 unstabledebian.tu-bs.de --- Package information. --- Depends(Version) | Installed -+-== dbus | 1.1.20-1 gconf2 (= 2.12.1-1) | 2.22.0-1 gnome-icon-theme(= 2.15.90) | 2.22.0-1 libatk1.0-0 (= 1.20.0) | 1.22.0-1 libc6 (= 2.7-1) | 2.7-10 libcairo2 (= 1.4.0) | 1.4.14-1 libdbus-1-3 (= 1.1.1) | 1.1.20-1 libdbus-glib-1-2 (= 0.74) | 0.74-1 libfontconfig1(= 2.4.0) | 2.5.0-2 libfreetype6 (= 2.3.5) | 2.3.5-1+b1 libgconf2-4 (= 2.13.5) | 2.22.0-1 libgl1-mesa-glx | 7.0.3~rc2-2 OR libgl1 | libglade2-0 (= 1:2.6.1) | 1:2.6.2-1 libglib2.0-0 (= 2.16.0) | 2.16.2-1 libgnome-menu2 (= 2.15.4) | 2.22.0-1 libgnomekbd2 | 2.22.0-1 libgnomekbdui2 | 2.22.0-1 libgtk2.0-0 (= 2.12.0) | 2.12.9-2 libice6 (= 1:1.0.0) | 2:1.0.4-1 libnotify1(= 0.4.4) | 0.4.4-3 libnotify1-gtk2.10 | libpam0g (= 0.99.7.1) | 0.99.7.1-6 libpango1.0-0(= 1.20.0) | 1.20.0-1 libpng12-0 (= 1.2.13-4) | 1.2.15~beta5-3 libsm6 | 2:1.0.3-1+b1 libx11-6 | 2:1.0.3-7 libxcursor1 ( 1.1.2) | 1:1.1.9-1 libxext6 | 2:1.0.4-1 libxfixes3 (= 1:4.0.1) | 1:4.0.3-2 libxi6 | 2:1.1.3-1 libxinerama1 | 2:1.0.3-1 libxklavier12 (= 3.4) | 3.5-1 libxml2 | 2.6.31.dfsg-2 libxrandr2 (= 2:1.2.0) | 2:1.2.2-1 libxrender1 | 1:0.9.4-1 libxss1 | 1:1.1.3-1 libxxf86misc1| 1:1.0.1-2 libxxf86vm1 | 1:1.0.1-2 zlib1g | 1:1.2.3.3.dfsg-11 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#457777: [gnome-screensaver] does not display login-dialog, locking out user
severity 45 important thanks On Sat, 2008-04-05 at 10:00 +0200, Paul Menzel wrote: I also encounter this bug. It is a freshly installed sid system and each time (three all in all), the dialog to enter the password is not displayed. I can see the mouse cursor only when moving the mouse, when I stop moving the mouse it vanishes. As a work-around I did System -- Preferences -- Screensaver -- Disable checkbox and when I get hit by this bug I do on tty1 killall gnome-screensaver. Please tell me, what other informations you need. And in my opinion the severity should be set to important. Hi, I'm increasing severity as requested. The gnome-screensaver FAQ have a few suggestions when it comes to bugs; http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-d50bc17e7d6f3a51c4715f02c657195e80e26c2c You could perhaps try to run g-s in verbose mode from a terminal first, and later try getting a backtrace if nothing interesting shows up. Second, it would be interesting if you and anyone else with this bug could compare configurations: Does it happen with a specific screensaver (the original reporter mentioned GL screensavers)? Do you use Compiz? Have you a non-standard setup when it comes to PAM? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
