To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=15229
------- Additional comments from [EMAIL PROTECTED] Thu Jan 24 17:55:04 +0000 2008 ------- I've just run into this today, as follows: 1)My desktop machine happens to have a copy of OOo running, with a document open. 2)I'm sitting at my laptop, and receive a word document by email. I scp it to the desktop, and open it by running oowriter over SSH.(*). This normally displays the document fine on my laptop's screen. 3)In this instance, the oowriter command simply exited, without appearing to do anything (and of course, the document opened on the wrong display). As a minimum workaround, can I suggest that if the startup script detects an existing Ooo process, but on a different $DISPLAY, it should print a message to stderr. I understand the reason why the document opens in the existing process, but the principle of "least surprise" would strongly suggest printing a message. As well as stderr, display this message (on the expected $DISPLAY) via xdialog (or kdialog, or zenity, whichever is installed). A suitable message might be: "You have tried to open the file $DOCUMENT on display $DISPLAY (on host $HOST). However, an instance of OpenOffice is already running on that machine (on display $DISPLAY2), so this file has been opened in the existing OOo process. [If you want it to open on this $DISPLAY, please close the other document. killall -15 oowriter will force an auto-save]" #is that actually true about killall -15? I hope so, but I haven't checked:-) (*)Why do I do it this way? The desktop is much faster, I have gigabit ethernet, and the laptop has an issue that clicking the file menu in Ooo usually causes X to hang. --------------------------------------------------------------------- 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]
