Version: (using KDE KDE 3.2.1) Installed from: SuSE RPMs Compiler: gcc 3.2.2 OS: Linux kde 3.2.0 and 3.2.1 Suse 8.1 and Suse 8.2 when logging out, I get sometimes a screen freeze. I got some useful hints, such as from Mario: ---start quote To prevent this problem at logout, add TerminateServer=false in the [X-*-Core] section of /etc/opt/kde3/share/config/kdm/kdmrc. ---end quote However, this is not helping at all, it is definitely not a driver/XFree problem. What is really happening: -> change in the control center some settings concerning colours, background or whatever. -> log out -> screen freeze / crash If i am logged in as root, my root reiserfs partition is corrupted, and if I am logged in as user, the user reiserfs partition is corrupted due to the necessary reset ! As long as you do not to change any settings, the screen frees does not show up. It seems (with my limited knowledge) that KDE is trying to write some configuration files at logout which makes the system going out for lunch.
it must read TerminateServer=true. false is the default.
both TerminateServer=true and false do not change the behaviour.
just to make sure ... you dont have a TerminateServer=false entry in some other section? independently from that, this _is_ a driver problem, or even a kernel problem. no user-space program without hardware access can cause such damage. check your RAM, just in case.
There is only one TerminateServer entry. Ok, you are the experts, if you think that it is a driver problem... Concerned boxes (Suse 8.1): SuSE kernel 2.4.21, ATI XFree 4.2.0 SuSS kernel 2.4.19, ATI XFree 4.3.0 SuSE kernel 2.4.19, Nvidia XFree 4.2.0 self compiled kernel 2.4.25, Nvidia prop. driver XFree 4.2.0 self compiled kernel 2.6.3, Nvidia prop. driver XFree 4.2.0 SuSE kernel 2.4.19, Nvidia prop. driver XFree 4.2.0 Since so many different configurations are concerned, I thought it is a problem of the (Suse ?) KDE scripts. Because it happens only if I chance specific settings in the KDE control center, both 3.2.0 and 3.2.1. And, it is not limited to SuSE 8.1, as other people mailed on the suse-kde list. I never had such a behaviour, back to KDE 2.x, where I started with linux. If you need further information, please contact me... Hopefully we get this resolved.
does http://portal.suse.com/sdb/en/2003/10/pohletz_desktop_90.html sound familiar?
hmm, I just checked. I do not have that desktop entry as kernel parameter, so it does not apply. But thanks for the hint. I just got a mail saying that reiserfs could be the problem. Indeed I upgraded the SuSE reiserfs package due to kernel 2.6.3. I will downgrade and check this.
ok, convinced. Seems to be a "driver" problem. I replaced a reiserfs partition by xfs and: the locking does not show up again. So I will change now step by step all user partitions to xfs and let the users play with kde 3.2.1. They are the best testers. If the locking does not show up again, it was indeed the reiserfs (on the kernels 2.4.19, 2.4.21, 2.4.25 and 2.6.3). keep you informed...
ok, NOTMYPROBLEM until further notice. :)
I am afraid, I have to re-open the bug... Ok, the screen freezes are going down to nearly zero, but: it still happens (sometimes). Coming to the facts: root is reiserfs (still on some machines, sorry), /home is XFS. Logged out from KDE as root -> screen freeze, forget about it, reiserfs. BUT: reboot, log-in as user and: Personal setting are gone (keramik, language settings, the bottom line, where the clock and the kde menue is located - called kicker? - has the original settings). However, screen saver and desktop background are kept. What is KDE, when looging out as root, writing to my user's /home/udo/.kde settings? Maybe this information may help tracking down the freeze mechanism ?
i'm still convinced that this is NOTMYPROBLEM. you can check the usual log files (~/.xsession-errors _before_ you start the next session, /var/log/kdm.log, any other files in /var/log/ mentioning kdm), but i'm almost sure that you won't find anything useful (except some kernel problems, maybe). "something" is causing your system to corrupt the file system and to freeze the system hard - kde/kdm has no power to do such a thing and has no way to prevent/fix it.
Yes, you are absolutely right. I traced down the bug and it is not only reiserfs, it is a problem alsa/arts which makes the freeze. After many tests it is now resolved.
*** Bug 78826 has been marked as a duplicate of this bug. ***
Hi Udo! I have the same problem. I read on the suse mailing list that executing "sync" just before logout circumvents this problem (http://lists.suse.com/archive/suse-kde/2004-Sep/0077.html) This works for me, but it's really incovenient to do this before each single logout. You said that alsa/arts is also involved in this system freeze. How did you resolve this problem? Arne
no way to properly shutdown with kdm (KDE 4.2.0 on test) through the kdm logging window ; now I end up with a black screen but nothing happens untill I hit again Ctrl+Alt+Suppr. Good news : now the music is back at first KDE logging session. Regards.
Oh man, a post after 5 years ... didn't know that I was on this KDE bugs thing ...