Re: Iceweasel problem
On Mon, 2009-01-05 at 11:57 -0600, Boyd Stephen Smith Jr. wrote:
> On Monday 2009 January 05 11:29:48 André Neves wrote:
> > Mitch, please clarify whether there are still any iceweasel|firefox
> > processes running (i.e. if any survived the killing).
>
> Wow! How many times are you guys going to tell the guy the same thing?
>
> Mitch, could you please post the output of:
> ps auwx | grep -E 'ice|fire|xul'
> and:
> find ~/.mozilla -iname '*lock*' -ls
>
> The ps command should show most processes related to iceweasel, as well as
> some unrelated, and let you and us confirm that they aren't running. If they
> are, perhaps you should kill them. I generally like the following commands:
> kill -INT <process_id>
> kill -TERM <process_id>
> kill -KILL <process_id>
> in that order, checking to see if the process is still around after issuing
> each one. The INT command is a like a "Ctrl+C"... most programs will cleanup
> and exit if they can, others will abort a long-running process and request
> more input. The TERM is more severe, an explicit instruction to terminate
> ASAP. The KILL is most severe, shuts down the program without giving it a
> chance to cleanup, the next time it would be eligible to receive a "signal"
> (technical term).
>
> After all the iceweasel processes are cleaned up, the find command above
> should list all the lock files, verbosely. You can inspect the files
> individually, but they are mostly likely ready to be removed. Repeating the
> command but with '-delete' instead of '-ls' should do that.
>
> If iceweasel continues to give the same error after killing those processes
> and removing those files, we may have to monitor iceweasel as it starts up
> using strace and/or ltrace. This will produce a lot of information but, when
> properly filtered, should indicate the next steps.
Okay, so, here is the out put.
> mitch@debian:~$ ps auwx | grep -E 'ice|fire|xul'
> mitch 15545 0.0 0.0 3592 688 pts/12 R+ 13:06 0:00 grep -E ice|fire|xul
> mitch@debian:~$ find ~/.mozilla -iname '*lock*' -ls
> 551443 0 -rw-r--r-- 1 mitch mitch 0 Jan 5 12:13 /home/mitch/.mozilla/default/d2pj9qe6.slt/.parentlock
> 551883 4 drwxr-xr-x 2 mitch mitch 4096 Jan 5 12:14 /home/mitch/.mozilla/default/d2pj9qe6.slt/adblockplus
I deleted the .parentlock and the ran the same grep and find, results below.
> mitch@debian:~$ ps auwx | grep -E 'ice|fire|xul'
> mitch 15637 0.0 0.0 3596 692 pts/12 R+ 13:09 0:00 grep -E ice|fire|xul
> mitch@debian:~$ find ~/.mozilla -iname '*lock*' -ls
> 551883 4 drwxr-xr-x 2 mitch mitch 4096 Jan 5 12:14 /home/mitch/.mozilla/default/d2pj9qe6.slt/adblockplus
> mitch@debian:~$
Tried starting Iceweasel once more and the same error message popped up,
the can't start because Iceweasel is already running
Reply to: