On Saturday 17 April 2010 20:45:32 David C. Rankin wrote:
Yast2 Gurus,
There appears to be a problem with suseconfig.gtk2 that results in an invalid icon cache being created. From /var/log/YaST2/suseconfig.log:
Executing /sbin/conf.d/SuSEconfig.gtk2... /sbin/conf.d/SuSEconfig.gtk2: line 67: test: /usr/share/icons/Azenis: binary operator expected /sbin/conf.d/SuSEconfig.gtk2: line 67: test: /usr/share/icons/Azenis: binary operator expected gtk-update-icon-cache: The generated cache was invalid. /sbin/conf.d/SuSEconfig.gtk2: line 67: test: too many arguments gtk-update-icon-cache: The generated cache was invalid. gtk-update-icon-cache: The generated cache was invalid. /sbin/conf.d/SuSEconfig.gtk2: line 67: test: /usr/share/icons/Royal: binary operator expected Finished.
What's going on here? It looks like there is a bug with the number of operators being passed when suseconfig.gtk2 is run. What does the invalid cache mean to me? Is there a fix? Any help will be greatly appreciated.
It looks like SuSEconfig.gtk2 does not expect there to be a space in the name of the icon theme. What are the full paths of /usr/share/icons/Royal* and /usr/share/icons/Azenis* ? Do they contain spaces? According to the Icon Theme spec, icon theme's internal names are the name of the /usr/share/icons subdirectory, and they may not contain spaces: http://standards.freedesktop.org/icon-theme-spec/latest/ar01s03.html But SuSEconfig.gtk2 should be more robust, therefore this is a bug. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org