Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
PC boots to runlevel 5 - I can log into the GUI sucessfully, and can drop to runlevel 3 (to save resources for running Daemons/ftp/etc) by entering init 3 at the command line.
However, when I try to go back to runlevel 5 (by entering init 5 at the command prompt) the computer loads the GUI login box and allows me to complete the GUI login again, but hangs immediatly thereafter at a blank blue (graphical) screen.... what you would see just before the KDE loading window appears. restarting the X server (cntrl+alt+backspace) takes me back to a frozen command prompt.
Am I going about changing runlevels the wrong way? If not, what logs should I check / where should I begin the troubleshooting process?
Distribution: Red Hat, Fedora, Yellow Dog, Debian, FreeBSD, Embedix
Posts: 106
Rep:
Quote:
Originally posted by t3___ my box does not have an xlog.txt file???
It won't have one until you execute startx like I suggested in prior post
Code:
startx > xlog.txt 2>&1
this launches X and saves any messages it generates, including potential error messages in xlog.txt file. The name is arbitrary, could use why_my_stpd_x_wont_boot if you like
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.