Bug 644861 - [abrt] terminator-0.95-2.fc13: remove_capslock_feedback: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] terminator-0.95-2.fc13: remove_capslock_feedback: Process /usr/bin/pyt...
Keywords:
Status: CLOSED DUPLICATE of bug 595840
Alias: None
Product: Fedora
Classification: Fedora
Component: terminator
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:573d290143001569699de96bdce...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-20 13:30 UTC by Andrew Chambers
Modified: 2011-03-23 19:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:47:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (30.29 KB, text/plain)
2010-10-20 13:30 UTC, Andrew Chambers 		no flags Details
View All

Description Andrew Chambers 2010-10-20 13:30:25 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/terminator
comment: Terminator crashed and I was not even using it... A python bug?
component: terminator
crash_function: remove_capslock_feedback
executable: /usr/bin/python
kernel: 2.6.34.7-56.fc13.x86_64
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: 1287581354
uid: 17129
Comment 1 Andrew Chambers 2010-10-20 13:30:31 UTC 
Created attachment 454571 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:47:57 UTC 

*** This bug has been marked as a duplicate of bug 642523 ***
Comment 3 Karel Klíč 2010-11-08 17:47:57 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #642523.

Sorry for the inconvenience.
Comment 4 Dominic Hopf 2011-03-23 19:06:15 UTC 

*** This bug has been marked as a duplicate of bug 595840 ***
Note You need to log in before you can comment on or make changes to this bug.