[apport] briquolo crashed with SIGSEGV

[Rocker3358]

Binary package hint: briquolo

Didn't even start

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Apr 8 09:30:17 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/briquolo
Package: briquolo 0.5.5-1ubuntu1
PackageArchitecture: i386
ProcCmdline: briquolo
ProcCwd: /home/rocker
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: briquolo
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? () from /usr/lib/libz.so.1
 ?? ()
Uname: Linux Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Martin Pitt (pitti)]

StacktraceTop:____strtod_l_internal () from /lib/tls/i686/cmov/libc.so.6
__strtod_internal () from /lib/tls/i686/cmov/libc.so.6
closestFit (target=3553, width=256, height=256, internalFormat=4, format=6408, type=5126, newWidth=0xbfbe4d5c, newHeight=0xbfbe4d58) at /usr/include/stdlib.h:330
gluBuild2DMipmaps (target=3553, internalFormat=4, width=256, height=256, format=6408, type=5126, data=0xb6e00008) at libutil/mipmap.c:4599
MOGL_Texture::_Init ()

[Boniek (boniek12p)]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. If you could test the
current Ubuntu development version, this would help us a lot. If you can
test it, and it is still an issue, we would appreciate if you could
upload updated logs by running apport-collect <bug #>, and any other
logs that are relevant for this particular issue.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".