Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 _g_closure_invoke_va at gclosure.c:840
#4 g_signal_emit_by_name at gsignal.c:3426
#5 gtk_tree_view_row_deleted at gtktreeview.c:9174
#10 gtk_tree_model_row_deleted at gtktreemodel.c:1867
#11 gtk_list_store_remove at gtkliststore.c:1230
#12 gtk_list_store_clear at gtkliststore.c:1444
Created attachment 901005 [details]
Created attachment 901006 [details]
Created attachment 901007 [details]
Created attachment 901008 [details]
Created attachment 901009 [details]
Created attachment 901010 [details]
Created attachment 901011 [details]
Created attachment 901012 [details]
Created attachment 901013 [details]
Created attachment 901014 [details]
Created attachment 901015 [details]
This bug is currently being discussed on the EasyTAG mailing list:
I am a bit busy at the moment, but hopefully there should be a complete fix soon (which will likely be rolled into a new 2.2.3 release).
The latest 2.2.3 release should solve this bug:
easytag-2.2.3-1.fc19 has been submitted as an update for Fedora 19.
easytag-2.2.3-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.2.3-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
easytag-2.2.3-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.2.3-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.