To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62416 Issue #:|62416 Summary:|autotest |f_scripting_organizers.bas::tScriptingOrganizers |fails due to incorrect workpath Component:|framework Version:|680m156 Platform:|All URL:| OS/Version:|All Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P3 Subcomponent:|ui Assigned to:|jsk Reported by:|jsk
------- Additional comments from [EMAIL PROTECTED] Wed Feb 22 00:59:50 -0800 2006 ------- On badly configured Solaris machines the UNO service to retrieve the users workpath might deliver a path like "$(user)/..." or - on some occasions, when the UNO connection breaks - there might be no path information at all. The function framework/tools/inc/filetools.inc::hGetWorkPath() must be changed that it can handle broken connections and invalid paths by using a fallback (gOfficePath & "user/work"). Beware that the fallback again relies on the UNO service which is kind of stupid but appears to work now and will break at a later time. --------------------------------------------------------------------- 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]
