crash on starting V 1.2.3-2ubuntu2 on breezy

[jpp]

Hi, if I run torcs with default option, I select the first choise each time, and I've got a crash with this:

Visual Properties Report
------------------------
Compatibility mode, properties unknown.
torcs-bin: indirect_vertex_array.c:1359: __indirect_glTexCoordPointer: Assertion `a != ((void *)0)' failed.
/usr/games/torcs: line 52: 10849 Abandon $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $*

Can I activate debug for more information ?

Thanks

[Zak B. Elep (zakame)]

Hi jpp :-)

Thanks for your bug report. Could you please try to obtain a backtrace by following the instructions on http://wiki.ubuntu.com/DebuggingProgramCrash ?

Thanks again,

Zakame

[Paul Dufresne (paulduf)]

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.

[jpp (jp-proux)]

hi, i'm using an other laptop now, and on this one, I'm not able to confirm
the problem. torcs run on the new one :)
You're right, if i'm alone, I think you can switch status to close.
Thanks.

2006/2/18, Paul Dufresne <email address hidden>:
>
> Public bug report changed:
> https://launchpad.net/malone/bugs/4180
>
> Task: ubuntu torcs
> Severity: Major => Normal
> Status: Unconfirmed => Needs Info
>
> Comment:
> 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.
>

[Carthik Sharma (carthik)]

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.