To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=90483
                 Issue #|90483
                 Summary|OOffice Mac/X11 cannot be started in nonstandard envir
                        |onment
               Component|framework
                 Version|OOo 2.4.0
                Platform|Macintosh
                     URL|
              OS/Version|Mac OS X
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|moriborg





------- Additional comments from [EMAIL PROTECTED] Sun Jun  8 00:40:10 +0000 
2008 -------
The "main.scpt" AppleScript that is used to launch the OOffice binary on Mac OS 
X has a reliability issue 
with determining the current DISPLAY. On line 238, the following code is used 
to get the display number 
from output of ps:

set xdisplay to do shell script "ps -wx -o command | grep X11.app | grep 
\":.$\" | sed \"s/^.*:/:/g\""

This works in principle, but only if the relevant line returned by ps is 
shorter than 133 characters. 
Otherwise, it is truncated, and the DISPLAY is not recovered (above command 
returns an empty string). 
This only happens if the X11 application is located in some nonstandard path 
that is very long, or if the 
same is the case for the .Xauthority file. For example, if $HOME is not 
/Users/user/, but somewhere else.

The problem is aggravated by the fact that the AppleScript has no error 
handling whatsoever for the case 
that the command cited above returns an empty string. The symptom of the 
problem is that OpenOffice.org 2.4.app just seems to hang, nothing happens. 
OpenOffice is indeed started in the 
background, but it doesn't appear because there is no correct DISPLAY set.

The fix to this problem is to replace all calls to `ps -w` by `ps -ww`, 
especially the one on line 238.

Also, some more robust error handling would probably be appropriate.

---------------------------------------------------------------------
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]

Reply via email to