GNOME Bugzilla – Bug 688554
GIMP crashes if a key is pressed in module manager
Last modified: 2012-11-17 22:12:07 UTC
When I press any input key (such as 'a' or '3' rather than any of the arrow keys, function keys, arrow keys, etc) and I have an item in the module selected gimp will crash. 1. Edit -> Modules 2. Select any item (you don't have to check or uncheck it) 3. Press an alphanumeric or symbolic key. 4. GIMP crashes. The following is then output to the console: (gimp:8578): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed (gimp:8578): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.34.0/./gobject/gtype.c:4204: type id `0' is invalid (gimp:8578): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced (script-fu:8585): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error I have gotten this issue on Windows 7: GNU Image Manipulation Program version 2.8.2 git-describe: GIMP_2_8_0-194-ga42a02e using GEGL version 0.2.0 (compiled against version 0.2.0) using GLib version 2.32.3 (compiled against version 2.32.3) using GdkPixbuf version 2.26.1 (compiled against version 2.26.1) using GTK+ version 2.24.10 (compiled against version 2.24.10) using Pango version 1.30.0 (compiled against version 1.30.0) using Fontconfig version 2.9.0 (compiled against version 2.9.0) using Cairo version 1.10.2 (compiled against version 1.10.2) as well as Ubuntu 12.10: GNU Image Manipulation Program version 2.8.2 git-describe: GIMP_2_8_0-194-ga42a02e using GEGL version 0.2.0 (compiled against version 0.2.0) using GLib version 2.34.0 (compiled against version 2.33.12) using GdkPixbuf version 2.26.4 (compiled against version 2.26.3) using GTK+ version 2.24.13 (compiled against version 2.24.12) using Pango version 1.30.1 (compiled against version 1.30.1) using Fontconfig version 2.10.1 (compiled against version 2.10.1) using Cairo version 1.12.2 (compiled against version 1.12.2)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 682585 ***