Your message dated Wed, 29 Mar 2006 17:52:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#359853: libgtk2.0-bin: missing dependencies to
libglib2.0-0 >= 2.10.1-2 and possibly to librsvg2-common >= 2.12.7-5+b1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libgtk2.0-bin
Version: 2.8.16-1
Severity: normal
I've got the following message while configuring libgtk2.0-bin:
Richte libgtk2.0-bin ein (2.8.16-1) ...
Updating the IM modules list for GTK+-2.4.0...done.
Updating the gdk-pixbuf loaders list for GTK+-2.4.0...g_module_open()
failed
for /usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so:
/usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so: undefined symbol:
rsvg_handle_new_gz
done.
upgrading to librsvg2-common from unstable solves that.
I don't know where to place the dependency to librsvg2-common but if
librsvg2-common is installed the svg-loader cause an error.
Furthermore I've got sporadically the following error:
Gtk-ERROR **: this version of Gtk+ requires GLib-2.10.1
upgrading to libglib2.0-0 from unstable eliminates that error.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)
Versions of packages libgtk2.0-bin depends on:
ii libatk1.0-0 1.10.3-1 The ATK accessibility
toolkit
ii libc6 2.3.5-13 GNU C Library: Shared
libraries an
ii libcairo2 1.0.2-3 The Cairo 2D vector
graphics libra
ii libfontconfig1 2.3.2-1 generic font configuration
library
ii libfreetype6 2.1.10-1 FreeType 2 font engine,
shared lib
ii libglib2.0-0 2.10.1-2 The GLib library of C
routines
ii libgtk2.0-0 2.8.16-1 The GTK+ graphical user
interface
ii libpango1.0-0 1.12.0-2 Layout and rendering of
internatio
ii libpng12-0 1.2.8rel-5 PNG library - runtime
ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol
client li
ii libxcursor1 1.1.3-1 X cursor management library
ii libxext6 6.8.2.dfsg.1-5 X Window System
miscellaneous exte
ii libxinerama1 6.8.2.dfsg.1-5 X Window System multi-head
display
ii libxrandr2 6.8.2.dfsg.1-5 X Window System Resize,
Rotate and
ii libxrender1 1:0.9.0.2-1 X Rendering Extension
client libra
ii zlib1g 1:1.2.2-4 compression library -
runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
Le mercredi 29 mars 2006 à 11:08 +0200, Viktor Abrams a écrit :
> Package: libgtk2.0-bin
> Version: 2.8.16-1
> Severity: normal
>
> I've got the following message while configuring libgtk2.0-bin:
> Richte libgtk2.0-bin ein (2.8.16-1) ...
> Updating the IM modules list for GTK+-2.4.0...done.
> Updating the gdk-pixbuf loaders list for GTK+-2.4.0...g_module_open()
> failed
> for /usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so:
> /usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so: undefined symbol:
> rsvg_handle_new_gz
> done.
>
> upgrading to librsvg2-common from unstable solves that.
> I don't know where to place the dependency to librsvg2-common but if
> librsvg2-common is installed the svg-loader cause an error.
>
>
> Furthermore I've got sporadically the following error:
> Gtk-ERROR **: this version of Gtk+ requires GLib-2.10.1
>
> upgrading to libglib2.0-0 from unstable eliminates that error.
Hi,
First please use 1 bug by issue, that's not easy to manage 2 different
topic on the same place. I'm rejecting that bug. The first issue is due
to you having an outdate librsvg2, the second issue due to the fact that
you use a package from experimental and didn't upgrade to the unstable
version then. Technically GTK should require a new glib but the buggy
version has not been uploaded to unstable so there is no point to
trigger a rebuild on GTK on all the architectures for that
Cheers,
Sebastien Bacher
--- End Message ---
