Package: iceweasel
Version: 2.0.0.6
The error message:
Iceweasel is already running, but it is not responding.
To open a new window, you must first close the existing
Iceweasel process, or restart your system.
Here are the problems:
1. There is no iceweasel process running.
2. The system is a shared system, so shutting it down
on 30 or 40 developers is impractical
3. The actual problem is the existence if a hidden,
secretive, undocumented file
CF:
> On Thu, Apr 26, 2007 at 09:28:03PM +0200, Gregory Colpart wrote:
>> Hi,
>>
>> I have same problem here with deleting lock file and nfs:/home.
>> My strange workaround is:
>> % mv ~/.mozilla ~/foo
>> % mv ~/foo ~/.mozilla
>
>Oops, sorry, I'm confused.
>The problem was presence of '.parent.lock' file.
>I knew 'lock' file but not other Mozilla lock files like
>'.parent.lock' or '.parentlock'...
So, for God's sake, augment the message with some information
about that horrid little secret file so it won't be a secret any more.
Two hours of messing around fixing a config problem that iceweasel
created for itself is, well, pretty nutty. Thank you.
P.S. another little problem, I am always getting warned over and over and over
about entering an encrypted site. The only option the popup gives me is
to always warn about it in the future. Since I am always warned and I
do not seem to be able to turn it off, how about adding an option to make
the warning shut up?
[ ] please keep bothering me about this
[ ] leave me alone. do not bother me about this any more ever.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
