Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 compiled KDE 3.2 from scratch to repair some errors that happened when I installed via RPM. From the looks of it, it was successful (so far), except for the fact that my (improved) login screen won't log me in anywhere. If I put in the password it goes to a blank screen for a second like normal, and then instead of popping up KDE it just pops back up at the load screen. This also happens regardless of which WM I try to load.
I figure a start would be booting straight into the console temporarily. Is there a Grub command I can use to do that? Or is there another solution to the problem?
Firstly are you using KDM to login? If so, there's normally a menu somewhere to allow a console login. I think the keyboard command is Alt+N, otherwise you can always use Ctrl+Alt+Fn (n=1-6). I had problems with this recently, and I suggest you try the following two things:
1. Type "df" at the prompt to check your disk space. KDM won't login as a normal user if there's no free space
2. Try "ls -l /dev/null" and make sure it can be written to by normal users, otherwise dcopserver won't start (although this probably isn't the problem, since it should give you an error)
3. Try to logon, and when it fails, go to the command prompt, type "less /var/log/kdm.log" and post the output corresponding to the correct date (if it's not dated, just post the last complete section). Also post the output of /var/log/XFree.log (or whatever it's called)
It gives me a whole bunch of trash about not being able ot connect to the X server and more specifically, when I type startx I get a message saying that kdeinit could not be loaded (this shows up in the console as well). However, I'm able to log on as root? Blackbox isn't working either now...
I've got plenty of disk space, and that specific folder you pointed out was readable. Everything was fine until I installed KDE 3.2 so it'd have to be a KDE issue I would think....Unless KDE can screw around with X while it's installing?
If I type in startx I can get into KDE using any non-root profiles now, however KDM still won't load up anything via the X server. Here's the message I get when I just type kde:
xset: unable to open display ""
xsetroot: unable to open display ""
startkde: KDE starting...
ksplash: Cannot connect to X server
kdeinit: Aborting. $DISPLAY not set
warning: Connect ()failed: : no such file or directory
ksmserver: Cannot connect to X server
startkde: Shutting down...
Error: Can't contact kdeinit!
The $DISPLAY line peaks my interest...
Also, when I run KDE by typing start X I have no kicker. This is the error message I get in the konsole when I try to start it up manually:
Alright things are looking better. I went through and completely deleted KDE, figured out how to get into Blackbox, and built it from scratch right outta there. So now by doing startx out of any non-root user it works. BUuuuuuuuut ~ I still have the KDM problem. During bootup it won't boot into anything, just brings me right back to the login screen. How would I go about diagnosing that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.