Bug#558270: warsow: fails to start with an oscure error message

[Bruno Kleinert]

Am Freitag, den 27.11.2009, 16:22 +0100 schrieb Fabian Greffrath:
> Am 27.11.2009 16:15, schrieb Bruno Kleinert:
> > It depends if you enabled "3D Acceleration" in VirtualBox for the guest
> > machine or not. If it's enabled, the OpenGL commands are redirected to
> > r300 on the host machine.
> 
> Yes, 3D Acceleration is enabled for this virtual machine, but the 
> hardware is different. Here I have an ATI Radeon HD 2400 XT. Inside 
> the VirtualBox X.org selects the VBoxVideo driver, of which I don't 
> know what it really does.
It doesn't touch Mesa/libGL.so, so it will use indirect rendering in the
guest OS and redirect the command stream to the r300 driver on the host
OS. So it's very likley it will give you the same result.

I installed warsow on my Intel notebook and can not reproduce the bug.

When I turn off hardware acceleration via driconf then warsow fails to
start with SIGSEGV while trying to initialize libGL.so. I bet it's a bug
in Mesa ;)

Maybe you can get a backtrace about what's going wrong and if it's in
the r300 library.

Cheers - Fuddl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.alioth.debian.org/pipermail/pkg-games-devel/attachments/20091127/ca176eeb/attachment.pgp>