On Mon, 2009-01-05 at 17:27 +0100, Florian Kulzer wrote: > On Mon, Jan 05, 2009 at 11:16:41 -0500, mitch wrote: > > On Mon, 2009-01-05 at 11:07 -0500, Michael Marsh wrote: > > > On Mon, Jan 5, 2009 at 10:26 AM, mitch wrote: > > > > Using Iceweasel 3.0.5-1, or was using, and yesterday the message below > > > > started. > > > > > > > > "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." > > > > > > > > Googled for reasons and possible fixes. Killed iceweasel processes. > > > > > > > > Still the error message persists. > > > > > > Try looking for (and removing) lock files in your iceweasel profile > > > directory. Some may start with a dot. It looks like "lock" (a > > > symlink) and ".parentlock" will be the offending files. > > > Iceweasel/Firefox usually removes these when it exits, but depending > > > on how you kill it, it might not have the opportunity. > > > Thanks. That was one of the tips I did find, the parentlock. > > > > Removed it before killing all and Iceweasel will still not start. > > Check if you have any "firefox-bin" processes left on your system. If > so, kill them. (I may be telling you something that you already know, > but since you only mention killing "iceweasel" processes I wanted to > make sure.) > > -- > Regards, | http://users.icfo.es/Florian.Kulzer > Florian |
"Check if you have any "firefox-bin" processes left on your system. If so, kill them." None running. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
