Ubuntu
warsow package

Warsow from default Gutsy package won't start

Bug #173668 reported by Ryan Prior
2
Affects Status Importance Assigned to Milestone
warsow (Debian)
Fix Released
Unknown
warsow (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: warsow

Warsow, as installed by the default Gutsy package, will not start. It complains that "You're [sic] OpenGL installation doesn't support direct rendering. If you have an NVIDIA or ATI card you'll probably need to install the proprietary driver."

I have an ATI card with the proprietary driver and I know for sure that it supports direct rendering.
Furthermore, if I install the Warsow linux tarball from its website to my Home directory, I can run it from there just fine.

The problem here, it would seem, is with the default Gutsy package. Perhaps just syncing with upstream builds would fix the problem - I don't know.

Revision history for this message
hangy (hangy) wrote :

Hi Ryan,

it seems like the startup-script used in the Ubuntu and Debian packages directly checks for direct rendering using `glxinfo`.
To me, the script /usr/games/warsow looks like it quits with exactly that message if `glxinfo | grep "direct rendering: No"` returns any content. Could it be possible that the check used there is not appropriate for ATI and its proprietary driver?
If you cannot tell by looking at the output of `glxinfo`, do not hesitate to attach it here, so that someone else could have a look at it.

Thanks,
-hangy

Bug Watch Updater (bug-watch-updater)
Changed in warsow:
status: Unknown → New
Revision history for this message
Eddy Petrisor (eddy-petrisor-gmail) wrote :

Ryan, please paste the output of this command:

glxinfo | grep -i direct

Revision history for this message
Ryan Prior (ryanprior) wrote :

me@my-laptop:~$ glxinfo | grep -i direct
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
OpenGL renderer string: Mesa GLX Indirect

As has been pointed out before, the launcher script for Warsow (in /usr/games) checks glxinfo to test "direct rendering" capabilities. Because the game downloaded straight from the site launched regardless of glxinfo's output, I see this as an error in the Warsow package (or perhaps in glxinfo itself?).

Revision history for this message
Ryan Prior (ryanprior) wrote :

Having delved further into the issues here, I am doubting that this really has anything to do with the way Warsow is packaged. It may be that glxinfo is reporting direct rendering incorrectly, but there are also issues with the video card drivers. I'm marking this bug as invalid - if I determine in the future that Warsow might need packaging changes, I'll open a new bug with more specific details and suggestions.

Changed in warsow:
status: New → Invalid
Revision history for this message
Andres Mejia (amejia1) wrote :

This has been fixed in the Debian package. The glxinfo check is left out entirely.

Changed in warsow:
status: Invalid → Fix Committed
Bug Watch Updater (bug-watch-updater)
Changed in warsow:
status: New → Fix Released
Revision history for this message
Reinhard Tartler (siretart) wrote :

fixed in intrepid.

for gutsy, I'd suggest backporting the new upstream version.

Changed in warsow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.