Login fails on 'std' session, works on 'failsafe' - how to fix?
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.
Login fails on 'std' session, works on 'failsafe' - how to fix?
My ubuntu 9.0.4 worked swell for a few days, then I got faield logins: a dialog saying I had installation problems or a full disk. Switching to either root-terminal or to a 'failsafe' session works fine, and my disk is not full (though for a short while last week, it was).
Looking at my .xsession-errors file:
Quote:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: line 73: ls: command not found
/etc/gdm/Xsession: Executing default failed, will try to run x-terminal-emulator
/etc/gdm/Xsession: line 205: exec: x-terminal-emulator: not found
which seems pretty whacked (no "/bin" or "/usr/bin" in the path? huh?)
Is there a single file I can whack, maybe a corrupted settings file? Or is it re-install time? :/
Not a dead helpful post- can you remember more or less exactly what the error was? If not, logs are saved in /var/log - if you can remember what errored specifically, see if it is in there.
If you have to, try to reproduce the error and give as many specifics as possible.
The second issue is bizarre, I remember some years ago this was in contention- though I'd have to look into exactly what it was, or even if it is relevant; its more a memory of seeing this before
The error was simply a dialog box, which appeared after I entered my name and pw, that announced that my session had lasted less than 10 seconds and that if I hadn't explicitly logged out, then either my disk was full or there was an installation error -- and it directed me to login using the failsafe session (which does work -- I'm logged-in that way right now). The "details" part of the dialogue contained the same text I've previously posted -- that is, the contents of ~/.xsession-errors
Looking at the timestamp of that file, and checking /var/log didn't show much though this one in daemon.log might be a hint:
Quote:
May 23 16:17:36 kupuna console-kit-daemon[2710]: WARNING: Couldn't read /proc/2709/environ: Failed to open file '/proc/2709/environ': No such file or directory
SO I just re-installed. It was a faster solution than trying to sort out why the Xsession was trying to aim at a non-existent directory, much less to fix it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.