Issue 55417 - Multiple X11 displays results in incorrect behavior
Summary: Multiple X11 displays results in incorrect behavior
Status: CLOSED DUPLICATE of issue 60696
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC Unix, all
: P3 Trivial with 4 votes (vote)
Target Milestone: OOo 2.x
Assignee: hennes.rohling
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-03 20:10 UTC by kumaran
Modified: 2007-05-31 15:41 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description kumaran 2005-10-03 20:10:55 UTC 
This issue is manifested when OpenOffice is used on a computer
with more than one X11 display.  It can easily be seen by using
VNC to create an additional X11 display.

The general problem is that the user is unable to launch two
instances of OpenOffice, one on each X11 display.  Instead, the
program opens a new window in the existing process.

It seems like the running instance detection algorithm is using
only the username to find the current instance.  Instead, the
instance should be tied to both the username and X11 display.

Here are the steps to reproduce this problem:

1) Launch a VNC server with an Xterm
2) Connect to it using a VNC client
3) Using the VNC xterm, launch oowriter
4) Go outside the VNC client to a normal Xterm
5) Launch oowriter

At this point, OpenOffice detects that there is an instance
running under the same username and launches another oowriter
inside the VNC server.  This is not the desired behavior, since
the user may have wanted to have instances both inside and
outside the VNC server.

I have not had a chance to look at the startup code, but I
would suspect that it is a relatively straightforward change
to have OpenOffice look at both username and $DISPLAY to
determine whether or not to open a new instance.

The issue is present in both the 1.x and 2.x series.
Comment 1 thorsten.martens 2005-10-14 11:23:01 UTC 
.
Comment 2 theferret 2006-05-08 23:24:54 UTC 
How is this "status: unconfirmed", after being in here for over 6 months?!?!?!

Come on people.. this is a definate bug, and its a very annoying one. I have two
monitors attached to my workstations for a reason: I like seeing documents
side-by-side, on two separate displays, :0.0 and :0.1

Please fix this bug soon :-(
Comment 3 Olaf Felka 2006-05-09 08:29:52 UTC 
This issue is unconfirmed because nobody has confirmed yet. Pretty simple, isn't
it? Issues don't just get confirmed if they are old enough. And I won't state
that this is a defect. That's how OOo works. Maybe it's misdesigned but I think
it works as designed. So at least this issue shouldn't be a defect but an
enhancement.
Comment 4 hennes.rohling 2007-05-23 00:58:17 UTC 
Taking over
Comment 5 hennes.rohling 2007-05-23 01:04:57 UTC 
Target set.
Comment 6 hennes.rohling 2007-05-31 15:35:50 UTC 
This is not a defect it's by design.

Yes, I share your opinion that the behavior should be changed. OOo uses username
+ user installation path to detect an already running office process.

Currently there's a workaround starting soffice with
-env:INIFILENAME=mydifferent_bootstraprc where you define a different user user
installation path.
Comment 7 hennes.rohling 2007-05-31 15:41:15 UTC 
The issue will be adressed along with faster loaders that should set a
meaningful context which params are used for process detection. Including
$DISPLAY was what I'm thinking about for "normal" desktop usage of OOo but there
are some other scenarios where $DISPLAY should be ignored.

*** This issue has been marked as a duplicate of 60696 ***
Comment 8 hennes.rohling 2007-05-31 15:41:53 UTC 
Closing duplicate