To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62176
------- Additional comments from [EMAIL PROTECTED] Sun Feb 26 09:05:13 -0800 2006 ------- Im 99% sure that the gtk-update-icon-cache message is NOT related to the problem of yast hanging up. If it was, then it would be a massive bug in yast. (Since 1st of all it should not hang at all and 2ndly it would hide messages printed to stderr - that would be a huge bug by itself) Ans although locolor might be KDE-specific, there still may applications making use of an icon-cache (that is not Gnome or GTK-only). And as the message from the reporter shows, there /is/ an icon-cache present. If there would not be a cache, that directory would be skipped anyway. Updating the icon-cache can take a while (but should not take 15 minutes) I installed SuSE 10.0 again yesterday and now making a disk-image so I can plug it in in future more easily. ######################## Just remove the icon-theme.cache file from the locolor-directory and you won't get the message. You can take this as a test whether the gtk-update-icon-cache really is the problem (I doubt that, but well - it is just software...) I'd rather say it is the trigger-scripts that fail to run when called by yast. But just skip the menu-integration package and see whether that causes yast to hang as well. If it doesn't hang, then there's something wrong with the menu-integration package. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
