You are not logged in.
Hello. I have a nice desktop with openbox, xcompmgr and cairo-dock. I don't know how to start it from my .xinitrc. Now I have this in it:
openbox &
xcompmgr &
exec cairo-dock
I get an error. Respawning to fast.
How can I start it automagically?
Something wrong with the order of it?
Last edited by jai134 (2008-12-13 18:53:28)
Offline
You're on the right track but your openbox-session should be the last executed.
ie.) xcompmgr &
cairo-dock &
exec openbox-session
And it's generally advised to start openbox with exec openbox-session--see wiki http://wiki.archlinux.org/index.php/Openbox
Edit: And welcome to the forums and Arch.
Last edited by bgc1954 (2008-12-13 14:18:48)
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
ive never used .xinitrc to load my apps at login. i have everything stored in ~/.config/openbox/autostart.sh. i believe the difference is that when loading from .xinitrc it is trying to launch before openbox starts.
if im wrong please someone correct me. ive really only used .xinitrc for configuring slim.
Offline
Actually, I must admit I use both. Normally apps like numlockx or eval `cat ~/.fehbg` I put in my .xinitrc as I run different wm's at times and then I don't have to put that into every startup script I have.
The OP might want to put cairo-dock in his openbox/autostart.sh as I'm not sure if that will start properly from .xinitrc--I think it should though. I think it's more a personnal preference than anything else as I'm sure I've put xcompmgr in my .xinitrc before--when I used it. But you do have a point as I run a few different computers and distros--some with and some without a login manager-- and login managers, like gdm, don't always pay proper attention to the .xinitrc, unless you specifically configure them to.
Edit: spelling
Last edited by bgc1954 (2008-12-13 14:54:40)
Time is a great teacher, but unfortunately it kills all its pupils ... - Louis Hector Berlioz
Offline
If you're using Openbox, and you don't mind if applications start after Openbox, you can always use it's built-in autostart function, configured in ~/.config/openbox/autostart.sh. I use a combination of .xinitrc and autostart.sh to do all of my startup related tasks.
[ lamy + pilot ] [ arch64 | wmii ] [ ati + amd ]
Offline
example:
xinitrc
#!/bin/sh
# Executed by startx
# pre X set-up stuff
xrdb $HOME/.Xdefaults & # just incase
xcompmgr -cCfF & # unstable with new xorg :(
eval `cat $HOME/.fehbg` & # restore background
kdeinit & # set up kde
numlockx on & # numlock on if it's not
# launch the WM
exec openbox-session # openbox
#exec awesome # awesome
autostart.sh
# This shell script is run before Openbox launches.
# Environment variables set here are passed to the Openbox session.
# Run the system-wide support stuff
#. $GLOBALAUTOSTART
# pre openbox stuff in .xinitrc now
# Programs to launch *after Openbox*
(sleep 3 && conky) &
(sleep 10 && synergys) &
i agree completely with bgc1954, if you can't tell. i'd put cairo dock in autostart.sh as a (slee 5 &&... line. see the openbox wiki for where to place these files
good luck
Last edited by brisbin33 (2008-12-13 15:37:05)
//github/
Offline
Thankyou for your help.
Offline