Your message dated Fri, 30 May 2008 16:05:25 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#483560: Unable to load image-loading modules
has caused the Debian Bug report #483560,
regarding libgtk2.0-0: Unable to load image-loading modules
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.)
--
483560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483560
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libgtk2.0-0
Version: 2.12.9-4
Severity: grave
Justification: renders package unusable
Subject: libgtk2.0-0: Fails to load icons (libpixbufloader-png.so)
Package: libgtk2.0-0
Version: 2.12.9-4
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libgtk2.0-0 depends on:
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.7-11 GNU C Library: Shared libraries
ii libcairo2 1.6.4-3 The Cairo 2D vector graphics libra
ii libcomerr2 1.40.8-2 common error description library
ii libcupsys2 1.3.7-5 Common UNIX Printing System(tm) -
ii libfontconfig1 2.5.93-1 generic font configuration library
ii libglib2.0-0 2.16.3-2 The GLib library of C routines
ii libgnutls26 2.2.5-1 the GNU TLS library - runtime libr
ii libgtk2.0-common 2.12.9-4 Common files for the GTK+ graphica
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libkrb53 1.6.dfsg.3-2 MIT Kerberos runtime libraries
ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio
ii libpng12-0 1.2.27-1 PNG library - runtime
ii libtiff4 3.8.2-8 Tag Image File Format (TIFF) libra
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxcomposite1 1:0.4.0-2 X11 Composite extension library
ii libxcursor1 1:1.1.9-1 X cursor management library
ii libxdamage1 1:1.1.1-4 X11 damaged region extension libra
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio
ii libxi6 2:1.1.3-1 X11 Input extension library
ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library
ii libxrandr2 2:1.2.2-2 X11 RandR extension library
ii libxrender1 1:0.9.4-1 X Rendering Extension client libra
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages libgtk2.0-0 recommends:
ii hicolor-icon-theme 0.10-1 default fallback theme for FreeDes
ii libgtk2.0-bin 2.12.9-3 The programs for the GTK+ graphica
-- no debconf information
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Fri, May 30, 2008, Ted Percival wrote:
>> # versions prior to 2.10.1-1 used the 2.4.0 binary version and generated
>> module
>> # files below /etc/gtk-2.0 which will we can not leave behind (since they
>> # reference modules not on the system anymore)
>> if [ "$1" = "configure" ] && dpkg --compare-versions "$2" lt "2.10.3-2"; then
>> echo "Removing generated module files coming from the previous Gtk
>> binary version..."
>> rm -v -f /etc/gtk-2.0/gdk-pixbuf.loaders
>> rm -v -f /etc/gtk-2.0/gtk.immodules
>> fi
>
> That dpkg --compare-versions "lt" looks like it should be a "gt".
I don't think so, it is meant to only be run when people upgrade from
an old version to a current version, so their old version is lt than
the new one.
> Changing that and re-running the postinst configure does the trick.
Right, because you're upgrading from new version to new version. I'm
closing the bug for now, and will reopen if we receive further reports.
This transition is quite old already and we didn't receive any
complaint until now.
--
Loïc Minier
--- End Message ---