[opensuse] System won't shut down
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages: Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup And then the computer just sits there. The only way to stop it is with the power-off button. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 09 January 2007 1:28 pm, Paul Abrahams wrote:
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages:
Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup
And then the computer just sits there. The only way to stop it is with the power-off button.
The problem started after I turned off ACPI in the BIOS, though I didn't immediately realize that. Turning ACPI back on restored the correct shutdown behavior. There still might be a bug lurking here, though; why should the ACPI setting prevent the computer from shutting down? Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 11 January 2007 09:35, Paul Abrahams wrote:
On Tuesday 09 January 2007 1:28 pm, Paul Abrahams wrote:
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages:
Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup
And then the computer just sits there. The only way to stop it is with the power-off button.
The problem started after I turned off ACPI in the BIOS, though I didn't immediately realize that. Turning ACPI back on restored the correct shutdown behavior. There still might be a bug lurking here, though; why should the ACPI setting prevent the computer from shutting down?
Because that's one primary purpose of ACPI. ACPI = Advanced Configuration and Power Interface
Paul
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Paul Abrahams wrote:
On Tuesday 09 January 2007 1:28 pm, Paul Abrahams wrote:
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages:
Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup
And then the computer just sits there. The only way to stop it is with the power-off button.
The problem started after I turned off ACPI in the BIOS, though I didn't immediately realize that. Turning ACPI back on restored the correct shutdown behavior. There still might be a bug lurking here, though; why should the ACPI setting prevent the computer from shutting down?
Paul
In my experience the shutdown from the various GUI choices are problematic, intermittant and not reliable. Using as root from a terminal session: shutdown -y -g0 -i0 always works for me. Someone needs to get serious about fixing the GUI versions of shutdown. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Robert Lewis wrote:
Paul Abrahams wrote:
On Tuesday 09 January 2007 1:28 pm, Paul Abrahams wrote:
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages:
Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup
And then the computer just sits there. The only way to stop it is with the power-off button.
The problem started after I turned off ACPI in the BIOS, though I didn't immediately realize that. Turning ACPI back on restored the correct shutdown behavior. There still might be a bug lurking here, though; why should the ACPI setting prevent the computer from shutting down?
Paul
In my experience the shutdown from the various GUI choices are problematic, intermittant and not reliable. Using as root from a terminal session: shutdown -y -g0 -i0 always works for me.
Since when does SUSE accept the Solaris command options? According to the man page (and the usage message) SUSE still uses the traditional shutdown -h now style to call. (Which is actually better, IMHO; if I want to switch to another init level, I can use telinit and maybe shutdown -k before.) Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2007-01-12 at 11:05 +0100, Joachim Schrod wrote:
Robert Lewis wrote:
Paul Abrahams wrote: In my experience the shutdown from the various GUI choices are problematic, intermittant and not reliable. Using as root from a terminal session: shutdown -y -g0 -i0 always works for me.
Since when does SUSE accept the Solaris command options?
According to the man page (and the usage message) SUSE still uses the traditional shutdown -h now style to call. (Which is actually better, IMHO; if I want to switch to another init level, I can use telinit and maybe shutdown -k before.)
Why not just use init 0 to shutdown (init 6 to reboot)? Seems much easier to me. pc5:~ # ll /sbin/telinit lrwxrwxrwx 1 root root 4 2005-12-22 11:16 /sbin/telinit -> init telinit is just a link to init. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joachim Schrod wrote:
Robert Lewis wrote:
Paul Abrahams wrote:
On Tuesday 09 January 2007 1:28 pm, Paul Abrahams wrote:
When I attempt to shut down my 10.2 system from KDE, the shutdown process stops when it's almost done. I get to runlevel 0, and then get these messages:
Failed services in runlevel 0: lm_sensors webmin Skipped services in runlevel 0: Susefirewall2_setup
And then the computer just sits there. The only way to stop it is with the power-off button.
The problem started after I turned off ACPI in the BIOS, though I didn't immediately realize that. Turning ACPI back on restored the correct shutdown behavior. There still might be a bug lurking here, though; why should the ACPI setting prevent the computer from shutting down?
Paul
In my experience the shutdown from the various GUI choices are problematic, intermittant and not reliable. Using as root from a terminal session: shutdown -y -g0 -i0 always works for me.
Since when does SUSE accept the Solaris command options?
According to the man page (and the usage message) SUSE still uses the traditional shutdown -h now style to call. (Which is actually better, IMHO; if I want to switch to another init level, I can use telinit and maybe shutdown -k before.)
Cheers, Joachim
What I was hoping for was a more direct response to why these icons for shutdown are intermittant. The shutdown command as I typed it predated Solaris and came from AT&T as early as System 3, Shutdown is better to use than init because it had more flexability and isn't as abrupt as init. I guess init 0 is ok if your the only (ab)user of the system. Meanwhile, back at the ranch, how about a little support from you guys for the concept of getting the GUI based shutdown to work reliably? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 12 January 2007 16:22, Robert Lewis wrote:
Meanwhile, back at the ranch, how about a little support from you guys for the concept of getting the GUI based shutdown to work reliably?
At least in KDE, the GUI shutdown won't shut down the system if there are programs that refuse to exit. For example if you have a program that pops up a window asking if you're sure you want to quit (eg. konversation) KDE won't exit, and the box won't shut down. Sometimes the programs refusing to exit may be in the background so it's not immediately obvious what's happening, so it can appear haphazard, but nearly always, the problem is with some other program and not actually KDE's shutdown itself Could that match what you're seeing? If not, you're going to have to be more specific -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Friday 12 January 2007 16:22, Robert Lewis wrote:
Meanwhile, back at the ranch, how about a little support from you guys for the concept of getting the GUI based shutdown to work reliably?
At least in KDE, the GUI shutdown won't shut down the system if there are programs that refuse to exit. For example if you have a program that pops up a window asking if you're sure you want to quit (eg. konversation) KDE won't exit, and the box won't shut down. Sometimes the programs refusing to exit may be in the background so it's not immediately obvious what's happening, so it can appear haphazard, but nearly always, the problem is with some other program and not actually KDE's shutdown itself
Could that match what you're seeing? If not, you're going to have to be more specific
I believe you have hit the nail on the head. Sometimes I see a few open applications go away and then the shutdown process just stops. As an experiment I will try to close down all applications and try this. I would bet that will work. I still think this is buggy though. Why can't the behavior be the same as the command like? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anders Johansson -
Joachim Schrod -
Kenneth Schneider -
Paul Abrahams -
Randall R Schulz -
Robert Lewis