Bug 455291

Can you do the following (as root in a terminal):
yum install yum-utils
debuginfo-install supertuxkart

And then as normal user from a terminal:
gdb supertuxkart

This will give you a gdb prompt:
(gdb)

Type "run" here and start playing, once supertuxkart crashes type (bt) and paste
the full output here please.

Thanks!

But, I have one error with this instruction.
http://forums.fedora-fr.org/viewtopic.php?id=34047

And, I don't find the correction, I am blocked...
Have you a suggestion ?

Try entering the following command on the console (while already root) before
doing the debuginfo-install:
"export LANG=en_US.utf8"

Maybe that will fix it, you can also try updating yum:
"yum update yum"

The error is :

"17:54:11 <3 998> [couretca@CHAMBRECAC ~]$ gdb supertuxkart
GNU gdb Fedora (6.8-11.fc9)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...

(gdb)
(gdb) run
Starting program: /usr/bin/supertuxkart
[Thread debugging using libthread_db enabled]
Data files will be fetched from: '/usr/share/supertuxkart/'
[New Thread 0x7f0262d8c740 (LWP 25743)]
[New Thread 0x12f8950 (LWP 25746)]
[Thread 0x12f8950 (LWP 25746) exited]
[New Thread 0x12f8950 (LWP 25747)]
[New Thread 0x4e5e950 (LWP 25748)]
Highscores will be saved in '/home/couretca/.supertuxkart/highscore.data'.
Error messages and other text output will be logged to
/home/couretca/.supertuxkart/stderr.log and stdout.log
[New Thread 0x1cf9950 (LWP 25749)]

Program received signal SIGABRT, Aborted.
0x0000003e08632215 in raise (sig=<value optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Current language:  auto; currently c
Missing separate debuginfos, use: debuginfo-install alsa-lib.x86_64
audiofile.x86_64 esound.x86_64 libX11.x86_64 libXau.x86_64 libXcursor.x86_64
libXdmcp.x86_64 libXext.x86_64 libXfixes.x86_64 libXrandr.x86_64
libXrender.x86_64 libXxf86vm.x86_64 libogg.x86_64 libxcb.x86_64"

	
I can't go further

The missing seperate debuginfo's really isn't a problem, its more of a warning,
you should still get a "(gdb)" prompt after that, please do it again and type
"bt" after the (gdb) prompt, and paste the output it gives then.

Oh, I am sorry

The complete error is :

03:27:04 <1 998> [couretca@CHAMBRECAC ~]$ gdb supertuxkart
GNU gdb Fedora (6.8-11.fc9)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) run
Starting program: /usr/bin/supertuxkart
[Thread debugging using libthread_db enabled]
Data files will be fetched from: '/usr/share/supertuxkart/'
[New Thread 0x7f81c72b1740 (LWP 21059)]
[New Thread 0x12f8950 (LWP 21062)]
[Thread 0x12f8950 (LWP 21062) exited]
[New Thread 0x12f8950 (LWP 21063)]
[New Thread 0x47fc950 (LWP 21064)]
Highscores will be saved in '/home/couretca/.supertuxkart/highscore.data'.
Error messages and other text output will be logged to
/home/couretca/.supertuxkart/stderr.log and stdout.log
[New Thread 0x7ced950 (LWP 21065)]

Program received signal SIGABRT, Aborted.
0x0000003e08632215 in raise (sig=<value optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Current language:  auto; currently c
Missing separate debuginfos, use: debuginfo-install alsa-lib.x86_64
audiofile.x86_64 esound.x86_64 libX11.x86_64 libXau.x86_64 libXcursor.x86_64
libXdmcp.x86_64 libXext.x86_64 libXfixes.x86_64 libXrandr.x86_64
libXrender.x86_64 libXxf86vm.x86_64 libogg.x86_64 libxcb.x86_64
(gdb) bt
#0  0x0000003e08632215 in raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x0000003e08633d83 in abort () at abort.c:88
#2  0x0000003e0862b039 in __assert_fail (assertion=<value optimized out>,
    file=<value optimized out>, line=<value optimized out>, function=<value
optimized out>)
    at assert.c:78
#3  0x00000000004703d8 in DefaultRobot::calc_steps (this=<value optimized out>)
    at robots/default_robot.cpp:789
#4  0x0000000000471cf8 in DefaultRobot::update (this=0x7f81bc62f620,
delta=0.00200000009)
    at robots/default_robot.cpp:100
#5  0x0000000000438674 in World::update (this=0x7f81bfb0b850, dt=0.00200000009)
at world.cpp:307
#6  0x00000000004435a0 in GameManager::run (this=0x2811c30) at game_manager.cpp:90

Thanks! Thats just the info I need, it may take a few days before I can find the
time to look into this, but I think there is a good chance I can fix this given
this info!

High, new supertuxkart maintainer.  

Three questions.  One, does this still happen to you, and after how long, and on which track?

Two, can I have the stderr.log and stdout.log files from ~./supertuxkart?

Three, is this the stock Fedora nvidia driver or the proprietary driver directly from nvidia?

Thanks!

1-I don't understand the first question. This bug happen few minutes after start the game, between 2-4 races. 

2-stderr.log

WARNING: sgMat4ToCoord: ERROR - Bad Matrix.

stdout.log is empty.

3-The proprietary driver from nVidia (via Livna).

1- I was just wondering if the game was still crashing for you.

3- Is the game playable if you use a different driver, such as the included nv driver, or the vesa driver, and if so, does it crash then?

Also, does the version in rawhide work for you?  You can get it here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=62154

If it does, I'll simply build that version for F-9.

Ping?

Still can't reproduce this, and no response from reporter.  If this is still a problem without the proprietary driver, please repoen.

Oh, sorry ! I don't read the email of Bugzilla...
This bug is solved...