Bug 651839 - [abrt] gkrellm-2.3.4-3.fc14: raise: Process /usr/bin/gkrellm was killed by signal 6 (SIGABRT)
Summary: [abrt] gkrellm-2.3.4-3.fc14: raise: Process /usr/bin/gkrellm was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 709860
Alias: None
Product: Fedora
Classification: Fedora
Component: pango
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cc7465f0e2133d32e7896780674...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 12:26 UTC by leandro
Modified: 2012-03-20 16:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:39:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (11.06 KB, text/plain)
2010-11-10 12:26 UTC, leandro
no flags Details

Description leandro 2010-11-10 12:26:50 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gkrellm
component: gkrellm
crash_function: raise
executable: /usr/bin/gkrellm
kernel: 2.6.35.6-48.fc14.i686.PAE
package: gkrellm-2.3.4-3.fc14
rating: 4
reason: Process /usr/bin/gkrellm was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289389045
uid: 500

How to reproduce
-----
1. /configuration/plugins
2. try to de-check gkrellmtop plugin
3. explosion!

Comment 1 leandro 2010-11-10 12:26:53 UTC
Created attachment 459425 [details]
File: backtrace

Comment 2 Hans de Goede 2010-11-11 12:22:02 UTC
Hmm,

I cannot reproduce this I'm afraid (F-14 x86_64), and the crash seems to be deep in pango. Maybe the pango maintainer has some idea what is causing this, changing component.

Regards,

Hans

Comment 3 abrt-bot 2012-03-20 16:39:07 UTC
Backtrace analysis found this bug to be similar to bug #709860, closing as duplicate.

Bugs which were found to be similar to this bug: 
  gkrellm: bug #660333, bug #709860
  gkrellm-weather: bug #628207

This comment is automatically generated.

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


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