Iceweasel is already running ...

[Albretch Mueller <lbrtchx@gmail.com>]

~
 Since I use a liveCD to go online as a user whose home dir is in a
ramdisk section, I have a "yeah, sure! ..." attitude when it comes to
enabling javascript or what have you
~
 Once in a while I would go "init 2" remove and recreate that ramdisk
home directory, but I get such "so und so is already running ..."
errors. Such applications may have been leaving data in some other
directories.
~
 How can you know to which files or directories a certain application
has written data to?
~
 How can you debug/troubleshoot such issues?
~
 thanks,
 lbrtchx

$ iceweasel --no-remote

(firefox-bin:9617): atk-bridge-WARNING **: AT_SPI_REGISTRY was not
started at session startup.

(firefox-bin:9617): atk-bridge-WARNING **: IOR not set.

(firefox-bin:9617): atk-bridge-WARNING **: Could not locate registry

 then I get a modal window telling me:

 "Iceweasel is already running, but is not responding. To open a new
window, you must first close the existing Iceweasel process, or
restart your system."

$ ps aux | grep iceweasel
knoppix   9643 11.2  1.1 248376 30088 pts/0    Sl+  17:25   0:01
/usr/lib/iceweasel/firefox-bin --no-remote
knoppix   9699  0.0  0.0   5136   740 pts/2    S+   17:25   0:00 grep
--colour=auto iceweasel

$ sudo ps aux | grep iceweasel
knoppix   9643  7.3  1.1 248376 30088 pts/0    Sl+  17:25   0:01
/usr/lib/iceweasel/firefox-bin --no-remote
knoppix   9701  0.0  0.0   5136   744 pts/2    S+   17:25   0:00 grep
--colour=auto iceweasel

$ sudo ps aux | grep mozilla
knoppix   9704  0.0  0.0   5136   740 pts/2    S+   17:25   0:00 grep
--colour=auto mozilla

 after closing that "Iceweasel is already running ... " window

$ which iceweasel
/usr/bin/iceweasel

$ iceweasel --version
Mozilla Iceweasel 10.0.4