On Mon, Oct 26, 2009 at 09:09:56AM +0100, Mike Hommey wrote: > On Mon, Oct 26, 2009 at 08:54:12AM +0100, Mario 'BitKoenig' Holbe wrote: > > Package: iceweasel > > Version: 3.5.3-2 > > > > Hello, > > > > iceweasel's "restore from crash" shows no restored windows anymore (or > > better: it hides them with no way to recover). > > > > How to reproduce: > > * Start with a fresh profile (mv -i .mozilla/firefox .mozilla/firefox.old) > > * Create some Tabs with some content > > * Kill the firefox process (ps -ef | grep iceweasel; kill -TERM) > > * Start iceweasel again > > An Iceweasel window together with the "Restore Session" Tab should > > appear. Sometimes it does not (why ever), just start from the beginning > > in this case. > > * Click on "Restore" > > The window disappears, nothing more happens. If you are quick or if you > > got lots of open tabs before the "crash" you can see the old tabs > > appearing for a very short time in the "Restore" window before it > > disappears. > > > > xwininfo -root -tree still shows the window(s), they are just not > > visible anywhere anymore. > > > > The issue is a bit more strange with only one tab: > > * sometimes no window appears at all, > > * sometimes the "Restore" Tab appears and the old Tab is restored and > > shown just normal after clicking on "Restore", > > * sometimes the "Restore" Tab appears and the window goes away after > > clicking on "Restore" as in the multi-Tab case. > > > > Opening multiple windows before the crash results in the windows being > > shown for a very short period after clicking on "Restore" and > > disappearing then. > > > > I'm using fvwm with "Interactive Window Placement" - just in case it > > matters. > > Interesting, I had the same issue a few days ago, and I blamed my window > manager. The problem disappeared after a reboot so I couldn't > investigate further...
I got the bug again, and could not reproduce it on purpose. The only thing I found out is that saving the sessionstore.js file from the profile that ends up with this problem and restoring it would trigger it again, while other sessionstore.js files from other sessions wouldn't. As I don't have time to track this down, would you mind trying to save your own sessionstore.js file when that happens, and try to edit stuff out of it until it works again, so that we can identify a pattern that triggers this bug ? Cheers Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
