The issue has been rapported to Debian on e.g https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=625203
The Debian gnome-pkg team looked at it and wrote that comment "postrm (of the old package) removes the loaders.cache file unconditionally and postinst (of the new package) creates it again. That means, during upgrades there is a timeframe where loaders.cache does not exist. When gtk-update-icon-cache is triggered via a file system trigger, it is possible that it is run while loaders.cache is not present. I talked to Joss on IRC. He suggested to on remove the loaders.cache file in postrm only on remove|purge. Otherwise gtk-update-icon-caches could be non-functional (this needs verification though) As we can't fix the postrm of the old package though, we should consider doing a stable update via a point release. We also need to make sure, to move/remove the loaders.cache for the multiarch transition explicitly, as this will be no longer done as side-effect of postrm." ** Bug watch added: Debian Bug tracker #625203 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625203 ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Triaged ** Package changed: ubuntu => gdk-pixbuf (Ubuntu) ** Also affects: gdk-pixbuf (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625203 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
