Ubuntu

GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

Reported by Stephen Cradock on 2010-08-17
234
This bug affects 54 people
Affects Status Importance Assigned to Milestone
gdk-pixbuf (Debian)
New
Unknown
gdk-pixbuf (Ubuntu)
High
Unassigned

Bug Description

During installation of updated version of libgdk-pixbuf2.0-0 on August 10th 2010, the apt term.log contained multiple (>300) copies of the following warning:

(gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

Nevertheless, the file complained about exists, and is readable in gedit.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Mon Aug 16 18:13:29 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdk-pixbuf

Stephen Cradock (s-cradock) wrote :
dino99 (9d9) wrote :

same issues on maverick i386

Bug 637813

Iain Lane (laney) on 2010-09-24
Changed in gdk-pixbuf (Ubuntu):
status: New → Confirmed
Hew McLachlan (hew) wrote :

Issue still exists when updating on 10.10 UNE.

philinux (philcb) wrote :

Upgrading from lucid to maverick.

Complains this file/directory does not exist.
(gtk-update-icon-cache:333) /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
Before the upgrade the only thing in /2/10.0/ is a Directory called loaders.

The file loaders.cache did not exist in lucid but is there after the upgrade. Are these just spam messages or real errors?

Anupam (anupambhatt) wrote :

Getting this warning message when upgrading/updating packages to maverick (from list). I have lost the menu and the status/task bar in the display and out of ideas on how to get the menus and taskbar. Desktop shortcuts appear fine though. Just thinking if this warning is the cause of menus etc disappearing.

Strange thing happened here during Lucid to Maverick upgrade.

Hardware: Asus eeepc 1005PE hooked to a Hyundai external monitor res 1440x900 and a Logitech external usb mouse/keyboard

At the middle of the upgrade, the machine started to be very slow, let's say about 10 to 20 times (or more) slower to perform the upgrade statements, cpu load constantly very high.
The mouse was moving very slowly by steps, and all interactions were completely slowed down.

After a while during upgrade, I disconnected the external monitor and mouse/kbd, and set the display back to netbook's with keys Fn F7, and it went back to a normal update speed until the end (upgrade seems OK).

Looking at the /var/log/dist-upgrade/apt-term.log after upgrading, I can see 8322 (out of 22221 total) lines containing:

(gtk-update-icon-cache:nnnnn): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': Aucun fichier ou dossier de ce type

These statements appear by packs of ~70 lines, regularly in the file.

Is there some relation here between those events, and is it necessary to perform the upgrade without connecting external devices like a monitor ?

Peter Lundqvist (peterl) wrote :

It happened to me to.

Running apt-get install --reinstall gdk-pixbuf2.0-0 fixed everything for me.

Is it just me or is the ubuntu upgrade getting worse and worse?

Did you manage to run this command during the upgrade ?

MAKAPOH (makapoh) wrote :

same problem on upgrade maverick -> natty alpha 3

MAKAPOH (makapoh) wrote :

screenshot of chromium

sdaau (sd-imi) wrote :

Also noticed this today - however, this is a fresh install of Natty (original install of alpha3)

FriedChicken (domlyons) wrote :

I also had this problem on doing a
sudo apt-get update && sudo apt-get dist-upgrade
on Natty.

Is this warning critical? Or is it safe to ignore it?

Peter Fletcher (peter-traal) wrote :

Is also happening to me during install of official 11.04 in update manager.

I don't yet know if it will cause any problems.

Lekensteyn (lekensteyn) wrote :

Confirmed, I'm upgrading using the kubuntu-11.04-alternate-amd64.iso.

(gtk-update-icon-cache:12165): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This message is repeated 12794 times, but the upgrade continues.

spidernik84 (alexander-rilik) wrote :

Confirmed here also. Upgrading from a 10.04.2 LTS to a 10.10, both amd64.
I'm updating via terminal with "sudo do-release-upgrade -d".

Mattias Andersson (matand) wrote :

I'm seeing a lot of these messages when running do-release-upgrade from 10.10 to 11.04.

Changed in gdk-pixbuf (Debian):
status: Unknown → New
wavded (wavded) wrote :

I'm getting this error whenever gdk-pixbuf is updated on 11.10, happened today again.

archenroot (archenroot-gmail) wrote :

I today started an upgrade from 10.04 LTS to newest version of ubuntu. I got this message when going to 10.10. Now I started upgrading again to 11.04 and the message appears again. I didn't try to reinstall gpx, I found this bug after the upgrade. I will try to reinstall this package and see what happen when I start upgrade to 11.10 version as soon as it will be available in release stage.

Thomas Coffee (tcoffee) wrote :

Problem still exists upgrading from 11.04 to 11.10.

Sergio Oller (zeehio) wrote :

This warning appeared to me also, but it disappeared when I installed the gtk2-engines-pixbuf package.

Just had this error appear on update on Raring. I ran apt-get install --reinstall gdk-pixbuf2.0-0 following update to see if that would prevent future reccurances.

Mike (web-g) wrote :

Same problem when updating 12.10 totally patched up to 13.04 initial release.

dino99 (9d9) on 2013-05-30
tags: added: raring
removed: maverick
Richard Bruce (richard-bruce) wrote :

Same problem when updating 13.04, totally patched, to 13.10

Ivan Larionov (xeron-oskom) wrote :

Same on 14.04.

papukaija (papukaija) on 2014-03-15
summary: - multiple warnings during installation
+ GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
+ /gdk-pixbuf-2.0/2.10.0/loaders.cache'
LAZA (laza74) on 2014-03-16
tags: added: trusty
Jesús Navarro (navarrojx) wrote :

After upgrade my 12.04, all icons and images are unrecognizable by pixbuf, all themes are affected and only see a black screen when login. I reinstall libgdk-pixbuf2.0-0 gtk2-engines-pixbuf librsvg2-2 librsvg2-common compiz metacity nvidia-304 unity ubuntu-desktop and nothing, just black screen, in the term.log see this

Processing triggers for libgdk-pixbuf2.0-0 ...
Segmentation fault (core dumped)

In the /var/log/auth.log

Mar 18 07:31:31 MyHost lightdm: pam_unix(lightdm:session): session opened for user lightdm by (uid=0)
Mar 18 07:31:31 MyHost lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
Mar 18 07:31:32 MyHost lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "MyUser"
Mar 18 07:31:32 MyHost dbus[939]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.25" (uid=104 pid=1752 comm="/usr/lib/indicator-datetime/indicator-datetime-ser") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.15" (uid=0 pid=1450 comm="/usr/sbin/console-kit-daemon --no-daemon ")
Mar 18 07:31:54 MyHost lightdm: pam_unix(lightdm:session): session closed for user lightdm

I try this as root

/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

But nothing, the response is

<b>Segmentation fault (core dumped)</b>

In the .xsessions.log there are several errors like this

(gnome-settings-daemon:2111): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1516:46: No se ha reconocido el formato de imagen del archivo
** (nm-applet:2150): WARNING **: Icon nm-device-wired missing: (3) No se ha reconocido el formato de imagen del archivo
** (nm-applet:2150): CRITICAL **: nm_secret_agent_register: assertion `priv->reg_call == NULL' failed
(classicmenu-indicator:2148): GLib-GIO-CRITICAL **: g_loadable_icon_load: assertion `G_IS_LOADABLE_ICON (icon)' failed
(classicmenu-indicator:2148): LIBDBUSMENU-GTK-WARNING **: Unable to create pixbuf data stream: El tipo de imagen «png» no está soportado
** (gnome-settings-daemon:2111): WARNING **: Failed to set the background '/home/MyUser/Wallpapers/IMG_20130822_101800.jpg': GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not authorized
** (gnome-settings-daemon:2111): WARNING **: Failed to set the background '/home/MyUser/Wallpapers/IMG_20130822_101800.jpg': GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not authorized

I hope you can help me with this, I do not want to have to reinstall my operating system

Jesús Navarro (navarrojx) wrote :

Finally I resolved the problem, copy and replace the loader folder and loaders.cache file from another computer, restart and all is well

LAZA (laza74) on 2014-03-21
tags: added: i386
Changed in gdk-pixbuf (Ubuntu):
importance: Undecided → High
Eric Ongerth (ericongerth) wrote :

I experienced this during the process of upgrading from 13.10 to 14.04 final beta in a terminal window using the command "sudo do-release-upgrade -d". Running the command suggested in the warning message in a console window during and after the upgrade did nothing useful. After completing the upgrade and rebooting there has been no problem and further invocations of apt-get update and apt-get upgrade have gone smoothly.

I did have one failure to boot, the very first reboot after the upgrade it appeared the video wasn't initialized or something. This may be unrelated but I summarize it here just in case. Rebooted again, chose Advanced Options, enabled network, ran dpkg several times to fix broken packages. Rebooted once more to find the wrong video mode, rebooted one final time and everything is running correctly ever since.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.