Bug 643021 - [abrt] gnote-0.7.2-2.fc14: operator*: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnote-0.7.2-2.fc14: operator*: Process /usr/bin/gnote was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 592157
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c7c82e1e92c44943f0327be5999...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-14 13:25 UTC by Juan Camilo Prada Ojeda
Modified: 2010-11-09 16:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:48:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.10 KB, text/plain)
2010-10-14 13:25 UTC, Juan Camilo Prada Ojeda 		no flags Details
View All

Description Juan Camilo Prada Ojeda 2010-10-14 13:25:31 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=28
comment: It doesnt happen that frequently but it does
component: gnote
crash_function: operator*
executable: /usr/bin/gnote
kernel: 2.6.35.6-39.fc14.x86_64
package: gnote-0.7.2-2.fc14
rating: 4
reason: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1287061199
uid: 500

How to reproduce
-----
1. Click on gnote icon
2. open a note
3. try to print it
Comment 1 Juan Camilo Prada Ojeda 2010-10-14 13:25:35 UTC 
Created attachment 453457 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:48:40 UTC 

*** This bug has been marked as a duplicate of bug 592157 ***
Comment 3 Karel Klíč 2010-11-09 16:48:40 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 #592157.

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