[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

On Sat, Sep 23, 2006 at 01:56:40PM +0200, Attilio Fiandrotti wrote:
> Sven Luther wrote:
> <snip/>
> >>>>Yes, i saw the vanished lines in your screenshots and i belive this may 
> >>>>be #385026, which  is GTKDFB 2.8.x related and affects all HW platforms.
> >>>>As Frans said, this is a quite annoying bug and i'll try to see if i 
> >>>>can fix it in GTKDFB 2.8.20 with a small patch (but i'm not sure it's 
> >>>>going to be an easy fix).
> >>>
> >>>
> >>>Is it fixed in 2.10.x ? 
> >>
> >>Basing on my past tests with different GTK+ 2.10 versions, it is.
> >
> >
> >This would be a reason to go with gtk 2.10.x, those packages are built and
> >uploaded to experimental, right ? So we could do a second build using the 
> >2.10
> >stuff ? 
> Yes, GDKDFB backend found in 2.10.4 is more stable and clean than one 
> found in 2.8.20, which is an old backported DFB backend some months old.
> If we can fix this issue[1] before GTK 2.10.5 is out, we may prefer 
> switching to GTK 2.10.5 later, otherwise we may need to backport current 
> GDKDFB backend from 2.10.4 to 2.8.20 for immediate use.
> 2.10.x, compared to 2.8.x, offers nothing we really need, but of course 
> avoiding dirty backports wouldn't be bad!
> [1] http://lists.debian.org/debian-boot/2006/09/msg00995.html

That would be the BOOM issue, right, in my experience, from my X hacking days,
is that stuff like this happens when the refresh is no more happening, and
when one is using a software cursor, which is still working or something.


Sven Luther

Reply to: