Bug#535858: iceweasel forgets first page setting on quit

[Mike Hommey]

On Sun, Jul 31, 2011 at 06:50:31PM +0200, Peter T. Breuer wrote:
> "Also sprach Mike Hommey:"
> > > That's what bug-buddy and other programs are for.
> > 
> > Without further feedback, I'll assume this got better and close this bug.
> > Please feel free to reopen if that is not the case.
> 
> Sorry about that. Actually, I think what happened was that I switched
> to using opera.  I must have meant to do some debugging, but I don't see
> evidence!
> 
> I've tested again, right now, and it seems OK now. A very cursory test.
> I've checked "show blank page" is set, and I closed with Alt-Q while I
> had news.bbc.co.uk open, and at next relaunch it came up with a blank
> page OK..
> 
> 
>   ii  iceweasel      3.5.19-3       Web browser based on Firefox
> 
> Firefox itself also has the bug cured.
> 
>   ii  firefox        3.6.17+build3+ safe and easy web browser from Mozilla
> 
> 
> But iceweasel is not rendering well .. most of the fonts are missing in
> the menus, same as in my kde installation (I largely switched to xfce
> for lighter weight windowing managers and gizmos and it has no such
> problem, so I don't care), and the lower half of images and indeed
> columns and pages is white until I do some mouse-overing or scrolling.
> The word "preferences" was not visible in the edit menu ..  it was black
> down there.  I just guessed and clicked and it turned out to be
> right.
> 
> Firefox itself is rendering fine, it seems.
> 
> I'm on debian unstable, up to date to within a few days.

Then you should be using iceweasel 5 ;)

> It could be that it's an X problem. I am on an IBM TP x40 and holding
> the X server at an older version, since newer intel drivers seem to give
> me just a blank screen.
> 
>   ii  xserver-xorg-v 2:2.2.1-1ubunt X.Org X server -- Intel i8xx, i9xx display d
> 
> (ubuntu's video driver is the most easily available most recent package
> that runs my display fine).

Your rendering corruption problem does indeed sound like a driver
problem. But that's not really related to this bug, so if you still have
the problem on an up-to-date system, please feel free to file a new bug.

Cheers,

Mike