| Summary: | [abrt] tuxmath-2.0.1-1.fc16: SDL_FreeSurface: Process /usr/bin/tuxmath was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jaimelozano09 | ||||||||
| Component: | tuxmath | Assignee: | Gwyn Ciesla <gwync> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | gwync, vyperlinux | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:d9b6f40bfe70e591702c094c1f29320f43315a02 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-02-14 01:51:12 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
jaimelozano09
2012-01-06 17:52:07 UTC
Created attachment 551215 [details]
File: dso_list
Created attachment 551216 [details]
File: maps
Created attachment 551217 [details]
File: backtrace
I have tried to reproduce the crash myself, just to help: [jaime@toshiba ~]$ gdb /usr/bin/tuxmath GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16) Copyright (C) 2011 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 "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/tuxmath...(no debugging symbols found)...done. Missing separate debuginfos, use: debuginfo-install tuxmath-2.0.1-1.fc16.i686 (gdb) start Function "main" not defined. Make breakpoint pending on future shared library load? (y or [n]) n Starting program: /usr/bin/tuxmath [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Initializing Tux4Kids-Common 0.1.1 [New Thread 0xb3d0cb40 (LWP 2187)] [Thread 0xb3d0cb40 (LWP 2187) exited] [New Thread 0xb3d0cb40 (LWP 2188)] Warning: requested speed below minimum, setting to 0,8. Warning: requested max speed above Tuxmath's maximum, setting to 20. Program received signal SIGSEGV, Segmentation fault. 0x4a70c86f in SDL_FreeSurface () from /usr/lib/libSDL-1.2.so.0 (gdb) I have had to kill /usr/bin/tuxmath after the crash. Another error in my system is the following: ALSA sound/pci/intel8x0.c569 codec_read 0: semaphore is not ready for register 0x20 Sometimes my systems loose the sound so I don't know if there is a relation with the "main" problem. When i start tux math on fedora 17 the green goes black then it is killed, I dunno if its the same error. f17 had a problem with the patch I made for libpng15, I've fixed that and that fix is on it's wat to updates-testing. I can't reproduce a crash on f16. Does it still crash for you on f16? Bug 829419 (with F-17) apparently is the same as this one. So we're looking at two crashes, one that was already there, and one that I introduced with my initial libpng15 patch. Now that I've fixed my patch, we can run long enough to hit this one. :) The TuxMath application just crashed after selecting the help option. backtrace_rating: 4 Package: tuxmath-2.0.1-2.fc17 Architecture: x86_64 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |