cant use svg icons
hi guys,
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? thx. |
Hi.
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? dj-tj |
anyone?
............. |
re: cant use svg icons
yep ;)
since last update in current, with gtk+2.6.4 you need to edit /etc/gtk-2.0/gdk-pixbuf.loaders, and add the fellowing lines: Code:
"/usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so" ------------------------------------------------------------------ http://ayo.blogsite.org |
Thanks!!!
It worked for me too. But I had to add one further line: Code:
"/usr/lib/gtk-2.0/2.4.0/loaders/svg_loader.so" |
ah thanx...it worked for me too....cheers
|
I had the same problem: I have just updated to slackware-current.
I spent to much time until I read Your solution ... Thanks. I think where is an "error" in the gtk-2.6 install script: the following instruction is missing: Code:
gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders |
I addes the lines but Rox still won't use the svg icons... rsvg works. I had it working before (prev. install) but I can't remember how.... Any suggestions?
edit. Ok, I got it working now. Some sort of dependency problem I think. |
Re: cant use svg icons
Quote:
To solve the problem, install librsvg after gtk+2 & gdk-pixbuf, then run as root : Code:
gdk-pixbuf-query-loaders > /etc/gtk-2.0/gdk-pixbuf.loaders LiNuCe |
thx LiNuCe, u did the trick.
|
Quote:
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 ... |
Quote:
|
Quote:
|
All times are GMT -5. The time now is 10:27 PM. |