Getting xprofile to work ...
I have been using Openbox in my Slack --current install for a few weeks now. I like it, but would also like some apps to autostart when I fire up X. When I decided I wanted this I realized I'd totally forgotten how to make it happen!
So I went searching here and saw a few threads re: using a file (variously /etc/xprofile and ~/.xprofile) to store these commands. So I created /etc/xprofile with the lines conky & xscreensaver & xclock & and set it executable. It didn't work. I tried creating a symlink called '.xprofile' in my home directory to this /etc/xprofile. That didn't work. I chmod -x 'd /etc/xprofile, thinking it might be a permissions thing. That didn't work. I'm sure it's something simple (I am something simple!), but I am currently stumped. All these commands are in /usr/bin, so I don't think adding the complete path is the answer, though it's easy enough to try ... Thanks for any hints. Glenn |
Just checking... but you do know that /etc/xprofile and ~/.xprofile are only used in runlevel 4?
Eric |
Quote:
So this isn't an option for folks who like to handstart X then? E.g. it is a thing to utilize if you go straight to KDM (or whatever) and do not collect $200? |
I'm not sure about openbox, but in fluxbox, there's a ~/.fluxbox/startup that gets this job done.
P.S. I launch my X manually as well. |
Code:
echo '#!/bin/sh P.S an additional thought... back up your current ~/.xsession file if it exists as this will over-write it. |
You can use /etc/xprofile or $HOME/.xprofile in run level 3. Just modify /usr/bin/startx to source the files.
Perhaps the following will help: A More Intelligent startx Script |
Quote:
Seems like it should work fine ... I am studying Woodsman's link. So much good stuff there! |
Quote:
Thanks to all for the responses. I am at home recovering from surgery, and it is fun to get back to playing ... - G |
Quote:
xscreensaver: 06:40:23: warning: $DISPLAY is not set: defaulting to ":0.0". xscreensaver: 06:40:23: Can't open display: :0.0 xscreensaver: 06:40:23: initial effective uid/gid was chexmix/shadow (1000/43) xscreensaver: 06:40:23: running as chexmix/users (1000/100) xscreensaver: 06:40:23: Errors at startup are usually authorization problems. But you're not logging in as root (good!) so something else must be wrong. Did you read the manual and the FAQ? http://www.jwz.org/xscreensaver/faq.html http://www.jwz.org/xscreensaver/man.html Conky: can't open display: Error: Can't open display: xauth: creating new authority file /home/chexmix/.serverauth.3212 ... which makes sense - it seems xscreensaver is trying to start up TOO SOON, e.g. before there is a display for it to start on. Am going to play with the placement of the lines in /usr/bin/startx where .xprofile gets sourced and see if that helps. GB |
Quote:
|
All times are GMT -5. The time now is 07:44 AM. |