[Bug 173668] Re: Warsow from default Gutsy package won't start

2008-05-20 Thread Reinhard Tartler
fixed in intrepid.

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

** Changed in: warsow (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2008-04-28 Thread Bug Watch Updater
** Changed in: warsow (Debian)
   Status: New = Fix Released

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2008-04-21 Thread Andres Mejia
This has been fixed in the Debian package. The glxinfo check is left out
entirely.

** Changed in: warsow (Ubuntu)
   Status: Invalid = Fix Committed

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2008-01-10 Thread Ryan Prior
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 (Ubuntu)
   Status: New = Invalid

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2007-12-04 Thread Eddy Petrisor
Ryan, please paste the output of this command:

glxinfo | grep -i direct

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2007-12-04 Thread Ryan Prior
[EMAIL PROTECTED]:~$ 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?).

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2007-12-03 Thread hangy
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

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2007-12-03 Thread hangy
** Bug watch added: Debian Bug tracker #454156
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454156

** Also affects: warsow (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454156
   Importance: Unknown
   Status: Unknown

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 173668] Re: Warsow from default Gutsy package won't start

2007-12-03 Thread Bug Watch Updater
** Changed in: warsow (Debian)
   Status: Unknown = New

-- 
Warsow from default Gutsy package won't start
https://bugs.launchpad.net/bugs/173668
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs