Hey all, I just have a minor question.
NetworkManager 0.7 is bugging me a little, but methinks the culprit is really ck-launch-session.
If I try and autostart ck-launch-session, either in .xinitrc or .config/openbox/.autostart.sh, for some strange reason it doesn't kick in.
I've tried putting it in xinitrc before openbox starts, putting it in after openbox starts, giving a sleep 10 && ck-launch-session in autostart.sh and many other variations.
yadda yadda yadda, none of it works.
But when openbox starts and I just run ck-launch-session from urxvt, there isn't a problem, it starts and stays there, then I run nm-applet & and it starts and runs perfectly.
So what am I missing?
Cheers for any help, I'm most likely missing something glaringly obvious.
Last edited by evol (2009-01-23 16:30:37)
What's in your /etc/pam.d/login file? Do you have something like:
session optional pam_ck_connector.so
in there somewhere?
I have the above and my xinitrc is just this (all apps are started from ~/.config/openbox/autostart.sh):
exec ck-launch-session openbox-session
Also, see this bug report for more discussion about this issue in case you haven't already: http://bugs.archlinux.org/task/12221
Last edited by fwojciec (2009-01-23 16:04:24)
hey, thanks for the fast response - I hadn't got that entry in pam.d/login and I guess due to pure incompetence wasn't exec'ing ck-launch-session when I had it in xinitrc before, i just had it entered plain.
chalk this one up to incompetence!
thanks for your help, everything's fine now
Last edited by evol (2009-01-23 16:32:10)