You are not logged in.

#1 2012-09-09 03:35:09

Xavion
Member
From: Australia
Registered: 2010-03-13
Posts: 41

GDM crashes on startup after booting my machine via 'systemd'

For some strange reason, GDM only launches correctly if I booted my system via 'sysvinit'.  Whenever I boot the machine with 'systemd', GDM just displays an error and I can't understand why.

After a delay of about half a minute, I get the dreaded "Oh no! Something has gone wrong" message in the latter case.  Here are the GDM logs generated after booting via 'sysvinit' and 'systemd'.

Does anyone know what's likely to be causing this problem and how it can be fixed?  I think it's related to one I've been having with GTK+ applications on my Arch systems for the last few years.

In that case, even after booting via 'sysvinit', GTK+ applications take about half a minute to load after every second time I've logged-in via any of the available display managers (e.g. GDM, KDM, ...).

Offline

#2 2012-09-10 03:15:17

Xavion
Member
From: Australia
Registered: 2010-03-13
Posts: 41

Re: GDM crashes on startup after booting my machine via 'systemd'

The GDM problem was caused by "/var/tmp/" being a symbolic link to "/tmp/" on my Arch systems.  After removing said symlink and reinstalling the 'filesystem' package, GDM and some other services started correctly.

This breakthrough was a major relief, as I'm definitely wanting to boot via 'systemd' by default from now on!  For the benefit of other affected users, I've added this information to the 'systemd' webpage on the ArchWiki.

Offline

Board footer

Powered by FluxBB