[Solved] Openbox doesn't start properly via SLIM

Dethredic · 2012-07-26 14:24:02

The power went out at my house last night and turned off my computer for the first time in a couple months applying a bunch of updates.

My normal setup is that I start SLIM via /etc/inittab, which auto logs my user account in, which starts openbox via .xinitrc. Anyways, that's not what happened. I was greeted with a grey screen and a X as a cursor (its been a while but I think thats the default Openbox setup). I could move the cursor but no mouse clicks / keyboard keys did anything.

I figured that X failed to start properly and rebooted in run level 3, logged in then ran startx, and everything worked as expected. I have tried rebooting several times and always get the grey screen unless I boot into run level 3 and manually start X.

Here is my slim log file (there are a lot more entries like this):

Fatal server error:
Server is already active for display 0
	If this server is no longer running, remove /tmp/.X0-lock
	and start again.


Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 

1 XSELINUXs still allocated at reset
SCREEN: 0 objects of 280 bytes = 0 total bytes 0 private allocs
COLORMAP: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 96 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 120 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 112 bytes = 112 total bytes 0 private allocs
GC: 0 objects of 80 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 8 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 24 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 24 bytes = 0 total bytes 0 private allocs
PICTURE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 112 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 112 bytes = 112 total bytes 0 private allocs
GC: 0 objects of 80 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 8 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 24 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 24 bytes = 0 total bytes 0 private allocs
PICTURE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 112 bytes, 0 allocs
slim: open_session: Unable to open session: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
1 XSELINUXs still allocated at reset
SCREEN: 0 objects of 280 bytes = 0 total bytes 0 private allocs
COLORMAP: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 96 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 120 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 112 bytes = 112 total bytes 0 private allocs
GC: 0 objects of 80 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 8 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 24 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 24 bytes = 0 total bytes 0 private allocs
PICTURE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 112 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 112 bytes = 112 total bytes 0 private allocs
GC: 0 objects of 80 bytes = 0 total bytes 0 private allocs
CURSOR: 0 objects of 8 bytes = 0 total bytes 0 private allocs
CURSOR_BITS: 0 objects of 8 bytes = 0 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 24 bytes = 0 total bytes 0 private allocs
GLYPH: 0 objects of 24 bytes = 0 total bytes 0 private allocs
PICTURE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
SYNC_FENCE: 0 objects of 8 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 112 bytes, 0 allocs


slim: waiting for X server to begin accepting connections.
slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

slim: open_session: Unable to open session: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

Here are my relevant config files:

[phil@fml ~]$ cat /etc/inittab
#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)	Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

## Only one of the following two lines can be uncommented!
# 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 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux

# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 9600 ttyS0 linux

# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 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



[phil@fml ~]$ cat .xinitrc 
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

sudo mount --bind /media/music/ /home/phil/music/ &
sudo mount --bind /media/videos/ /home/phil/videos/ &
sudo mount --bind /media/pictures/ /home/phil/pictures/ &
xbindkeys &
exec openbox-session



[phil@fml ~]$ cat /etc/slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        /bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments -nolisten tcp vt07

# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/xauth 

# Xauth file for server
authfile           /var/run/slim.auth


# Activate numlock when slim starts. Valid values: on|off
# numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login ~/.xinitrc %session

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
# sessionstart_cmd	some command
# sessionstop_cmd	some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon	yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions            xfce4,icewm-session,wmaker,blackbox

# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      import -window root /slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host

# Session message. Prepended to the session name when pressing F1
# session_msg         Session: 

# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        phil

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password      no

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login          yes


# current theme, use comma separated list to specify a set to 
# randomly choose from
current_theme       default

# Lock file
lockfile            /var/lock/slim.lock

# Log file
logfile             /var/log/slim.log

Last edited by Dethredic (2012-07-26 19:43:59)

kalle97 · 2012-07-26 15:35:26

Can you also post your xinitrc and SLiM's config file? It's probably not that which is the prob but just in case.

Dethredic · 2012-07-26 15:38:02

kalle97 wrote:

Can you also post your xinitrc and SLiM's config file? It's probably not that which is the prob but just in case.

scroll down in the relevant config files paste

kalle97 · 2012-07-26 16:46:21

Aa, sorry, I'm on my phone and can't do so.

Jelle · 2012-07-26 17:11:57

There's no openbox in your sessions in slim.conf, that's the only thing I can come up with right away.

Dethredic · 2012-07-26 17:54:54

Jelle wrote:

There's no openbox in your sessions in slim.conf, that's the only thing I can come up with right away.

According to the wiki you just modify the .xinitrc file

los_locos · 2012-07-26 19:01:12

my inittab has it this way

x:5:respawn:/usr/bin/slim >& /dev/null

without 2>&1 at the end.

Edit: .xinitrc as follows

exec dbus-launch openbox-session

Last edited by los_locos (2012-07-26 19:04:11)

bgc1954 · 2012-07-26 19:04:58

if you search "dbus /var/run" there are several threads that seem to deal with your issue. Perhaps you don't have a proper link to the /run directory.

DSpider · 2012-07-26 19:07:57

Instead of auto logging in from SLiM, why not use this?

Here's my /etc/inittab:

id:3: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

c1:2345:respawn:/sbin/agetty --noclear -n -l /usr/local/sbin/autologin -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

(uncommented because I don't consider myself newbie anymore, and with only 3 tty's because I don't like coping a feel in the dark for the F7 key)

Then follow the advice from here, and add this to your ~/.xinitrc:

exec ck-launch-session dbus-launch openbox-session

And this to ~/.bash_profile:

if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
  startx
fi

This method has worked for me for about 3 years now.

scjet · 2012-07-26 19:17:50

use ArchBang instead, 'cause it is afterall just Arch + Openbox, + Slim, ... customize it later to suit your needs -problem solved.
http://bbs.archbang.org/viewtopic.php?id=2501
Or,
http://bbs.archbang.org/viewtopic.php?id=3143

Last edited by scjet (2012-07-26 19:24:27)

Arch Linux

#1 2012-07-26 14:24:02

[Solved] Openbox doesn't start properly via SLIM

#2 2012-07-26 15:35:26

Re: [Solved] Openbox doesn't start properly via SLIM

#3 2012-07-26 15:38:02

Re: [Solved] Openbox doesn't start properly via SLIM

#4 2012-07-26 16:46:21

Re: [Solved] Openbox doesn't start properly via SLIM

#5 2012-07-26 17:11:57

Re: [Solved] Openbox doesn't start properly via SLIM

#6 2012-07-26 17:54:54

Re: [Solved] Openbox doesn't start properly via SLIM

#7 2012-07-26 19:01:12

Re: [Solved] Openbox doesn't start properly via SLIM

#8 2012-07-26 19:04:58

Re: [Solved] Openbox doesn't start properly via SLIM

#9 2012-07-26 19:07:57

Re: [Solved] Openbox doesn't start properly via SLIM

#10 2012-07-26 19:17:50

Re: [Solved] Openbox doesn't start properly via SLIM

Board footer