GIMP Version: 2.8
Operating System: Linux
OS Version: Linux Fedora & Windows 7 (64-bit)
GIMP Experience: Basic Level

---

Every thing works fine in my Gimp-2.8 but when I export to save a png, it shuts down. Although it does do the save, it shuts down and I lose the XCF.
I am operating in Fedora-17

My error log is attached below, and if someone can understand what it says I would appreciate the feed back.

Thank you!!

Hi molly,
This may sound ridiculous but there aren't any errors in the file you attached.
Somewhere in your /home/molly directory there probably is a file .xsession-errors.
Notice the dot it's a "hidden" file.
You use Gnome as a desktop and I use KDE so I am not entirely sure that you have such a file.
Another way to catch errors is to start gimp from a console.
Gimp sends all error messages to "standard error" which in Linux means the terminal or console.
So when it quits again after saving something you'll probably find what exactly happened.
Good luck.
Gerard.

Thank you Gerard, I will give that a try.

Edit: I started Gimp from the terminal and added the error to my first post and deleted the previous one.

Hope this one gives more information.

Molly has been able to capture GIMP 2.8.2 crashing a couple of time during an export/save while running with the --verbose option.

It appears to be bug/conflict of some kind causing a crash and core dump. Does anyone see where a potential problem might be in these messages from the console (under the spoiler)?

I found a similar bug report here.

Did happens only with png not with jpg too ?
Maybe you have also the apng plugin ?

Not sure of Linux but in Windows the apng plugin could create some problems :
Well "problems" only cause a failure to save a readable png, no Gimp crashes

Neverthless if you have the apng plugin may be worth temporary unistall it, just too see if the problem remain

Thanks PC but no, I didn't install the apng plug-in in Fedora. All my error messages say "problems with Gimp package."

i see

NOT A SOLUTION BUT A WORKAROUND :

using instead then "export" "save for the web" to save png should avoid the crash
"save for the web" http://registry.gimp.org/comment/3257

I am getting frustrated by gimp-2.8.2 also.
I haven't saved anything as png or jpg yet so can't tell if it works or not.
But I am working on a scan of a damaged postcard.
The size of this scan is 104 MB.
When I want to remove the border it either segfaults or takes ages to make the cut.
I have 8 GB memory.
I reinstalled 2.6 on a separate Gentoo install and tried to make the same cut.
With default preferences settings it did the cut in a second!
IMHO 2.8 is still flaky.

Another thing that's a pita is Tool Options.
After working with 2.8 for a while it suddenly hides and you have to click in the panel to get it back.
The only way to get it to stay under the Tool Box is to delete sessionrc and set everything again.
(For as long as it lasts.)
Gerard.

Thanks Gerard but I think it is a FF problem this time because my home page where I get my email etc, is the same as it is in Gimp Chat.

Perhaps updating libpng will work?

Fedora is currently at libpng 1.5.10 but I did notice version 1.5.12 has been released, which should soon show up the Fedora update repos.

I have not used GIMP 2.8.2 as extensively as Molly but I'm not having any crashes while saving or exporting. Molly does use Fedora 64bit, whereas I'm using the 32bit version. I don't know if that is a factor but I do know that 64bit versions of apps and operating systems tend to be less stable, and have more issues, than the 32bit versions.

I tried and finally succeeded in finding what caused the problem with cutting part of an image.
See my post on the first page of this thread dated Sept 14.

It was caused by the settings of KDE's klipper!
Default setting is "ignore images" and "text selection only".
Mine was set to the opposite.
Now it doesn't quit any more though it still is a lot slower than 2.6

I hate KDE ever since the demise of KDE-3.5.
But Gnome is no option and the other desktops lack a lot of possibilities.
Gerard.

@gerard, I am very happy that you were able to solve your KDE problem.

My Gimp is still shutting down, with Export. It did it one right after the other yesterday but today it hasn't happened at all YET.
If this thing was more consistent, it might be easier to find a solution.
Sometimes it will crash just by moving the blue bar over so I can see a window below.

Well it took me about 4 days molly.
You see KDE uses Qt libraries for display things while Gimp uses GTK.
Never thought the two would interfere with each other.
And KDE's .xsession-errors showed absolutely nothing other than the regular nonsense.
Gerard.

Edit:I started gimp in verbose manner in a console opened a .xcf image and exported it as .png.
This is the last line I see in my console after doing that and before closing gimp.

So nothing like what you have after that same line your file.
From what I see in GnuTux post your gimp needs some dependency correctly installed.
But I have no idea which.

I wish mine was the same, lol

Other than it just being a bug, maybe something else is causing your instability in GIMP, Molly. I had a problem with gpaste sucking up all my memory and causing instability issues in Firefox and GIMP.

You could try removing gpaste, just as a precaution.

yum remove gpaste

It might also be due to problems with plugins or other scripts that you have installed. Is there a script or plug-in that you are using just prior to it crashing? Keep that in mind the next time you are having crashing problems.

That's about all I got.

Ok thank you tux, I will run that yum thang. Right now I can't think of anything I have been using before the crash but I will keep my eye out. I just can't understand this error. I was sure we got rid of that then but it must have come back. "script-fu: gimp_wire_read(): error
[molly@localhost

This is my yum results:
[molly@localhost ~]$ su -
Password:
[root@localhost ~]# yum remove gpaste
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
No Match for argument: gpaste
No Packages marked for removal
[root@localhost ~]#

I guess gpaste isn't your problem then.

Those gimp_wire read() startup errors, we got rid of, were from old scripts/plugins you had installed.

As you can see, the "script-fu: gimp_wire_read(): error appears to be the last message most people get just before GIMP seg faults and crashes, for whatever reason.

See here.

That is very interesting. Seems to me that maybe this started after I upgraded to gimp-2.8.2. I don't know if I can find the date when it started so I can trace it back. I will have to do some poking around to see when I upgraded.

My Gimp is also still crashing. Almost every time now when I click save as.xcf and when I export save as.png, it closes, no error messages, no nothing. It is getting beyond annoying.
I have have lots of people respond to this thread and we have tried it all.

What I would like to do but don't know if that is the way to go or not but what about if I un-install Gimp 2.8.2 (64-bit) and install 32-bit.

Suggestions please