GNOME Bugzilla – Bug 224885
Does Not Allow Multiple Sessions
Last modified: 2012-02-08 22:50:09 UTC
Evolution has 2 problems that are related to the same issue. It does not support multiple logins by the same users working on different $DISPLAY's. If a user logs in at their desk, and then is another part of the building and tries to log in from there, it won't let you start another session. It starts another session back at their desk. Evolution should allow a user to be logged in from multiple terminals at the same time. If when a user logs out of Evolution, if some of the processes don't die for whatever reason, and the user comes in the next day and logs in from another terminal, their sessions start up again on the original terminals. It seems to find the hung processes and use them to figure out where to run. Those processes have to be killed before they can log into the new terminal.
Tentatively putting this on the 1.2 list.
Setting target milestone to 1.4.
Still not working in 1.3 developers build. The first session starts correctly, the second time that you try and run it, it just sits at the evolution-1.3 prompt and never comes back. No GUI appears.
*** bug 226898 has been marked as a duplicate of this bug. ***
Re-assigning to myself. I made a patch yesterday and sent it to the list which allows evolution to be used on multiple displays by the same user.
What was the patch fate?
*** bug 237001 has been marked as a duplicate of this bug. ***
So, multiple displays can work, but there is the problem of a shared camel session that makes the mail views get out of sync.
that sounds like an object activation problem to me.
adding dependency as discussed with nags on irc.
Dave: Is this still a problem in recent versions? (I wonder how I could test this.)
It's always wonderful to see 10 year old requests. ;) It would be wonderful if this worked but it seems like the infrastructure to handle this is a huge rewrite. The two sessions would have to be aware that two instances of running. If settings were changed in one, the other would have to make the changes too. If there are any tmp type files that are written, they would have to be engineered to never clobber each other. Having this feature would allow enterprise users to have email open twice from different workstations. To replicate it, you'd have to ssh into your computer from another computer and set your DISPLAY and start a second instance.
All you need these days is a separate D-Bus message bus for two separate Evolution instances to run simultaneously, then you can corrupt your local cache files to your heart's content. No intention of changing Evolution's single-instance characteristics. WONTFIX.