GNOME Bugzilla – Bug 683983
Gimp crashes on exporting JPEG files (probably related to Exif data)
Last modified: 2013-04-26 08:43:12 UTC
Using Ubuntu 12.0.4 and Gimp 2.8.2 After editing and image save .xcf ok but on exporting to .jpg save is completed and gimp then shuts down/crashes. Command line log : ....@rdg-desktop:~$ gimp While parsing XMP metadata: Error on line 45 char 1: End of element <exif:Flash> not expected in this context While parsing XMP metadata: Error on line 61 char 1: End of element <exif:Flash> not expected in this context Metadata parasite seems to be corrupt While parsing XMP metadata: Error on line 45 char 1: End of element <exif:Flash> not expected in this context ** (file-jpeg:6651): WARNING **: JPEG - unable to decode XMP metadata packet (gimp:6606): Gimp-Core-CRITICAL **: _gimp_unit_get_factor: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed (gimp:6606): Gimp-Core-CRITICAL **: _gimp_unit_get_digits: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed (gimp:6606): Gimp-Core-CRITICAL **: _gimp_unit_get_factor: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed (gimp:6606): Gimp-Core-CRITICAL **: _gimp_unit_get_digits: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed (gimp:6606): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed (script-fu:6612): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error Segmentation fault (core dumped) ....@rdg-desktop:~$ Gimp restarts OK but problem is repeated with next image. Help will be appreciated Roger
*** Bug 684287 has been marked as a duplicate of this bug. ***
I have never seens this, we need a stack trace of this warning: gimp:6606): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed I have no clue either where the unit warnings are coming from. Please run GIMP in gdb with the --g-fatal-warnings option and attach the stack trace, if possible find an image that doesn't trigger the unit warnings, they are probably unrelated.
Roger, please provide the information I asked for in comment 2.
Hi Michael Sorry I have not replied before however being an amateur at these things I have not managed to do what you asked: "run GIMP in gdb with the --g-fatal-" Any chance of an idiots guide to this process. Thank you Roger
Install gtk's and gimp's debug packages from your distribution. run gimp like this: "gdb --args gimp-2.8 --g-fatal-warnings" at the gdb prompt: "run" reproduce the error, it will stop at the first Gimp-Core-CRITICAL say "c" at the gdb prompt until you hit the Gtk-CRITICAL say "bt" at the gdb prompt attach the stack trace to this bug
Mike, I followed your instructions and I have been unable to recreate the blow up. For your documentation this is the output of the debugging session. gdb --args gimp-2.8 --g-fatal-warnings GNU gdb (GDB) Fedora (7.4.50.20120120-50.fc17) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gimp-2.8...Reading symbols from /usr/lib/debug/usr/bin/gimp-2.8.debug...done. done. (gdb) run Starting program: /usr/bin/gimp-2.8 --g-fatal-warnings [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb652cb40 (LWP 5147)] [New Thread 0xb5bffb40 (LWP 5148)] [New Thread 0xb53feb40 (LWP 5149)] Detaching after fork from child process 5150. [New Thread 0xadb1ab40 (LWP 5152)] [New Thread 0xad1ffb40 (LWP 5153)] [Thread 0xadb1ab40 (LWP 5152) exited] Detaching after fork from child process 5158. [Thread 0xad1ffb40 (LWP 5153) exited] [New Thread 0xad1ffb40 (LWP 5177)] [New Thread 0xadb1ab40 (LWP 5178)] [Thread 0xad1ffb40 (LWP 5177) exited] [Thread 0xadb1ab40 (LWP 5178) exited] [New Thread 0xadb1ab40 (LWP 5184)] [New Thread 0xad1ffb40 (LWP 5185)] Detaching after fork from child process 5186. [Thread 0xad1ffb40 (LWP 5185) exited] [Thread 0xadb1ab40 (LWP 5184) exited] [New Thread 0xadb1ab40 (LWP 5189)] [New Thread 0xad1ffb40 (LWP 5192)] [New Thread 0xac774b40 (LWP 5193)] [New Thread 0xabf73b40 (LWP 5194)] [New Thread 0xab772b40 (LWP 5195)] [Thread 0xab772b40 (LWP 5195) exited] [Thread 0xabf73b40 (LWP 5194) exited] [Thread 0xac774b40 (LWP 5193) exited] [Thread 0xadb1ab40 (LWP 5189) exited] [Thread 0xad1ffb40 (LWP 5192) exited] [New Thread 0xad1ffb40 (LWP 5217)] [New Thread 0xadb1ab40 (LWP 5218)] [Thread 0xad1ffb40 (LWP 5217) exited] [New Thread 0xad1ffb40 (LWP 5221)] [New Thread 0xac774b40 (LWP 5222)] Detaching after fork from child process 5223. [Thread 0xadb1ab40 (LWP 5218) exited] [Thread 0xac774b40 (LWP 5222) exited] [Thread 0xad1ffb40 (LWP 5221) exited] [New Thread 0xad1ffb40 (LWP 5224)] [Thread 0xad1ffb40 (LWP 5224) exited] [New Thread 0xad1ffb40 (LWP 5259)] [New Thread 0xac774b40 (LWP 5260)] [Thread 0xac774b40 (LWP 5260) exited] [Thread 0xb5bffb40 (LWP 5148) exited] [Thread 0xad1ffb40 (LWP 5259) exited] [Thread 0xb53feb40 (LWP 5149) exited] [Thread 0xb652cb40 (LWP 5147) exited] [Inferior 1 (process 5143) exited normally] Missing separate debuginfos, use: debuginfo-install GConf2-3.2.5-3.fc17.i686 OpenEXR-libs-1.7.0-4.fc17.i686 PackageKit-0.7.5-1.fc17.i686 SDL-1.2.14-16.fc17.i686 atlas-3.8.4-3.fc17.i686 expat-2.1.0-1.fc17.i686 gamin-0.1.10-12.fc17.i686 gtk2-engines-2.20.2-4.fc17.i686 gvfs-1.12.3-1.fc17.i686 ilmbase-1.0.2-4.fc17.i686 libXau-1.0.6-3.fc17.i686 libXcomposite-0.4.3-3.fc17.i686 libXdamage-1.1.3-3.fc17.i686 libXi-1.6.1-1.fc17.i686 libXinerama-1.1.2-1.fc17.i686 libXrandr-1.3.1-3.fc17.i686 libXrender-0.9.7-1.fc17.i686 libbluray-0.2.3-1.fc17.i686 libcanberra-0.28-6.fc17.i686 libcanberra-gtk2-0.28-6.fc17.i686 libcroco-0.6.5-1.fc17.i686 libffi-3.0.10-2.fc17.i686 libgcc-4.7.2-2.fc17.i686 libgfortran-4.7.2-2.fc17.i686 libogg-1.3.0-1.fc17.i686 libopenraw-0.0.9-1.fc17.i686 libquadmath-4.7.2-2.fc17.i686 libselinux-2.1.10-3.fc17.i686 libstdc++-4.7.2-2.fc17.i686 libtdb-1.2.10-15.fc17.i686 libtool-ltdl-2.4.2-3.1.fc17.i686 libvorbis-1.3.3-1.fc17.i686 libxcb-1.8.1-1.fc17.i686 nss-softokn-freebl-3.13.5-1.fc17.i686 pixman-0.24.4-2.fc17.i686 suitesparse-3.6.1-3.fc17.i686 (gdb) I know quite a few things have changed since I reported this bug. I know I am at a new Kernel 3.6.2. I think I am at the same level of gimp. Here is my installed version. I will keep the instructions, if the blows up again. - Raj Installed Packages Name : gimp Arch : i686 Epoch : 2 Version : 2.8.2 Release : 1.fc17 Size : 59 M Repo : installed From repo : updates Summary : GNU Image Manipulation Program URL : http://www.gimp.org/ License : GPLv3+ Description : GIMP (GNU Image Manipulation Program) is a powerful image : composition and editing program, which can be extremely useful for : creating logos and other graphics for webpages. GIMP has many of : the tools and filters you would expect to find in similar : commercial offerings, and some interesting extras as well. GIMP : provides a large image manipulation toolbox, including channel : operations and layers, effects, sub-pixel imaging and : anti-aliasing, and conversions, all with multi-level undo.
Thanks Raj! Roger, is the bug gone for you too on 2.8.2?
Michael Thank you. I have edited 6 pics with no problems so I think I can say yes, the bug has gone. regards Roger
Created attachment 226591 [details] GDB output for GIMP crash Comments made in bug report section
Michael Sorry I spoke too soon. I have just done several more picture edits and the GIMP started crashing on ctrl-e to export an image. The image does appear to be saved ok but the program freezes for a while and then crashes. However I did manage to repeat the problem with gdb running so a copy of the output is attached. At the first crash this evening some small windows appeared suggesting that Ubuntu had a system error - I have seen a few of these recently since we went to 12.04. I caught one of the messages as "Application - upgrade.py - closed unexpectedly. I trust this info will be helpful. Roger
Is there a way you can post a simple picture and I will try to recreate on Fedora 17?
Created attachment 226626 [details] The image being saved when GIMP crashed I opened three images and chose this one to edit. After cropping, resizing, changing levels and then exporting GIMP crashed closing all images. The three images were successive images from the same camera. This is the edited image since the original is too large to attach. I can make it available on a URL if necessary. Roger
Created attachment 226631 [details] gdb output re crash when saving previous image
I tried with several images on my workstation. One that was created RAW and then converted to JPEG by GIMP or a helper app. I tried one that my Canon 30D shot and converted to JPEG in the camera. I tried your image, Roger (nice shot, BTW) that you successfully attached. I did crop, rescale to 200% and export to JPEG. It didn't blow up. I think the problem is with large images. I shoot with 8.2 Megapixels and create JPEGs that around 10 MB in size. I am still not sure how to re-create this, and will keep trying as time allows. - Raj Upadhyaya
Thanks Roger, but there is no stack trace in that gdb log. say: "run --g-fatal-warnings" and when it stops at the first, unit related warnings, say "c" at the gdb prompt. When you hit this warning: (gimp:3847): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed say "bt", and paste the resulting stack trace here.
Created attachment 226655 [details] GDB report as requested I have run GIMP as requested and attach the stack trace. However, GIMP failed at an earlier stage when I called the 'scale image' routine (I use ctrl-k). I will attach a screen grab of that stage for information. I will also try GIMP again and see where I get to.
Created attachment 226656 [details] screen grab at point of failure
Created attachment 226677 [details] GIMP crash on 'e' export GIMP continues to fail at scale image process so I have loaded an image and gone straight to 'export' and the failure occurred there. The critical warning (Gimp:3388)came up rather than the (Gimp:3847) suggested. What I believe to be the stack trace is attached for info. Regards Roger
Using GIMP again today, crash on 'export' continues - the file is saved OK. However I have just done another 2 where I have done a second edit to a previously 'exported' image and this has 'exporte' without problem. GIMP continued to run normally. When then exporting a new image the crash reoccurred.
Another clue that might be useful. In the majority of crashes mentioned above, during the 'export' routine I ahve 'named' the image file by clicking on a previous image and amending a digit in the name box. However I have just 'exported' 2 images and entered the image title in full in the 'name' box. This process did not result in a crash! Reverting to the 'click and amend' process induced the crash.
After working fine for a few days problems returned again today. Initially crashing after exporting an edited image file. I then ran the gdb process as mentioned above and the crash occurred this time as I used the 'scale image' function. I use 'ctrl k' as a keyboard shortcut to call this function. The gdb output is below.... (gimp-2.8:3693): Gimp-Core-CRITICAL **: _gimp_unit_get_factor: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed Program received signal SIGTRAP, Trace/breakpoint trap. 0xb732f69d in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 (gdb) c Continuing. (gimp-2.8:3693): Gimp-Core-CRITICAL **: _gimp_unit_get_digits: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed Program received signal SIGTRAP, Trace/breakpoint trap. 0xb732f69d in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 (gdb) bt
+ Trace 231128
The crash on (gimp:6606): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed is actually a duplicate of bug 681845, but you seem to get crashes on (gimp-2.8:3693): Gimp-Core-CRITICAL **: _gimp_unit_get_digits: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed Is this correct? If so, please give instructions how exactly to reproduce it, attach a small sample image and your unitrc file.
Roger, please provide the information I asked for in comment 22.
Created attachment 228839 [details] small image used in crash routine I loaded an image and cropped it to save a small image OK. Restarted GDB GIMP and loaded this image. Crash occurred on selecting 'scale image' from menu. This image 'graphic06.jpg' is attached. All the terminal output is below. I cannot find a 'unitrc' file. Perhaps you can advise on that. roger@rdg-desktop:~$ gdb gimp GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/gimp...Reading symbols from /usr/lib/debug/usr/bin/gimp-2.8...done. done. (gdb) run --g-fatal-warnings Starting program: /usr/bin/gimp --g-fatal-warnings [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb65f7b40 (LWP 7110)] [New Thread 0xb5bffb40 (LWP 7111)] [New Thread 0xb51ffb40 (LWP 7112)] [New Thread 0xb49feb40 (LWP 7113)] [New Thread 0xb3b46b40 (LWP 7114)] [New Thread 0xb0113b40 (LWP 7118)] [New Thread 0xaf912b40 (LWP 7119)] [New Thread 0xaf111b40 (LWP 7120)] [New Thread 0xae910b40 (LWP 7121)] [New Thread 0xae10fb40 (LWP 7122)] [New Thread 0xad90eb40 (LWP 7123)] [New Thread 0xad10db40 (LWP 7124)] [New Thread 0xac90cb40 (LWP 7125)] [New Thread 0xac10bb40 (LWP 7126)] [Thread 0xad90eb40 (LWP 7123) exited] [Thread 0xaf111b40 (LWP 7120) exited] [Thread 0xac90cb40 (LWP 7125) exited] [Thread 0xae910b40 (LWP 7121) exited] [Thread 0xb3b46b40 (LWP 7114) exited] [Thread 0xae10fb40 (LWP 7122) exited] [Thread 0xb0113b40 (LWP 7118) exited] [Thread 0xaf912b40 (LWP 7119) exited] [Thread 0xac10bb40 (LWP 7126) exited] [New Thread 0xac10bb40 (LWP 7127)] [New Thread 0xaf912b40 (LWP 7128)] [Thread 0xaf912b40 (LWP 7128) exited] [Thread 0xad10db40 (LWP 7124) exited] While parsing XMP metadata: Error on line 61 char 1: End of element <exif:Flash> not expected in this context While parsing XMP metadata: Error on line 77 char 1: End of element <exif:Flash> not expected in this context Metadata parasite seems to be corrupt While parsing XMP metadata: Error on line 61 char 1: End of element <exif:Flash> not expected in this context ** (file-jpeg:7129): WARNING **: JPEG - unable to decode XMP metadata packet (gimp:7107): Gimp-Core-CRITICAL **: _gimp_unit_get_factor: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed Program received signal SIGTRAP, Trace/breakpoint trap. 0xb732f69d in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 (gdb) c Continuing. (gimp:7107): Gimp-Core-CRITICAL **: _gimp_unit_get_digits: assertion `unit < (GIMP_UNIT_END + gimp->n_user_units)' failed Program received signal SIGTRAP, Trace/breakpoint trap. 0xb732f69d in g_logv () from /lib/i386-linux-gnu/libglib-2.0.so.0 (gdb) bt
+ Trace 231169
This is th output from gimp 2.8.2 on a Debian testing: gimp --g-fatal-warnings (gimp:7875): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed (script-fu:7943): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error `trap' para punto de parada/seguimiento
caralu, as you sure that this is the same problem?
Yes. Under gnome3 it crash. But under KDE work nice. I can edit and export a jpg file without troubles.
Under Win7 work nice as well.
Caralu, try disabling the gnome3 accessibility stuff, I think I have seen this before, and it was a GTK+ problem.
I have tested again to export to jpg and png under Gnome 3 and crash. So I suppose it is matter of GTK or Gnome.
I do not see any gnome3 accessibility stuff running on system monitor.
Carulu, you are seeing bug #681845 which is fixed in GTK+ 2.24.14, please upgrade your GTK+.
So are all of caralu's comments unrelated to this bug?
Yes.
Does comment #24 provide enough information to proceed?
My gimp has been crashing every time I try to export. It doesn't seem to matter how I go about it or what type of export type I choose. I've tried to understand this long bugzilla record without much success. I tried your comment "Install gtk's and gimp's debug packages from your distribution. run gimp like this: "gdb --args gimp-2.8 --g-fatal-warnings" at the gdb prompt: "run" reproduce the error, it will stop at the first Gimp-Core-CRITICAL say "c" at the gdb prompt until you hit the Gtk-CRITICAL say "bt" at the gdb prompt attach the stack trace to this bug" I've looked at what I have installed and I don't see which gtk and gimp debug packages I should look for. So I tried running the command. I ran it as you suggest, and here is the record. In fact gimp crashed when I tried to export the image, but this is what I got. $ gdb --args gimp-2.8 --g-fatal-warnings GNU gdb (GDB) Fedora (7.4.50.20120120-52.fc17) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gimp-2.8...(no debugging symbols found)...done. Missing separate debuginfos, use: debuginfo-install gimp-2.8.4-1.fc17.x86_64 (gdb) run Starting program: /usr/bin/gimp-2.8 --g-fatal-warnings [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe52f7700 (LWP 4756)] [Thread 0x7fffe52f7700 (LWP 4756) exited] [Inferior 1 (process 4753) exited normally] (gdb) c The program is not being run. (gdb) It may be that I don't have the right debug packages installed. If so, tell me which ones I need, and be very explicit. Please tell me what I did wrong and tell me exactly what I should do to get useful information.
I should have added that I am running gimp 2.4.8 under Fedora 17 Linux
You seem to do the right thing but it looks like the crash didn't happen in that GIMP session. I don't see any warning in comment 37 either, and what GTK+ version are you running?
gtk+-1.2.10-72.fc17.x86_64 The crash did happen. But I see it told me to run debuginfo-install gimp-2.8.4-1.fc17.x86_64 I am going to try that.
After running debuginfo_install, I tried it again, and this time I got $ gdb --args gimp-2.8 --g-fatal-warnings GNU gdb (GDB) Fedora (7.4.50.20120120-52.fc17) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gimp-2.8...Reading symbols from /usr/lib/debug/usr/bin/gimp-2.8.debug...done. done. (gdb) run Starting program: /usr/bin/gimp-2.8 --g-fatal-warnings [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe52f7700 (LWP 6042)] [New Thread 0x7fffe4af6700 (LWP 6043)] [New Thread 0x7fffdffff700 (LWP 6044)] (gimp-2.8:6039): Gimp-Widgets-CRITICAL **: gimp_device_info_set_device: assertion `(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x5555559301f1 "Gimp-Widgets", log_level= G_LOG_LEVEL_CRITICAL, format=0x7ffff369c8fa "%s: assertion `%s' failed", args1=args1@entry=0x7fffffffd4e8) at gmessages.h:101 101 void g_logv (const gchar *log_domain, Missing separate debuginfos, use: debuginfo-install OpenEXR-libs-1.7.0-4.fc17.x86_64 PackageKit-0.7.5-1.fc17.x86_64 SDL-1.2.14-16.fc17.x86_64 at-spi2-atk-2.4.0-2.fc17.x86_64 at-spi2-core-2.4.2-1.fc17.x86_64 atlas-3.8.4-3.fc17.x86_64 expat-2.1.0-1.fc17.x86_64 gtk2-engines-2.20.2-4.fc17.x86_64 ilmbase-1.0.2-4.fc17.x86_64 libXau-1.0.6-3.fc17.x86_64 libXcomposite-0.4.3-3.fc17.x86_64 libXdamage-1.1.3-3.fc17.x86_64 libXi-1.6.1-1.fc17.x86_64 libXinerama-1.1.2-1.fc17.x86_64 libXrandr-1.3.1-3.fc17.x86_64 libXrender-0.9.7-1.fc17.x86_64 libcanberra-0.28-6.fc17.x86_64 libcanberra-gtk2-0.28-6.fc17.x86_64 libcroco-0.6.5-1.fc17.x86_64 libffi-3.0.10-2.fc17.x86_64 libgcc-4.7.2-2.fc17.x86_64 libgfortran-4.7.2-2.fc17.x86_64 libogg-1.3.0-1.fc17.x86_64 libopenraw-0.0.9-1.fc17.x86_64 libquadmath-4.7.2-2.fc17.x86_64 libselinux-2.1.10-3.fc17.x86_64 libstdc++-4.7.2-2.fc17.x86_64 libtdb-1.2.10-15.fc17.x86_64 libtool-ltdl-2.4.2-3.1.fc17.x86_64 libvorbis-1.3.3-1.fc17.x86_64 libxcb-1.9-1.fc17.x86_64 nss-softokn-freebl-3.14.3-1.fc17.x86_64 pixman-0.28.0-1.fc17.x86_64 suitesparse-3.6.1-3.fc17.x86_64 (gdb) I then tried two more c's and got (gdb) c Continuing. Detaching after fork from child process 6048. /home/len/.gimp-2.8/plug-ins/PanTools: error while loading shared libraries: libgimp-2.0.so.0: cannot open shared object file: No such file or directory (gimp-2.8:6039): LibGimpBase-WARNING **: gimp-2.8: gimp_wire_read(): error Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7ffff5c8cddc "LibGimpBase", log_level= G_LOG_LEVEL_WARNING, format=0x7ffff5c8ddf4 "%s: gimp_wire_read(): error", args1=args1@entry=0x7fffffffd6b8) at gmessages.h:101 101 void g_logv (const gchar *log_domain, Missing separate debuginfos, use: debuginfo-install GConf2-3.2.5-3.fc17.x86_64 gamin-0.1.10-12.fc17.x86_64 gvfs-1.12.3-1.fc17.x86_64 libbluray-0.2.3-1.fc17.x86_64 (gdb) c Continuing. Detaching after fork from child process 6049. [New Thread 0x7fffd823b700 (LWP 6050)] [New Thread 0x7fffd7655700 (LWP 6052)] [New Thread 0x7fffd6e54700 (LWP 6053)] [New Thread 0x7fffd6653700 (LWP 6054)] [New Thread 0x7fffd5e52700 (LWP 6055)] [New Thread 0x7fffd4fbb700 (LWP 6056)] [New Thread 0x7fffbffff700 (LWP 6057)] [New Thread 0x7fffbf7fe700 (LWP 6058)] [New Thread 0x7fffbeffd700 (LWP 6059)] [New Thread 0x7fffbe7fc700 (LWP 6060)] [Thread 0x7fffbf7fe700 (LWP 6058) exited] [Thread 0x7fffbe7fc700 (LWP 6060) exited] [Thread 0x7fffbffff700 (LWP 6057) exited] [Thread 0x7fffd6e54700 (LWP 6053) exited] [Thread 0x7fffd5e52700 (LWP 6055) exited] [Thread 0x7fffd4fbb700 (LWP 6056) exited] [Thread 0x7fffd6653700 (LWP 6054) exited] [Thread 0x7fffd7655700 (LWP 6052) exited] [Thread 0x7fffd823b700 (LWP 6050) exited] Detaching after fork from child process 6062. Detaching after fork from child process 6063. While parsing XMP metadata: Error: No XMP packet found [New Thread 0x7fffd823b700 (LWP 6064)] [New Thread 0x7fffd7655700 (LWP 6065)] [New Thread 0x7fffd4fbb700 (LWP 6066)] [New Thread 0x7fffd6653700 (LWP 6067)] [New Thread 0x7fffbd908700 (LWP 6068)] [New Thread 0x7fffbd107700 (LWP 6069)] [Thread 0x7fffbd908700 (LWP 6068) exited] [Thread 0x7fffd6653700 (LWP 6067) exited] [Thread 0x7fffbeffd700 (LWP 6059) exited] [Thread 0x7fffd823b700 (LWP 6064) exited] [Thread 0x7fffd4fbb700 (LWP 6066) exited] [Thread 0x7fffd7655700 (LWP 6065) exited] [Thread 0x7fffbd107700 (LWP 6069) exited] [New Thread 0x7fffbd107700 (LWP 6070)] [New Thread 0x7fffd7655700 (LWP 6071)] [New Thread 0x7fffd4fbb700 (LWP 6072)] Detaching after fork from child process 6073. [Thread 0x7fffd4fbb700 (LWP 6072) exited] [Thread 0x7fffd7655700 (LWP 6071) exited] [New Thread 0x7fffd7655700 (LWP 6078)] (gimp-2.8:6039): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion `GTK_IS_TREE_MODEL (tree_model)' failed Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7ffff773c4bb "Gtk", log_level=G_LOG_LEVEL_CRITICAL, format=0x7ffff369c8fa "%s: assertion `%s' failed", args1=args1@entry= 0x7fffffffa488) at gmessages.h:101 101 void g_logv (const gchar *log_domain, Missing separate debuginfos, use: debuginfo-install ibus-gtk2-1.4.99.20121109-9.fc17.x86_64 ibus-libs-1.4.99.20121109-9.fc17.x86_64 (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. __strlen_sse2_pminub () at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:39 39 movdqu (%rdi), %xmm1 (gdb) During this gimp came up and when I tried to export a file, it crashed again. Any suggestions?
'c' just continues when the program is already in an undefined state after the first warning. Please paste the result of 'bt'.
Okay, I entered bt after the rest of the stuff. Here is what I got. I hoppe soemeone finds it useful. If I should start all over and use bt at a different poit, let me know. (gdb) bt
+ Trace 231822
Thanks that was the right one, fortunately you pasted that and not what I asked for ;) It's crashing in gtk_entry_finalize() when setting the completion to NULL, and due to whatever bad interaction with gail it bombs. GTK+ moved this call to gtk_entry_dispose(), I'll do the same in gtk-2-24 after testing.
Fixed in gtk-2-24: commit ba5ac33cdc18fe252de9baac6a2927f9ea77e6ab Author: Michael Natterer <mitch@gimp.org> Date: Sun Apr 21 05:09:52 2013 +0200 entry: unset the completion in dispose() not finalize() Most likely fixes whatever evil gail interaction causing a crash I could never reproduce but has been reported several times against GIMP. The same fix is in GTK+ 3.x already (bug #683983). gtk/gtkentry.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
So what is the status of my problem with exporting files? Can I hope this will be fixed in an update to Fedora 17, or will I have to wait until I upgrade to Fedora 18?
The fix will be in GTK+ 2.24.18, when that is included in your distro you have to figure yourself :)
This is irrelevant to the bug itself, but I've figured out a way to work around it. I process my images in gimp and save them as .xcf files. I then use the ImageMagick program convert to convert the .xcf files to .tif files. That means I can avoid gimp crashing each time I export an image.
*** Bug 698603 has been marked as a duplicate of this bug. ***
Hi, I realize this bug is fixed in GTK+ 2.24.18 but is there a suggested work around, besides resorting to image magik for those us us using GTK+ 2.24.10-0ubuntu6 which is the version that comes with Ubuntu 12.04 LTS and do not have the option of upgrading? Thanks.
Try disabling accessibility.
Thanks Michael, your suggestion worked perfectly. Gimp seems to be stable once again. I used this: sudo chmod a-x /usr/lib/kde4/libexec/kaccessibleapp to disable the app in question from automatically executing.
How do I disable accessibility? I tried sudo chmod a-x /usr/lib/kde4/libexec/kaccessibleapp but it didn't work, perhaps, because I am not running kde.
*** Bug 698914 has been marked as a duplicate of this bug. ***