Bug#379940: boson: detects incorrectly DRI off, when DRI on

[Andreas Beckermann]

On Saturday 16 September 2006 14:58, Eddy Petrişor wrote:
> On 07/09/06, Andreas Beckermann <b_mann at gmx.de> wrote:
> > Hi
> > first of all: DRI drivers usually don't work very well. They have lots of
> > problems and produce a lot of "weird" effects. That said direct rendering
> > _should_ work with DRI drivers.
> >
> > Finding the issue however is a pretty difficult issue. Let's try some
> > shots into the dark, please post:
> > * The output of ldd /usr/games/boson
[...]
> > * The output of ldd /usr/bin/glxgears
[...]
> > * The output of glxinfo
[...]
> > * The first about 20 lines of console output when starting boson
>
> eddy at merci ~/usr/src/traduceri/dipo/di/4th/samba $ boson 2>/dev/null | head
> -n25 eddy at merci ~/usr/src/traduceri/dipo/di/4th/samba $ boson 2>&1 | head
> -n25 [int main(int, char**)] resolving GL, GLX and GLU symbols
> [QLibrary* loadLibrary(const QString&)] Trying to guess correct
> filename for libGL
> searching in dir /usr/lib/
> using file /usr/lib/libGL.so

Please post the output of ls -l /usr/lib/libGL.so

[...]
> boson: ERROR:
> [/build/buildd/boson-0.12dfsg1/boson/gameengine/speciestheme.cpp:288] oops
> - no unit properties for 18

This is probably unrelated - but it looks like your data module is improperly 
installed.

[...]
> > Boson checks the result of glXIsDirect(), which tells whether the GLX
> > context is direct (accellerated) or not. So the warning message is just
> > fine :-)
>
> Are you sure that's what boson is doing? 

Yes

> Glxgears does what you are 
> saying and gets a different result:
[...]

glxgears uses a different X display and a different GLX context. It actually 
may receive a direct context, while boson does not (e.g. if incompatible 
properties are requested).
Finding out _why_ this happens is the trick here. Hard without direct access 
to your system :(


Does anything change if you start boson using
LD_PRELOAD_LIBRARY=/usr/lib/libGL.so boson
?

CU
Andi