Hello, I just tripped on this bug while upgrading my Debian-jessie box. It looks like the upgrade is removing the file and then recreating it later:
[...] Unpacking libgdk-pixbuf2.0-common (2.30.8-1) over (2.30.7-1) ... Preparing to unpack .../libgdk-pixbuf2.0-dev_2.30.8-1_amd64.deb ... Unpacking libgdk-pixbuf2.0-dev (2.30.8-1) over (2.30.7-1) ... Preparing to unpack .../libgdk-pixbuf2.0-0_2.30.8-1_amd64.deb ... De-configuring libgdk-pixbuf2.0-0:i386 (2.30.7-1) ... Unpacking libgdk-pixbuf2.0-0:amd64 (2.30.8-1) over (2.30.7-1) ... Preparing to unpack .../libgdk-pixbuf2.0-0_2.30.8-1_i386.deb ... Unpacking libgdk-pixbuf2.0-0:i386 (2.30.8-1) over (2.30.7-1) ... [...] Unpacking xserver-xorg-dev (2:1.16.0-2+b1) over (2:1.16.0-2) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for dbus (1.8.6-2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:30268): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Nie ma takiego pliku ani katalogu This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for mime-support (3.56) ... [...] Konfigurowanie pakietu libgdk-pixbuf2.0-common (2.30.8-1) ... Konfigurowanie pakietu libgdk-pixbuf2.0-0:amd64 (2.30.8-1) ... Konfigurowanie pakietu libgdk-pixbuf2.0-0:i386 (2.30.8-1) ... [...] Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.30.8-1) ... Processing triggers for menu (2.1.47) ... Just guessing: maybe the trigger or configuration should be done just after unpacking replacement libgdk-pixbuf if it recreates the 'loaders.cache' file. Bug #640150 looks like a duplicate of this one. Best Regards, Michał Mirosław -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
