------------------------------

Message: 2 Date: Wed, 10 Dec 2014 21:06:14 +0100 From: Juergen Daubert <jue@jue.li> Subject: Re: Now xorg-1.16.2.901 does not work with slim display manager To: crux@lists.crux.nu Message-ID: <20141210200614.GA31308@jue.netz> Content-Type: text/plain; charset=us-ascii

On Wed, Dec 10, 2014 at 04:13:36PM +0000, Googlemail wrote:

...

I've just upgraded the xorg-server and I find I can't start it via slim. Sometimes I get a blank screen, sometimes I just stay in the console. I can get X up by using startx. It starts on the same console and appears to work normally.

[...]

...

and right at the end: [ 13258.578] (EE) systemd-logind: failed to get session: The name org.freedesktop.login1 was not provided by any .service files

Obviously configure's autodetection doesn't work properly and builds the xorg-server with systemd-logind enabled even if no systemd is installed.

I've committed a new release of our xorg-server port which explicit disables systemd-logind.

HTH and best regards Juergen

I've done some more work on this and there are in fact two separate problems. The error messages were due to a stale dbus socket in /var/run. If I deleted this, launched dbus (which I don't usually have running) and *then* restarted slim, the messages disappeared. But these messages turn out not to be fatal. The real problem must lie elsewhere, because the slim login screen comes up normally when I start with a fresh boot, but not when I use "slim restart" as I did yesterday. In that case, there is a black screen for a very long time and then suddenly the login window appears. I timed it this morning and it took all of three minutes! What could cause that? ------------------------------ Hazel Russman <hazeldebian@gmail.com>