Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 554173 - [abrt] crash in gnote-0.7.1-1.fc13
Summary: [abrt] crash in gnote-0.7.1-1.fc13
Keywords:
Status: CLOSED DUPLICATE of bug 568905
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:63891f029dc9129b0bf4b36f34c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-10 19:41 UTC by Zoltan Hoppar
Modified: 2010-02-26 21:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-26 21:09:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (deleted)
2010-01-10 19:41 UTC, Zoltan Hoppar 		no flags Details
View All

Description Zoltan Hoppar 2010-01-10 19:41:23 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1.Open gnote
2.click on a tray icon, select an existing group note
3. program collapses as an puppet


Attached file: backtrace
cmdline: gnote
component: gnote
executable: /usr/bin/gnote
kernel: 2.6.31.9-174.fc12.i686.PAE
package: gnote-0.7.1-1.fc13
rating: 4
reason: Process was terminated by signal 6 (Aborted)
Comment 1 Zoltan Hoppar 2010-01-10 19:41:26 UTC 
Created attachment 382860 [details]
File: backtrace
Comment 2 Rahul Sundaram 2010-01-10 20:32:40 UTC 
Thanks for reporting the crash. It appears debug information is missing however. Please follow 

https://fedoraproject.org/wiki/StackTraces
Comment 3 Adam Williamson 2010-02-26 21:09:48 UTC 
closing as a dupe of my newer bug, since it has what should be a valid backtrace.

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