SuSE freezes after KDE login.
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing! This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI 3) After some time I issue a "telinit 3" command and the machine goes to runlevel 3 (I switch the GUI off to free up RAM usage) 4) Wanting to use the GUI again I issue a "telinit 5", the login dialog box appears, I log in as a user and the machine completely freezes - everything stops. I use the computer as a webserver. When I work on the server I usually issue commands via WEBMIN. Does anyone have any idea what I can do to fix the problem? Regards, Dan
On Mon, 2005-01-31 at 08:21, Dan wrote:
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing!
This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI
Instead of issuing init5 use startx instead.
3) After some time I issue a "telinit 3" command and the machine goes to runlevel 3 (I switch the GUI off to free up RAM usage) 4) Wanting to use the GUI again I issue a "telinit 5", the login dialog box appears, I log in as a user and the machine completely freezes - everything stops.
I use the computer as a webserver. When I work on the server I usually issue commands via WEBMIN.
Does anyone have any idea what I can do to fix the problem?
Regards, Dan -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-01-31 at 08:21, Dan wrote:
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing!
This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI
Instead of issuing init5 use startx instead.
Thanks. I will try that in the future. When I am in KDE and want to shut that down to free up memory, what should issue, telinit 3 ?
3) After some time I issue a "telinit 3" command and the machine goes to runlevel 3 (I switch the GUI off to free up RAM usage) 4) Wanting to use the GUI again I issue a "telinit 5", the login dialog box appears, I log in as a user and the machine completely freezes - everything stops.
I use the computer as a webserver. When I work on the server I usually issue commands via WEBMIN.
Does anyone have any idea what I can do to fix the problem?
Regards, Dan
On Mon, 31 Jan 2005 19:18:32 +0100, Dan
Ken Schneider wrote:
On Mon, 2005-01-31 at 08:21, Dan wrote:
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing!
This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI
Instead of issuing init5 use startx instead.
Thanks. I will try that in the future. When I am in KDE and want to shut that down to free up memory, what should issue, telinit 3 ?
Why not the other way. Always boot in runlevel 3. When you need KDE, login and startx. When you finish, just logout from the button. It will shut down KDE and bring you back in CLI. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
On Mon, 2005-01-31 at 13:18, Dan wrote:
Ken Schneider wrote:
On Mon, 2005-01-31 at 08:21, Dan wrote:
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing!
This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI
Instead of issuing init5 use startx instead.
Thanks. I will try that in the future. When I am in KDE and want to shut that down to free up memory, what should issue, telinit 3 ?
No, just log out and you will go back the original terminal window you used for startx. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-01-31 at 13:18, Dan wrote:
Ken Schneider wrote:
On Mon, 2005-01-31 at 08:21, Dan wrote:
Hi all. I have a strange problem with my SuSE 9.0 box. The problem happens now and then: When I log on as a user at the KDE login prompt, the login dialog box disappears and the system COMPLETELY freezes. All the services STOP and I can't get in contact with it, so the only thing I can do is power it off manually and reboot the machine which I don't like doing!
This doesn't happen everytime, but I have noticed that it happens after I have done the following: 1) the machine boots into runlevel 3 2) I issue a "telinit 5", log in to the GUI
Instead of issuing init5 use startx instead.
Thanks. I will try that in the future. When I am in KDE and want to shut that down to free up memory, what should issue, telinit 3 ?
No, just log out and you will go back the original terminal window you used for startx.
Thanks for all the feedback. I understand how it works now. :-) Regards, Dan
On Monday 31 January 2005 13:18, Dan wrote:
Ken Schneider wrote:
Instead of issuing init5 use startx instead.
Thanks. I will try that in the future. When I am in KDE and want to shut that down to free up memory, what should issue, telinit 3 ? This should do it. init 3 (or telinit 3) sets the system to run level 3. All the GUI processes should be stopped. Alternatively you can specify run level 3 when booting the system. This will boot into run level 3. You can use YaST/Hardware/Graphics Card and Monitor to set your system to boot in text mode, or simply edit /etc/inittab: # The default runlevel is defined here id:5:initdefault: ^ +-----> default run level Change the default run level to 3.
While in run level 3, you can easily run startx to bring up kde (or gnome).
One caveat with any GUI, is that the GUI likes to own the keyboard and
mouse. If it somehow hangs, you might have difficulty killing it, even
using ctrl-alt-backspace. Sometimes, I simply log in through my network
and kill the GUI.
If KDE always hangs on you, the problem could be your graphics card
configuration. Try to run sax2 (or YaST/Hardware/Graphics Card and Monitor)
to rewrite yourXF86Config file. Then test it via the startx command. You
can use startx to try GNOME also.
Also, if you are upgrading from an old version of KDE, your local
configuration may be messed up. I had that happen when I had a dual boot
KDE2 and KDE3 system. I just blew away my .kde directory and .kderc file..
--
Jerry Feldman
participants (4)
-
Dan -
Jerry Feldman -
Ken Schneider -
Sunny