soon as logut shutdown or restart pressed
screen goes blank but the function works in few seconds.
no messaages.
power off happens
restart works but no indication if it is shutting down or what
what is missing?
end current session just goes blank and gets stuck.
then ctl alt del or hard reset
i use kdm4 for login.
kde3 installed.
suse-11.1 fully updated.
intel 845 vesa xorg
not sure if this will help you, but in /var you will find boot.omsg, its the log file of your previous boot (and shutdown), the boot part will end around:
Master Resource Control: previous runlevel: 5, switching to runlevel: 0
<notice>killproc: kill(3280,15)
then the shutdown will begin, similair to:
Shutting down service kdmdone
Shutting down service kdmdone
Shutting down cupsd<notice>killproc: kill(3288,15)
done
Shutting down mail service (Postfix)<notice>killproc: kill(3573,15)
done
maybe you can find some error or problem in this file ?
Master Resource Control: previous runlevel: 5, switching to runlevel: 6
<notice>Shutting down service kdmkillproc: kill(2027,15)
done
Shutting down CRON daemon<notice>killproc: kill(2546,15)
done
Shutting down smartd <notice>killproc: kill(2712,15)
done
Shutting down cupsd<notice>killproc: kill(2395,15)
done
Shutting down mail service (Postfix)<notice>killproc: kill(2506,15)
done
Shutting down the Firewall skipped
Shutting a11ydone
Shutting down auditd <notice>killproc: kill(2316,15)
done
Shutting down Avahi daemon done
Shutting down brlddone
Shutting down service kdmdone
Shutting down java.binfmt_misc done
/etc/init.d/kbd stopdone
<notice>checkproc: /usr/sbin/NetworkManager 2423
Shutting down the NetworkManager<notice>killproc: kill(2423,15)
Shutting down suse-blinuxdone
<notice>killproc: kill(1774,15)
Shutting down acpid done
<notice>killproc: kill(2807,15)
Shutting down SSH daemondone
<notice>killproc: kill(2414,15)
Saving random seeddone
Shutting down Name Service Cache Daemondone
done
Shutting down (remotefs) network interfaces:
Not stopping NFS client services:unused
Shutting down rpcbind <notice>killproc: kill(2082,15)
done
Shutting down syslog services<notice>killproc: kill(1755,15)
<notice>killproc: kill(1752,15)
done
done
<notice>killproc: kill(1822,15)
Shutting down HAL daemondone
Shutting down (localfs) network interfaces:
eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
doneShutting down service (localfs) network . . . . . . . . .done
Shutting down D-Bus daemon<notice>killproc: kill(1764,15)
nm-system-settings: disconnected from the system bus, exiting.
nm-system-settings: nm_sysconfig_settings_remove_connection: assertion `NM_IS_SYSCONFIG_SETTINGS (self)’ failed
done
<notice>killproc: kill(4701,3)
there it ends.
there is no indication where screen goes blank
it is supposed to show the shutdown splash and progress bar
I have a similar problem on shutdown. I get the same messages in the text console:
nm-system-setting: nm_sysconfig_settings_remove_connection: assertion ‘NM_IS_SYSCONFIG_SETTINGS (self)’ failed
I have to manually disconnect the power. The screen displays the splash logo. I am using openSUSE11.1 also openSUSE11.0 (which I am using now) and previously 10.3 on an Athlon 64 Compaq Presario 3200. 11 and 10.3 worked fine on this machine.
correct me if I am wrong, but the shutdown splash is only shown if you have th bootup splash and not removed it with esc (as far as I know)
my shutdown log is a little bit diffrent to yours, taking it from the HAL daemon:
Shutting down HAL daemon<notice>killproc: kill(2001,15)
done
<notice>killproc: kill(1814,15)
<notice>killproc: kill(1843,15)
acpid: exiting
<notice>killproc: kill(1873,15)
Shutting down acpid done
Shutting down resource managerdone
Shutting down ConsoleKitdone
Shutting down D-Bus daemon<notice>killproc: kill(1801,15)
done
Running /etc/init.d/halt.local
done<notice>killproc: kill(23805,3)
Sending all processes the TERM signal…
done
<notice>pidofproc: /sbin/blogd 23805
there is no mention of the nm-system-settings where yours seems to end. You seem to mis the halt.local and TERM signal, which might be the reason it just hangs, maybe because of nm-system-settings ? not sure I can be of any more help on this tough.
mmm…
iam having the same issue
how to solve it?
Do you have radeon graphics? If you do, uninstall fglrx driver and try to log out/login again. I had the sam problem, but when I removed fglrx driver everything was fine.