Bug#726002: xserver-xorg-video-mga: Dualheading using 1.6.2 segfaults
Tormod Volden writes:
> On Fri, Oct 18, 2013 at 1:34 AM, Robert Jacobs wrote:
> > Tormod Volden writes:
> >> Mouse droppings, is this traces of the mouse pointer not being cleaned
> >> up? Did dual head at one point work for you without such droppings? In
> >> this case testing of older versions (of server and driver) can help to
> >> spot the regression. Anyway, dual head with mouse droppings is better
> >> than no dual head.
> >
> > Yeah, mouse droppings from the outline moves by ctwm, regardless of
> > whether using EXA or nothing. Bad interactions between the line
> > drawing X calls and whatever is being done for the mouse cursor on the
> > second head.
> >
> > Doesn't happen with XAA or NoAccel on 1.5.0, something worse happens
> > with EXA on 1.5.0 (but we don't care).
>
> Is that mga 1.5.0? So it is independent of the server?
Oh, no, sorry, I was just using snapshot.debian.net to compare the
entire xorg release as of mga 1.5.0 (core 1.12.4) being in the
repository vs when mga 1.6.2 hit (core 1.14.3)
Using NoAccel, ctwm, with mga 1.6.2 built against debian's
xserver-xorg-core 1.12.4 does not cause mouse droppings on the second
head. EXA in same context terminates with
Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/mga_drv.so: undefined symbol: XAACreateInfoRec
which is just confusing.
1.5.0 doesn't build against debian's xserver-xorg-core 1.14.3 due to
the XAA removal.
So I guess the mouse droppings are actually the new core's fault?
- Robert
Reply to: