Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 30700 bytes cmdline: /usr/bin/nazghul -I /usr/share/nazghul/haxima -G /home/mot/.haxima component: nazghul Attached file: coredump, 62443520 bytes crash_function: main_menu executable: /usr/bin/nazghul kernel: 2.6.35.14-106.fc14.x86_64 package: nazghul-0.7.0-0.4.20090928cvs.fc13 rating: 4 reason: Process /usr/bin/nazghul was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1328116601 uid: 500 comment ----- Loaded a savegame, this is always reproducible. Searching the corpse, fetching the items, a ghast appears, game crashes. Warritrix quest, the skeleton contains the rune. How to reproduce ----- 1. Playing the game 2. Crash
Created attachment 558877 [details] File: backtrace
Not sure how this got filed; Fedora 14 has been end-of-life for some time now and I thought ABRT was supposed to refuse to file tickets in that case. The Fedora 15/16 version is a newer snapshot and what's in rawhide is even newer; I can't say if either of them has the same issue. This could also be an SDL issue; the backtrace isn't really clear to me. There's no chance of fixing a bug in Fedora 14 as I can't push updates for it. If your problem is present in Fedora 15 or 16, I can potentially push an update there. You're also welcome to build the current rawhide version for F14 and try it, if you have an F14 development environment around. (I don't, having moved on to supported Fedora versions.) I'll keep this bug open for a while in case you have information to add, though I expect some automatic process will just go come and clean up things reported against EOL releases before long.
Thanks for your feedback. I'll upgrade to Fedora 15 now and will try to reproduce. It's an older computer I had not upgraded yet.
Okay, upgrading to Fedora 15 fixed it, I ca not reproduce the crash any longer. So smells like some library issue. I don't know which "resolved as" status would be appropriate so please change it if necessary. The ticket can be closed. I'm trying to reproduce #786666 which is another crash I've run over, but I can not provoke it as easily as I could with this one.
I just experienced this error on Fedora 17, x86_64.