On Mon, Apr 14, 2008 at 11:14:55AM +0200, David wrote: > > > I tried the various things listed at the start of reportbug (run with a > > > clean home directory, remove plugins, disable pango, etc), none of these > > > help. Anything else I can try? > > > > Normally, a clean home directory should solve this. Anyways, you can > > try with the -safe-mode options, it should work. > > > > Mike > > > > Hi and thanks for your reply. This is encouraging, there's nothing > worse than reporting bugs but getting no feedback for months if ever. > > I tried these (and all the other things suggested when you run > reportbug against iceweasel) and they didn't help. I have a suspicion > that there is an issue somewhere in Debian Testing, such that purging > your system and then reinstalling everything from Testing will cause > this problem. > > Maybe a gtk or library dependancy that's in stable/unstable but not in > testing. Or possibly there is a config file somewhere under var or etc > (generated by some package but not tidied up when you purge it) which > wasn't removed, but is now causing problems. > > I'll do some more experimentation - add a completely new system user, > re-install my system against Unstable (and/or Stable) instead of > Testing, run 'cruft' against my system to find files which don't get > tidied up, etc. > > When/if I find a combination which gets it working I'll try to find > what causes this problem and then mail an update.
Typically, what you see comes from broken xul files, and by extension, broken xul cache. Cleaning your home directory should remove this xul cache, so this should solve the issue if the cache is responsible. If only xul files are responsible, then -safe-mode should disable the extension that has bad xul and is responsible for that. Did you really try to clean $HOME/.mozilla ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
