gimp crashes after save as

Bug #1087920 reported by Pietro Bernardi on 2012-12-08
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
Undecided
Unassigned

Bug Description

opened and modified file <name>.xcf, save as, file <new_name>.xcf, Save
After while error popup 'window <name>.xcf not respond', then Gimp crashes and close.
Error console empty.
But <new_name> file is saved w/o errors. After relaunching Gimp, I can open it and continue until the next 'Save as'.

OS Ubuntu 12.04.1, Gimp 2.6.12

RaduStoica (radumstoica) wrote :

Hi,

  This might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/912909 .

  Could you try a couple of things?

  First, it would help to get a stack trace. Open a terminal and run gimp --stack-trace-mode always, try to "save as" and copy here the lines you get in the terminal.

  Second, look through the comments on the bug I have mentioned. Maybe a suggestion from there might fix your problem.

  Thanks.

Il 08/12/2012 17:26, RaduStoica ha scritto:
> Hi,
>
> This might be a duplicate of
> https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/912909 .
>
> Could you try a couple of things?
>
> First, it would help to get a stack trace. Open a terminal and run
> gimp --stack-trace-mode always, try to "save as" and copy here the lines
> you get in the terminal.
>
> Second, look through the comments on the bug I have mentioned. Maybe a
> suggestion from there might fix your problem.
>
> Thanks.
>
Hi,

no aid - suggested deletion of ~/.config/dconf done, the same behavior.
Open file, then save as <another nome> crashes Gimp.

Stack-trace is a little bit short, maybe I need configure smth.

pietro@pietro-acer:~$ gimp --stack-trace-mode always

(gimp:4439): Gtk-CRITICAL **: IA__gtk_tree_model_get: assertion
`GTK_IS_TREE_MODEL (tree_model)' failed
gimp: fatal error: Errore di segmentazione (aka segfault)

(script-fu:4445): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
pietro@pietro-acer:~$

Don't hesitate ask next infos, if I can dig them from my box.

Thanks to you :)

Pietro

dan downs (ddowns) wrote :

I had the same problem ... crash on Save As.
But if I just create a new file with touch, Gimp doesn't crash.
Don't know if that helps.

Frederic (anthra-norell) wrote :

Same here. It's been a nuisance ever since I upgraded to 12.04 months ago. As the error is certain to happen and causes the loss of unsaved edits, I have made it a habit of saving everything before doing a "save as". I'd be more that grateful for any advice at all.

Frederic

Nelly (launch-ecostat) wrote :

This bug is also regsitrated as https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1048657
It is not solved there.

I have the same problem.
I am using Ubuntu 12.04 and Gimp 2.6.12

A new GIMP image can be save under a given name with "save as". When I try to save an already named file under a new name with "save as", GIMP crashes. The file is saved under the new name before crash, and can be opened again and can be edited.
If I use "save as", but do not change the name, no crash occurs.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gimp (Ubuntu):
status: New → Confirmed
Wayah-man (alton36) wrote :

I just installed Gimp 2.8.6 on 2013-07-03 and i have this problem as well as crashing when in Text Mode. It seems that if a file name already exists it will "save as" to that name - At least it did it once today. Also, it works OK on my windoze machine.
I am using Ubuntu 12.04 LTS on the machine that crashes.

Same problem as above.
Windows 7 64bit, Gimp 2.8.6 and 2.6.12
Gimp hangs whes using "save as" .xcf to an external usb pendrive, not to pc internal hard disk. Gimp gets stuck in that saving process and I need to force it to close. Interesting is that it saves the .xcf but with missing layers etc.

Just noticed this bug page is for linux only. If you want to cancel my bug report please proceed.

MP (pagel-d) wrote :

As I just posted on #1048657 , I had this crash bug in 2.6 and 2.8. It had apparently been caused by an inadvertent substitution of my .X display manager. This substitution also caused shell scripts running as root (on system startup) to fail .X related tasks due to a bad MIT magic cookie and and a lack of proper authorization (gdm was changing the XAUTHORITY cookie directory for my main login at every reboot, so the root user couldn't link to that cookie)

In any case
sudo apt-get install --reinstall lightdm unity-greeter
rm ~/.Xresources
rm ~/.Xauthority #without this (and possibly the one above) you may have difficulty logging in to your primary user account
sudo dpkg-reconfigure lightdm #select lightdm, rather than gdm, etc
echo -e "/usr/sbin/lightdm" | sudo tee /etc/X11/default-display-manager #this may have been redundant

MP (pagel-d) wrote :

Probably dup of bug #912909, but crashing situation (abort) different there

I added a potential workaround to Bug #1048657 and Bug #1087920

adrenochrome (adrenochrome) wrote :

@MP (pagel-d) , thanks for the workaround from comment #10, it solved perfectly the problem for me

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers