2005-11-11 09:24:28 |
jpp |
bug |
|
|
added bug |
2005-11-11 09:25:34 |
jpp |
torcs: severity |
Normal |
Major |
|
2005-11-11 09:25:34 |
jpp |
torcs: statusexplanation |
|
I switch to major, because crashing, and not usable. |
|
2005-11-15 12:20:42 |
Daniel Holbach |
torcs: assignee |
|
motugames |
|
2006-02-18 17:43:26 |
Paul Dufresne |
torcs: status |
Unconfirmed |
Needs Info |
|
2006-02-18 17:43:26 |
Paul Dufresne |
torcs: severity |
Major |
Normal |
|
2006-02-18 17:43:26 |
Paul Dufresne |
torcs: statusexplanation |
I switch to major, because crashing, and not usable. |
Well, it is unclear if most people trying
torcs get this error or not. So for now
I am switching it back to normal severity.
(In setting severity, we consider the number
of ubuntu users affected, since just a few
will use this package, and that the bug is
unconfirmed yet, I'll set it back to normal).
Although your description shows exactly
where the program halted, it is not much
usefull, because we won't know from where
the function was called (with a bad value).
So please, consider adding a trace by
following instructions on:
https://wiki.ubuntu.com/DebuggingProgramCrash
I can hardly test it myself because I
use a PII 330Mhz, with no OpenGL card. |
|
2006-05-05 04:16:54 |
Carthik Sharma |
torcs: status |
Needs Info |
Rejected |
|
2006-05-05 04:16:54 |
Carthik Sharma |
torcs: statusexplanation |
Well, it is unclear if most people trying
torcs get this error or not. So for now
I am switching it back to normal severity.
(In setting severity, we consider the number
of ubuntu users affected, since just a few
will use this package, and that the bug is
unconfirmed yet, I'll set it back to normal).
Although your description shows exactly
where the program halted, it is not much
usefull, because we won't know from where
the function was called (with a bad value).
So please, consider adding a trace by
following instructions on:
https://wiki.ubuntu.com/DebuggingProgramCrash
I can hardly test it myself because I
use a PII 330Mhz, with no OpenGL card. |
Closing this bug since the original reporter hasn't had this problem in more than 2 months, and no one else seems to be having this problem as well. Please reopen if this still bugs you. |
|