Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Bit of an annoying problem on my laptop since I upgraded to Kubuntu Gutsy - on bootup I get a black screen and have to drop to a console after 5 minutes of blankness. If I startx I get an error message saying X is already started and a /tmp lock file created. If I delete this lock file I can start X... so why doesn't it start properly on startup?
No error message of note appears on the console screen and ctrl-alt-F7 sends me back to a blank screen if I don't restart X.
~/.xsession-errors doesn't enlighten me much. It doesn't get updated until after I startx either.
Bit of an annoying problem on my laptop since I upgraded to Kubuntu Gutsy - on bootup I get a black screen and have to drop to a console after 5 minutes of blankness. If I startx I get an error message saying X is already started and a /tmp lock file created. If I delete this lock file I can start X... so why doesn't it start properly on startup?
Maybe the problem is that the lock file is not being deleted when X shuts down. You could shut down your system and use a live CD to see if the lock file was deleted during shutdown.
The ~/.xsession-errors is only updated if you start the X server as a user. If the system starts the X server as part of the switch to a certain run level, it will be logged in the system log files (not sure on Kubuntu, but Fedora is /var/log/Xorg.0.log). I'm guessing X is starting, it just isn't launching your login window or something. You may also want to look at the gdm log (once again, on Fedora /var/log/gdm/:0.log).
Nothing untoward in the Xorg.log and the kdm.log is empty. No gdm log or folder in my var.
When I boot up and fall back to the console I can never see the lock file. It only seems to appear once I try to run startx.
Is there some way of deleting kdm's settings and starting again?
Uy! I solved the problem somehow the last time (probably a reformat) and have forgotten how. Just updated to Hardy Heron and have exactly the same problem again. Christ, I hate these half-assed releases!
Again, if anyone has a tip this time apart from reformatting, I'm all ears
I'm sorry, I don't get it. I booted up, dropped to console, logged in, ran those three commands you gave me and ended up at a console login screen. There didn't seem to be much else to do after that, apart from login again...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.