[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"
Same here when upgrading 16.04 LTS to 18.04 The bug is six years old ? We should send it to preschool =) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory 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. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory 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 hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory 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. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
This bit me today, 16.04LTS to 18.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp