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 695845 - "Reload directory" just unloads it and then fails
"Reload directory" just unloads it and then fails
Status: RESOLVED DUPLICATE of bug 693613
Product: easytag
Classification: Other
Component: general
2.1.x
Other Linux
: Normal minor
: 2.1
Assigned To: EasyTAG maintainer(s)
EasyTAG maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-03-14 13:35 UTC by Oliver Joos
Modified: 2013-03-14 23:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Oliver Joos 2013-03-14 13:35:28 UTC 
I tested 2.1.8 with GTK+ 2. If I click on "Reload Directory" in context menu of a directory then nothing seems to happen. But when I then left-click on the directory then it is reloaded! I guess the context menu entry just unloads the current directory and then something fails. If I start easytag in a terminal then the following messages appear every time "Reload Directory" is clicked:

(easytag:16574): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->stamp == tree_store->stamp' failed
(easytag:16574): Gtk-CRITICAL **: gtk_tree_store_iter_children: assertion `VALID_ITER (parent, tree_store)' failed
(easytag:16574): Gtk-CRITICAL **: gtk_tree_store_get_path: assertion `iter->stamp == tree_store->stamp' failed
Comment 1 David King 2013-03-14 14:55:40 UTC 
Hi, thanks for the bug report. This is almost certainly a duplicate of bug 693613 (or alternatively bug 695749). Please test the patches mentioned in those bugs and see if that fixes the problem for you, as testing with current git master reloads the directory successfully for me.
Comment 2 Oliver Joos 2013-03-14 23:07:51 UTC 
I tested git master and you're right - this bug is already fixed!
Comment 3 Oliver Joos 2013-03-14 23:08:23 UTC 

*** This bug has been marked as a duplicate of bug 693613 ***