Apache OpenOffice (AOO) Bugzilla – Issue 41864
Issue with remote OpenOffice
Last modified: 2008-05-17 23:58:01 UTC
Letz have 2 machine local.machine.com and remote.machine.com 1. from local.machine.com open a ssh -X to remote.machine.com. 2. Start OpenOffice remotely on remote.machine.com with display exported to local.machine.com 3. It comes up properly. 4. With the OOo open, now go to remote.machine.com and open a terminal an start Openoffice. It displays OOo on local.machine.com instead displaying locally. Itz seriously bad. Im seeing it on m72.
wrong component, changing to framework
Hi sragavan, thanks for using and supporting OpenOffice.org... I see this issue, too... reassigned to pl... mci -> pl: Hi pl, this is about the issue I showed you a time ago... Same procedure by trying to start Office from Solaris on a remote Linux machine... Same procedure by trying to start Office from Solaris on a remote Solaris machine... Please have a look at this, thanks...
mci: i don't know what you showed me "a while ago" This problem is known since before OOo became open source; OOo is not capable of running multiple OOo processes for the same user on the same machine. Instead a newly started OOo signals the running instance to come to top. This is not a gsl limitation rather a problem of concurrent file access; whether there are motions to change this i do not know. pl->mba: perhaps you know whether this is planned to be fixed ?
There is a plan to start OOo with a command line parameter that tells it to either use no user configuration. That would workaround the problem. Even the current version can work with different user installations if the UserInstallation bootstrap parameter is specified on the command line. IIRC this should be documented in the Developers Guide. Everything else (either in configuration handling or in VCL) is too much and there are no further plans to change it. So the status of this issue for the next time (25 years or so ;-)) is "WontFix". Perhaps the workaround I mentioned is useful.
mci -> pl: Ooops, I didn't see that the first session was left open....
Srini - there are a number of potential fixes. One would be to do some interlocking via the X root window, to grab a random key fragment to mangle into the shared socket name I guess in /tmp/OSL_*. Or as a cheaper/easier fix we could attempt to canonicalise the DISPLAY environment variable [ there is unfortunately no really reliable way to do this ], and mangle that into the factory socket path. either way - if it's not a regression since 1.1.x then it's of a lower priority I guess. We should file a bug in our internal bugzilla if up-stream don't have plans to address the issue though.
*** Issue 30872 has been marked as a duplicate of this issue. ***
*** Issue 57321 has been marked as a duplicate of this issue. ***
*** Issue 58800 has been marked as a duplicate of this issue. ***
This issue makes it very difficult to use OpenOffice efficiently on nonXinerama multiheaded displays. I'm looking at switching to another word processor because I can't have more than one document open at once on my three monitors. OpenOffice is the only program I have this difficulty with, and I encourage you to consider solutions to this issue.
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew