GNOME Bugzilla – Bug 625769
entered appointments getting lost when working from remote and local and suspend to RAM
Last modified: 2017-07-29 15:16:51 UTC
Sorry for the bad summary. Please improve if you can. I am using the terminal server project X2go [1]. One desktop system – let us call it A – is acting as a server and a client. The following happened. On a different system (B) I started a GNOME session on A using X2go and started Evolution and entered some appointments into the calendar. Then I suspended this session and logged into A using GDM. (So two GNOME session should be active now. (?)) From this session I resumed the suspended X2go GNOME session where Evolution was still running and entered appointments too. Then I suspended A (`pm-suspend`) from the regular session and turned the system back on and continued to work in the X2go session and entered appointments. Then I closed Evolution in the X2go session and logged out, so only the regular session was running on A. I started Evolution and all the appointments entered after the suspend were gone. Sorry, I find it very hard to describe. I hope my description makes sense. I chose critical as the severity, because I lost some data. I do not know what might be the culprit. Do you have an idea? Thanks, Paul [1] http://www.x2go.org/
I don't get it, even after reading it three times.
(In reply to comment #1) > I don't get it, even after reading it three times. I am sorry. Where do you get lost? I tried my best and I do not how to describe it differently.
Apart from my bad reading skills, does that problem still exist in 3.12 or 3.10?
Can this specific issue still be seen in the latest 3.12 release(s)?
It truly depends on what the calendar type is. Evolution stores the events immediately in all of them, but it can take longer in certain types. The appointment/meeting editor doesn't close, if there was any error reported about the failed event saving. That can include things like lost connection to the server and so on. Maybe bug #673894 is related. It really depends what calendar type you use and see this misbehaviour with.
(In reply to Milan Crha from comment #5) > really depends what calendar type you use and see this misbehaviour with. Closing this bug report as no further information about the calendar type has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!