The Tuesday 2005-04-26 at 23:33 +0200, Anders Johansson wrote:
Is it really hanging hard? If you do a 'ps aux', what does the suseplugger process look like?
cer 8615 0.1 1.0 23092 8328 ? S 11:31 0:00 suseplugger --quiet cer 8649 1.8 2.1 28984 16504 ? S 11:31 0:02 \_ suseplugger --quiet cer 8617 0.1 0.9 21760 7596 ? S 11:31 0:00 susewatcher --quiet cer 8650 0.0 1.0 21760 8020 ? S 11:31 0:00 \_ susewatcher --quiet cer 8652 0.1 0.9 21920 7556 ? S 11:31 0:00 \_ /opt/kde3/bin/kdeinit --suicide cer 8662 0.0 1.0 21920 8448 ? Ss 11:31 0:00 \_ kdeinit Starting up... cer 8695 0.0 1.2 22608 9472 ? S 11:31 0:00 \_ klauncher [kdeinit] klauncher cer 8726 0.0 1.1 22060 8704 ? S 11:31 0:00 \_ kded [kdeinit] kded cer 8732 0.2 1.5 25980 11892 ? S 11:31 0:00 \_ kded [kdeinit] kded The window is empty, does not even redraw its gray emptiness (if I click the window menu (minimize, maximize, etc) it stays there). If I tell it to close clicking the "X" at the right-top corner, it doesn't, till gnome forces quit it. My 9.3 system is fully updated. I can "kill -9" process 8732, and both suseplugger and susewatcher dies. Good! Now, I don't want them to ever start again. How? I'm using gnome, I don't want kde there. I don't want those automatisms, thankyou.
Have you tried it in KDE? Do you see the same behaviour there?
I tried to start another session with kde, with the command: startx kde -- :1 on a tty, and it hangs. No session, only a "starting desktop" or similar message, then a gray emptiness with an "X" mouse cursor. It worked fine in 9.1 -- Cheers, Carlos Robinson