after latest update, 'time expired' dialog hangs indefinitely, has to be hard-killed from the console
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-screensaver (Ubuntu) |
Fix Released
|
High
|
Chris Coulson | ||
Karmic |
Fix Released
|
High
|
Chris Coulson |
Bug Description
Binary package hint: gnome-screensaver
With gnome-screensaver 2.28.0-0ubuntu2, if the screensaver ever lands at the 'time expired' message, the dialog hangs; the only way to restore the session is by switching to a VT to kill the screensaver.
Backtrace of the gnome-screensaver process:
(gdb) bt
#0 0x00007f28c0871c9e in __libc_waitpid (pid=<value optimized out>, stat_loc=
at ../sysdeps/
#1 0x0000000000412fec in ?? ()
#2 0x00000000004145be in ?? ()
#3 0x000000000041486d in ?? ()
#4 0x00007f28bd723bbe in g_main_dispatch (context=0x2493910) at /build/
#5 IA__g_main_
#6 0x00007f28bd727588 in g_main_
at /build/
#7 0x00007f28bd7279e5 in IA__g_main_loop_run (loop=0x24f4600) at /build/
#8 0x00007f28bfd260e7 in IA__gtk_main () at /build/
#9 0x000000000040aa53 in main ()
Backtrace of the dialog process:
(gdb) thread apply all bt
Thread 2 (Thread 0x7f178fd21910 (LWP 7680)):
#0 pthread_
#1 0x000000000040d434 in ?? ()
#2 0x00007f179d8dc7d1 in pam_vprompt () from /lib/libpam.so.0
#3 0x00007f179d8dc9bf in pam_prompt () from /lib/libpam.so.0
#4 0x00007f17922a2250 in ?? () from /lib/security/
#5 0x00007f17922a0893 in pam_sm_authenticate () from /lib/security/
#6 0x00007f179d8d7bde in ?? () from /lib/libpam.so.0
#7 0x00007f179d8d74e8 in pam_authenticate () from /lib/libpam.so.0
#8 0x000000000040cf3a in ?? ()
#9 0x00007f17999c5b34 in g_thread_
#10 0x00007f179a07da04 in start_thread (arg=<value optimized out>) at pthread_
#11 0x00007f17996d17bd in clone () at ../sysdeps/
#12 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f179ee447d0 (LWP 7679)):
#0 0x00007f179a07ecfd in pthread_join (threadid=
#1 0x00007f179ea5d0b1 in g_thread_
#2 0x00007f17999c4f73 in IA__g_thread_join (thread=0x1f6b390) at /build/
#3 0x000000000040d803 in gs_auth_verify_user ()
#4 0x0000000000407859 in ?? ()
#5 0x00007f179999cbbe in g_main_dispatch (context=0x1d9ebc0) at /build/
#6 IA__g_main_
#7 0x00007f17999a0588 in g_main_
#8 0x00007f17999a09e5 in IA__g_main_loop_run (loop=0x1d6e6b0) at /build/
#9 0x00007f179c4010e7 in IA__gtk_main () at /build/
#10 0x000000000040769b in main ()
Given where the dialog's stack points, it's probably worth noting that I use pam_krb5, and not just the default pam_unix module.
ProblemType: Bug
Architecture: amd64
Date: Sun Oct 18 13:30:19 2009
DistroRelease: Ubuntu 9.10
Package: gnome-screensaver 2.28.0-0ubuntu2
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gnome-screensaver
Uname: Linux 2.6.31-14-generic x86_64
Changed in gnome-screensaver (Ubuntu Karmic): | |
assignee: | nobody → Chris Coulson (chrisccoulson) |
status: | Triaged → In Progress |
Confirmed that this change appears to fix the problem for me.