2012/1/14 Александр Цамутали <asts...@yandex.ru>: > Sergey Mironov <ier...@gmail.com> writes: > >> Hi. I've installed oxygen-gtk theme and tried to switch it on by linking >> >> [ierton@pokemon:~]$ ls -l .gtkrc-2.0.mine >> lrwxrwxrwx 1 ierton users 64 Янв 13 13:55 .gtkrc-2.0.mine -> /var/run/ >> current-system/sw/share/themes/oxygen-gtk/gtk-2.0/gtkrc >> >> (.gtkrc-2.0.mine is included from .gtkrc-2.0) >> >> It works, partly. Now all my gtk apps issue a warning >> >> /nix/store/nb08bx0r8hj14l9gf7xprv1kb0vy1w2m-wicd-1.7.1-beta2/share/gtk/ >> gui.py:152: GtkWarning: Unable to locate theme engine in module_path: >> "oxygen-gtk", >> >> and some parts of interface look ugly. >> >> Well, I am not a gtk expert. Lxappearance app (not in tree, i've installed it >> locally) didn't help - it couldn't detect the presence of oxygen theme in my >> system. Does anybody know a better way of setting things up? > > I tried the same with murrine a long time ago with the same result. It > seems we need to patch GTK+ to help it find paths to theme engines for > ex. from environment variable.
It's not ideal/pure, but this is how I do it for KDE: https://nixos.org/wiki/Enable_GTK_themes_in_KDE _______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev