F22 unusable - system freezes on login

Joe Zeff joe at zeff.us
Thu Jun 18 21:16:30 UTC 2015


On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
> Hmm... is it expected that there are no entries*at all*  for the last
> few boots? The only entries I have are for June 5. (And yes, my system
> date is correct: June 18.) Anyway, I have no idea what I'd be looking for.

If memory serves, most of the file system isn't mounted in single-user 
mode.  You can use this to mount everything once you've gotten to a 
command line:

mount -a

Once you've done that, you can go to your regular user's home directory:

cd /home/$USER

and examine the hidden file .xsession-errors to see if X even started, 
and why it crashed.  Just remember, you'll be running as root, so be 
very, very careful about deleting files.  (My preference when I have to 
do things like this is to rename them instead of deleting them, although 
it's easy to forget to clean up later.  Still, it's better than nuking 
something that you really, really needed.)


More information about the users mailing list