Now xorg-1.16.2.901 does not work with slim display manager
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. The log from a failed attempt shows that the video and input drivers (intel and evdev) are loaded, and the keyboard and mouse recognised. Then I get repeated error messages like this: [ 13198.518] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.NoServer (Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused) [ 13208.528] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.NoServer (Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused) 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 xorg thinks it's running on a systemd system (that stuff creeps into everything nowadays!) It's true that the socket referred to doesn't exist - I checked for it under /var/run. But launching a dbus daemon before starting slim doesn't make any difference. And why is it needed anyway? -- H Russman
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
On Thu, Dec 11, 2014 at 6:06 AM, Juergen Daubert <jue@jue.li> wrote:
Obviously configure's autodetection doesn't work properly and builds the xorg-server with systemd-logind enabled even if no systemd is installed.
And they wonder why there is such a divide over this. Seriously.
I've committed a new release of our xorg-server port which explicit disables systemd-logind.
Good work :) cheers James James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au
participants (3)
-
Googlemail
-
James Mills
-
Juergen Daubert