Description of problem: I backed up a calendar file from an fc20 system. When I restored to an fc22 system, evolution would not automatically restart. Version-Release number of selected component (if applicable): evolution-3.16.3-2.fc22.x86_64 How reproducible: Tried only once Steps to Reproduce: 1. Generated backup file on FC20 system 2. Restored to FC22 system Actual results: Evolution refused to restart, saying another inactive evolution might be active. Expected results: Automatic restart Additional info: After complete system shutdown and restart, evolution works OK.
Thanks for a bug report. What did you use to backup the calendar file and what to restore it, please? Using Evolution's built-in File->Backup Evolution Data and File->Restore Evolution Data (eventually restore within the first time wizard) saves/restores everything, not only calendars.
Yes, I used File-Backup and File-Restore, as described. In both systems, Evolution forced a shutdown of itself, with a possible restart. But restarting in the same session failed for me. I still have the backup file, but if I provoide a copy, it would have to be treated as confidential.
(In reply to Peter H. Jones from comment #2) > I still have the backup file, but if I provoide a copy, it would have to be > treated as confidential. That's okay, I'll generate one myself and will try to reproduce. Thanks.
I was able to reproduce the behaviour, even my error message is slightly different, it says: > Cannot start Evolution. Another Evolution instance may be unresponsive. > System error: No such interface 'org.freedesktop.DBus.ObjectManager' on > object at path /org/gnome/evolution/dataserver/SourceManager The first line is rather informative and doesn't change at all. It's only a guess. The other two lines show the exact error message, as reported by the system, which leads to the right issue. Interestingly trying to run evolution from a command line leads to a different error, just as you reported. In any case, I filled this upstream [1] and fixed it for the next release as well. [1] https://bugzilla.gnome.org/show_bug.cgi?id=751108