Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

evolution doesn't understand the concept of multiple X displays, and
does bad things if you start in on display #1 when it's already running
on display #2.

Steps to reproduce the problem:

1. Start evolution on the console of some Linux PC.
2. Log into the PC via rlogin or ssh from some other PC, set DISPLAY
    to point to the x server of the other PC.
3. Start evolution on the second machine.

Actual Results:

I would expect something like what elm does: a message saying that
evolution  is already running, possibly with an option to try to kill the
other instance.

Expected Results:

evolution simply exits, but a new evolution window pops up on the remote
machine.  This was really bad the first time I encountered it, because one
of the two machines was at home and one was at work.  On my home machine
I saw no error message of any kind, it appeared that evolution just
immediately, silently exited.

How often does this happen? 

Every time.

Additional Information: