Delay when shutting down.

[The Liquidator]

When I go to shut down/logout etc and I hit the option button, there is a delay of about 20 seconds before anything at all happens. Does anyone have any idea what this is?

Is there an option I can use that will enable me to see what is going on please? It's currently quicker to hibernate or to hit Ctrl+Alt+Backspace and shut down from there.

Thanks
ian

[Detonate]

Re: Delay when shutting down.

Open a terminal and run:
sudo shutdown -P now
or
sudo shutdown -r now

The first one turns the computer off. the second one shuts down and then reboots.

Maybe you will see what's taking so long to close. Do you have a network running?

[dibl]

Re: Delay when shutting down.

Is there an option I can use that will enable me to see what is going on please?

It's not exactly an option -- but you can Ctrl-Alt-F1, log in, and then issue

sudo shutdown now

and observe the messages on screen, while timing the process. It would be interesting to learn whether it takes the same time, or less time, than it does when you initiate the process from the GUI.

Sorry Detonate -- your solution is a fine one.

[The Liquidator]

Re: Delay when shutting down.

the sudo shutdown options start the process immediately so I guess it's something to do with KDM

[Detonate]

Re: Delay when shutting down.

I could be wrong here, but I think all the shutdown button does is issue the same command as you used in the terminal, so that should not cause a delay. Remember, if you have any programs running, it has to shut those down first before it begins the actual shutdown. Also networking can be a factor, as it has to close all the connections. And it has to unmount any drives or network directories before it can shutdown.

[suplero]

Re: Delay when shutting down.

I sort of see a delay when starting different applications too. Konqueror can take at least a minute to start, and then maybe 20 seconds to change states.

I tried to start dolphin from the console and got the message

<unknown program name>(12371)/: Communication problem with "dolphin" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

Konqueror also takes forever to start or do anything [like a new window/tab] and even close. There are no error messages for konqueror in the console.

I looked at the running processes and there are about 30 instances of

/usr/lib/scim-1.0/scim-panel-gtk --no-stay --display :0 -c socket -d

running. I don't know if this is the problem, but it seems to be a problem. Maybe it is trying to close a running program gracefully and has to wait for a response that isn't coming.

[The Liquidator]

Re: Delay when shutting down.

My experience of scim is that it made my computer completely freeze so I uninstalled it. It seems to simply be an application to ensure a common input method across all apps. There was a bad update (well for me anyway) yesterday.

What happens if you uninstall scim? My guess is the problem will go away.

Ian

[suplero]

Re: Delay when shutting down.

Uninstalling scim and killing all of the running processes worked.

There must have been some starting processes in limbo too, because when I killed all of the scim processes, about 5 windows popped up.

Thanks