Red Hat Bugzilla – Bug 1027408
[abrt] easytag-2.1.7-3.fc19: gtk_tree_store_get_path: Process /usr/bin/easytag was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-27 08:09:17 EST
Description of problem:
Selected a directory which had been deleted.
Version-Release number of selected component:
runlevel: N 3
var_log_messages: Nov 7 05:27:54 politemadness abrt-hook-ccpp: Saved core dump of pid 19056 (/usr/bin/easytag) to /var/tmp/abrt/ccpp-2013-11-07-05:27:49-19056 (59977728 bytes)
Thread no. 1 (1 frames)
#0 gtk_tree_store_get_path at gtktreestore.c:533
Created attachment 820652 [details]
Created attachment 820653 [details]
Created attachment 820654 [details]
Created attachment 820655 [details]
Created attachment 820656 [details]
Created attachment 820657 [details]
Created attachment 820658 [details]
Created attachment 820659 [details]
Created attachment 820660 [details]
Created attachment 820661 [details]
I tested this with 2.1.8-1, which is currently in updates-testing for F19 (and is in updates for F20):
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?
Just crashed Easytag.
$ rpm -q easytag
1) Have two directories
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
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.
easytag-2.1.9-1.fc19 has been submitted as an update for Fedora 19.
easytag-2.1.9-1.fc20 has been submitted as an update for Fedora 20.
* 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:
then log in and leave karma (feedback).
I tried 2.1.9-1 and it doesn't crash in this same way any more. Thanks.
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.
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.