GNOME Bugzilla – Bug 723604
Crash during startup when easytagrc has a non-existent path in default_path_to_mp3
Last modified: 2014-03-13 09:53:26 UTC
Fedora 19 64bit 3.12.6-200.fc19.x86_64 #1 SMP Mon Dec 23 16:33:38 UTC 2013 x86_64 GNU/Linux [peter@localhost ~]$ easytag (easytag:12431): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->stamp == tree_store->stamp' failed (easytag:12431): Gtk-CRITICAL **: gtk_tree_store_iter_children: assertion `VALID_ITER (parent, tree_store)' failed (easytag:12431): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed (easytag:12431): GLib-GObject-WARNING **: gtype.c:4239: type id `0' is invalid (easytag:12431): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced EasyTAG version 2.1.9: Abnormal exit (PID: 12431). Received signal 'Segmentation fault' (11) You have probably found a bug in EasyTAG. Please, file a bug report with a GDB backtrace ('gdb easytag core' then 'bt' and 'l') and information to reproduce it at: https://bugzilla.gnome.org/enter_bug.cgi?product=easytag Segmentation fault (core dumped) -------------------------------------------------------------------------------- [peter@localhost ~]$ gdb easytag core bt l Excess command line arguments ignored. (bt ...) GNU gdb (GDB) Fedora 7.6.1-46.fc19 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/easytag...Reading symbols from /usr/bin/easytag...(no debugging symbols found)...done. (no debugging symbols found)...done. "/home/peter/core" is not a core dump: Is a directory Missing separate debuginfos, use: debuginfo-install easytag-2.1.9-1.fc19.x86_64
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. Thanks in advance!
Installing the 87 Bazillion packages required (Hopefully?) will get back to you.
Thanks! Sorry about the large number of dependencies required for getting a stack trace. it might be sufficient to have just glib2, gtk3 and easytag debuginfo packages installed, but they probably pull in large numbers of dependencies anyway.
This is from ABRT [New LWP 3613] [New LWP 3615] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `easytag'. Program terminated with signal 11, Segmentation fault.
+ Trace 233126
Thread 1 (Thread 0x7f50b22d39c0 (LWP 3613))
Thanks for the stack trace. I cannot immediately see the problem while looking through the code in src/browser.c, so could you get another stack trace? This time, please run gdb and EasyTAG from a terminal, as follows: gdb easytag Then, in gdb: set environment G_DEBUG fatal-criticals run thread apply all bt This should give a stack trace from the first critical warning, which should give a better hint as to what the root cause is. Did you upgrade from 2.1.8 or earlier, and did that version work correctly? In the configuration file ~/.config/easytag/easytagrc is the variable "default_path_to_mp3" set, and what is the value?
Hi David I cannot test this until tonight as the machine is at home. Yes I did upgrade to the latest version a couple of weeks ago and Easytag has been working fine, I use it for all our podcast files. The only thing I can think of is I did a system update a couple of days ago? EasyTag starts, or at least flashes up, on my screen for like one or two milliseconds then crashes. I'm sorry I'm not more skilled to help you. I will send you the info hopefully around 18:30 GMT
Hi Peter It is not a problem if it takes some time to get the information I requested, in fact I appreciate the time that you have spent to get the bug fixed. 2.1.8 was pushed to Fedora 19 on the 18th of January, and 2.1.9 was pushed on the 27th of January: https://admin.fedoraproject.org/updates/FEDORA-2014-0535/easytag-2.1.8-1.fc19 https://admin.fedoraproject.org/updates/FEDORA-2014-1132/easytag-2.1.9-1.fc19 Another update could have caused a problem, but it is more likely that this is an EasyTAG bug. I suspect that it is related to a change to allow browsing of executable paths: https://git.gnome.org/browse/easytag/commit/?id=77485d2b62060f9311a33b4cec820793834a07d9 This change was made between 2.1.8 and 2.1.9, and the crash occurs in the middle of it. Hopefully, the stack trace from the first critical warning will give some extra context that helps to solve the root cause.
Hi Dave? David? How about a Pete explanation? "Umm? When I first installed EasyTag the icon was flat and boring. After the update its curvy and sexy." :-D Right less mucking around and more seriousness. I'll send the stuff when I get home. Pete
Hi Dave Have a serious problem that is probably not connected. My fedora box is horribly broken and I may end up having to wipe it which would mean this bug is dead in the water. I'll know more tonight. I'm really sorry. Pete
Hi Pete I found an entry in the Fedora retrace tracker that looks like it is identical to the problem you found: https://retrace.fedoraproject.org/faf/problems/1530181/ There are only reports from F19 in that retrace, but the sample size is too small to draw anything meaningful from. I hope that you get your Fedora system fixed, as I would like to get to the bottom of this bug (I also suspect that it is, er, inconvenient).
Sadly I blew away the Fedora 19 last night and installed Fedora 20 However I have not installed EasyTag yet and will do that tonight. Lets see if all goes well? I suspect this bug is now closed? Sorry about that.
No problem. Feel free to reopen the bug if it reoccurs on F20.
I just pushed a patch that should avoid this problem in the future: https://git.gnome.org/browse/easytag/commit/?id=15fc326f8eda8f3df86d31d9dd362efae66fd2de I have not yet pushed it as an update to the Fedora package (and I have not encountered it myself, but a Coverity scan helped to pinpoint the problem), but will be making a 2.1.20 release including the fix in the next fortnight.
I have fixed the remainder of the warnings from the problem, after another bug report gave a hint that the bug was related to an invalid default path. The fix is in master: https://git.gnome.org/browse/easytag/commit/?id=aa20526caa45d213cf36b18c27bfbffc3618eccc It will be included in a new 2.1.10 release in the next few days.
Hi David Excellent! I'm glad you squished it. Regards Pete.
Hi Pete The update to 2.1.10 has now been pushed to stable in Fedora 20 (F19 will be updated in another day or two). It might take a little while to show up at the mirrors: https://admin.fedoraproject.org/updates/FEDORA-2014-2863/easytag-2.1.10-1.fc20 If it works for you , please change the status of this bug report from RESOLVED to VERIFIED. Thanks!
Hi David As I say I no longer have the Fedora 19 machine I am now on Fedora 20 and Easytag works fine. Would you like me to set this to? Regards Pete
Hi Pete Ah, if it is working fine for you on Fedora 20 then all is well. Please feel free to report any other bugs that you find. Thanks again