Arch Linux

camphor

Member

Registered: 2009-03-01

Posts: 32

Unable to use standalone Openbox after KDE install.

Hello all. I currently have Openbox (my default), awesome, and kde in rotation in my SLIM login. However, trying to get into Openbox fails. Everything is loaded and appears to be ready, but then suddenly crashes the X server. This comes after having installed KDE4 from the kdemod repos, and I'm unsure what the cause of the problem could be. Here's my .xinitrc

DEFAULT_SESSION=openbox-session

case $1 in
awesome)
        exec awesome
        ;;
kde)
        exec startkde
        ;;

*)
        exec openbox-session
        ;;
esac

#exec numlockx &
#exec openbox-session
#exec startfluxbox
#exec awesome

And my 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            openbox-session,awesome,kde

# 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        simone

# 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          no


# 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

Thanks for the help!

EDIT: Just for clarity, I'm able to load awesome and KDE with no problems. I use Compiz in KDE, not Openbox.

EDIT2: PROBLEM SOLVED! Sorry to take up space. Trouble came from fusion trying to start when Openbox does, thereby crashing both.

Last edited by camphor (2009-04-05 05:07:00)

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Unable to use standalone Openbox after KDE install.

I'm glad you got your problem solved. Please mark this thread as [SOLVED] if you're finished with it.