On Fri, 2003-07-25 at 11:48, Jeffrey Stedfast wrote: > ah, and what do you know... I've already reported a gconf bug about this > very problem and even submitted a patch back in March :-) > > http://bugzilla.gnome.org/show_bug.cgi?id=108574 > > Jeff > > On Fri, 2003-07-25 at 14:27, Jeffrey Stedfast wrote: > > On Fri, 2003-07-25 at 14:13, guenther wrote: > > > > We were only cloning Outlook "features", we thought this was expected > > > > behaviour :-) > > > > > > *outch* > > > > > > > > > > unfortunately I have no idea what the problem is and I would tend to > > > > think that somehow gconfd is not actually saving the settings to disk or > > > > something? > > > > > > As this works for a few reboots, doesn't this look more like "deleting" > > > or "corrupting" the CGonf entries, rather than "not saving"? > > > > here's what I think (tho I could be wrong): > > > > 1) evo saves the new settings to gconf (which caches them and doesn't > > save them to disk... or maybe it does save them to disk but xmlSaveFile > > corrupts the file (which it does, believe me... I was the bonobo-conf > > maintainer and had to work around this problem...) but gconf doesn't > > notice). > > > > 2) evo gets shut down, gconf is still being used by other apps and so > > stays up and running > > > > 3) evo gets restarted, retrieves cached settings from gconfd > > > > 4) repeat steps 2 & 3 a few times > > > > 5) gconfd gets shut down for some reason (idle quit?) > > > > 6) evo gets started up, starts up gconfd because it wasn't running, and > > queries for the settings. Since the settings were corrupted away back in > > step 1, evo doesn't have values (or invalid values) for some settings > > and so has to default them to whatever the default values happen to be > > for those corrupted settings. > > > > 7) user sends mail to [EMAIL PROTECTED] > > > > 8) fejj blames gconf :-) > >
Is there a workaround for this? I've tried 'evolution --force-shutdown' but that doesn't seem to do it. I would think killing the gconf processes would be a little to harsh and most likely cause other problems. But I'm relatively uneducated in this area. > > > > > > This would mean, Evolution silently imports the settings again. > > > > well, possibly... but ONLY if gconf is buggy in the first place and > > didn't save the setting that tells evo we've already imported the old > > settings. or else if thats etting got corrupted by gconf somehow... > > > > > > > > I would suggest dumping some values to a file (after setting these to > > > correct values) and dumping again when settings are being reset. There > > > must be a difference visible. > > > > > > Jeff, do you agree? > > > > yes, I would concur :-) OK, I can do that and reproduce the problem. Please tell me how. Is there a program/script I can run, or just make a copy of some file? Thanks for your help I really appreciate it. Mike -- Mike Dougherty Sr. Software Engineer | [EMAIL PROTECTED] XIFIN, Inc. | http://www.xifin.com Ph: 858.793.5700 | Fax: 858.793.5701 Fingerprint: 29DE DC92 822E B6F0 6A66 BCB8 8FE2 C562 7FB2 B342
signature.asc
Description: This is a digitally signed message part
