Your message dated Tue, 20 Aug 2013 08:02:50 -0400
with message-id <[email protected]>
and subject line Re: Bug#720309: gimp: Gimp erroneously assumes I want to 
convert all files to .xcf
has caused the Debian Bug report #720309,
regarding gimp: Gimp erroneously assumes I want to convert all files to .xcf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
720309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720309
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gimp
Version: 2.8.4-1
Severity: wishlist

   * What led up to the situation?
Opened filename.png file, edited it a bit, tried to save it. The
normal action for saving is "File->Save"

   * What was the outcome of this action?
Gimp wanted to create filename.xcf

   * What outcome did you expect instead?
I expected to save my changes to filename.png. I did not want a new
file format. The file started out as a png - it only needed some editing.



I understand that xcf may be a preferred format - and the correct default
when creating a new file. But this was not a new file - I made minor
modifications to an existing file. In such cases, I expect saving to
the same file - in the same format.

If I wanted to save to a different file, I would use "Save As" or
possibly "Export". But plain "Save" should save to whatever file
I opened - and in the same format. (Or possibly refuse, if I really added
something that cannot be saved to such a file. I understand that I can't
save 32-bit color to a .gif, for example.)

Trying to unconditionally reformat every file as xcf is not userfriendly.
That format may have some advantages, but gimp does not know what
I am using my files for. In this case, the file is used by a webpage
where (1) its name is hardcoded, and (2) not all clients support xcf.

I am filing this as a wishlist bug - obviously the maintainers can
take the program in whatever direction they decide. But the program
got harder to use for me, and I cannot see that this offers improvement.
So although gimp works, I consider this insistence on "xfc" a (small)
design bug.

Helge Hafting

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable'), (700, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gimp depends on:
ii  gimp-data                   2.8.4-1
ii  libaa1                      1.4p5-40
ii  libatk1.0-0                 2.8.0-2
ii  libbabl-0.1-0               0.1.10-1
ii  libbz2-1.0                  1.0.6-4
ii  libc6                       2.17-92
ii  libcairo2                   1.12.14-4
ii  libdbus-1-3                 1.6.12-1
ii  libdbus-glib-1-2            0.100.2-1
ii  libexif12                   0.6.21-1
ii  libexpat1                   2.1.0-4
ii  libfontconfig1              2.10.2-2
ii  libfreetype6                2.4.9-1.1
ii  libgdk-pixbuf2.0-0          2.28.2-1
ii  libgegl-0.2-0               0.2.0-3
ii  libgimp2.0                  2.8.4-1
ii  libglib2.0-0                2.36.3-3
ii  libgs9                      9.05~dfsg-8
ii  libgtk2.0-0                 2.24.20-1
ii  libgudev-1.0-0              175-7.2
ii  libice6                     2:1.0.8-2
ii  libjasper1                  1.900.1-14
ii  libjavascriptcoregtk-1.0-0  1.8.1-4
ii  libjpeg8                    8d-1
ii  liblcms1                    1.19.dfsg-1.2
ii  libmng1                     1.0.10-3
ii  libpango1.0-0               1.32.5-5+b1
ii  libpng12-0                  1.2.49-4
ii  libpoppler-glib8            0.22.5-1
ii  librsvg2-2                  2.36.4-2
ii  libsm6                      2:1.2.1-2
ii  libsoup2.4-1                2.42.2-6
ii  libtiff4                    3.9.7-1
ii  libwebkitgtk-1.0-0          1.8.1-4
ii  libwmf0.2-7                 0.2.8.4-10.3
ii  libx11-6                    2:1.6.0-1
ii  libxcursor1                 1:1.1.14-1
ii  libxext6                    2:1.3.2-1
ii  libxfixes3                  1:5.0.1-1
ii  libxmu6                     2:1.1.1-1
ii  libxpm4                     1:3.5.10-1
ii  libxt6                      1:1.1.3-1+deb7u1
ii  python                      2.7.5-2
ii  python-gtk2                 2.24.0-3+b1
ii  python2.7                   2.7.5-5
ii  zlib1g                      1:1.2.8.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.05~dfsg-8

Versions of packages gimp suggests:
pn  gimp-data-extras          <none>
pn  gimp-help-en | gimp-help  <none>
ii  gvfs-backends             1.16.3-1
ii  libasound2                1.0.27.1-2

--- End Message ---
--- Begin Message ---
This behavior is not going to change any time soon. It was the result of
extensive UI analysis in collaboration with upstream, and it's designed
to prevent people from losing their full changes, which is very easy
with most exported output formats. You can still overwrite the original
file with File -> Overwrite.

--- End Message ---

Reply via email to