On 2015-06-18 14:04, Paul Cartwright wrote:
On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
> (ยน *Once and only once* I was able to log in, but the system froze as
> soon as I tried to run an application. Also, I can log in in single-user
> mode, but this isn't good for much but running dnf and fiddling with
> enabled services. I *have* applied all updates as of a few hours ago to
> no effect.)
do you have a choice of logins, like KDE/gnome??
maybe you didn't allow enough space for root..
Does "TTY" count? I'd be quite surprised if changing DE works when I
can't log in at a TTY either. It *might* be kdm, though I don't claim to
know how to change that.
BTW, 'systemctl start graphical.target' from single-user mode also kills
the system.
does # df -h
show enough space in root?
/ 108G
/boot 336M
/boot/efi 55M
/var 119G
/home 881G
New system, remember? There's nothing on it but the initial install
(modulo updates). I haven't even gotten to installing additional
software that I'll eventually want, because the system is unusable ATM.
if you can get in as single user you might look at journalctl to see
what happened when it locks up
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.
--
Matthew