Bug 688665 - [abrt] terminator-0.95-2.fc14: remove_capslock_feedback: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] terminator-0.95-2.fc14: remove_capslock_feedback: Process /usr/bin/pyt...
Keywords:
Status: CLOSED DUPLICATE of bug 595840
Alias: None
Product: Fedora
Classification: Fedora
Component: terminator
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e18118a39b3eb14b35d1a504de9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 16:42 UTC by George Tat
Modified: 2011-03-23 19:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-23 19:09:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.02 KB, text/plain)
2011-03-17 16:42 UTC, George Tat
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.