GNOME Bugzilla – Bug 662757
Gnome-Shell lock screen does not always display password prompt
Last modified: 2013-08-16 11:43:16 UTC
Hello everyone, when the screen locks, I do not always get the password prompt when I come back to my PC. I see the top bar but that is it, moving the mouse and typing keys do nothing. It is hard to reproduce as it doesn't always happen, I have not been able to find a use case that causes this, as even overnight screen locking does not always cause this to happen. I stress that the computer is always on, I do not make it hibernate or suspend either. I have dual screens, I found the following bug in Ubuntu's tracker that is basically the same thing: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/848562, they mention that it may be the dual screens. I am using the latest Ubuntu (11.10, upgraded from 11.04) with all updates applied. I also have a laptop with the same software config that does not have this issue, it does not have dual screens though, so that may be the issue. Apparently in the Ubuntu bug report a user states that he can login by blindly typing in the password, I have not tried this yet, but it could be a security issue IMO if people start doing that. Please note that no one at Ubuntu is looking into this issue. Thank you, Gabriel Misc info: gnome-shell : 3.2.0-0ubuntu1 gnome-core : 1:3.0+1ubuntu1 gnome-screensaver : 3.2.0-0ubuntu1 gnome-power-manager : 3.2.0-0ubuntu1 Kernel : 3.0.0-12-generic Architecture : 64bit Shout if you need more info.
Which graphics card and driver are you using?
Nvidia: nvidia-current-280.13-0ubuntu6 Yesterday I semi-had the issue, I could see the password box, but it was just a grey box. I was able to log in by blindly typing my password.
I get similar issue with my dual screen setup in Ubuntu using gnome-shell. It happens once in 2 times when I lock the screen using ctrl+alt+l. There is no password box when I come back or there is only a white boundary of it. With the white boundary version typing password blindly works, otherwise I have to kill gnome-session. Even if I manage to log back in, I get constant 30% CPU usage by gnome-shell. If I reproduce the issue afterwards I get another 30% making it 60% which makes the environment unusable. gnome-session: 3.2.1-0ubuntu1 gnome-shell: 3.2.0-0ubuntu1 gnome-screensaver: 3.2.0-0ubuntu1 kernel: 3.0.0-12-generic-pae nvidia: 285.05.09
I believe this has to do with putting dual monitors to sleep more than it does the lock screen itself - at least in my experience. If I lock the screen and then immediately return before the monitors go to sleep the dialog always seems to work. If the monitors have gone to sleep, moving the mouse will wake them up, but I don't get the login box. I am able to successfully login blindly and there are no adverse side-effects for me (not even the CPU usage after login) unlike Adam above. It's been five days since I rebooted so I've blindly logged in probably 50 times without difficulty - other than the lack of a password box. monitors: Dual Acer 24" LED on DVI cables gnome-session: 3.2.1-0ubuntu1 gnome-shell: 3.2.0-0ubuntu1 gnome-screensaver: 3.2.0-0ubuntu1 kernel: 3.0.0-12-generic (3.0.0.12.14) uname: 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux nvidia: 280.13-0ubuntu6 (280.13 - GeForce 9800 GT PCI) I deploy a forced Gnome setting for a 3 minute screensaver timeout with zero lock delay on my network as part of our security policy. I do not have any actual "screensaver" running, it just goes to the default black with the clock bar at the top. I first visited the Ubuntu bug tracker, where they state it's an upstream and redirect users to come here.
One more observation: When the monitors wake up I get a completely black screen on the left. The right screen will display the top activity bar with clock and the remaining of that screen is black. And there is no password dialog. When I lock the screen and come back before the monitors wake up the LEFT screen has the activity bar with clock and the right screen has the password box. It's as if when waking the hardware it shifts the login screen off the right monitor and forgets to use the left monitor...?
I see this problem very regularly and I'm also running a dual screen setup using the nvidia-current driver from Ubuntu 11.10. I've also seen the same problem using the Nouveau driver. The bug is currently marked as NEEDINFO. I can pretty regularly see the problem and I'm happy to provide any info that's needed. What data is missing?
Is there something interesting in your ~/.xsession-errors?
I don't see anything interesting in my ~/.xsession-errors file, but because there are no timestamps it's pretty hard to correlate any errors with the problem. I'll keep an eye on that file after I experience the problem again and update this defect if anything comes up.
Hi All, I had this today again but this time the screens didn't go into power saving mode. I locked the screen for maybe 5 minutes and came back, the background was showing but no password prompt. I blindly entered it just like I do when this happens and it worked. Cheers, Gabriel
Gabriel, same question: Is there something interesting in your ~/.xsession-errors?
it's a bit strange, it has just this: (gnome-settings-daemon:1942): GLib-CRITICAL **: g_variant_get_int32: assertion `g_variant_is_of_type (value, G_VARIANT_TYPE_INT32)' failed (check-new-release-gtk:23096): Gtk-WARNING **: Unknown property: GtkMessageDialog.has-separator WARNING:root:timeout reached, exiting ** (gnome-fallback-mount-helper:1981): DEBUG: Screensaver active changed to 0 but the file is 1.3MB. .xsession-errors.old has more stuff in it, but it's only 5k. I'm going to delete both to get a nice clean one.
Just had it, locked the screen manually and came back less than 5 minutes later, the screen was still on, here's all my xsession errors file contains: ** (update-notifier:2610): WARNING **: log file empty (logrotate?) /var/log/dpkg.log ** (update-notifier:2610): WARNING **: log file empty (logrotate?) /var/log/apt/term.log ** (gnome-settings-daemon:1904): WARNING **: Connection failed, reconnecting... (gnome-settings-daemon:1904): media-keys-plugin-WARNING **: Unable to get default sink Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed ** (gnome-fallback-mount-helper:1945): DEBUG: Screensaver active changed to 0 Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed ** (gnome-fallback-mount-helper:1945): DEBUG: Screensaver active changed to 1 Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed Window manager warning: Log level 8: meta_window_focus: assertion `!window->override_redirect' failed ** (gnome-fallback-mount-helper:1945): DEBUG: Screensaver active changed to 0 Doesn't look interesting to me, but it may mean something to someone.
(In reply to comment #12) > Doesn't look interesting to me, but it may mean something to someone. Yes, it does, thanks. It could be the related to bug 662757. Could you get us a backtrace? You'd need to follow instructions at https://live.gnome.org/GnomeShell/Debugging and reproduce the bug. But please replace gdb /usr/bin/gnome-shell (gdb) run --replace with G_DEBUG=fatal-warnings gdb /usr/bin/gnome-shell (gdb) run --replace Thanks!
is it supposed to do this when I run the run --replace command (the last 2 lines)?: $ G_DEBUG=fatal-warnings gdb /usr/bin/gnome-shell GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/gnome-shell...(no debugging symbols found)...done. (gdb) run --replace Starting program: /usr/bin/gnome-shell --replace [Thread debugging using libthread_db enabled] [New Thread 0x7fffe4086700 (LWP 22513)] [New Thread 0x7fffe3885700 (LWP 22514)] [New Thread 0x7fffe2e7d700 (LWP 22515)] [New Thread 0x7fffe267c700 (LWP 22516)] [New Thread 0x7fffd6dff700 (LWP 22519)] gnome-shell-calendar-server[22521]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting [New Thread 0x7fffcca14700 (LWP 22525)] [New Thread 0x7fffcc213700 (LWP 22526)] JS LOG: System monitor applet init from /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com JS LOG: System monitor applet enabling JS LOG: System monitor applet enabling done JS ERROR: !!! WARNING: 'redefining arguments is deprecated' JS ERROR: !!! WARNING: file '/usr/share/gnome-shell/extensions/updateindicator@aegirxx.googlemail.com/extension.js' line 282 exception 0 number 237 Window manager warning: Log level 10: shell_tray_manager_manage_stage: assertion `manager->priv->stage == NULL' failed Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007ffff5cea313 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Well, that's not the same bug, but that would still be something to debug. Please disable all extensions and retry. If it still happens, type this in gdb: t a a bt call gjs_dumpstack ()
Oh, and you'll probably need to install debugging symbols from: http://ddebs.ubuntu.com/pool/universe/m/mutter/ (choose the package corresponding to your version)
Ok, sorry for the delay. I did that and still had the error mentioned in comment #14, so I did as told in comments 15 & 16 (but in the correct order), I attached the output. However, I had to stop after that as I have trouble getting my gnome-shell session back (the screen is black but the mouse shows up), I can't spend too much time on this since I'm at work. I hope the output is useful at least.
Created attachment 203647 [details] debuf output, see comment 17
Comment on attachment 203647 [details] debuf output, see comment 17 Sorry, but as it's not the same bug now, you need to install Cogl, Clutter and gnome-shell debugging symbols too... http://ddebs.ubuntu.com/pool/universe/g/gnome-shell/ http://ddebs.ubuntu.com/pool/main/c/clutter-1.0/ http://ddebs.ubuntu.com/pool/main/c/cogl/ Thanks!
I haven't had a chance to do the debugging since I have trouble switching back to X session and I can't stop working (and I can't reproduce the problem, it's sort of random). I haven't forgotten it though :-).
I've been having this problem for months and now that my wife also uses the desktop and we need to be able to switch users, I figured I'd see if there was a fix. I'm surprised that there are only 22 people on the ubuntu bug (#848562) and only 9 on this one. This doesn't seem to be directly related to putting monitors to sleep. Sometimes, just by going to the menu and clicking "Lock Screen", this happens. One screen will go blank and the other will either display the desktop background or the desktop background color (solid blue for me). Then the dialog does not show up, unless I do the Esc/move mouse trick. Other times, I have come back to my computer and on one monitor, it looks like the system never locked at all, but I quickly discover I can't click on anything. When this happens, I know it's the lock screen still showing my active session. I then have to type blindly and hope I'm not sending my password into a chat window. The next time this happens, I will try to get a gdb as described above. However, I will share the workaround found on the Ubuntu bugtracker. Maybe knowing the workaround will help point the developers in the right direction. """ https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/848562/comments/7 I have found a workaround: for some reason, the password dialog wants to only show up on one of the monitors, but only the one on which the mouse is when showing the password dialog is displaying "stuff" (stuff being anything else besides the top bar). So what I do when I don't see the password dialog is to press escape once, then move the mouse to the other monitor, and press escape again. """
Hello, just dropping by to ask if there is anything I can do to help with this. I'm having the exact same issue(s) described above, though in my case this happens only when using a dual-monitor setup (until now never saw this bug in a single-monitor setup). When I have the time I'll try to provide a backtrace using instructions provided in comment 13 and following (never done that before but never to late to begin). Thanks! env. info: debian unstable kernel: 3.2.0-2-amd64 GNOME Shell 3.4.1 Driver NVIDIA-Linux-x86_64-295.40
Affects me too. Only happens when I use two monitors. Sometimes it works ok. Sometimes after blanking second monitor shows desktop and password prompt doesn't show up, but screen unlocks if I type password blindly. Probably only happens after monitors turn off.
1. Displays aren't fully blanked: https://www.dropbox.com/s/xntwvg626uyxwfi/IMG_20120716_142713.jpg 2. Password box doesn't show up, probably obscured by partially left black rect: https://www.dropbox.com/s/v735cfj1s0btmwq/IMG_20120716_142724.jpg
Partial blanking only happens when I lock screen with focus in left monitor.
Weall, actually mouse pointer, not focus.
Related lines of .xsession-errors Window manager warning: Treating resize request of legacy application 0x1400909 (gnome-scre) as a fullscreen request Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x1400909 not in stack Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: window 0x140090c not in stack Window manager warning: Log level 16: STACK_OP_LOWER_BELOW: sibling window 0x140090c not in stack Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x140090c not in stack Window manager warning: Treating resize request of legacy application 0x1400924 (gnome-scre) as a fullscreen request Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400924 (gnome-scre) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400927 (gnome-scre) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Log level 16: STACK_OP_LOWER_BELOW: sibling window 0x1400927 not in stack Window manager warning: Log level 16: STACK_OP_RAISE_ABOVE: sibling window 0x1400927 not in stack
I just wanted to mention that I have exactly the same problem. I can easily reproduce it by just pressing "Lock Screen" and shaking the mouse afterwards. No need for the monitors to shut off. Then, my laptop LCD shows the normal workspace, but my external monitor which also contains the top bar and notification area shows only the top bar and the mouse pointer while everything else is just black. I cannot type my password blindly, although I remember it used to work at some point in time. And also I remember that at some other point in time the password went straight into some Empathy window and I've sent my password to some buddy! ;-) I use Gentoo with Gnome 3.4.1 and an intel graphics card and the usual open-source drivers that come with X.org. So at least we can exclude some Nvidia-specific problem.
Hi again, now I wanted to do some more debugging, but I cannot reproduce the issue anymore. I updated the following packages yesterday and this morning, so it might be that one of them brought the cure: Tue Jul 17 20:40:59 2012 >>> sys-apps/pciutils-3.1.10 Tue Jul 17 20:41:19 2012 >>> sys-apps/less-450 Tue Jul 17 20:41:44 2012 >>> dev-perl/Net-SSLeay-1.480.0-r1 Tue Jul 17 20:43:33 2012 >>> sys-kernel/gentoo-sources-3.4.5 Tue Jul 17 20:49:12 2012 >>> dev-lang/v8-3.12.11 Tue Jul 17 20:49:30 2012 >>> app-admin/eselect-opengl-1.2.6.1 Tue Jul 17 20:51:04 2012 >>> dev-libs/elfutils-0.154-r1 Tue Jul 17 21:05:06 2012 >>> app-emulation/virtualbox-modules-4.1.18 Tue Jul 17 21:16:11 2012 >>> dev-lang/nacl-toolchain-newlib-0_p9093 Tue Jul 17 21:18:49 2012 >>> dev-libs/glib-2.32.4 Tue Jul 17 21:23:16 2012 >>> x11-libs/gtk+-2.24.11 Tue Jul 17 21:23:38 2012 >>> sys-apps/kmod-9-r3 Tue Jul 17 21:23:56 2012 >>> x11-proto/glproto-1.4.16 Tue Jul 17 21:38:03 2012 >>> sys-devel/llvm-3.1-r2 Tue Jul 17 21:40:09 2012 >>> dev-cpp/glibmm-2.32.1 Tue Jul 17 21:46:33 2012 >>> media-libs/mesa-8.0.3-r1 Tue Jul 17 21:46:53 2012 >>> www-client/firefox-bin-14.0.1 Tue Jul 17 22:14:21 2012 >>> sys-devel/clang-3.1-r5 Tue Jul 17 22:18:51 2012 >>> x11-libs/gtk+-3.4.4 Tue Jul 17 22:19:21 2012 >>> gnome-extra/gnome-screensaver-3.4.2-r1 Wed Jul 18 00:04:31 2012 >>> www-client/chromium-22.0.1207.1 Wed Jul 18 00:05:35 2012 >>> media-gfx/eog-3.4.3 Wed Jul 18 00:07:31 2012 >>> net-misc/networkmanager-0.9.4.0-r5 Wed Jul 18 00:08:17 2012 >>> media-libs/libchamplain-0.12.3 Wed Jul 18 00:17:32 2012 >>> media-libs/opencv-2.4.2 Wed Jul 18 08:05:08 2012 >>> dev-perl/YAML-Syck-1.200.0 Wed Jul 18 08:05:49 2012 >>> dev-perl/DateManip-6.320.0 The most likely candidate is probably gtk+-3.4.4.
Yeah. Upgrading gtk+ to 3.4.4 fixed this for me.