Your message dated Sun, 17 Apr 2011 20:27:41 -0400
with message-id <[email protected]>
and subject line Re: Bug#623107: "Unable to run plug-in "file-jpeg"
(/usr/lib/gimp/2.0/plug-ins/file-jpeg)"
has caused the Debian Bug report #623107,
regarding running out of memory while forking plugin only prints useful error
to console
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.)
--
623107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623107
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gimp
Version: 2.6.10-1
Severity: normal
When I open many jpeg files (almost ten for three times, but the bug is random
when I open many images) I obtain this error: Unable to run plug-in "file-jpeg"
(/usr/lib/gimp/2.0/plug-ins/file-jpeg) and, in Italian: Esecuzione di fork non
riuscita (Impossibile allocare della memoria). I cannot anymore open jpeg
files. I have to close and restart Gimp to work again.
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gimp depends on:
ii gimp-data 2.6.10-1 Data files for GIMP
ii libaa1 1.4p5-38 ascii art library
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libbabl-0.0-0 0.0.22-1 Dynamic, any to any, pixel format
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.24-4 simple interprocess messaging syst
ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst
ii libexif12 0.6.19-1 library to parse EXIF files
ii libfontconfig1 2.8.0-2.1 generic font configuration library
ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib
ii libgegl-0.0-0 0.0.22-2+b1 Generic Graphics Library
ii libgimp2.0 2.6.10-1 Libraries for the GNU Image Manipu
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface
ii libhal1 0.5.14-3 Hardware Abstraction Layer - share
ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG
ii liblcms1 1.18.dfsg-1.2+b3 Color management library
ii libmng1 1.0.10-1+b1 Multiple-image Network Graphics li
ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio
ii libpng12-0 1.2.44-1 PNG library - runtime
ii libpoppler-glib4 0.12.4-1.2 PDF rendering library (GLib-based
ii librsvg2-2 2.26.3-1 SAX-based renderer library for SVG
ii libtiff4 3.9.4-5+squeeze1 Tag Image File Format (TIFF) libra
ii libwebkit-1.0-2 1.2.7-0+squeeze1 Web content engine library for Gtk
ii libwmf0.2-7 0.2.8.4-6.1+b1 Windows metafile conversion librar
ii libx11-6 2:1.3.3-4 X11 client-side library
ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.5-1 X11 miscellaneous 'fixes' extensio
ii libxmu6 2:1.0.5-2 X11 miscellaneous utility library
ii libxpm4 1:3.5.8-1 X11 pixmap library
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge
ii python-support 1.0.10 automated rebuilding support for P
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
gimp recommends no packages.
Versions of packages gimp suggests:
ii ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF
pn gimp-data-extras <none> (no description available)
pn gimp-help-en | gimp-help <none> (no description available)
ii gvfs-backends 1.6.4-3 userspace virtual filesystem - bac
ii libasound2 1.0.23-2.1 shared library for ALSA applicatio
-- no debconf information
--- End Message ---
--- Begin Message ---
Oh, okay. Initially I thought you said there weren't any other errors in
the message window. Closing as not a bug then.
On 04/17/2011 08:22 PM, Alessandro Sardone wrote:
The error was showed in a message window, not only in the console.
Simply, I followed your tip to launch the application via console and
read the errors. The only difference is that in the message window the
application says to consult stderr because of the big number of
errors.
--- End Message ---
