LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Login fails on 'std' session, works on 'failsafe' - how to fix? (https://www.linuxquestions.org/questions/linux-newbie-8/login-fails-on-std-session-works-on-failsafe-how-to-fix-728077/)

bjorke 05-23-2009 06:53 PM

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? :/

thanks
kb

jamescondron 05-23-2009 07:30 PM

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

bjorke 05-23-2009 08:50 PM

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
which is true, there's no such directory.

thx for the pointers,
kb

bjorke 05-26-2009 10:17 AM

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.

Robustness score so far: low :/


All times are GMT -5. The time now is 12:01 AM.