GNOME Bugzilla – Bug 322951
gw: Cache Oddness On New Accounts
Last modified: 2013-09-14 16:49:02 UTC
Please describe the problem: I have seen this before and it's still in the current builds. When you set up a new user from scratch, there seems to be a temp file or something that isn't being built. When you try and check the box for GroupWise calendars the first time, you get a dialog that reads "Error on groupwise://drichard@128.222.30.30/: Could not create cache file" (attaching shot) It continues to do this over and over again, and finally a combintation of clicking on it and closing Evolution over again it finally checks and works. Once checked, it always works and has no problems. I really think somewhere a directory isn't being built or something and the program doesn't have a place to store the Cache information. Maybe in the place where this dialog is produced, you can put in a check to ensure the cache directory is really there. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Created attachment 55490 [details] Dialog that displays when first activating a GW calendar checkbox.
Bumping to "High". It's not fun spending 10 minutes going in and out of Evolution to get the calendar source to connect.
Please start evolution-data-server separately and check if you get any warnings in the terminal while this error appears. It would be really helpful if you attach them here.
Ok, I got it to happen with EDS running in the foreground. Attaching file of everything that came out on the command line. Hope something appears here that is useful.
Created attachment 56730 [details] EDS log when cache dialog appears.
If you want to see this in action, just delete all of your Evolution and gconf directories and create a GroupWise account from scratch. It's buggy in regards to cache getting it to connect and work. You have to go out and in a few times and click through these messages and then it works. Once it works, it seems more stable and to 'stick'.
must be a threading issue. The GType values is getting reinitialized to 0 which is causing the problem. I have sent a patch for review.
Have committed the fix to CVS HEAD.
Can you please test the build provided and see if the issue has been fixed ?
I haven't seen this since the fix went in....I'll close and continue to monitor.