Your message dated Mon, 30 Apr 2012 20:17:33 -0400
with message-id <[email protected]>
and subject line Re: Bug#670784: gimp: GIMP does not recognize nor save any
image format other than its own and colored xhtml
has caused the Debian Bug report #670784,
regarding gimp: GIMP does not regognize nor save any image format other than
its own and colored xhtml
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.)
--
670784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670784
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gimp
Version: 2.6.12-1+b2
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
As the Subject abovesays...
GIMP does not regognize no save any image format other than its own and colored
xhtml.
Using it to open a jpg file fails ("unrecognized"). I haven't bothered with
any others than a png file.
The Save/Save As dialogs have only the above two formats as options for saving.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gimp depends on:
ii gimp-data 2.6.12-1
ii libaa1 1.4p5-39
ii libatk1.0-0 2.4.0-2
ii libbabl-0.1-0 0.1.6-2
ii libc6 2.13-30
ii libcairo2 1.12.0-2.1
ii libdbus-1-3 1.5.12-1
ii libdbus-glib-1-2 0.98-1
ii libexif12 0.6.20-2
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.9-1
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libgegl-0.1-0 0.1.8-3
ii libgimp2.0 2.6.12-1+b2
ii libglib2.0-0 2.32.0-4
ii libgtk2.0-0 2.24.10-1
ii libjpeg8 8d-1
ii liblcms1 1.19.dfsg-1+b2
ii libmng1 1.0.10-3
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1
ii libpoppler-glib6 0.16.7-3
ii librsvg2-2 2.36.1-1
ii libtiff4 3.9.6-5
ii libwebkitgtk-1.0-0 1.8.0-2
ii libwmf0.2-7 0.2.8.4-10
ii libx11-6 2:1.4.99.901-1
ii libxext6 2:1.3.1-2
ii libxfixes3 1:5.0-4
ii libxmu6 2:1.1.1-1
ii libxpm4 1:3.5.10-1
ii python 2.7.2-10
ii python-gtk2 2.24.0-3
ii python2.7 2.7.3~rc2-2.1
ii zlib1g 1:1.2.6.dfsg-2
Versions of packages gimp recommends:
ii ghostscript 9.05~dfsg-4
Versions of packages gimp suggests:
ii gimp-data-extras 1:2.0.1-3
ii gimp-help-en | gimp-help <none>
ii gvfs-backends 1.12.1-1
ii libasound2 1.0.25-2
-- no debconf information
--- End Message ---
--- Begin Message ---
On 04/29/2012 11:06 PM, Kenward Vaughan wrote:
> ** Removing the .gimp-2.6/plugins directory worked (as did my
> original trashing of the whole thing). **
>
> Any thoughts on what caused the problem?
...
> Thanks for the help! Is there something I can possibly tell you that
> would shed light on what happened?
Unless you know what could have created those plug-ins, I guess there
isn't really much left to do here.
--- End Message ---
