Since upgrading to evolution 1.2.x from 1.0.8 (initially with ~ppc packages, but now with current 1.2.3), I have had the following error messages when attempting to use my calendar: "The calendar backend for file:///home/cwitt/evolution/local/Calendar/calendar.ics has crashed. You will have to restart Evolution in order to use it again." and "The task backend for file:///home/cwitt/evolution/local/Calendar/calendar.ics has crashed. You will have to restart Evolution in order to use it again." These messages show up any time I attempt to view my calendar...specifically, when I attempt to move beyond the displayed view that initially pops up (current day, or week) to a day or week in the past or in the future. I've checked for the installation of current gnome apps and libraries. I also unmerged evolution, and re-emerged the current 1.2.3 version, but the problem persists. The only thing I can think of (if this isn't *really* an evolution bug) is that I have a library issue somewhere. Forum searches, bug searches, and chat room conversations have yielded no information to resolving the issue. This is my "last resort" to try to resolve the issue. Any help or insight greatly appreciated. Reproducible: Always Steps to Reproduce: 1. Open evolution. 2. Select calendar. Initial view does not initiate crash. 3. Move to a different day or week. Crash occurs. Actual Results: See error message descriptions above. Expected Results: Well, allow me to use, view, manipulate my calendar... I've exhausted all obvious (to me) avenues except uninstalling all my Gnome libraries and re-emerging them (making sure to do so all with non-"~ppc" versions). I'm just hoping someone can provide me with some insight on a direction I've not yet pursued. I've read of similar crashes occurring with the 1.4 cvs versions of evolution, which is why I assume this is a Gnome2 library I need to re-install or downgrade. Currently my system is set to ACCEPTED_KEYWORDS="~ppc" for some other applications, leaving me well open to having installed a buggy version of a library somewhere along the way.
this seems more like an evolution problem than a ppc problem hope you guys don't mind if i take this one..
thanks for the detailed report. there are a couple of things i want you to try: 1. making sure your evolution config files are correct a) backup your current ~/evolution directory b) start evolution using : evolution --force-upgrade 2. if it still crashes, can you do this: a) exit evolution and then run killev b) in one terminal window, run : gdb evolution-calendar - then type "run" and enter c) in another terminal window run: evolution d) then do what you need to do the make the crash happen e) when the crash does happen, go back to the first terminal window and type in: "thread apply all bt" and enter f) paste in the contents of the backtrace back here
OK. Followed your instructions (thank you). I had attempted the --force-upgrade option before, but to be thorough I did it again for our purposes here. Crash happened again. The gdb backtrace (such that it is) produced the following output: (gdb) run Starting program: /usr/bin/evolution-calendar (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 15623)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... gal-CRITICAL **: file gal-view-instance.c: line 376 (gal_view_instance_set_current_view_id): assertion `instance != NULL' failed. set_prop path: /commands/Week_View Week_View cal-client-Message: cal_query_destroy(): Could not release/unref the query cal-client-Message: cal_query_construct(): Could not issue the getQuery() request cal-client-CRITICAL **: file query-listener.c: line 314 (query_listener_stop_notification): assertion `ql != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `BonoboObject' Bonobo-CRITICAL **: file bonobo-object.c: line 270 (bonobo_object_unref): assertion `BONOBO_IS_OBJECT (object)' failed. calendar-gui-Message: update_query(): Could not create the query cal-client-Message: cal_query_construct(): Could not issue the getQuery() request cal-client-CRITICAL **: file query-listener.c: line 314 (query_listener_stop_notification): assertion `ql != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `BonoboObject' Bonobo-CRITICAL **: file bonobo-object.c: line 270 (bonobo_object_unref): assertion `BONOBO_IS_OBJECT (object)' failed. calendar-gui-Message: update_query(): Could not create the query cal-client-Message: cal_query_construct(): Could not issue the getQuery() request cal-client-CRITICAL **: file query-listener.c: line 314 (query_listener_stop_notification): assertion `ql != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `BonoboObject' Bonobo-CRITICAL **: file bonobo-object.c: line 270 (bonobo_object_unref): assertion `BONOBO_IS_OBJECT (object)' failed. calendar-gui-Message: update_query(): Could not create the query (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... cal-client-Message: cal_query_destroy(): Could not release/unref the query cal-client-Message: destroy_cal(): could not unref the calendar client interface object cal-client-Message: destroy_cal(): could not unref the calendar client interface object cal-client-Message: cal_query_destroy(): Could not release/unref the query (no debugging symbols found)...(no debugging symbols found)... Program exited normally. (gdb) thread apply all bt Cannot find new threads: generic error (gdb) Hope this helps. Thanks for your time.
Just did a ^c on the running gdb with evolution still running, then typed the "thread apply all bt" and got what I think you were actually looking for: Thread 1 (Thread 16384 (LWP 16147)): #0 0x0e73de8c in poll () from /lib/libc.so.6 #1 0x0e9fb8f0 in g_main_poll () from /usr/lib/libglib-1.2.so.0 #2 0x0e9fd460 in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #3 0x0e9fc3d8 in g_main_run () from /usr/lib/libglib-1.2.so.0 #4 0x0eb6cdfc in gtk_main () from /usr/lib/libgtk-1.2.so.0 #5 0x0fc4c6a0 in bonobo_main () from /usr/lib/libbonobo.so.2 #6 0x10082fdc in main () #7 0x0e684d2c in __libc_start_main () from /lib/libc.so.6 Now, I *really* hope this helps. :) Thanks again.
unfortauntely they don't help much. but thanks for the effort. the debugging message seems to indicate a problem with gal. do you have gal-0.23 merged? can you try re-emerging it and see if it does any better?
Yep. Had gal-0.23 merged. Re-emerged it as you suggested, but no joy. Problem persists (without restarting the entire Gnome backend). I'll test again after a reboot to make sure the problem didn't exist in something loaded prior to execution of evolution. Unlikely, but possible. What about bonobo? Could a problem there be causing an issue with gal?
Got curious, so I went and looked at bonobo packages to follow-up on my own question. evolution-1.2.3 is unmasked for ppc, but the required bonobo-1.0.21 is still a ~ppc masked package (as is bonobo-1.0.22, which is what I had installed). bonobo-1.0.19-r1 is the latest package that is fully unmasked for ppc. I emerged the 1.0.21 bonobo package (it is the version specified as a requirement for the evolution build), and am recompiling evolution-1.2.3 now to see if this resolves the issue. As they are not listed in the requirements for either bonobo or evolution, I am making the assumption that libbonobo and libbonoboui have no bearing on the problem.
Problem remained after bonobo adjustments. I'm out of ideas. You? My Palm conduits still work, so I guess I may just have to continue doing what I've been doing: anytime I want to look at or manage my calendar, I use my Palm instead of my desktop...and just make sure to sync regularly to get changes into the desktop (so they're there once evolution magically begins to work for me again). Sub-optimal, but functional.
ok, there are many people reporting a similar problem in ximian's bugzilla. the recommended fix was : killev; oaf-slay; evolution can you try that? for reference: http://bugzilla.ximian.com/show_bug.cgi?id=33568
All that does is kill the running evolution processes, and then kill the running oafd process before restarting evolution. Despite the lack of communication in this ximian bugzilla ticket...I tried it...it doesn't fix the issue. If it did, so would a reboot, as the oafd process would be reinstantiated at that time, prior to running evolution. They've got the issue resolved on their site, and I'm hesitant to attempt to reopen it just yet. Based on the fact that this doesn't appear to be just me, I suspect that there is a ximian tweak to a gnome library involved somewhere that hasn't propogated to the Gentoo builds (yet). Ximian used to be pretty notorious about forcing their own library versions onto people to "guarantee" the apps would run correctly. Also, they used to fix identified bugs in "updates" via RedCarpet, and then act as if the fix was there all along. I'm just suprised that no one else using Gentoo has identified an issue (or reported it). Begging the question again, "is it just me"?
installed evo on a ~ppc box, all fine. I'm about to update the "missing packages"
i can't reproduce it either. i'm pretty sure 1.2.3 has all the dependencies that the same ximian rpms specify. the most important of which is gal-0.23. you can try one thing, which is moving your ~/evolution directory aside and starting evolution fresh, see if it crashes when you select the calendar (because the error does suggest problems opening your calendar.ics) and changing view.
I moved my existing ~/evolution directory aside, and allowed Evolution to recreate a new one. Replicated the problem with a clean calendar. Could I be dealing with a "dirty" library that has been left behind during an upgrade somewhere along the way? If so, what might the likely culprits be?
Since I had already rebuilt gal, I decided a shotgun approach of rebuilding everything listed in the evolution-1.2.3.ebuild dependency list couldn't hurt. I don't know what it was, but something in: emerge scrollkeeper bonobo-conf bonobo gnome-common gal gconf gtkhtml oaf ORBit libglade gdk-pixbuf libxml gnome-vfs gnome-print gob soup followed by: emerge evolution resolved the issue. All the versions were kept the same in the rebuild process, so something must have had a bit flipped that was causing the problem *just* on my machine. Thank to everyone that tried to replicate my problem. Helped a lot to figure out the best course of action. Cheers.
well .. what can i say? :) kind of unfortunate that we can't get to the root of the problem. it is possible that one of the libraries was compiled against a buggy older version and statically linked. but i'm happy that you've got it working now. i wish all bug reporters were as cooperative and patient as you :) thanks! i guess i can close this one now.
