Your message dated Fri, 6 Feb 2026 14:30:45 -0500
with message-id
<caaajcmav46swvkuvpbnrb6xzccrrcqpcfk1tjl3o57rxs7c...@mail.gmail.com>
and subject line closing old gdk-pixbuf bugs
has caused the Debian Bug report #625203,
regarding gnome-icon-theme: Cannot open pixbuf loader module file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
625203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-icon-theme
Version: 3.10.0-1
Severity: normal
Hi,
I saw the following while updating:
Processing triggers for gnome-icon-theme (3.10.0-1) ...
(gtk-update-icon-cache-3.0:32480): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linu$
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.
Is this related to #640150 at all?
Thanks,
Nick
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-icon-theme depends on:
ii hicolor-icon-theme 0.13-1
ii libgtk-3-bin 3.8.6-1
ii librsvg2-common 2.40.0-1
gnome-icon-theme recommends no packages.
gnome-icon-theme suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
