F22 unusable - system freezes on login

Matthew Woehlke mwoehlke.floss at gmail.com
Fri Jun 19 20:13:53 UTC 2015


On 2015-06-19 15:10, Joe Zeff wrote:
> On 06/19/2015 11:26 AM, Matthew Woehlke wrote:
>> On 2015-06-18 17:47, Joe Zeff wrote:
>>> >There should also be a ~/.xsession-errors.old and with luck, it
>>> >might have something in it.
>> There isn't. (I'd be inclined to suspect that things have only gotten to
>> the point where a .xsession-errors would be created the one time.)
> 
> Interesting.  My guess is that there's a three step process here: delete
> .xsession-errors.old, move .xsession-errors to .xsession-errors.old,
> create a new version of .xsession-errors, one right after the other.

Probably, but...

> Having no .old file makes it look like it crashed between steps one and
> two, which seems improbable.  I do wish I knew what that meant!

...my guess is that once and only once has it even gotten to step 1.
Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh,
*not at all*. No login --> never even tries to start X (not as my user,
anyway).

I'm increasingly unconvinced that it has anything whatsoever to do with
X. More like it can't start a login session. I'd guess that recovery
mode does something that's just a bit different, as that is the *only*
way I can get to a usable environment of any kind.

(Hrm... on that note, it's interesting to note that the one and only GUI
program I was able to try to run is Konsole... which tries to start a
new pty and shell session immediately, i.e. isn't entirely unlike
logging in a second time. I'd *almost* say it's starting the shell
that's the trouble, except I'm not sure why that would work in emergency
mode but not otherwise.)

-- 
Matthew



More information about the users mailing list