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 307066 - Crash when saving image
Crash when saving image
Status: RESOLVED DUPLICATE of bug 303312
Product: GIMP
Classification: Other
Component: Plugins
2.2.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-06-09 21:02 UTC by Petter Sundlöf
Modified: 2008-01-15 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Petter Sundlöf 2005-06-09 21:02:29 UTC 
Go to http://www.furious.com/perfect/indiedownloads.html

Drag the first image (chriscutler.jpg) to GIMP, and then do Save As...

GIMP now crashes.

Here's stdout:
(22:57:12) peppo@senap:~$ gimp
dcraw -i '/home/peppo/.gimp-2.2/tmp/gimp_temp_104720.jpg'
/home/peppo/.gimp-2.2/tmp/gimp_temp_104720.jpg: unsupported file format.
Segmentation fault
(22:57:29) peppo@senap:~$
(script-fu:10473): LibGimpBase-WARNING **: script-fu: wire_read(): err
Comment 1 weskaggs 2005-06-10 14:49:32 UTC 
Hmm.  A stack trace would be helpful here.  Please do the following:  run the
command "gdb gimp"; at the prompt type "run"; do what it takes to make GIMP
crash; at the prompt type "where"; copy the output you get and put it into this
bug report.

Please also let us know your Linux distro, your Gtk+ version, and where you got
GIMP from -- any of these could be relevant.
Comment 2 Petter Sundlöf 2005-06-10 15:19:55 UTC 
I reckon this info is not very useful.

Program received signal SIGSEGV, Segmentation fault.

+ Trace 60794

Thread NaN (LWP 14986)

  • #0 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #1 gtk_file_folder_get_info
    from /usr/lib/libgtk-x11-2.0.so.0
  • #2 _gtk_file_chooser_entry_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #3 _gtk_file_chooser_entry_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 g_io_condition_get_type
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_io_condition_get_type
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 app_run
  • #13 main
Comment 3 Manish Singh 2005-06-10 16:54:20 UTC 
Are you using the gnome-vfs backend for the file chooser?
Comment 4 Petter Sundlöf 2005-06-10 17:10:04 UTC 
/me points at the debian package.

should I remove this bug and open up a debian one instead?
Comment 5 Manish Singh 2005-06-10 17:22:26 UTC 
Pointing at the debian package doesn't answer the question. If you are using the
gnome-vfs backend, this bug is a duplicate.
Comment 6 Petter Sundlöf 2005-06-10 17:24:45 UTC 
I thought this was dependent on how GIMP was compiled. I had mailed the Debian
GIMP developer ari for an answer to that.

What components decides if I am using the gnome-vfs back for the file chooser?
By the _looks_ of it, it looks like the GNOME file chooser, but I cannot be sure.
Comment 7 Manish Singh 2005-06-10 17:33:03 UTC 
If you're using the full gnome desktop, check the gconf setting:

/desktop/gnome/interface/file_chooser_backend

If that's set to 'gnome-vfs', you are. If it is and you set it to 'gtk+' and
this problem goes away, this is a duplicate bug.
Comment 8 Petter Sundlöf 2005-06-10 17:38:28 UTC 

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