GNOME Bugzilla – Bug 697870
Gimp crashes when directory being displayed changes
Last modified: 2018-04-15 00:28:14 UTC
Annoyingly not consistent, but has happened twice this week, so evidently not just transient. How to reproduce: File->Open Navigate to a directory containing picture files. Rename one of the files in the directory. Gimp crashes with the following messages: ----------------------------------------------------------- (gimp:24309): Gimp-Core-CRITICAL **: gimp_drawable_get_floating_sel: assertion `GIMP_IS_DRAWABLE (drawable)' failed (gimp:24309): Gimp-Core-CRITICAL **: gimp_drawable_get_floating_sel: assertion `GIMP_IS_DRAWABLE (drawable)' failed Connection closed by server ** Gtk:ERROR:/build/buildd/gtk+2.0-2.24.10/gtk/gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion failed: (r == n_visible_rows) gimp: terminated: Aborted (script-fu:24313): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error Connection closed by server ---------------------------------------------------------------- In case it's significant, the files I renamed were RAW files.
Update: just spotted how to reproduce. Multi-select several files, then rename one of the selected files. This seems to be what kills the program.
Ok this is clearly a GtkFileChooser problem, I'm moving this bug to GTK+. But, there are these gimp_drawable_get_floating_sel warnings, can you please file a separate bug about these if you find a way to reproduce them?
OK, I'll have a play when I've finished the task I'm working on.
(In reply to comment #1) > Update: just spotted how to reproduce. > > Multi-select several files, then rename one of the selected files. This seems > to be what kills the program. That doesn't kill my testfilechooser here. Stacktrace needed.
oh, I was testing in gtk master. It does indeed crash in gtk 2.24
Created attachment 241467 [details] stacktrace
A fix for this seems to have been pushed to 3.6 an up see bug #687196
*** Bug 672887 has been marked as a duplicate of this bug. ***
*** Bug 680521 has been marked as a duplicate of this bug. ***
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new