After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 221098 - [KB-Fixed] Evolution opens in a different display
[KB-Fixed] Evolution opens in a different display
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Shell
2.6.x (obsolete)
Other All
: Normal normal
: Future
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[kill-bonobo]
: 200740 209777 216177 216919 217361 218492 227570 246497 250398 263699 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-02-26 21:06 UTC by Alex Wallace
Modified: 2009-08-30 05:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alex Wallace 2002-02-26 21:06:31 UTC
Description of Problem: When in gnome, in a different display, let's say through a second login or if running from within a vnc server display, evolution instead of opening in the current display, opens always at display :0


Steps to reproduce the problem:
1. Login into gnome
2. Goto System/New Login And log in under a different user.
3. Try to run evolution from the new login

Actual Results: Evolution opens in first gnome session.


Expected Results: Evolution should open in the current session


How often does this happen? Every time


Additional Information:
Comment 1 Gerardo Marin 2002-03-29 08:51:12 UTC
*** bug 218492 has been marked as a duplicate of this bug. ***
Comment 2 Gerardo Marin 2002-03-29 08:54:01 UTC
*** bug 216919 has been marked as a duplicate of this bug. ***
Comment 3 Gerardo Marin 2002-04-11 02:32:27 UTC
*** bug 217361 has been marked as a duplicate of this bug. ***
Comment 4 Gerardo Marin 2002-04-11 02:37:30 UTC
*** bug 209777 has been marked as a duplicate of this bug. ***
Comment 5 Gerardo Marin 2002-04-24 03:16:59 UTC
*** bug 216177 has been marked as a duplicate of this bug. ***
Comment 6 Gerardo Marin 2002-07-11 16:45:46 UTC
*** bug 227570 has been marked as a duplicate of this bug. ***
Comment 7 Gerardo Marin 2002-10-01 20:10:50 UTC
Ettore: any milestone on this?
Futuring for now.
Comment 8 Gerardo Marin 2003-07-17 17:16:53 UTC
*** bug 246497 has been marked as a duplicate of this bug. ***
Comment 9 Gerardo Marin 2003-07-17 17:19:23 UTC
*** bug 200740 has been marked as a duplicate of this bug. ***
Comment 10 Antonio Xu 2003-07-28 10:04:06 UTC
Who can tell me when we can fix this issue?
Comment 11 Gerardo Marin 2003-10-31 21:24:43 UTC
*** bug 250398 has been marked as a duplicate of this bug. ***
Comment 12 Ettore Perazzoli 2003-12-02 21:00:49 UTC
I don't think this can be fixed for 2.0, it's too much work to make
the whole app multi-display aware...
Comment 13 Andreas J. Guelzow 2005-03-29 21:06:08 UTC
Can't you at least let evolution start a second instance if it is
started from a login on a second (remote) display?
Comment 14 Not Zed 2005-04-12 06:39:06 UTC
no we can't.  you can only have one instance of evolution running at a time for
a given user.
Comment 15 Not Zed 2005-08-09 09:59:50 UTC
*** Bug 263699 has been marked as a duplicate of this bug. ***
Comment 16 Ed Avis 2005-08-20 10:36:22 UTC
This bug may be a lot of work to fix, but you could make things better by
popping up a message box

    'Sorry, Evolution is already running on a different display.  Please close
Evolution there if you want to run it here, blah blah blah...'

The current behaviour is very puzzling to the user since there is no feedback on
the display they're now using to say what is happening.  So at least give some
message.

If nothing else, displaying a message to the user would reduce the volume of
duplicate bug reports that come in about this.
Comment 17 André Klapper 2006-03-29 23:55:42 UTC
guess this still hasn't changed?
Comment 18 Luke Hutchison 2006-04-03 17:21:01 UTC
No, still broken for me on Evolution-2.6.  Evo just opens the second window on the same display as the one it is currently running on.

Firefox does what was suggested in Comment #16, but that is annoying in its own right.

Comment 19 Matthew Barnes 2008-11-19 11:21:43 UTC
Running multiple instances could lead to data corruption, but perhaps we can look into the warning dialog after the kill-bonobo branch lands.  I'll probably wind up using libunique for single instance support, so I'll try to remember to look into it then.
Comment 20 Matthew Barnes 2009-01-28 18:17:55 UTC
I have libunique integrated into Evolution now, and libunique appears to be designed to handle this correctly.  Reminder to myself to double check.
Comment 21 Matthew Barnes 2009-08-25 02:33:10 UTC
Tagging this as fixed on kill-bonobo.
Comment 22 Matthew Barnes 2009-08-30 05:52:51 UTC
The "kill-bonobo" branch has been merged into "master" and will debut as Evolution 2.29.1.  We believe the branch has addressed the reported issue.  If you find the issue still exists in version 2.29 or later please feel free to re-open this bug.

Closing as FIXED.