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.
Whenever I try to start gdm and/or X, it keeps restarting in an infinite loop. Not sure if it's X or gdm that's crashing.
This all started after I ran alsaconf as root from the console. It somehow hosed the permissions of roots home dir, and /home as well. I tried chmoding these back to 700 and 755 to no avail. The permissions, are just all out of whack, and I'm not sure what they're supposed to be.
Can someone please help? I am running TinyMe (a pclos remaster)
It never makes it to the login screen. It tries to initially load gdm, and then just restarts over and over.
The only thing it says in .xsession-errors is something like...
s2u: cookies for :0 = '<some long uid>'
The application 's2u' lost its connection to the display :0.0;
most likely the X server was shut down or your killed/destroyed the application.
Try to find your xorg log files and look for lines with EE on them. These are fatal errors and should give you some more information which should make it possible to diagnose the problem.
Where the xorg logfile goes varies from distro to distro. Typical locations include /var/log and the name might include xorg or x11.
I looked in /var/log and found a bunch of numbered Xorg.log files, so I did a 'cat Xorg*.log | grep EE' and the only thing I saw was something saying "module AIGXL not loaded", or words to that effect.
I think this has to do with permissions, cause this only started after I tried to fix the screwed up permissions that alsaconf left me with.
It might be that the driver you are using does not support AIGLX, but it is requested.
Edit your /etc/X11/xorg.conf file (again, I'm not 100% sure if this is the right location on pclos) and look for a line which looks something like this:
Code:
Option "AIGLX" "true"
Comment out that line by putting a # at the start of the line.
Do you get the login screen but get kicked out when you try to log in?
I do yes - it just started happening.
Root logs-in, but no other users can.
All I have done since I last successfully logged-in was mess around with the sound devices in KDE to try and get avidemux to work with audio...
Any ideas where to go next?
EDIT: I started the system in runlevel 3 and logged in successfully as a non-root user. When I then tried to 'startx', I received an X error message saying:
"Call to lnusertemp failed (temporary directories full?). Check your installation."
What should I do to remedy this?
Last edited by __spc__; 08-28-2008 at 02:58 AM.
Reason: More info
It seem, with 'df' I had indeed run out of disk space - it just took me an age to find a file hiding in /home/USER/.local/share/Trash/files/ that was 9GB (an AVI rip).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.