Bug 613488 - [abrt] crash in gnote-0.7.2-1.fc13: raise: Process /usr/bin/gnote was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnote-0.7.2-1.fc13: raise: Process /usr/bin/gnote was killed ...
Status: CLOSED DUPLICATE of bug 607024
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:80529a19e3f462eaf55ce70e1b5...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-12 01:14 UTC by jackonweb
Modified: 2010-11-09 14:54 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
File: backtrace (32.00 KB, text/plain)
2010-07-12 01:14 UTC, jackonweb
no flags Details

Description jackonweb 2010-07-12 01:14:09 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=24
component: gnote
crash_function: raise
executable: /usr/bin/gnote
global_uuid: 80529a19e3f462eaf55ce70e1b57bb4928385be5
kernel: 2.6.33.5-124.fc13.i686
package: gnote-0.7.2-1.fc13
rating: 4
reason: Process /usr/bin/gnote was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 jackonweb 2010-07-12 01:14:13 UTC
Created attachment 431043 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:54:42 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:54:42 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 #607024.

Sorry for the inconvenience.


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