Ubuntu
gdk-pixbuf package

  1. Bug #1492767
  2. Comment #0

Comment 0 for bug 1492767

Revision history for this message
Mélodie (meets) wrote :

Hello,

I did a fresh install with a Trusty 14.04.3 (x86_64) custom version yesterday, and today, I updated the system (with the console, because other issues came first which led me to do a filesystem check). Then I started Synaptic, and oops! no GUI, only the borders of the window would show. Several other programs were affected and would not start (Geany, text editor), or show their content. After tests and research it appeared only GTK3 programs were affected. If using a theme with GTK2, or move the GTK configuration out of the way, the programs would work.

The upgrade contained the following packages:
gir1.2-gdkpixbuf-2.0_2.30.7
libgdk-pixbuf2.0-0_2.30.7
libgdk-pixbuf2.0-common_2.30.7

I fixed the issue by booting to the Live USB I had used to install, and repackage the programs with dpkg-repack, then reinstalled them using "sudo dpkg -i *.deb". (copied from the live usb to the home in the install, rebooted and reinstalled there).

Problem solved for this install, where I have for now blocked the update for these three packages.

At post-install, after I had updated, I had the same message as the people who reported that bug:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294

****
(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.
****

and when trying to do so, the console returned a message stating gdk-pixbuf-query-loaders was not installed. (no such package in the repos either).

More information can be found at
http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html

where I discussed about this bug and my findings.

Now I will try to produce this bug again in the Live USB (which has no persistence).

Best regards,
Mélodie