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 386436 - dataloss: image lost when trying to save to the old filename
dataloss: image lost when trying to save to the old filename
Status: RESOLVED DUPLICATE of bug 409799
Product: gthumb
Classification: Other
Component: general
2.8.x
Other Linux
: Normal critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2006-12-16 09:30 UTC by Niels Weber
Modified: 2007-02-20 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Niels Weber 2006-12-16 09:30:46 UTC 
Using 2.8.1.

I changed a jpg picture and then tried to save the changes. When asked for a filename to write to, I provided the old filename as I didn't want to keep the old version.

Ghtumb then told me that this filetype was not supported and I was left with a picture with a size of 0 Bytes (and the old filename). -> the picture was lost, both in original and changed version.

What should happen:
Obviously the old version should be overwritten with the new one.
Comment 1 Michael Chudobiak 2006-12-17 19:05:46 UTC 
Niels,

Do you have libjpeg installed on your system? What distro are you using?

- Mike
Comment 2 Niels Weber 2006-12-29 10:37:16 UTC 
I am using Fedora Core 6 64Bit. I have libjpeg-6b-37 installed.

I'll try to reproduce the bug with 2.9.1.
Comment 3 Niels Weber 2006-12-29 13:42:15 UTC 
With 2.9.1 everything worked as it should, so it either was a bug in 2.8.1 that's been fixed or something weird went wrong when the bug happened.
Comment 4 Alexander Ovcharenko 2007-01-18 18:23:04 UTC 
I have the same problem in gthumb. When I saved the modified image "Image type 'lain' is not supported" appeared.
Comment 5 Michael Chudobiak 2007-02-20 14:01:14 UTC 
This is probably the same as bug 409799.

- Mike


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