Bug 706417

Summary: [abrt] easytag-2.1.6-5.fc14: gtk_tree_store_get_path: Process /usr/bin/easytag was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Walter <Zscoundrel>
Component: easytagAssignee: Matthias Saou <matthias>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: matthias
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:423e91f8a9c94e09e2fce993a33a9ee64a87c623
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 15:05:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Walter 2011-05-20 14:04:33 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 17529 bytes
cmdline: easytag
comment: I selected a different directory from the directory list.  This directory was empty as the files had been moved.  The application crashed.
component: easytag
Attached file: coredump, 5283840 bytes
crash_function: gtk_tree_store_get_path
executable: /usr/bin/easytag
kernel: 2.6.35.13-91.fc14.i686.PAE
package: easytag-2.1.6-5.fc14
rating: 4
reason: Process /usr/bin/easytag was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1305853399
uid: 500

How to reproduce
-----
1. selected a different directory from the directory list. 
2. This directory was empty as the files had been moved. 
3.

Comment 1 Walter 2011-05-20 14:04:35 UTC
Created attachment 500064 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 15:05:55 UTC
Backtrace analysis found this bug to be similar to bug #739341, closing as duplicate.

Bugs which were found to be similar to this bug: bug #637452, bug #739341

This comment is automatically generated.

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