On Wednesday 11 May 2011 14:00:57 Anton Aylward wrote:
benefici@fastmail.fm said the following on 05/11/2011 05:28 AM:
My desktop PC (with openSUSE 11.4) does not shutdown completely at times.
This is happening to me as well, with a interesting variation. KDE4 is not saving the session on shut-down. I've tried logging out before shutting down; I've tried logging out, going to the text mode console. I go to 'init 3' and then I try unmounting the file systems one by one but find that KDE is still running.
I think this is different from my problem. KDE4 exits cleanly in my case. On the other hand, I have seen similar behaviour earlier and I believe it happened because I ran KDE4 applications in a KDE3 session. The KDE4 apps started kded4 which failed to exit on logging out. I had to manually kill kded4 with kill -9. I could see the stuck kded4 process after logging out with ps -fu $myuser I could not find a way around the problem so in the end gave up and removed all KDE3 packages. The problem does not occur in a clean KDE4 session.
I haven't seen lost files, but then I'm not saving large files as you are, Tom.
If I were, I'd start by checking the file systems - FSCK, free space. Free space might matter since a lack of it can cause problems with latency in allocation with some file systems that make use of fragmented blocks. I'd check logs. *ALWAYS* check logs! I'd see if its a problem with file closing or with file unmounting independently from the shutdown. Slice and dice and localise the problem. That's what I'm doing with my KDE4/sound problems.
Fsck runs without errors and free space does not seem to be a problem (more than 9 GB free on both of the file systems that are not umounted). Which logs should I check? There is hardly anything in /var/log/messages about a shutdown, and no errors at all even if the shutdown was incomplete (just checked the shutdown from yesterday evening). Are there any other logs? The problem clearly happens at shutdown time - some of the scripts are simply not executed. Unmounting manually works. Anyway, I find the behaviour of init quite stupid. If a file system was not successfully umounted then why still go on and power down the system? I think not even a sync is executed in such a case, based on the hundreds if not thousands of transactions to be replayed sometimes at next boot up. Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org