Bug 572029 - [abrt] crash in gnote-0.7.1-3.fc13: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnote-0.7.1-3.fc13: Process /usr/bin/gnote was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 572543
Alias: None
Product: Fedora
Classification: Fedora
Component: 0xFFFF
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:913e45b19c65f4855ff1e2e2f56...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-10 03:12 UTC by KEVIN JOHN PANZKE
Modified: 2010-03-12 09:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-12 09:59:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.47 KB, text/plain)
2010-03-10 03:12 UTC, KEVIN JOHN PANZKE 		no flags Details
View All

Description KEVIN JOHN PANZKE 2010-03-10 03:12:04 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=19
component: gnote
executable: /usr/bin/gnote
kernel: 2.6.33-0.52.rc8.git6.fc13.x86_64
package: gnote-0.7.1-3.fc13
rating: 3
reason: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)

How to reproduce
-----
1. DOWNLOAD AMD64 OPEN SOURCE LINUX FEDORA 13.0 ALPHA.
2. BURN IT 2 DISK.
3. INSTALL IT.
4. REBOOT YOUR COMPUTER.
5. COMPLETE POST SETUP.
6. LOGIN 2 COMPUTER.
7. RED ALERT ICON APPEARS IN THE MESSAGE CENTER (INDICATING A CRASH OCCURED).

THE END.
Comment 1 KEVIN JOHN PANZKE 2010-03-10 03:12:06 UTC 
Created attachment 398985 [details]
File: backtrace
Comment 2 Volodymyr Shcherbyna 2010-03-12 09:42:45 UTC 

How to reproduce
-----
1. Install new Fedora 13 alpha
2. Reboot
3. On first start observe crash of package
Comment 3 Rahul Sundaram 2010-03-12 09:59:03 UTC 

*** This bug has been marked as a duplicate of bug 572543 ***
Note You need to log in before you can comment on or make changes to this bug.