After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343952 - beagled crashing on EvolutionDataServer
beagled crashing on EvolutionDataServer
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
0.2.6
Other Linux
: Normal major
: ---
Assigned To: Beagle Bugs
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-06-05 21:41 UTC by Russell Harrison
Modified: 2007-01-22 20:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
output from "beagled --fg --debug" (2.48 KB, text/plain)
2006-06-05 21:42 UTC, Russell Harrison 		Details
beagled log file (2.71 KB, text/plain)
2006-06-05 21:44 UTC, Russell Harrison 		Details
BeagleExceptions file (2.62 KB, text/plain)
2006-06-05 21:45 UTC, Russell Harrison 		Details

Description Russell Harrison 2006-06-05 21:41:25 UTC 
beagled seems to run just fine until I start Evolution, or when it gets around to indexing things from the data server.  I'm pretty sure this started with the last update of the FC5 evolution packages.

This bug has already been reported on Red Hat's bugzilla but I wanted to make sure it was here as well.
Comment 1 Russell Harrison 2006-06-05 21:42:33 UTC 
Created attachment 66795 [details]
output from "beagled --fg --debug"
Comment 2 Russell Harrison 2006-06-05 21:44:24 UTC 
Created attachment 66796 [details]
beagled log file
Comment 3 Russell Harrison 2006-06-05 21:45:00 UTC 
Created attachment 66797 [details]
BeagleExceptions file
Comment 4 Russell Harrison 2006-06-05 21:47:20 UTC 
Red Hat Bugzilla link:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186144
Comment 5 Kevin Kubasik 2006-06-06 01:23:58 UTC 
I believe there is a workaround for this in CVS, (we catch the exception and let the program continue to run, although that calendar will not be indexed) I believe it stems from a version mismatch in evolution-sharp and eds...
Comment 6 Russell Harrison 2006-06-06 01:35:14 UTC 
Should this be kicked over to evolution-sharp then, or is it a packaging problem?  I'm going to try rebuilding evolution-sharp and see if that fixes the problem.
Comment 7 Veerapuram Varadhan 2006-06-06 11:21:00 UTC 
This is a bug in evolution-sharp.  As of from 1.6 and (1.5) releases, a change has been made to the Calendar backend for which, before opening a calendar, we should set a default timezone for it.  However, I guess, this shouldn't crash. Let me try to dig it out.
Comment 8 Russell Harrison 2006-07-12 21:41:45 UTC 
This seemed to be fixed for awhile but it looks like its back with the latest push of evolution-sharp to Fedora Core 5.

Shouldn't the expected behavior be that failed backends are simply disabled and logged (perhaps a dialog box).  There really isn't any reason beagled shouldn't continue indexing the other backends.
Comment 9 Debajyoti Bera 2006-11-25 04:46:13 UTC 
There is news that new evo-sharp is in town. Does that fix this problem ?
Comment 10 Russell Harrison 2006-11-27 16:50:38 UTC 
I guess from your standpoint it is.  I've upgraded to FC6 where the problem is fixed.  I don't have a machine to test FC5 with any more.  :-(  I wish it were possible to handle upgrades of the evolution data server better.  Almost every package that uses it breaks when upgrades get pushed.
Comment 11 Joe Shaw 2007-01-22 20:17:09 UTC 
Ok, I am going to close this then.  Reopen it if you see the problem.