Bug 752638 - [abrt] gnote-0.7.3-2.fc13: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnote-0.7.3-2.fc13: Process /usr/bin/gnote was killed by signal 11 (SI...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a0b6b677425b47cb7bfb251d1ea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-10 02:05 UTC by phutauruk
Modified: 2011-11-10 19:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 19:22:16 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (44.30 KB, text/plain)
2011-11-10 02:06 UTC, phutauruk
no flags Details

Description phutauruk 2011-11-10 02:05:59 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=19
component: gnote
crash_function: backlinks::BacklinksNoteAddin::update_menu()
executable: /usr/bin/gnote
kernel: 2.6.34.9-69.fc13.i686
package: gnote-0.7.3-2.fc13
rating: 4
reason: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1320890555
uid: 500

How to reproduce
-----
1.
2.
3.
help

Comment 1 phutauruk 2011-11-10 02:06:21 UTC
Created attachment 532707 [details]
File: backtrace

Comment 2 Jake Shipton 2011-11-10 19:22:16 UTC
Thank you for your bug report. 

We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from: 

http://fedoraproject.org/get-fedora

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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