I won't argue about dependency issues; that may well be the case. In fact, the "libgdk-pixbuf2-dev" package wasn't installed on my Xubuntu system either.
I will add that the problem is not specific to Xubuntu, though. I found reports about it under Debian and ArchLinux as well.
Also, it must have been known for quite a long time to the Slackware team, since they have the following code fragment in their "/etc/rc.d/rc.M" script, which is executed upon each boot:
---<cut>----------
if [ -x /usr/bin/update-gdk-pixbuf-loaders ]; then
/usr/bin/update-gdk-pixbuf-loaders --verbose
fi
---<tuc>----------
When this is executed, the following output is produced:
---<cut>----------
Updating gdk-pixbuf.loaders for x86_64-slackware-linux:
/usr/bin/gdk-pixbuf-query-loaders-64 --update-cache
---<tuc>----------
That is, obviously, one way to circumvent the problem: rerun the command upon each boot...
dino99,
I won't argue about dependency issues; that may well be the case. In fact, the "libgdk- pixbuf2- dev" package wasn't installed on my Xubuntu system either.
I will add that the problem is not specific to Xubuntu, though. I found reports about it under Debian and ArchLinux as well.
Also, it must have been known for quite a long time to the Slackware team, since they have the following code fragment in their "/etc/rc.d/rc.M" script, which is executed upon each boot:
---<cut>---------- update- gdk-pixbuf- loaders ]; then bin/update- gdk-pixbuf- loaders --verbose
if [ -x /usr/bin/
/usr/
fi
---<tuc>----------
When this is executed, the following output is produced:
---<cut>---------- slackware- linux: bin/gdk- pixbuf- query-loaders- 64 --update-cache
Updating gdk-pixbuf.loaders for x86_64-
/usr/
---<tuc>----------
That is, obviously, one way to circumvent the problem: rerun the command upon each boot...