| Summary: | X freezes when logging out of kde 3.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Felix Rodriguez <frodriguez> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.4_rc2 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Felix Rodriguez
2003-02-22 19:55:43 UTC
Do you use kdm? Do other DEs (gnome etc) work? Does restartig the X server (xtrl-alt-backspace) work? Try logging the output of startkde: start an X server, and from a vt run startkde. See what it tries to do last before X hangs. If the freeze means you can't switch back to the vt pipe its output to a file. I use only kdm. When it locked up again I hit ctrl-alt-bkspace and it popped me out of X to the first vt. I tried running startkde from the vt with and without X already running. In both instances X did not startup. startkde won't start the X server, you have to start it manually and export DISPLAY=0:0 before running startkde. Ok I think I know what's going on. X is not freezing. I'm just getting the gray screen when I logout of KDE instead of getting the kdm_greet screen or shutting down. KDE is not communicating with KDM on logout like it should. The only problem is it only happens occasionally. It doesn't happen all the time. Looks like kde doesn't cleanup well. Could it be that you run tmpreaper or some similar app? If so configure it to ignore the kde dirs, as without them kde cannot communicate well to itself and will display this kind of behaviour. Is this now fixed? No it is not fixed. I do not have anything such as tmpreaper running on my machine. It only happens occasionally. When it does happen I notice that there are two kdm processes still running and one of the kdm processes can't be killed even with a kill -9. Could it be that the kdm process is stuck in kernel mode and can't be killed. Ok. I think this bug can be closed now. I recreated my XF86Config file by running xf86cfg instead of xf86config. Now I have no problems on logout. I guess there was something wrong with the other configuration file. fixed for the reporter |