Colin Watson wrote:
> On Fri, Jan 04, 2008 at 05:23:24PM +0100, Frans Pop wrote:
> > On Friday 04 January 2008, Colin Watson wrote:
> > > Err, how so? Surely this is #430545 ("xresprobe breaks display at the
> > > middle of installation").
> >
> > I'd forgotten about that one. Yes, could very well be.
> >
> > I wonder if my BR has the same cause.
>
> Yours looks very different to me. I'd be surprised. Looks like a newt
> redrawing bug, at a guess.
I tend to think they're all related.
#430545 and #458916 are clearly the same bug ("blank screen with
unreadable boxes"), a followup report to #430545 even has blurry
pictures of the same form of corruption.
#449055 only manifests at a given vga= setting, and apparently can also
corrupt the shell on a different VT, which both point to an issue at the
level of the video hardware, not at the level of newt. It also shows the
gtk frontend being affected in a relatively minor way. Looks like it
probably blacked out the screen there but didn't mess up the video mode,
so gtk was able to redraw over it, at a guess.
(A test to be sure would be to see if #449055 could be reproduced on a
system where xresprobe was replaced with a shell script that echoed
whatever it normally echos on that hardware, without touching the video
card. If it's a newt bug that's somehow caused by the particular debconf
question, I'd expect to still see it.)
--
see shy jo
signature.asc
Description: Digital signature
