GNOME Bugzilla – Bug 305588
Saving twice into a non-readable dir crashes GIMP
Last modified: 2008-01-15 12:54:59 UTC
Version details: gimp-2.2.7-4 Distribution/Version: Fedora Core 4 test Have a directory you own that has permissions d-wx------. The relevant part is that you have write and execute permissions for it, but no read permission. Save an image there under any name. Use fe. JPEG format. Then choose Save As to save again. GIMP now crashes either immediately, or shows errors on stderr and crashes after you've done some UI clicking. Works also with other image formats, at least XCF. This is reproducible for me. Happens on my Athlon64 as well as on a 32 bit Athlon.
Works for me, no problem whatsoever. Tested with GIMP 2.2 and 2.3. Can you please tell us what version of GTK+ you are using (try to upgrade if possible) and please do also paste those error message that appear on stderr.
Gtk 2.6.7-4 from FC's rpm. The errors on stderr vary even between seemingly identical invokations, but one run I got these when opening the save dialog for the second time: (gimp:5721): GLib-GObject-WARNING **: gsignal.c:2319: signal name `files-removed' is invalid for instance `0x211ab10' (gimp:5721): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed And these when clicking on its Save button: (gimp:5721): GLib-GObject-WARNING **: invalid cast from `(null)' to `GtkFileFolder' (gimp:5721): GLib-GObject-WARNING **: invalid cast from `(null)' to `GtkFileFolderGnomeVFS' (gimp:5721): GLib-GObject-WARNING **: gsignal.c:2319: signal name `files-added' is invalid for instance `0x211ab10' (gimp:5721): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gimp:5721): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed After creating two more pictures and saving them, gimp crashed with: (script-fu:5723): LibGimpBase-WARNING **: script-fu: wire_read(): error Segmentation fault I could give proper stack traces if somebody tells me how to use Redhat's debuginfo rpm's :)
Figured out the debuginfo thing. Here's a backtrace of a crash such as the one described in the previous comment:
+ Trace 60251
I would suggest reporting this to RedHat's Bugzilla, since it may well have been caused by something the Fedora developers changed in Gtk+. This is the default assumption until somebody else on a different system replicates the problem.
Samuli, did you do what was suggested in comment #4? What is the corresponding Redhat bug number?
The bug is 159027 in RedHat's bugzilla.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159027 BTW, your bug report there is pretty useless - you should have at least provided a link to this one here.
There is a link to this bug, see section "External Bugzilla References".
Hm, pretty easy to overlook this - they should consider to have it add a comment automatically.
Samuli, what's the status of this?
Still happens. Libs are the latest stuff in FC4. Athlon64. Gimp 2.2.10.
There's not much activity in the Redhat bug. Can anyone else reproduce this on Fedora?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Michael asked for. Thanks very much in advance!