From: Tony H. <h...@re...> - 2008-07-29 22:30:40
|
On Tue, 29 Jul 2008 22:35:34 +0100 Mark Williams <mar...@nt...> wrote: > Tony Houghton wrote: > > > > Damn, it's truncated the filenames. Can you run it again as > > "COLUMNS=500 ps ax -O ppid,user". > > > >> 10170 10158 mark S tty1 > >> 00:00:00 /usr/bin/ck-launch-session /home/mark/. > > > > I think this might be the culprit. It looks as if slim is using it > > to launch your session and it's still running 0install stuff. > > > Did that, and I've emailed the output to you. I'll reply here with the important bits though in case it's helpful to anyone else. 10158 8256 root S tty1 00:00:00 slim 10170 10158 mark S tty1 00:00:00 /usr/bin/ck-launch-session /home/mark/.xsession 10220 10170 mark S ? 00:00:00 /usr/bin/ssh-agent /usr/bin/ck-launch-session /home/mark/.xsession 10225 10170 mark S tty1 00:00:00 python /home/mark/.cache/0install.net/implementations/sha1new=80f48c5dd798ff135c91df32e9d777c081ed1c15/ROX-Session/AppRun -w 10236 1 mark S tty1 00:00:00 dbus-launch --exit-with-session 0launch http://rox.sourceforge.net/2005/interfaces/ROX-Session -w I'm not sure what's going on with 10236 claiming to be launched from init (pid 1), and why ck-launch-session claims to have started ssh-agent instead of the other way round. But it looks as if ck-launch-session is definitely responsible for using 0launch. Are you sure you've edited /home/mark/.xsession to stop it from using 0launch? If you have then you must have done something to slim at some point to make it run the 0install version and you need to reconfigure it to run 0.40.0. -- TH * http://www.realh.co.uk |