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 522277 - crash in Evolution: sending, receiving, dele...
crash in Evolution: sending, receiving, dele...
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.22.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 495055 498099 522956 528194 533859 544436 545730 548799 550833 554880 559141 566927 567046 571354 573124 574608 581287 581545 584195 587258 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-03-13 17:36 UTC by Reid Thompson
Modified: 2009-07-24 21:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
proposed eex patch (4.12 KB, patch)
2008-12-08 17:48 UTC, Milan Crha
committed Details | Review

Description Reid Thompson 2008-03-13 17:36:06 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 ()

Thread 1 (Thread 0xb61f26d0 (LWP 25154))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at ../../../glib/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at ../../../glib/glib/gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 IA__g_str_hash
    at ../../../glib/glib/gstring.c line 95
  • #10 g_hash_table_lookup_node
    at ../../../glib/glib/ghash.c line 118
  • #11 IA__g_hash_table_lookup
    at ../../../glib/glib/ghash.c line 659
  • #12 message_removed
    at ../../../evolution-exchange/mail/mail-stub-exchange.c line 400
  • #13 sync_deletions
    at ../../../evolution-exchange/mail/mail-stub-exchange.c line 1203
  • #14 folder_from_name
    at ../../../evolution-exchange/mail/mail-stub-exchange.c line 276
  • #15 expunge_uids
    at ../../../evolution-exchange/mail/mail-stub-exchange.c line 1547
  • #16 connection_handler
    at ../../../evolution-exchange/mail/mail-stub.c line 187
  • #17 g_io_unix_dispatch
    at ../../../glib/glib/giounix.c line 162
  • #18 g_main_dispatch
    at ../../../glib/glib/gmain.c line 2003
  • #19 IA__g_main_context_dispatch
    at ../../../glib/glib/gmain.c line 2555
  • #20 g_main_context_iterate
    at ../../../glib/glib/gmain.c line 2636
  • #21 IA__g_main_loop_run
    at ../../../glib/glib/gmain.c line 2844
  • #22 bonobo_main
    at bonobo-main.c line 311
  • #23 main
    at ../../../evolution-exchange/storage/main.c line 238
  • #0 __kernel_vsyscall


----------- .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...
--------------------------------------------------
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2008-05-20 09:29:52 UTC
*** Bug 533859 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2008-07-24 04:22:54 UTC
*** Bug 544436 has been marked as a duplicate of this bug. ***
Comment 3 Sebastien Bacher 2008-07-26 15:05:08 UTC
https://bugs.launchpad.net/evolution-exchange/+bug/204702 is similar on GNOME 2.21
Comment 4 Akhil Laddha 2008-08-01 03:22:04 UTC
*** Bug 545730 has been marked as a duplicate of this bug. ***
Comment 5 Kandepu Prasad 2008-08-21 10:22:43 UTC
*** Bug 548799 has been marked as a duplicate of this bug. ***
Comment 6 Kandepu Prasad 2008-08-21 10:25:16 UTC
*** Bug 528194 has been marked as a duplicate of this bug. ***
Comment 7 Kandepu Prasad 2008-08-21 10:26:40 UTC
Confirming as per the  number of duplicates
Comment 8 Akhil Laddha 2008-09-05 04:17:45 UTC
*** Bug 550833 has been marked as a duplicate of this bug. ***
Comment 9 Akhil Laddha 2008-11-04 05:24:19 UTC
*** Bug 559141 has been marked as a duplicate of this bug. ***
Comment 10 Milan Crha 2008-12-08 15:32:24 UTC
*** Bug 554880 has been marked as a duplicate of this bug. ***
Comment 11 Milan Crha 2008-12-08 17:48:03 UTC
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.
Comment 12 Reid Thompson 2008-12-08 21:34:45 UTC
i've applied the patch to current svn head.
Comment 13 Reid Thompson 2008-12-08 21:43:04 UTC
(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
Comment 14 palfrey 2009-01-07 17:45:57 UTC
*** Bug 566927 has been marked as a duplicate of this bug. ***
Comment 15 palfrey 2009-01-08 17:29:58 UTC
*** Bug 567046 has been marked as a duplicate of this bug. ***
Comment 16 Akhil Laddha 2009-02-12 03:36:37 UTC
*** Bug 571354 has been marked as a duplicate of this bug. ***
Comment 17 palfrey 2009-02-25 16:27:17 UTC
*** Bug 573124 has been marked as a duplicate of this bug. ***
Comment 18 palfrey 2009-03-09 15:28:53 UTC
*** Bug 574608 has been marked as a duplicate of this bug. ***
Comment 19 Fabio Durán Verdugo 2009-05-04 12:17:33 UTC
*** Bug 581287 has been marked as a duplicate of this bug. ***
Comment 20 Akhil Laddha 2009-05-06 03:18:58 UTC
*** Bug 581545 has been marked as a duplicate of this bug. ***
Comment 21 Akhil Laddha 2009-05-06 03:19:58 UTC
Reid, any update on the patch ? TIA
Comment 22 Akhil Laddha 2009-05-22 06:47:15 UTC
*** Bug 495055 has been marked as a duplicate of this bug. ***
Comment 23 Akhil Laddha 2009-05-22 06:52:24 UTC
Reid, ping. After your reply (positive / negative) only, we can decide on patch :-)
Comment 24 Reid Thompson 2009-05-22 12:21:07 UTC
(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.
Comment 25 Fabio Durán Verdugo 2009-05-29 13:43:06 UTC
*** Bug 584195 has been marked as a duplicate of this bug. ***
Comment 26 Akhil Laddha 2009-06-29 04:04:46 UTC
*** Bug 587258 has been marked as a duplicate of this bug. ***
Comment 27 Akhil Laddha 2009-06-29 04:05:10 UTC
*** Bug 522956 has been marked as a duplicate of this bug. ***
Comment 28 Akhil Laddha 2009-07-20 04:38:03 UTC
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. 
Comment 29 Milan Crha 2009-07-20 08:20:04 UTC
*** Bug 498099 has been marked as a duplicate of this bug. ***
Comment 30 Milan Crha 2009-07-20 08:47:10 UTC
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.
Comment 31 Eric Sandall 2009-07-20 23:55:09 UTC
(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
Comment 32 Eric Sandall 2009-07-21 00:58:50 UTC
(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.
Comment 33 Milan Crha 2009-07-21 08:05:09 UTC
(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.
Comment 34 Eric Sandall 2009-07-21 18:58:54 UTC
(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.
Comment 35 Milan Crha 2009-07-22 09:25:19 UTC
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.
Comment 36 chrispope 2009-07-23 00:49:44 UTC
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.
Comment 37 Eric Sandall 2009-07-23 01:09:05 UTC
(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.
Comment 38 Milan Crha 2009-07-23 07:40:48 UTC
(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
Comment 39 Eric Sandall 2009-07-24 21:48:12 UTC
(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!