Bug#388450: loaders/immodules not updated on upgrade
Loïc Minier
lool at dooz.org
Thu Sep 21 07:28:31 UTC 2006
tags 388450 + experimental
close 388450 2.10.3-2
stop
Hi,
On Thu, Sep 21, 2006, Damyan Ivanov wrote:
> severity 388450 grave
> # initial bugreport was against 2.10.1-2, but problem is
> # still reproducible with 2.10.3-1
> found 388450 2.10.3-1
> # change the title according to the new findings
> title 388450 pixbuf loaders broken by an obsolete file in /etc
> thanks
Your commands are a bit late, I already uploaded a fix to remove the
/etc files. :-(
> Raising the severity to grave then (breaks unrelated software). See
> below for recipe for reproducing.
I explained in a later message that I understood the problem...
> Hmm. You said gtk 2.10 needs no file in /etc. But I do have
> /etc/gtk-2.0/gdk-pixbuf.loaders, which is full with entries like
> "/usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so".
The initial plan was to leave it behind for backwards compatibiliy, but
it "masks" the good modules because it has bad data. Hence, -2 simply
removes it. I wondered whether it would be cleaner to continue
updating it for a while, but since I have the control over the update-*
commands as well, I think it's ok to make them no-ops as I did in -2.
> If I remove this file, gqview now gives a warning at startup
> ((gqview:28333): GdkPixbuf-WARNING **: Cannot open pixbuf loader
> module file '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or
> directory) but runs just fine.
Yeah, I'll remove the warning in the next upload as well.
> This explains why the problem goes away when update-gdkpixbuf-loaders
> is run.
Yes.
So, thanks for your report. Please be careful with your commands to
not revert changes to the state of a bug (I always open the bug I'm
about to update before sending commands to change its state).
Bye,
--
Loïc Minier <lool at dooz.org>
More information about the Pkg-gnome-maintainers
mailing list