Bug 688665

Summary: [abrt] terminator-0.95-2.fc14: remove_capslock_feedback: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: George Tat <geotri314>
Component: terminatorAssignee: Dominic Hopf <dmaphy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dmaphy, mclasen, steve
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e18118a39b3eb14b35d1a504de9dd205101ffc44
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-23 19:09:53 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 George Tat 2011-03-17 16:42:26 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32786 bytes
cmdline: /usr/bin/python /usr/bin/terminator
component: terminator
Attached file: coredump, 40189952 bytes
crash_function: remove_capslock_feedback
executable: /usr/bin/python
kernel: 2.6.35.10-74.fc14.x86_64
package: terminator-0.95-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300379062
uid: 500

How to reproduce
-----
1.running two instances of rtorrent and mplayer
2.pressed Ctrl+U to view a page's source code
3.and then terminator crashed
Comment 1 George Tat 2011-03-17 16:42:29 UTC 
Created attachment 486061 [details]
File: backtrace
Comment 2 Dominic Hopf 2011-03-22 21:51:34 UTC 
Thanks very much for reporting this issue. Your description to reproduce is not that useful, unfortunately. The back trace looks interesting anyway, seems to me like this is a GTK+ issue, thus I'm changing the component and re-assigning this bug.
Comment 3 Dominic Hopf 2011-03-23 19:09:53 UTC 

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