Description of problem: If defined illegal path in easytagrc/default_path_to_mp3 so application crashes. Version-Release number of selected component: easytag-2.1.9-2.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: easytag crash_function: gtk_tree_model_get_valist executable: /usr/bin/easytag kernel: 3.12.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 gtk_tree_model_get_valist at gtktreemodel.c:1470 #1 gtk_tree_model_get at gtktreemodel.c:1432 #2 Browser_Tree_Select_Dir at src/browser.c:858 #3 Browser_Load_Default_Directory at src/browser.c:273 #4 Init_Load_Default_Dir at src/easytag.c:4234 #9 gtk_main at gtkmain.c:1257 #14 g_application_activate at gapplication.c:1414 #15 et_local_command_line at src/application.c:77 #16 g_application_run at gapplication.c:1585
Created attachment 863797 [details] File: backtrace
Created attachment 863798 [details] File: cgroup
Created attachment 863799 [details] File: core_backtrace
Created attachment 863800 [details] File: dso_list
Created attachment 863801 [details] File: environ
Created attachment 863802 [details] File: exploitable
Created attachment 863803 [details] File: limits
Created attachment 863804 [details] File: maps
Created attachment 863805 [details] File: open_fds
Created attachment 863806 [details] File: proc_pid_status
Created attachment 863807 [details] File: var_log_messages
Thanks for the report. This was already worked around upstream with: https://git.gnome.org/browse/easytag/commit/?id=15fc326f8eda8f3df86d31d9dd362efae66fd2de This will be in a coming 2.1.10 release. Now that I know the cause behind the invalid iter (thanks!), I can avoid the remaining warnings and come up with a complete fix for that release too.
I just fixed this in EasyTAG: https://git.gnome.org/browse/easytag/commit/?id=aa20526caa45d213cf36b18c27bfbffc3618eccc There is now a warning message shown in the log when this occurs, and no critical warnings. I will make an upstream release and new Fedora package in the next few days.
easytag-2.1.10-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/easytag-2.1.10-1.fc20
easytag-2.1.10-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/easytag-2.1.10-1.fc19
easytag-2.1.10-1.fc20 works
Package easytag-2.1.10-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.10-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2863/easytag-2.1.10-1.fc20 then log in and leave karma (feedback).
easytag-2.1.10-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.10-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.