dogpile found a couple of mentions of (what appears to be) the bug in question and refers you to
http://bugs.kde.org/buglist.cgi ...where the response time is, unfortunately, not great. Do a query there for the error string you mentioned and you'll get this petite little URL which seems to point you to a script that may help diagnose/fix what may be a setup problem: http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=Mutex+destroy+failure%3A+Device+or+resource+busy&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0= _______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss