GNOME Bugzilla – Bug 155321
long wait time before logout
Last modified: 2016-01-05 20:30:51 UTC
start gnome wait until gnome launches all apps and system becomes idle menu-> logout wait for a minute or two and then logout During the waiting period: gnome is fully functional: you can do whatever you want including launching applications. As soon as the wait is over, the console will have a message displaying: saving gnome-session (even though this option is turned off on my system) If I run a session for a longer period, I can logout immidiately (but not always).
I've got the same problem except that there's no console output at all. I didn't find anything suspect. The problem is alway reproducible. My system: gentoo, kernel 2.6.10, gnome 2.8.1 Here are the processes that are running on my machine: PID TTY STAT TIME COMMAND 1 ? S 0:00 init [3] 2 ? SN 0:00 [ksoftirqd/0] 3 ? S< 0:00 [events/0] 4 ? S< 0:00 [khelper] 5 ? S< 0:00 [kacpid] 27 ? S< 0:00 [kblockd/0] 28 ? S 0:00 [khubd] 38 ? S 0:00 [pdflush] 39 ? S 0:00 [pdflush] 41 ? S< 0:00 [aio/0] 40 ? S 0:00 [kswapd0] 112 ? S 0:00 [kseriod] 132 ? S 0:00 [kjournald] 236 ? S<s 0:00 udevd 5576 ? S 0:00 [pccardd] 5798 ? S<s 0:00 /sbin/cardmgr -s /var/run/stab -f 5819 ? S<s 0:00 /sbin/dhcpcd eth0 7624 ? Ss 0:00 metalog [MASTER] 7635 ? S 0:00 metalog [KERNEL] 7665 ? Ss 0:00 /usr/sbin/acpid -c /etc/acpi/events 7759 ? Ss 0:00 /usr/sbin/cupsd 7808 ? Ss 0:00 /usr/bin/dbus-daemon-1 --system 7929 ? Ss 0:00 /sbin/portmap 7940 ? Ss 0:00 /usr/sbin/famd -T 0 -c /etc/fam.conf 8017 ? Ss 0:00 /usr/sbin/hald 8134 ? Ss 0:00 /usr/sbin/cron 8385 ? Ss 0:00 /usr/X11R6/bin/xfs -daemon -config /etc/X11/fs/config -droppriv -user xfs -port -1 8429 tty1 Ss+ 0:00 /sbin/agetty 38400 tty1 linux 8432 tty2 Ss+ 0:00 /sbin/agetty 38400 tty2 linux 8433 tty3 Ss+ 0:00 /sbin/agetty 38400 tty3 linux 8434 tty4 Ss+ 0:00 /sbin/agetty 38400 tty4 linux 8437 tty5 Ss+ 0:00 /sbin/agetty 38400 tty5 linux 8438 tty6 Ss+ 0:00 /sbin/agetty 38400 tty6 linux 8556 ? Ss 0:00 /usr/bin/gdm 8558 ? S 0:00 /usr/bin/gdm 8563 ? S 0:11 /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 8739 ? Ss 0:00 gnome-session 8758 ? Ss 0:00 /usr/bin/ssh-agent -- gnome-session 8760 ? S 0:01 /usr/libexec/gconfd-2 11 8766 ? S 0:00 /usr/bin/gnome-keyring-daemon 8771 ? Ss 0:00 /usr/bin/esd -terminate -nobeeps -as 2 -spawnfd 17 8773 ? Ss 0:00 /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=19 8775 ? Ss 0:00 gnome-smproxy --sm-config-prefix /.gnome-smproxy-0UEpXp/ --sm-client-id 117f000001000110459389500000221440000 8777 ? S 0:00 /usr/libexec/gnome-settings-daemon --oaf-activate-iid=OAFIID:GNOME_SettingsDaemon --oaf-ior-fd=22 8787 ? S 0:00 xscreensaver -nosplash 8796 ? Ss 0:01 metacity --sm-save-file 1104595065-31364-746127735.ms 8813 ? Ssl 0:04 nautilus --sm-config-prefix /nautilus-0AyxDp/ --sm-client-id 117f000001000110459389900000221440003 --screen 0 --no-default-window 8815 ? Ss 0:05 gnome-panel --sm-config-prefix /gnome-panel-9EQyUp/ --sm-client-id 117f000001000110459389800000221440002 --screen 0 --profile defa 8819 ? Ssl 0:00 /usr/libexec/evolution/2.0/evolution-alarm-notify --sm-config-prefix /evolution-alarm-notify-TBiEFp/ --sm-client-id 117f0000010001 8821 ? Ss 0:00 gnome-volume-manager 8826 ? Sl 0:00 /usr/libexec/evolution-data-server-1.0 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_CalFactory:1.0 --oaf-ior-fd=30 8829 ? Sl 0:00 /usr/libexec/gnome-vfs-daemon --oaf-activate-iid=OAFIID:GNOME_VFS_Daemon_Factory --oaf-ior-fd=33 8849 ? S 0:00 /usr/libexec/mapping-daemon 8854 ? S 0:00 /usr/libexec/stickynotes_applet --oaf-activate-iid=OAFIID:GNOME_StickyNotesApplet_Factory --oaf-ior-fd=36 8856 ? S 0:00 /usr/libexec/wnck-applet --oaf-activate-iid=OAFIID:GNOME_Wncklet_Factory --oaf-ior-fd=38 8863 ? S 0:00 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=26 8865 ? S 0:00 /usr/libexec/gnome-netstatus-applet --oaf-activate-iid=OAFIID:GNOME_NetstatusApplet_Factory --oaf-ior-fd=40 8867 ? S 0:00 /usr/libexec/notification-area-applet --oaf-activate-iid=OAFIID:GNOME_NotificationAreaApplet_Factory --oaf-ior-fd=42 8874 ? S 0:00 /bin/bash /usr/bin/firefox 8884 ? Sl 0:09 /usr/lib/MozillaFirefox/firefox-bin 8969 ? Sl 0:01 gnome-terminal 8970 ? S 0:00 gnome-pty-helper 8971 pts/0 Ss 0:00 -bash 9043 pts/0 R+ 0:00 ps ax
Confirming this since we have separate reports of the same thing happening. Have any of you had the chance to test with 2.9.x? Could the original reporter tell us a bit more about his system and what apps are running when the problem occurs?
I've experienced this too. It has only happened once so far, and as far as I can remember I was only running a gnome terminal session. I clicked "Log Out", and got no response. So I tried it again. Nothing. Then again. Still nothing. At this point I was thinking "that's really weird". The menus still worked, and everything else seemed fine, but "Log Out" just didn't seem to work. After about another 40 seconds though, the logout dialog box appeared. I clicked cancel. Then a second logout dialog box appeared (presumably stacked-up from the second and third times I tried to log out), cancelled, then the third log out dialog appeared, and I clicked cancel. I then rebooted, and I wasn't able to reproduce the problem. The box is a Macintosh G3 PowerPC, running Ubuntu 4.10, with their 2.6.8.1-5-powerpc kernel.
*** Bug 323378 has been marked as a duplicate of this bug. ***
I've been able to reproduce this. I have a custom TCL/TK app being restarted from ~/.gnome2/session-manual on my Suse 10.0 box with gnome-session 2.12.0. This app is not session manager aware because TCL/TK is not session manager aware. When I press the logout button on the desktop, it waits 2 minutes before it will allow a logout after it comes up. The system will however allow logout if a sesion-management aware application is started afterwords. Aka start a gnome terminal after clicking logout and the logout window will appear instantaneously. If you then click cancel from the logout window, the terminal will appear. I've also observed that if a session-manager aware application goes to sleep without calling a select on the ICE socket created by SmcOpenConnection then this will also hang the logout. From my experience, I'm guessing that the session manger gets stuck waiting for the application to register with the session manager and doesn't get unstuck until a session management aware application registers with SmcOpenConnection.
See comments in bug #94754 for possible explanations.
*** This bug has been marked as a duplicate of bug 704665 ***