Bug#497274: Unresponsive shutdown/restart/logout
reassign 497274 gnome-session thanks Le vendredi 05 septembre 2008 à 01:33 +0200, Cesare Leonardi a écrit : The guilty seems to be the file ~/.gnome2/session. I've tried to analyze the problem with 3 user accounts: two existing one and a fresh new one. I've found that the new account doesn't show the problem. Same thing if i rename the session file to something else: i can logout/reboot/shutdown correctly. I haven't ever modified this file by hand but i remember that in some Gnome version ago, there was a Save profile checkbox on every logout, and i remember that i've enabled that. I verified that both faulty account have that flag on (under System - Preferences - Sessions - Session options) but the new account have the flag off. So i tried to disable that flag on these two accounts and now i can logout correctly from one of the two. In the other account i've also experimented the button Remember Currently Running Applications but that made the logout problem persist even without the save profile flag. I've corrected the problem renaming the file ~/.gnome2/session. Now i've renamed the session file and reenabled the remember flag: the logout/reboot/poweroff works correctly and a new session file was created. I think the .gnome2/session file was created by a buggy version of gnome-session (around 2.18 I think) that did not remove autostarted applications from it. But the real bug is to have this one in it: 6,RestartCommand=/usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable If it is here, it means that the --sm-disable option did not work in some past version, because it did register to the gnome-session. And now that this option works, the program is still started but does not register to the session, and gnome-session won’t consider it has failed to start before a 120 seconds timeout. There is no more bug in gnome-volume-manager now, but there may be one in gnome-session if it still records this process as needing to be restarted when you save the session again. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#497274: Unresponsive shutdown/restart/logout
Josselin Mouette wrote: Please provide the list of running processes when this is happening (log in to the console and type ps auxw), the contents of ~/.gnome2/session (if any), the list of files in /etc/xdg/autostart and /usr/share/autostart (if any). Your request was very helpful, because has given me some input on how to debug the problem. And i think i've found the cause. The guilty seems to be the file ~/.gnome2/session. I've tried to analyze the problem with 3 user accounts: two existing one and a fresh new one. I've found that the new account doesn't show the problem. Same thing if i rename the session file to something else: i can logout/reboot/shutdown correctly. I haven't ever modified this file by hand but i remember that in some Gnome version ago, there was a Save profile checkbox on every logout, and i remember that i've enabled that. I verified that both faulty account have that flag on (under System - Preferences - Sessions - Session options) but the new account have the flag off. So i tried to disable that flag on these two accounts and now i can logout correctly from one of the two. In the other account i've also experimented the button Remember Currently Running Applications but that made the logout problem persist even without the save profile flag. I've corrected the problem renaming the file ~/.gnome2/session. Now i've renamed the session file and reenabled the remember flag: the logout/reboot/poweroff works correctly and a new session file was created. I've attached the initial session file of my account and the other file you asked for. The file bug.user1.ps-auxw.txt shows the process situation after i've said to logout to my just opened session (and the command was ignored). The /usr/share/autostart directory is not present in my system. Regards. Cesare Leonardi. [Default] 0,id=11c0a80a0100012120132050027750012 0,RestartStyleHint=2 0,Priority=40 0,Program=nautilus 0,CurrentDirectory=/home/cesare 0,CloneCommand=nautilus --sm-config-prefix /nautilus-R4FJdT/ 0,RestartCommand=nautilus --sm-config-prefix /nautilus-R4FJdT/ --sm-client-id 11c0a80a0100012120132050027750012 --screen 0 --load-session /home/cesare/.nautilus/saved-session-HBCUGU 1,id=11c0a80a010001127687727005630 1,RestartStyleHint=2 1,Priority=40 1,Program=gnome-panel 1,CurrentDirectory=/home/cesare 1,CloneCommand=gnome-panel --sm-config-prefix /gnome-panel-QAwF6Y/ 1,RestartCommand=gnome-panel --sm-config-prefix /gnome-panel-QAwF6Y/ --sm-client-id 11c0a80a010001127687727005630 --screen 0 2,id=11c0a80a0100011954221960029790007 2,RestartStyleHint=2 2,Priority=20 2,Program=metacity 2,CurrentDirectory=/home/cesare 2,DiscardCommand=rm -f /home/cesare/.metacity/sessions/11c0a80a0100011954221960029790007.ms 2,CloneCommand=metacity 2,RestartCommand=metacity --sm-client-id 11c0a80a0100011954221960029790007 3,RestartCommand=gnome-power-manager --sm-disable 4,RestartCommand=bluetooth-applet 5,RestartCommand=gnome-at-visual -s 6,RestartCommand=/usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable 7,RestartCommand=/usr/bin/system-config-printer-applet 8,RestartCommand=kerneloops-applet 9,RestartCommand=system-config-printer-applet num_clients=10 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2100 712 ?Ss Sep02 0:01 init [2] root 2 0.0 0.0 0 0 ?S Sep02 0:00 [kthreadd] root 3 0.0 0.0 0 0 ?S Sep02 0:00 [migration/0] root 4 0.0 0.0 0 0 ?S Sep02 0:00 [ksoftirqd/0] root 5 0.0 0.0 0 0 ?S Sep02 0:00 [watchdog/0] root 6 0.0 0.0 0 0 ?S Sep02 0:00 [events/0] root 7 0.0 0.0 0 0 ?S Sep02 0:00 [khelper] root39 0.0 0.0 0 0 ?S Sep02 0:00 [kblockd/0] root41 0.0 0.0 0 0 ?S Sep02 0:00 [kacpid] root42 0.0 0.0 0 0 ?S Sep02 0:00 [kacpi_notify] root 114 0.0 0.0 0 0 ?S Sep02 0:00 [kseriod] root 146 0.0 0.0 0 0 ?SSep02 0:00 [pdflush] root 147 0.0 0.0 0 0 ?SSep02 0:00 [pdflush] root 148 0.0 0.0 0 0 ?S Sep02 0:00 [kswapd0] root 149 0.0 0.0 0 0 ?S Sep02 0:00 [aio/0] root 611 0.0 0.0 0 0 ?S Sep02 0:00 [ksuspend_usbd] root 612 0.0 0.0 0 0 ?S Sep02 0:00 [khubd] root 636 0.0 0.0 0 0 ?S Sep02 0:00 [khpsbpkt] root 721 0.0 0.0 0 0 ?S Sep02 0:00 [knodemgrd_0] root 727 0.0 0.0 0 0 ?S Sep02 0:00 [ata/0] root 728 0.0 0.0 0 0 ?S Sep02 0:00 [ata_aux] root 819 0.0 0.0 0 0 ?S Sep02 0:00 [kstriped] root
Bug#497274: Unresponsive shutdown/restart/logout
Le dimanche 31 août 2008 à 15:25 +0200, Cesare Leonardi a écrit : For me it's always reproducible: - login with gdm; - *IMPORTANT*: do nothing (ie not start any application); - click on System - Log out... or System - Shut down...; For me the operation seems completely ignored, until i try to launch something (a terminal, an application). This last operation seems to trigger or unlock something and then the logout procedure (or restart, or shutdown) start up. Sometimes you can't even see the application launched, that get killed immediately. If it is a Gnome app, it will be restarted automatically on the next login. Please provide the list of running processes when this is happening (log in to the console and type ps auxw), the contents of ~/.gnome2/session (if any), the list of files in /etc/xdg/autostart and /usr/share/autostart (if any). Thanks, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#497274: Unresponsive shutdown/restart/logout
Package: gnome Version: 1:2.22.2~4 Severity: minor Debian/Sid user. Since the Lenny release is approacing, i think it'll be useful to describe a problem i've seen for a long time. For me it's always reproducible: - login with gdm; - *IMPORTANT*: do nothing (ie not start any application); - click on System - Log out... or System - Shut down...; For me the operation seems completely ignored, until i try to launch something (a terminal, an application). This last operation seems to trigger or unlock something and then the logout procedure (or restart, or shutdown) start up. Sometimes you can't even see the application launched, that get killed immediately. If it is a Gnome app, it will be restarted automatically on the next login. I don't know what is the package responsible of this, so i filed the bug to gnome. Feel free to change this. Regards. Cesare. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
