Prev: tar -cz causes diff problem
Next: ESX hardware configuration
From: Vilmos Soti on 14 Apr 2010 16:45
Hello,

We have some users whose iceweasel (3.0.6) doesn't start up.

They are Debian 5.0.2 systems, and the home dirs are on nfs.

So the machines sometimes spontaneously reboot (we haven't
yet figured out why), and afterwards whenever the user
tries to start iceweasel, it always presents the "restore
session or start new session" dialog box. Whatever we
do, it doesn't restore any session, and also forgets the
bookmarks and default page. I removed the .../lock and
..../.parentlock file, but it didn't help. The only way to
stop iceweasel asking the "restore session" stuff is to
remove the ~/.mozilla/firefox/whatever directory. Which
is of course not the ideal solution.

Anybody has seen this problem or knows what's wrong here?

Thanks, Vilmos
From: The Natural Philosopher on 14 Apr 2010 17:38
Vilmos Soti wrote:
> Hello,
>
> We have some users whose iceweasel (3.0.6) doesn't start up.
>
> They are Debian 5.0.2 systems, and the home dirs are on nfs.
>
> So the machines sometimes spontaneously reboot (we haven't
> yet figured out why), and afterwards whenever the user
> tries to start iceweasel, it always presents the "restore
> session or start new session" dialog box. Whatever we
> do, it doesn't restore any session, and also forgets the
> bookmarks and default page. I removed the .../lock and
> .../.parentlock file, but it didn't help. The only way to
> stop iceweasel asking the "restore session" stuff is to
> remove the ~/.mozilla/firefox/whatever directory. Which
> is of course not the ideal solution.
>
> Anybody has seen this problem or knows what's wrong here?
>

Possibly.

I run this icedove on NFS mounted Mail directory.

IF I start it with the server down, it defaults to a completely
different data directory, and I have to manually shut it, start the
server, restart it, tell it to use the correct mail directory, shut it
and restart it again.

My GUESS is that you are losing the NFS mounted directories, and its
automagically resetting itself to some default afterwards.

That may be what's causing the random crashes too.

As to why it wont restart correctly, it may be that it has an inherent
default behoviour in the situatin where its starting up from a known
crash, that isn't quitre what it should be.,

I don't like NFS mounted home dirs.

I guess if you are 'hot desking' there ain't no other way though.


> Thanks, Vilmos
 | 
Pages: 1
Prev: tar -cz causes diff problem
Next: ESX hardware configuration