Bug 651627

Summary: [abrt] terminator-0.95-2.fc13: remove_capslock_feedback: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ahmad Zulkarnain <sniffit>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f78402f4ac767e0cd149213953aa85be6fddfa4a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-11 21:18:03 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 Ahmad Zulkarnain 2010-11-09 22:48:11 UTC 
abrt version: 1.1.13
architecture: i686
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-61.fc13.i686.PAE
package: terminator-0.95-2.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1289319744
uid: 500
Comment 1 Ahmad Zulkarnain 2010-11-09 22:48:15 UTC 
Created attachment 459279 [details]
File: backtrace
Comment 2 Dominic Hopf 2010-11-19 23:22:45 UTC 
Hi Ahmad,

I'm very sorry for my late reaction on this. Is there any chance to get this issue reproduced? Do you remember what you did when this crash occurred?

Regards,
Dominic
Comment 3 Ahmad Zulkarnain 2010-11-20 02:01:43 UTC 
Hi Dominic,

I wish I could reproduce the bug but so far I have been unsuccessful. What I remember roughly is that the application was running with multiple tabs connecting to different SSH sessions. 

Will advise further if I am able to replicate the crash.
Comment 4 Dominic Hopf 2010-12-11 21:18:03 UTC 
Hi Ahmad, since I didn't heard of you in the meantime, I'll close this bug for now. Please feel free to reopen in case you face this issue again and are able to reproduce it. :)
Comment 5 Dominic Hopf 2011-03-23 19:11:33 UTC 

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