I have a recurring problem with some Gnome programs running in KDE (such as Galeon and Grip). It seems that if they crash, my PC freezes up, and every subsequent time that I log on with the same username. I am inexperienced with Linux, and so my my only remedy has been to delete the username and set up a new username for myself. This is tedious, since I have to save and move all of my files, then change the permissions to the new user. The problem seems to be that there are some runaway programs are trying to initiate in the background. Is there any way around this? Can I edit the user profile to not initiate these programs? Any help would be appreciated. ____________________________________________________________ Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! http://login.mail.lycos.com/r/referral?aid=27005
On December 31, 2003 12:57, Peter Fasi wrote:
I have a recurring problem with some Gnome programs running in KDE (such as Galeon and Grip). It seems that if they crash, my PC freezes up, and every subsequent time that I log on with the same username. I am inexperienced with Linux, and so my my only remedy has been to delete the username and set up a new username for myself. This is tedious, since I have to save and move all of my files, then change the permissions to the new user.
That's a little extreme. Run KDE System Guard or another, similar program that lets you view the processes that are running. Then kill the ones that hang. If your KDE session is completely frozen, then try [Ctrl][Alt][F1] to get to a console session. From there, you can login (as yourself or as root) and use command-line tools to check and kill processes. Then go back to your KDE session [Ctrl][Alt][F7] which should still be running, now without runaway or hung processes. If you prefer to work in a GUI environment, then when you get the F1 console session, login and type: startx -- :1 That's "startx" followed by a space, followed by two dashes, followed by another space, followed by a colon and the number of the new X-session that you wish to start. Your old, frozen session was probably on X-session "0" (that's zero). The new one is X-session 1. You can move back and forth between separate local X sessions by typing [Ctrl][Alt][F7], [Ctrl][Alt][F8] and so on. Hope that helps. Of course, if your entire system is frozen, then the above won't be much help. However, if you only ever run GUI, then a frozen KDE session on X looks a lot like a frozen system. Either way, it'll be good to find out. That information would bring you to the next step in finding out what's wrong. /kevin
participants (2)
-
elefino
-
Peter Fasi