SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have the same problem. It occurred directly after the latest Slackware-current upgrade with swaret.
gtk+2 was also updatet to version 2.6.4. I think it has to do something with this gtk package, quote from the rox-filer page: "The filer uses GTK to load images. As long as you have SVG support in GTK, ROX-Filer will load them fine."
Sorry that I can't give a solution. I only wanted to say that another one has this problem.
Anyone else? Or anyone has already a solution?
I am using fluxbox and I can't use any svg icons for Rox-filer icons theme. I installed librsvg already... Any ideas on how to make it works?
With the recent GNOME removal, Patrick Volkerding also removes the lbrsvg library which was in gnome/. So a current, fully installed slackware-current system lacks this library : when building the GTK+ package tree, the SVG loader does not get register to GTK+ and you can't use SVG icons with GTK+ anymore. It means that current GTK+/GNOME icon themes with SVG icons can not load SVG icons.
To solve the problem, install librsvg after gtk+2 & gdk-pixbuf, then run as root :
(Of course, it gives the same result as editing the file "by hand" as you tell it before)
In fact, a well-designed package would execute the gdk-pixbuf-query-loaders command at install time.
However it seems that Patrick Volkerding prefers to take a kind of snapshop of installed files to avoid using a post-install script (install/doinst.sh). IMHO, it is really a bad solution unless you only use official Slackware packages : the next time you will upgrade your gtk+2 package with a new Slackware one, it will overwrite your gdk-pixbuf.loaders file. And obviously, you will have to run (again) the gdk-pixbuf-query-loaders command to register the pixbuf loaders which were not installed on Patrick Volkerding's computer : it would not be the case if a proper post-installation script (install/doinst.sh) is used.
And you guess it, it will be so until Patrick Volkerding decides to do "the right thing", as there is no technical reason against it. Even when installing from the install disks (or cdrom) which use a relocated root directory with "installpkg -root root_fs", he could use "chroot . command_to_run" from the install/doinst.sh script to run the command_to_run on the being installed Slackware system. At least, provided that "ldconfig -r root_fs" (or "chroot root_fs ldconfig" since ldconfig is not present on the installation system) is used by installpkg to update the libraries cache and links of the being installed Slackware system. But installpkg does not currently run ldconfig that way...
Another issue : the gtk+2 package does not generate icons cache files for improved memory managment with GTK+ > 2.6.x (see the gtk-update-icon-cache man page). You have to build them manually with gtk-update-icon-cache to used this feature. And you should run it every time you install or upgrade a new GTK (or GNOME) icon theme.
And the gtk+2 package is not the only one in that case ...
And you guess it, it will be so until Patrick Volkerding decides to do "the right thing", as there is no technical reason against it.
well, you might send Pat an email with a link to this thread.........so he can do the right thing.............but he may just blow it off since he does not support using "swaret" at all...........you never know.......
Originally posted by freakyg well, you might send Pat an email with a link to this thread.........so he can do the right thing.............but he may just blow it off since he does not support using "swaret" at all...........you never know.......
Sorry, I'm not talking about Swaret or other third party package managers for Slackware Linux. I am really talking about the official Slackware's package managment tools, the PkgTools (installpkg, removepkg and upgradepkg) which are the only tools I used to manage packages for years. Installpkg does support a post-installation script (install/doinst.sh in the TGZ package) : this is a standard feature of the PkgTools ... for years