Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/seamonkey-2.0.11/seamonkey-bin component: seamonkey crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/seamonkey-2.0.11/seamonkey-bin kernel: 2.6.34.7-66.fc13.x86_64 package: seamonkey-2.0.11-1.fc13 rating: 4 reason: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce: I was just reading a web page that hadn't finished download yet, and it just crashed. time: 1297193443 uid: 65001749
Created attachment 477676 [details] File: backtrace
Thank you for taking the time to make this bug report. Unfortunately, crash here happened in the moonlight extension, which is on the Forbidden Items (http://fedoraproject.org/wiki/ForbiddenItems#Moonlight) list and as such is not shipped with Fedora or within it's native repositories, so unfortunately we cannot help you with it. Closing as CANTFIX (because that's our situation) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
It would be nice if the crash reporter told me the module name where the crash actually occurred. Searching through the log for the stack trace isn't intuitive at all. I understand that Moonlight bugs are off-limits, but if people have to scour the bug report in order to determine that, there are going to be lots of Moonlight bugs reported here.