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
Loïc Minier
lool at dooz.org
Wed Mar 29 14:08:05 UTC 2006
Hi,
On Wed, Mar 29, 2006, Viktor Abrams wrote:
> 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.
Thanks for your report.
/usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so belongs to
librsvg2-common, if it was unusable, it is a librsvg2-common bug. What
version of librsvg2-common were you using *prior* to the upgrade?
(Check your aptitude.log or dpkg.log.)
> I don't know where to place the dependency to librsvg2-common but if
> librsvg2-common is installed the svg-loader cause an error.
The problem would be an incorrect dependency of librsvg2-common on
librsvg2-2, or a regression in librsvg2-2 (symbols removed).
> 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.
This is a separate bug, it seems Gtk should force a stronger dependency
on libglib2.0-0 (it currently only requires >= 2.10.0 as the shlibs
said, but the message you quote implies it needs >= 2.10.1).
Gtk's NEWS indeed say:
at least GLib-2.10.1 is required now
Thanks,
--
Loïc Minier <lool at dooz.org>
Current Earth status: NOT DESTROYED
More information about the Pkg-gnome-maintainers
mailing list