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 255248 - Launching Evo when already running shouldn't start second instance
Launching Evo when already running shouldn't start second instance
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Shell
2.6.x (obsolete)
Other other
: Normal enhancement
: Future
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 333715 433312 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-03-06 09:35 UTC by Julien Olivier
Modified: 2008-11-19 14:25 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Julien Olivier 2004-03-06 09:35:08 UTC
Description of Problem:

Sometimes, I accidently click on Evolution's
launcher while Evolution is already running. I'd
like it to show the already running instance
instead of opening a new window.

Steps to reproduce the problem:
1. Launch Evolution.
2. Minimize the main window.
3. Launch Evolution again.

Actual Results:

You get 2 main windows.

Expected Results:

The first main window should be brought up instead
of creating a new one.

How often does this happen? 

Always.

Additional Information:

Tested on Fedora Core 1.
Comment 1 André Klapper 2006-03-07 16:16:43 UTC
shortening summary
Comment 2 André Klapper 2006-03-07 16:17:34 UTC
*** Bug 333715 has been marked as a duplicate of this bug. ***
Comment 3 Kevin R. Page 2006-08-29 13:13:54 UTC
This is still occuring for me - running FC5.

Furthermore, when I use the original instance of Evo after accidentally launching the second, the first instance crashes (it seems to be when I first access a different mailbox or message).

This happens even if I've closed the second instance before going back to using the first.

This is especially confusing for novice users who are tempted to run "Run Again" when the first instance crashes, starting the whole cycle again.
Comment 4 Sam Morris 2006-09-07 16:13:17 UTC
Perhaps not a related issue... usually if I run evolution a second time, it exits after telling the original instance to open a new window. However sometimes (if evo has been open for a few days) the new instance can't find/locate/contact the first instance and so a whole new copy of evolution is launched.
Comment 5 André Klapper 2007-04-28 01:09:49 UTC
*** Bug 433312 has been marked as a duplicate of this bug. ***
Comment 6 tmp 2007-05-13 06:39:16 UTC
This still happens with version 2.10.0

The behaviour should be like Gedit's behaviour - which only starts one instance even when clicking on Gedit's launcher again.
Comment 7 tmp 2007-06-16 08:38:09 UTC
This bug is still in Evolution 2.11.3. Following bug describes the same problem:

http://bugzilla.gnome.org/show_bug.cgi?id=430149

It is very annoying especially if you click on a date in the clock applet and Evolution is already open...

How many bug reports shall be written about that until it gets confirmed?

Isn't it possible to check at startup if Evolution is already running?

Thanks.
Comment 8 lsof 2007-06-17 20:06:51 UTC
Just to add my own comment - running two instances on the same machine should not be possible, but running two instances of the evolution client (one local, one remote) both talking to the same evolution data server shouldn't be forbidden.
Comment 9 Martin Meyer 2007-10-01 13:48:13 UTC
Could GtkUnique be useful to do this? I remember some chatter about it on d-d-l a couple months ago, maybe it would help here.
Comment 10 Gilles Dartiguelongue 2007-12-03 13:14:51 UTC
guys please consider that it is also a feature where you can view two both calendars, mails and contacts without clicking like mad to go back & forth.

Imho, it should be possible to be able to choose whether or not starting a component a second time should:
1 - raise the component's view (if started) or start one
2 - switch the running evolution window to this view
3 - create a new view (current behavior).

This behavior would be controlled by a gconf setting and most distros would probably want to set it to 1.
Comment 11 Matthew Barnes 2008-03-11 00:28:59 UTC
Bumping version to a stable release.
Comment 12 Matthew Barnes 2008-11-19 14:25:14 UTC
Launching Evolution a second time informs the first instance to open a new window.  The second instance then terminates.  Closing as NOTABUG.