You are not logged in.
I just installed arch a few days ago (not on my main machine), and I was trying to get SLiM to play nice when I ran into this issue, from /var/log/slim.log:
slim: waiting for X server to begin accepting connections.
slim: open_session: Unable to open session: Message did not receive a reply (timeout by message bus)
I checked that dbus is running, and it's in my rc.conf daemons array. To follow are my rc.conf, inittab, and .xinitrc. Fluxbox starts fine with startx, so I'm not sure where to go from here (and yes, I've looked at other forum posts for hours now).
EDIT: dbus 1.6.8-1, slim 1.3.4-3. I also forgot to mention that the same exact setup is running perfectly fine on my main machine (arch, slim, fluxbox)
/etc/rc.conf:
DAEMONS=(syslog-ng dbus wicd !network crond alsa)
#HARDWARECLOCK="UTC"
# Storage
#
# USEDMRAID="no"
# USELVM="no"
# Network
#
# interface=
# address=
# netmask=
# gateway=
/etc/inittab:
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
#c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
x:5:respawn:/usr/bin/slim >/dev/null 2>&1
# End of file
/home/user/.xinitrc (executable):
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
#cairo-compmgr &
#xset -b
#{ sleep 2 && ~/.conky_start.sh; } &
#{ sleep 2 && eval $(cat ~/.fehbg); } &
#{ sleep 2 && tint2; } &
#{ sleep 2 && wicd-client -t; } &
#dbus-launch startfluxbox
#exec ck-launch-session gnome-session
exec startfluxbox
Last edited by FugitivePlatypus (2012-10-21 05:00:38)
Offline
Try adding "dbus-launch" to your ~/.xinitrc:
[...]
exec dbus-launch startfluxbox
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
That doesn't really change anything, still the same error from slim and startx still works.
Offline
A bit off-topic I am sorry but I just noticed that you have disabled the first getty in your inittab setup which isn't something wise to do as far as I know. Might be even related to your problem?
\(o_X)/
'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols
Offline
I disabled it so that I could still see output from the boot, cause a while back I had an error appear on another machine, and as far as i could find no log had that specific information. I can definitely change it if that causes problems though.
Offline
As of the most recent update, this is magically fixed 0.o
Offline