On Apr 23, 2013 7:40 AM, "Tomasz Kowalski" <[email protected]> wrote: > > I have the same problem. All I can say at the moment is that > slim+fvwm work for me as a stop-gap solution. I suspect the problem has > to do with infinality (or with fonts, at any rate), but I can't be any > more specific. Anyway, here's what "worked for me": > (1) During the boot sequence, before gdm hangs, switch to a tty<#n> via
No, this won't work for me, unfortunately. I don't get to GDM, in fact I don't even get to a point where I have any tty to switch to :-( I'll see if I can get some logs out once I have another way to boot. > ctrl-alt-F<#n> > (2) Login as root > (3) Disable gdm (#> systemctl disable gdm.service) > (4) Enable slim (#> systemctl enable slim.service) > (5) In ~/.xinitrc replace "exec gnome-session" with "exec fvwm" > > There are a few obvious alternatives available, such as booting from > another media, mounting the filesystem and then doing (3) - (5) > manually, possibly with different login/window managers. > > Cheers, > > T. > > > > > > > On Tue, 2013-04-23 at 13:54 +1000, Dean Thomson wrote: > > Probably best bet is to post this in the forum with any relevent systemd > > logs. > > > > On 23/04/13 13:53, Magnus Therning wrote: > > > Hi, > > > > > > I performed a large-ish update yesterday, gnome 3.8, linux kernel and a few > > > other bits and bobs, which left my computer in an unbootable state. I still > > > haven't any more details on why since I've left my other boot option at > > > work. All I see is that the kernel boots and systemd is started but never > > > progresses to a login prompt or GDM. I also don't get any of the virtual > > > terminals. > > > > > > Maybe this is enough for someone to point me in a direction for solving it. > > > If it isn't ill get back with more details this evening when I have some > > > other mean of booting the system. > > > > > > /M > > > >
