GNOME Bugzilla – Bug 522277
crash in Evolution: sending, receiving, dele...
Last modified: 2009-07-24 21:48:12 UTC
What were you doing when the application crashed? sending, receiving, deleting email Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.20.3 2008-01-17 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.23-gentoo-r9 #1 SMP PREEMPT Tue Mar 4 12:02:45 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: marble-look Icon Theme: gnome Memory status: size: 89645056 vsize: 89645056 resident: 32493568 share: 10186752 rss: 32493568 rss_rlim: 4294967295 CPU usage: start_time: 1205429640 rtime: 407 utime: 365 stime: 42 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb61f26d0 (LWP 25154)] [New Thread 0xb6023b90 (LWP 25155)] 0xb7f83410 in __kernel_vsyscall ()
+ Trace 192324
Thread 1 (Thread 0xb61f26d0 (LWP 25154))
----------- .xsession-errors (98 sec old) --------------------- ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ** (nautilus-sendto:25145): CRITICAL **: view_completed_cb: assertion `status == E_BOOK_ERROR_OK' failed ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 533859 has been marked as a duplicate of this bug. ***
*** Bug 544436 has been marked as a duplicate of this bug. ***
https://bugs.launchpad.net/evolution-exchange/+bug/204702 is similar on GNOME 2.21
*** Bug 545730 has been marked as a duplicate of this bug. ***
*** Bug 548799 has been marked as a duplicate of this bug. ***
*** Bug 528194 has been marked as a duplicate of this bug. ***
Confirming as per the number of duplicates
*** Bug 550833 has been marked as a duplicate of this bug. ***
*** Bug 559141 has been marked as a duplicate of this bug. ***
*** Bug 554880 has been marked as a duplicate of this bug. ***
Created attachment 124193 [details] [review] proposed eex patch for evolution-exchange; I had a chat with Varadhan and he said to add some locking around mfld structure. I added on some places there. Can anybody of you, with compiling environment, try this please? I cannot reproduce it myself, thus this is sort of guess. Thanks in advance.
i've applied the patch to current svn head.
(In reply to comment #12) > i've applied the patch to current svn head. > to make that a little more clear -- i've applied the patch to my local build of svn head
*** Bug 566927 has been marked as a duplicate of this bug. ***
*** Bug 567046 has been marked as a duplicate of this bug. ***
*** Bug 571354 has been marked as a duplicate of this bug. ***
*** Bug 573124 has been marked as a duplicate of this bug. ***
*** Bug 574608 has been marked as a duplicate of this bug. ***
*** Bug 581287 has been marked as a duplicate of this bug. ***
*** Bug 581545 has been marked as a duplicate of this bug. ***
Reid, any update on the patch ? TIA
*** Bug 495055 has been marked as a duplicate of this bug. ***
Reid, ping. After your reply (positive / negative) only, we can decide on patch :-)
(In reply to comment #23) > Reid, ping. After your reply (positive / negative) only, we can decide on patch > :-) > Positive. I noticed no adverse effects from the patch. And to my knowledge, I did not experience this crash again. I 'lost' the patch when moving from svn to git in the past couple of weeks. I just re-applied the patch to my git tree and will rebuild and continue to run with it.
*** Bug 584195 has been marked as a duplicate of this bug. ***
*** Bug 587258 has been marked as a duplicate of this bug. ***
*** Bug 522956 has been marked as a duplicate of this bug. ***
Please see comment http://bugzilla.gnome.org/show_bug.cgi?id=498099#c16 @ abharah, milan If committed patch in bug 581908 makes this bug obsolete, please do the needful.
*** Bug 498099 has been marked as a duplicate of this bug. ***
Created commit c367362 in eex master (2.27.5+) Slightly modified, as part for the unverified index is obsolete in actual sources. Otherwise I rather committed this, as it still applies to the code. Thanks for remind me, I forgot of this absolutely.
(In reply to comment #11) > Created an attachment (id=124193) [edit] > proposed eex patch > > for evolution-exchange; > > I had a chat with Varadhan and he said to add some locking around mfld > structure. I added on some places there. Can anybody of you, with compiling > environment, try this please? I cannot reproduce it myself, thus this is sort > of guess. Thanks in advance. I tried the patch on evolution-exchange 2.26.2 and all it does is make the error not appear anymore in the Evolution statusbar, but when I try to click on an unread e-mail I still get: Unable to retrieve message Lost connection to Evolution Exchange backend process
(In reply to comment #31) > (In reply to comment #11) > > Created an attachment (id=124193) [edit] > > proposed eex patch > > > > for evolution-exchange; > > > > I had a chat with Varadhan and he said to add some locking around mfld > > structure. I added on some places there. Can anybody of you, with compiling > > environment, try this please? I cannot reproduce it myself, thus this is sort > > of guess. Thanks in advance. > > I tried the patch on evolution-exchange 2.26.2 and all it does is make the > error not appear anymore in the Evolution statusbar, but when I try to click on > an unread e-mail I still get: > Unable to retrieve message > Lost connection to Evolution Exchange backend process After restarting Evolution a few times this fix seems to have taken affect. :) The first few times I saw the behaviour in my prior post, but it fixed itself it seems.
(In reply to comment #32) > After restarting Evolution a few times this fix seems to have taken affect. :) > The first few times I saw the behaviour in my prior post, but it fixed itself > it seems. Hmm, let's see. One can always reopen the bug for further investigation. I guess evolution --force-shutdown was good to do to work with latest binaries. Maybe you did it, I do not know.
(In reply to comment #33) > (In reply to comment #32) > > After restarting Evolution a few times this fix seems to have taken affect. :) > > The first few times I saw the behaviour in my prior post, but it fixed itself > > it seems. > > Hmm, let's see. One can always reopen the bug for further investigation. I > guess evolution --force-shutdown was good to do to work with latest binaries. > Maybe you did it, I do not know. I did the `evolution --force-shutdown` each restart when trying this. Took two shutdowns for the fix to seem to take effect. If I leave the box to catch up on a week's worth of e-mail it still seems to lose the exchange backend connection, but it's much rarer now and not as annoying.
Sounds like something with your folder summary, maybe it took it some time until it got synced properly. Maybe. when you have backtrace for any other crashes, please file a new bug report, and maybe CC me there. Thanks in advance.
I had the same experience as Eric. After I applied the patch, evolution worked much better, but eventually the same problem happened. When this happened, I did force shutdown, cleaned out the exchange data store from my .evolution directory and re-downloaded my mail. Since then, I haven't had the "lost connection to backend" happen again. The bug may not be 100% fixed, but before this fix, evolution was unuable with my OWA account, it is now.
(In reply to comment #36) > I had the same experience as Eric. After I applied the patch, evolution worked > much better, but eventually the same problem happened. > > When this happened, I did force shutdown, cleaned out the exchange data store > from my .evolution directory and re-downloaded my mail. Since then, I haven't > had the "lost connection to backend" happen again. I didn't try cleaning out the .evolution directory, I'll try that next and see if it removes my recurring problem.
(In reply to comment #37) > (In reply to comment #36) > > When this happened, I did force shutdown, cleaned out the exchange data store > > from my .evolution directory and re-downloaded my mail. Since then, I haven't > > had the "lost connection to backend" happen again. > > I didn't try cleaning out the .evolution directory, I'll try that next and see > if it removes my recurring problem. Please just note not clearing all the ~/.evolution, but only exchange related folders there, like ~/.evolution/exchange ; ~/evolution/mail/exchange
(In reply to comment #38) > (In reply to comment #37) > > (In reply to comment #36) > > > When this happened, I did force shutdown, cleaned out the exchange data store > > > from my .evolution directory and re-downloaded my mail. Since then, I haven't > > > had the "lost connection to backend" happen again. > > > > I didn't try cleaning out the .evolution directory, I'll try that next and see > > if it removes my recurring problem. > > Please just note not clearing all the ~/.evolution, but only exchange related > folders there, like ~/.evolution/exchange ; ~/evolution/mail/exchange Yeah, jus the exchange folders. :) After clearing out the exchange folders under ~/.evolution and having the above patch applied I cannot seem to reproduce this bug, thanks!