Bug 642523

Summary: [abrt] terminator-0.95-1.fc13: remove_capslock_feedback: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrew Chambers <andrewrchambers>
Component: terminatorAssignee: Dominic Hopf <dmaphy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dmaphy, steve
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d6dee956720a65edc3bafda5780624cceb5d81af
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-11 21:23:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Andrew Chambers 2010-10-13 09:02:32 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/terminator
component: terminator
crash_function: remove_capslock_feedback
executable: /usr/bin/python
kernel: 2.6.34.7-56.fc13.x86_64
package: terminator-0.95-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1286959533
uid: 17129

comment
-----
Unfortunately I can't work out how to reproduce this but I thought the backtrace may be useful.

FYI It has crashed in the same way 3 times now - I'll try to crash it more slowly next time so I can remember exactly what happened :P
Comment 1 Andrew Chambers 2010-10-13 09:02:36 UTC 
Created attachment 453118 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:47:57 UTC 
*** Bug 644861 has been marked as a duplicate of this bug. ***
Comment 3 Dominic Hopf 2010-12-11 21:23:02 UTC 
Hi Andrew, thanks very much for reporting this issue. Having a look on the backtrace it doesn't tell me much, unfortunately. Without a way to reproduce I unfortunately am not able to act on this issue. I'm going to close it. Feel free to reopen in case you face it again. :)
Comment 4 Dominic Hopf 2011-03-23 19:06:30 UTC 

*** This bug has been marked as a duplicate of bug 595840 ***