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.
I interrupted a "make install" process that seemed to be taking longer than it should have. After rebooting the system I noticed that there was no longer a graphical login screen, just a big, blue, blank screen. I was able to log in using runlevel 2, but I just couldn't get that graphical login screen back, and, as a result, I couldn't get KDE to run at all. I must have messed up something in the runlevel that controls that initial login screen. Does anybody know how to repair this problem? Any help would be greatly appreciated.
I was compiling a program that required the source code in /usr/X11R6/include/X11. It's a rather large package (500 MB) that's used for research purposes in radiation therapy. I may have been logged in as root at the time I ran it, which worries me a bit. I apologize for my vague response, but that's really all I know about it. I'm unable to post any of the code since it's proprietary. It might actually not help anyway since I have no idea what part of the code may have caused the problem, and there's so much of it. I know that it works, though, since I installed it on a different computer running the same operating system.
Just a thought....
Have you tried recompiling from the command line and letting the make install go all the way through this time? Might "fix" itself once the whole package is in place. Dunno, but i'm hopin' for ya!
I did try that and it didn't work. I just backed-up my data and reinstalled SuSE 9.1 completely. That fixed the problem. Normally that would be too brute-force for my liking, but it wasn't a big deal since I had just installed the OS anyway, so I didn't have much to back up. From now on I'll be more careful when compiling something big while logged in as root!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.