when shutdown ubuntu7.10, computr does not turn off automaticallye

Thanks for your bug report. Which version of Ubuntu and gnome-session do you use? Can you check the .xsession-errors file for anything interesting?

Daniel Holbach wrote:
> Thanks for your bug report. Which version of Ubuntu and gnome-session do
> you use? Can you check the .xsession-errors file for anything
> interesting?
>
> ** Changed in: gnome-session (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
>
Ubuntu 6.06 LTS
gnome-session 2.14.2-0ubuntu

Nothing unusual in .xsession-errors

The problem seems to be with gnome-session-save --kill
It opens the screen offering Logout, Lock Screen, Switch User,
Hibernate, Restart, Shutdown, Cancel
then whichever option you choose it saves the session and exits without
carrying out the "kill"
I tried running gnome-session-save --kill as root in case it's a
permissions problem, but this makes no difference.

Phil.

Any point in me running this under strace?

Does it happen with any user or just your current one?

Sebastien Bacher wrote:
> Does it happen with any user or just your current one?
>
>
ah, that's interesting. Only happens with me as the user. Must be
something I'm running that alters the behaviour of gnome-session-save.

I will look into this further and see if I can find out which program it is.

Thanks.

I had this problem once when the lookback interface wasn't up for some reason. Just in case it's your problem here, here is a quick list of things to check:
* ping 127.0.0.1
* ping yourhostname
* ifconfig -a | grep "UP LOOPBACK RUNNING"

If any of these fail, or don't show a result, you have a problem. Check your /etc/hosts file (is your hostname correctly setup there if it needs to?), check your /etc/network/interfaces (got a "lo" entry? is it set to "auto" and "inet loopback" ?)

Also, another symptom will be that stracing "gnome-session-save --kill" will block on some network stuff with 127.0.0.1 or something similar.

Mathieu Pillard wrote:
> I had this problem once when the lookback interface wasn't up for some reason. Just in case it's your problem here, here is a quick list of things to check:
> * ping 127.0.0.1
> * ping yourhostname
> * ifconfig -a | grep "UP LOOPBACK RUNNING"
>
> If any of these fail, or don't show a result, you have a problem. Check
> your /etc/hosts file (is your hostname correctly setup there if it needs
> to?), check your /etc/network/interfaces (got a "lo" entry? is it set to
> "auto" and "inet loopback" ?)
>
> Also, another symptom will be that stracing "gnome-session-save --kill"
> will block on some network stuff with 127.0.0.1 or something similar.
>
>
Thanks for the response.

The problem seems to be mythfrontend. If that program is running then
shutdown fails. If I kill mythfrontend first it all works properly.

I've downloaded the sourcecode to mythfrontend to try and see if it does
anything unusual, but no joy so far.

Phil.

Do you still have that problem with edgy or feisty?

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

I am having the same problem. When Mythfrontend is running, I cannot logout/shutdown/restart.

Pressing the logout button only has as result that Mythfrontend shows the screen: Do you really want to quit MythTV?

I would think that this is blocking the logout process. I added a line in the .bash_logout file:

killall mythfrontend.real

But without effect.
Please let me know what other information is needed so I can post that.

Attaching my .xsession-errors.

I am not sure what is supposed to happen, but trying to log out gives this line:
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-13856--1032536501-1195160776 --active --geometry 80x24+360+348 --title joris@poppie: ~ --working-directory /home/joris --zoom 1

Reopening since I can provide any information that is necessary, let me know what is needed...

I don't think my problem is the same as the one in the new description. I will open a new bug-report and close this one again.