Bug 615011 - [abrt] crash in glista-0.4-3.fc12: gtk_tree_store_get_path: Process /usr/bin/glista was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in glista-0.4-3.fc12: gtk_tree_store_get_path: Process /usr/bin/...
Status: CLOSED DUPLICATE of bug 577846
Alias: None
Product: Fedora
Classification: Fedora
Component: glista   
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:b5c177f0d286ed1c3a8f86497d5...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-15 18:57 UTC by dweb98
Modified: 2010-07-15 20:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-15 20:55:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (26.14 KB, text/plain)
2010-07-15 18:57 UTC, dweb98
no flags Details

Description dweb98 2010-07-15 18:57:12 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: glista
comment: This happens every time on all of my Fedora 12 and 13 installs. If you move to another note before hitting the clear done notes button, it works fine, but not it the note you are clearing is selected. 
component: glista
crash_function: gtk_tree_store_get_path
executable: /usr/bin/glista
global_uuid: b5c177f0d286ed1c3a8f86497d5fba5e928e64f7
package: glista-0.4-3.fc12
rating: 4
reason: Process /usr/bin/glista was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.make a note in glista
2.check that note as done
3.click on clear done notes with the same "done" note selected in the glista window

Comment 1 dweb98 2010-07-15 18:57:14 UTC
Created attachment 432200 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-07-15 20:55:56 UTC

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

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