GNOME Bugzilla – Bug 712582
Crash on directory selection
Last modified: 2017-08-25 20:10:30 UTC
I'm on Kubuntu 13.10, x86_64. When I try to start a directory comparison, I press the Directory comparison button on the main scree, and then try to select one of the directories to compare by choosing Other in one of the combo-boxes below. Then Meld crashes with the following backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00007f94861edd05 in IA__gtk_tree_model_get_valist (tree_model=tree_model@entry=0x1a01c20, iter=iter@entry=0x7fff3ba5eba0, var_args=var_args@entry=0x7fff3ba5ea48) at /build/buildd/gtk+2.0-2.24.20/gtk/gtktreemodel.c:1470 1470 /build/buildd/gtk+2.0-2.24.20/gtk/gtktreemodel.c: No such file or directory. (gdb) thread apply all bt
+ Trace 232791
Thread 1 (Thread 0x7f948919a740 (LWP 6215))
The problem doesn't happen if I try individual file comparison instead (the combo-box opens the standard file selection dialogue).
Forgot to mention that Meld version is 1.8.1.
Does this happen every time? If you run Meld from a terminal, do you get a Python traceback? Unfortunately the stack trace doesn't really help much.
Yes, it happens every time. The console output is as follows: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed gtk.main() /usr/bin/meld:167: Warning: /build/buildd/glib2.0-2.38.1/./gobject/gtype.c:4215: type id '0' is invalid gtk.main() /usr/bin/meld:167: Warning: can't peek value table for type '<invalid>' which is not currently referenced gtk.main() Segmentation fault (core dumped)
Sorry for the delay. I'm pretty sure that what you're seeing is a bug in GTK or the oxygen theme, take your pick. Either way, the crash isn't anywhere in Meld, so I'm going to close this. This bug sounds like the problem you're seeing: https://bugs.kde.org/show_bug.cgi?id=326424 Thanks anyway for the bug report.
*** Bug 738250 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 729651 ***