Bugzilla – Bug 146137
SuSE 10.0 reboot or shutdown failure from KDE
Last modified: 2006-02-09 11:44:54 UTC
If any apps are open while trying to shutdown or reboot from within KDE, it will fail, sometimes even with just konqueror running. If multiple attempts are made, the system can lockup completely and file corruptions have actually occurred. I have this on two Athlon systems. Logout --> Turn off system/reboot --> nothing happens. Have a second try and it may hang needing a hard reset. CTRL-ALT-F1 after it does nothing, login, reboot/shutdown and it's OK. Shutdown all apps in KDE and shutdown/reboot works every time. 10.0 + YOU 2 days ago. Problem from 10.0 fresh install on one system and 9.3 -> 10.0 upgrade on the other.
I just had a similar issue on 10.1 beta1 - but because of several previous problems (kernel bug, Yast (running SuSEconfig) hanging, load > 9, but no CPU activity) I am not sure if it is KDE-related in my case.
please attach /var/log/messages and /var/log/Xorg.0.log* after trying it again.
Created attachment 65554 [details] messge log The effect is a load of commits and removals by reiserfs when system rebooted, even after ALT-SYSRQ-S/U/B sequence.
Created attachment 65555 [details] Xorg.0.log
This box has KDE-3.5.0, the other one has the 10.0 distro version of KDE. On both, the only ways to get a successful shutdown/reboot 1. CTRL-ALT-F1, init 3, reboot or halt 2. Close all the apps running in KDE, then KDE Logout followed by selecting reboot or shutdown. On my x86_64 laptop (third box), with all apps up, did a Logout/reboot, the hard drive activity light showed for about 30 seconds, runlevel still shows N 5 and just Skype closed down, second try 3 minutes later, hard disk activity, then it stays the same N 5, everything is still running. Closed YaST and it now reboots cleanly, no file commits or removals. On the other boxes, YaST was never running and sometimes I'd have to close konqueror as well. Later today I shall have to try on the P-II 333 laptop (10.1beta1) with fvwm.
Just a clue: This could have todo something with the power-management or ACPI. Try booting with ACPI=off and check if it still does not work.
*** Bug 147971 has been marked as a duplicate of this bug. ***
Sid: Please look into this, this might be an important thing to fix.
Unfortunately the 64-bit laptop I have running at present won't boot with acpi=off. The P-II/333 laptop running openbox reboots without problems and the Athlon 32-bit box is currently being upgraded to 10.1Beta3.
Sid: Please check if it does still occurr with beta3. KDE-Maintainers: Is this a known issue? Any suggestions?
It looks fixed in 10.1 Beta3. The upgrade wiped skype, I shall reinstall skype and test as one of the symptoms was that it would only close skype and stop, though the problem was there without skype running.
Please reopen this if the bug still occurrs with a later version.