GNOME Bugzilla – Bug 82629
Logging out hangs gnome-session
Last modified: 2009-08-15 18:40:50 UTC
Testing on Solaris 8 with source taken from CVS on 22nd May User attempts to logout of gnome and gnome-session hangs. User cannot shut down machine without telnetting /rlogining in from another host or turning machine off. Happens even if not saving session. Telnet in from remote host and a ps shows 5524: /opt/gnome-2.0/bin/gnome_segv gnome-session 11 1.5.19 5524: /opt/gnome-2.0/bin/gnome_segv gnome-session 11 1.5.19 ----------------- lwp# 1 / thread# 1 -------------------- fde99884 poll (ffbee990, 1, ffffffff) fde4c968 select (5, 0, fdebb1dc, fdebb1dc, ffbeea30, ffbee990) + 2cc fe0db470 select (4, 1, ffbeea30, 10, 4, fde9bd70) + 34 fdc9bcc4 _XRead (ffffffff, ffbeec38, 20, 8, 8, ffbeec38) + ec fdc997ec XOpenDisplay (0, 0, fdd1e000, b, 1, 0) + 4e8 fedd9500 gdk_open_display (0, ffbeef1c, fdebba58, fdea48b8, 6, fdebba34) + 30 fed9ada0 gdk_init_check (ffbeef20, ffbeef1c, fdeb801c, feb95554, 6, 0) + 90 fe99fec8 gtk_init_check (ffbeef20, ffbeef1c, 0, 0, 0, 0) + f8 fe9a09ac gtk_init (ffbeef20, ffbeef1c, 1, 0, ff3e2668, fefc283f) + 3c ff1d2ff4 bonobo_ui_gtk_post_args_parse (2cb00, ff2642f4, ffbef25c, 35518, 0, 2b600) + b4 fefd50fc gnome_program_postinit (2cb00, 13ce8, 13cf4, 4, ffbef25c, 2d) + 1ac fefd5970 gnome_program_initv (2fb60, 13ce8, 13cf4, ff370908, 4, ffbef25c) + 700 fefd522c gnome_program_init (13ce8, 13cf4, ff370908, 4, ffbef25c, ff3396c4) + 8c ff306e2c gnome_init_with_popt_table (0, ff37b11c, 4, ffbef25c, 0, 0) + 9c 00012740 main (4, ffbef25c, ffbef270, 24000, 0, 0) + b8 00012358 _start (0, 0, 0, 0, 0, 0) + 108 ----------------- lwp# 2 / thread# 2 -------------------- fde9b048 signotifywait () fe0ce8f0 _dynamiclwps (fe0ee000, 5a, 0, 0, ffbeed34, 0) + 1c fe0d1b98 thr_yield (0, 0, 0, 0, 0, 0) + 8c ----------------- lwp# 3 -------------------------------- fde9b688 lwp_cond_wait (fe0f55a0, fe0f55b0, fdc45bf0) fde92fc8 _lwp_cond_timedwait (0, 3cebc819, fdc45c58, fe0f55a0, fe0f55b0, 0) + 98 fe0c8e34 _age (fe0eed98, fe0eed9c, fe0ee000, 0, 0, 4) + 94 fde98c48 _door_return (fe0ef6a8, 3, fe0ee000, 1, fdc45cb8, fe0ca484) + 68 ----------------- lwp# 4 -------------------------------- fde9b688 lwp_cond_wait (fe0f55a0, fe0f55b0, fdc23c48) fde92fc8 _lwp_cond_timedwait (0, 3cebc819, fdc23cb0, fe0f55a0, fe0f55b0, 0) + 98 fe0c8e34 _age (fe0eed98, fe0eed9c, fe0ee000, 3, fe0ee000, 1) + 94 fe0ca484 _lwp_start (fdc23d78, 0, 4000, fdc0fc34, 0, 0) + 18 fe0d1b98 thr_yield (0, 0, 0, 0, 0, 0) + 8c ----------------- lwp# 5 -------------------------------- fde98bec door (0, 0, 0, 0, fdc35d18, 4) fe0ca484 _lwp_start (0, 0, 0, 0, 0, 0) + 18 -------------------------- thread# 3 -------------------- fe0cd958 _reap_wait (fe0f2a08, 20984, 0, fe0ee000, 0, 0) + 38 fe0cd6b0 _reaper (fe0eee30, fe0f4770, fe0f2a08, fe0eee08, 1, fe400000) + 38 fe0dbad0 _thread_start (0, 0, 0, 0, 0, 0) + 40
ok, looks like gnome-session is seg faulting. can you get a stack trace of gnome-session (rather than gnome_segv) ?
silly me - here's the gnome-session stack trace: 16604: /opt/gnome-2.0/bin/gnome-session ----------------- lwp# 1 / thread# 1 -------------------- fde1bc68 waitid (0, 459b, ffbee558, 3) fddd6038 _waitpid (0, ffbee660, 0, ffbee660, 0, 0) + 60 fe05ae34 waitpid (b, ffbeeb38, ffbee880, fe06e000, 5af38, 5af28) + 34 fe05905c __libthread_segvhdlr (b, ffbeeb38, ffbee880, fe06e000, b, 0) + e4 fe05bbcc __sighndlr (b, ffbeeb38, ffbee880, fe058f78, 5af38, 5af28) + c fe0583b8 sigacthandler (b, 5aea0, 0, 0, 0, fe06e000) + 704 --- called from signal handler with signal 11 (SIGSEGV) --- 0002bafc display_gui (3fd94, 1, 0, 0, 0, 0) + 654 0002bd00 maybe_display_gui (3eb04, 2, 1, 2, 0, 1) + 48 00021a3c process_save_request (19b3f0, 2, 1, 2, 0, 1) + d4 00021df0 save_yourself_request (6eb68, 19b3f0, 2, 1, 2, 0) + f8 ff376300 _SmsProcessMessage (196f70, 6eb68, ffffffff, ff38a000, 1, 4) + 954 ff3487f8 IceProcessMessages (196f70, 0, 0, ff364000, 198460, 0) + 3b8 ff06b170 process_ice_messages (19d9b8, 1, 196f70, 0, 0, 0) + 48 fdf2ace4 g_io_unix_dispatch (19cf08, ff06b128, 196f70, ffbeeff8, 0, 0) + cc fdee0408 g_main_dispatch (6c7a8, 0, ffffffff, 0, 0, 0) + 270 fdee23c0 g_main_context_dispatch (6c7a8, 7fffffff, 879d8, e, e, 0) + c8 fdee2b20 g_main_context_iterate (6c7a8, 1, 1, 5bf38, 0, 0) + 6b8 fdee3b48 g_main_loop_run (8bb40, 8bb40, 8d8d0, 0, 756c7400, 756c7400) + 5c0 fe9a0dc8 gtk_main (8bb40, 53434, 53448, 53450, 89440, 88bc8) + 1c0 00025504 main (1, ffbef2ec, ffbef2f4, 52c00, 0, 0) + 444 0001f110 _start (0, 0, 0, 0, 0, 0) + 108 ----------------- lwp# 2 / thread# 2 -------------------- fde1b048 signotifywait () fe04e8f0 _dynamiclwps (fe06e000, 5a, 0, 0, ffbeedc4, 0) + 1c fe051b98 thr_yield (0, 0, 0, 0, 0, 0) + 8c ----------------- lwp# 3 -------------------------------- fde18bec door (0, 0, 0, 0, fdc45d18, 4) fe04a484 _lwp_start (0, 0, 0, 0, 0, 0) + 18 ----------------- lwp# 4 -------------------------------- fde1b688 lwp_cond_wait (fe0755a0, fe0755b0, fdc33c48) fde12fc8 _lwp_cond_timedwait (0, 3cece594, fdc33cb0, fe0755a0, fe0755b0, 0) + 98 fe048e34 _age (fe06ed98, fe06ed9c, fe06e000, 3, fe06e000, 1) + 94 fe04a484 _lwp_start (fdc33d78, 0, 4000, fdc0fc34, 0, 0) + 18 fe051b98 thr_yield (0, 0, 0, 0, 0, 0) + 8c -------------------------- thread# 3 -------------------- fe04d958 _reap_wait (fe072a08, 20984, 0, fe06e000, 0, 0) + 38 fe04d6b0 _reaper (fe06ee30, fe074770, fe072a08, fe06ee08, 1, fe400000) + 38 fe05bad0 _thread_start (0, 0, 0, 0, 0, 0) + 40
that stack trace isn't so helpful w/o which line it crashes on. but it should now be fixed by: 2002-05-23 jacob berkman <jacob@ximian.com> * logout.c (display_gui): more fixups for the commit 2 monday should fix #82629 2002-05-21 jacob berkman <jacob@ximian.com> * logout.c (display_gui): don't reference destroyed widgets. thanks owen.
*** Bug 82719 has been marked as a duplicate of this bug. ***
fix verified in source take from cvs on 24th may
closing