UbuntuThis forum is for the discussion of Ubuntu Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've just downloaded the "hoary hedgehog" beta and installed it on my old IBM 600X laptop. I used "warty warthog" on it for a while (a few months) without this problem.
I've tried deleting (eventually all) the config files and dirs from my home directory, but it does the same thing... just after the brown background appears, the disk stops chugging and the mouse cursor is all that's displayed. The cursor works, but that's it.
I've tried manually killing off my processes, by using the text vtty login on ctrl-alt-f1, but none of the processes individually seem to be the cause of the hangup. The only thing that makes any difference is killing X itself, which is kind-of counter productive ;-)
X-Window isn't crashing as far as I can tell, because it stays running, consuming practically no cpu. There are no errors shown in /var/log/Xorg.log.
Anyone got any ideas what might be choking? My bet is something Gnome related, but I'm more familiar with KDE, and Gnome has changed a lot since I last used it heavily (C 1999). Next step is to put debugging echoes into startx, I guess!!
-cybervegan (Ubuntu, but not Linux newbie)
No, not yet - really busy lately, no time to play ;-(
As I'm not that familiar with the debian system layout, and I can't remember exactly what I did, all I can really say is this: I think I used the quick'n'dirty, underhanded method of renaming esd to something else, and letting it silently fail...
"Root shell" under "applications/system tools"
find / -name esd # to find where it's hiding
mv <directory path from find>/esd <directory path from find>/esd.disabled # fill in the path from what find told you
Just in case you don't know, the stuff after the #'s is just my rambling - don't type it(not trying to teach grandma to suck eggs).
Note that this is not really a fix, just a kludge, and those better versed in deb/ubuntu should be able to tell you a better way - one that gives you sound, too, hopefully!