Bug 623982 - [abrt] crash in gnote-0.7.2-1.fc13: elf_dynamic_do_rela: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnote-0.7.2-1.fc13: elf_dynamic_do_rela: Process /usr/bin/gno...
Status: CLOSED DUPLICATE of bug 624650
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:02a54229d4ed8b76306db0af12d...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-13 10:48 UTC by Jeremy Nix
Modified: 2010-11-09 14:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 14:19:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (96.98 KB, text/plain)
2010-08-13 10:48 UTC, Jeremy Nix
no flags Details

Description Jeremy Nix 2010-08-13 10:48:07 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=52
comment: GNote Applet is aprt of my gnome panel.  When I log in the applet has been crashing.  I'm unable to add it back to the panel.
component: gnote
crash_function: elf_dynamic_do_rela
executable: /usr/bin/gnote
global_uuid: 02a54229d4ed8b76306db0af12d395ddf4851b59
package: gnote-0.7.2-1.fc13
rating: 4
reason: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.Log in

Comment 1 Jeremy Nix 2010-08-13 10:48:08 UTC
Created attachment 438647 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:19:38 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:19:38 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 #624650.

Sorry for the inconvenience.

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