Bug 1027408

Summary: [abrt] easytag-2.1.7-3.fc19: gtk_tree_store_get_path: Process /usr/bin/easytag was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kerry <mothlight>
Component: easytagAssignee: David King <amigadave>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: amigadave, matthias, mothlight
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/146a98a972ab214a5576c63b7c95f1b50a81e48a
Whiteboard: abrt_hash:df134e4fd9d9c0a5790fc8771fe9e99301dcf8c7
Fixed In Version: easytag-2.1.9-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 05:48:43 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:
Bug Depends On: 1051759    
Bug Blocks:    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Kerry 2013-11-06 18:43:12 UTC 
Description of problem:
Selected a directory which had been deleted.

Version-Release number of selected component:
easytag-2.1.7-3.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        easytag
crash_function: gtk_tree_store_get_path
executable:     /usr/bin/easytag
kernel:         3.11.6-200.fc19.x86_64
runlevel:       N 3
type:           CCpp
uid:            500
var_log_messages: Nov  7 05:27:54 politemadness abrt-hook-ccpp[18871]: Saved core dump of pid 19056 (/usr/bin/easytag) to /var/tmp/abrt/ccpp-2013-11-07-05:27:49-19056 (59977728 bytes)

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 gtk_tree_store_get_path at gtktreestore.c:533
Comment 1 Kerry 2013-11-06 18:43:29 UTC 
Created attachment 820652 [details]
File: backtrace
Comment 2 Kerry 2013-11-06 18:43:32 UTC 
Created attachment 820653 [details]
File: cgroup
Comment 3 Kerry 2013-11-06 18:43:40 UTC 
Created attachment 820654 [details]
File: core_backtrace
Comment 4 Kerry 2013-11-06 18:43:43 UTC 
Created attachment 820655 [details]
File: dso_list
Comment 5 Kerry 2013-11-06 18:43:46 UTC 
Created attachment 820656 [details]
File: environ
Comment 6 Kerry 2013-11-06 18:43:49 UTC 
Created attachment 820657 [details]
File: exploitable
Comment 7 Kerry 2013-11-06 18:43:53 UTC 
Created attachment 820658 [details]
File: limits
Comment 8 Kerry 2013-11-06 18:43:56 UTC 
Created attachment 820659 [details]
File: maps
Comment 9 Kerry 2013-11-06 18:43:59 UTC 
Created attachment 820660 [details]
File: open_fds
Comment 10 Kerry 2013-11-06 18:44:02 UTC 
Created attachment 820661 [details]
File: proc_pid_status
Comment 11 David King 2014-01-16 15:38:44 UTC 
I tested this with 2.1.8-1, which is currently in updates-testing for F19 (and is in updates for F20):

https://admin.fedoraproject.org/updates/FEDORA-2014-0535/easytag-2.1.8-1.fc19

To reproduce, I:

1. started EasyTAG
2. selected a directory in the browser tree
3. in Nautilus, deleted a different directory which was also visible in the EasyTAG browser tree
4. selected the (deleted) directory in the browser tree

I got a popup dialogue which said that the directory was not found, but there was no crash. Can you try with 2.1.8-1 and check if the problem is solved for you?
Comment 12 Kerry 2014-01-16 20:11:52 UTC 
Just crashed Easytag. 
$ rpm -q easytag
easytag-2.1.8-1.fc20.x86_64

1) Have two directories
    a
    x/y/z
2) Select directory z in Easytag
3) Select directory a in Easytag
4) Delete directory tree x/y/z in Nautilus
5) Select directory z in Easytag
6) Easytag tells you 3 times it can't find directory z, then y, then x
7) Crash
Comment 13 David King 2014-01-16 20:35:39 UTC 
Thanks, I was able to reproduce with those steps. The behaviour with 2.1.9 is better, as there is no crash, although the browser tree is inconsistent until the tree is reloaded. I will file an update for 2.1.9 tomorrow.
Comment 14 Fedora Update System 2014-01-17 17:35:00 UTC 
easytag-2.1.9-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/easytag-2.1.9-1.fc19
Comment 15 Fedora Update System 2014-01-17 17:36:23 UTC 
easytag-2.1.9-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/easytag-2.1.9-1.fc20
Comment 16 Fedora Update System 2014-01-19 04:05:44 UTC 
Package easytag-2.1.9-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing easytag-2.1.9-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1118/easytag-2.1.9-1.fc20
then log in and leave karma (feedback).
Comment 17 Kerry 2014-01-20 00:16:21 UTC 
I tried 2.1.9-1 and it doesn't crash in this same way any more. Thanks.
Comment 18 Fedora Update System 2014-01-21 05:48:43 UTC 
easytag-2.1.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 19 Fedora Update System 2014-01-27 13:09:17 UTC 
easytag-2.1.9-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.