After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 730326 - segmentation fault in easytag-2.2.2 while parsing hidden directory
segmentation fault in easytag-2.2.2 while parsing hidden directory
Status: RESOLVED FIXED
Product: easytag
Classification: Other
Component: general
2.2.x
Other Linux
: High critical
: 2.2
Assigned To: EasyTAG maintainer(s)
EasyTAG maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-05-18 12:34 UTC by arcctgx
Modified: 2014-05-18 13:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description arcctgx 2014-05-18 12:34:13 UTC 
If the "show hidden directories" option is unchecked, when easytag tries to load a directory located inside a hidden directory, a segfault occurs:

$ mkdir -p .hiddendir/mydir
$ easytag .hiddendir/mydir

(easytag:4419): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion 'iter->stamp == tree_store->stamp' failed

(easytag:4419): Gtk-CRITICAL **: gtk_tree_store_iter_children: assertion 'VALID_ITER (parent, tree_store)' failed

(easytag:4419): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion 'VALID_ITER (iter, tree_store)' failed

(easytag:4419): GLib-GObject-WARNING **: /home/portage/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/gobject/gtype.c:4215: type id '0' is invalid

(easytag:4419): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault

If "show hidden directories" is checked, this does not happen. The other way to trigger this bug is to activate "show hidden directories" option, navigate to a hidden directory and deactivate this option.
Comment 1 David King 2014-05-18 13:31:51 UTC 
Thanks for the bug report. I just fixed this on easytag-2-2 and master branches as 4bfe75daa174c6211e9f01e72c6d06c2051a2db  and 4bfe75daa174c6211e9f01e72c6d06c2051a2db2. The behaviour is not perfect, as the current path is not updated to the first parent which is not a hidden path, but fixing this would need more severe refactoring.