SLiM fails to start xfce4 because of some weird dbus error

jawnah · 2012-06-28 17:58:06

I'm glad I found this thread. I installed Arch yesterday and have been driving myself nuts with the two issues reported in this thread: slim will not start my session properly and I also have a problem with the inability to control the power through the XFCE menu in a manually initiated session. In addition, based on what I've seen from other threads in the past, I believe my inability to use NetworkManager properly through nm-applet in XFCE may be related to these dbus permissions as it wouldn't show any devices. I had to switch to wicd temporarily.

jawnah · 2012-06-28 18:08:19

Downgrading dbus back to 1.4.20 seemed to resolve all 3 of my problems. There definitely appears to be a bug here. I switched back to NetworkManager and enabled slim and everything is playing together nicely now. Thanks again for all of the suggestions here.

parliament · 2012-09-08 04:59:03

I have this same problem. startx works fine, slim doesn't work (black X cursor) and gives that dbus error in the log. This is a new arch install so I can't downgrade

pincy · 2012-09-15 16:22:53

Anything new on this?
Today upgraded to slim 1.3.4-3 and still the only message in the log is:

slim: open_session: Unable to open session: Message did not receive a reply (timeout by message bus)

Running Dbus 1.6.4-1, Slim is started from inittab.

I'd like to use slim again

David Batson · 2012-09-16 02:26:31

Works fine here with XFCE. I just updated everything a couple of days ago. Same version of SLiM. Using a pure systemd environment as per the systemd wiki. Basically you have to set up everything according to the systemd wiki, including creating and enabling /etc/systemd/system/slim.service. You also need the other files in order as per the following post: https://bbs.archlinux.org/viewtopic.php … 6#p1017386

Note that inittab is not used in a pure systemd environment. You should also see the following with ck-list-sessions as a normal user. Note that active = TRUE.

$ ck-list-sessions
Session1:
	unix-user = '1000'
	realname = ''
	seat = 'Seat1'
	session-type = 'x11'
	active = TRUE
	x11-display = ':0.0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-09-16T02:12:06.211289Z'
	login-session-id = '1'

https://wiki.archlinux.org/index.php/Systemd

pincy · 2012-09-16 22:22:11

Thank you, starting slim with systemd works like a charm.

Arch Linux

#26 2012-06-28 17:58:06

Re: SLiM fails to start xfce4 because of some weird dbus error

#27 2012-06-28 18:08:19

Re: SLiM fails to start xfce4 because of some weird dbus error

#28 2012-09-08 04:59:03

Re: SLiM fails to start xfce4 because of some weird dbus error

#29 2012-09-15 16:22:53

Re: SLiM fails to start xfce4 because of some weird dbus error

#30 2012-09-16 02:26:31

Re: SLiM fails to start xfce4 because of some weird dbus error

#31 2012-09-16 22:22:11

Re: SLiM fails to start xfce4 because of some weird dbus error

Board footer