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 349413 - Evolution (FC5/x86_64) Faling to fetch new mails.
Evolution (FC5/x86_64) Faling to fetch new mails.
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other other
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 348219 350346 350924 351995 352321 353419 357096 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-31 10:55 UTC by b.king
Modified: 2006-09-25 14:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
patch (1.54 KB, patch)
2006-07-31 15:12 UTC, Sushma Rai
none Details | Review
Patch committed to head by Varadhan. (710 bytes, patch)
2006-08-10 08:43 UTC, Sushma Rai
committed Details | Review

Description b.king 2006-07-31 10:55:24 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution Exchange
Severity: major
Version: GNOME2.14.2 2.6.0
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution (FC5/x86_64) quits after loading new messages from Exchange
Bugzilla-Product: Evolution Exchange
Bugzilla-Component: Connector
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Evolution / Evolution-connector quits just after loading new messages,
at the start of filtering new messages.
Version is 2.6.2 from FC5, fully up to date.

Steps to reproduce the crash:
1.  Start evolution with exchange mailbox

Expected Results:
Be able to read messages.

How often does this happen?
All the time.

Additional Information:
camel-exchange-provider-ERROR **: file camel-exchange-store.c: line 1098
(stub_notification): should not be reached
aborting...



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496425552 (LWP 5604)]
[New Thread 1168148800 (LWP 5625)]
[New Thread 1157658944 (LWP 5622)]
[New Thread 1147169088 (LWP 5621)]
[New Thread 1136679232 (LWP 5619)]
[New Thread 1126189376 (LWP 5618)]
[New Thread 1115699520 (LWP 5617)]
[New Thread 1105209664 (LWP 5616)]
[New Thread 1094719808 (LWP 5615)]
[New Thread 1084229952 (LWP 5607)]
(no debugging symbols found)
0x0000003b9aec3806 in poll () from /lib64/libc.so.6

Thread 8 (Thread 1105209664 (LWP 5616))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 stub_notification
    at camel-exchange-store.c line 1098
  • #9 camel_object_trigger_event
    from /usr/lib64/libcamel-1.2.so.0
  • #10 status_main
    at camel-stub.c line 134
  • #11 start_thread
    from /lib64/libpthread.so.0
  • #12 clone
    from /lib64/libc.so.6
  • #13 ??




------- Bug created by bug-buddy at 2006-07-31 10:55 -------

Comment 1 Bevis King 2006-07-31 12:41:35 UTC
Instead of the assert at line 1098 of camel-exchange-store.c, I added the following code:

        default:
                fprintf( stderr, "camel-exchange-store.c: event code was %d\n",
                                retval );
                break;

The following was the output of this routine as the code failed:

camel-exchange-store.c: event code was 558007555
camel-exchange-store.c: event code was 1

With this modification it proved possible to read just one message after the summary information had been downloaded but before the filtering had timed out and brought evolution-connector to a halt.

After this the following messages appear:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

(evolution-2.6:5811): e-data-server-WARNING **: Error in execution: Failed to retrieve message

The attempt to grab the second message ultimately resulted in:
Unable to retrieve message
Lost connection to Evolution Exchange backend process

With this modification in place, the other IMAP/S mailbox could continue to be used without evolution quiting.

Regards, Bevis.
Comment 2 Sushma Rai 2006-07-31 15:12:44 UTC
Created attachment 69977 [details] [review]
patch

Can you please test this patch?
Comment 3 Sushma Rai 2006-07-31 15:14:08 UTC
Please upgrade to 2.6.2 (couple of patches have gone in after that)
and then try this patch?

Comment 4 Bevis King 2006-07-31 15:22:37 UTC
The 2.6.0 report from bug buddy is erroroneous (as far as I know) - here are the RPM versions installed on the machine - the SEPS is my hacked one based upon the evolution-connector-2.6.2-1.fc5.4 SRPM.

% rpm -qa | grep evo
evolution-2.6.2-1.fc5.5
evolution-connector-2.6.2-1.SEPS.5
evolution-sharp-0.10.2-9.5
evolution-connector-debuginfo-2.6.2-1.fc5.4
evolution-webcal-2.4.1-3.4
evolution-debuginfo-2.6.0-1
evolution-data-server-1.6.2-1.fc5.1
evolution-sharp-debuginfo-0.10.2-9
evolution-data-server-devel-1.6.2-1.fc5.1
evolution-data-server-debuginfo-1.5.92-1
evolution-webcal-debuginfo-2.4.1-3.2
evolution-devel-2.6.2-1.fc5.5

I'll try the patch.

Regards, Bevis.
Comment 5 Bevis King 2006-07-31 15:37:24 UTC
OK, one out of three of the patches failed to apply - this from the .rej file:

+               if ((n = camel_read (marshal->fd, buf + nread, len - nread)) <=
0)
+                       break;
+               nread += n;
+       } while (nread < len);

If I'm reading the code correctly, this is how do_read() at line 90 appears on the version of the sources I'm looking at - ie it's nothing like the code being patched.

static gboolean
do_read (CamelStubMarshal *marshal, char *buf, size_t len)
{
        if (camel_read (marshal->fd, buf, len) == -1) {
                close (marshal->fd);
                marshal->fd = -1;
                return FALSE;
        }

        return TRUE;
}

Since the other two parts of the patch went in, I'll try it with just those two.

Regards, Bevis.
Comment 6 Bevis King 2006-07-31 15:47:55 UTC
Not looking too good - It openned the exchange mail box [Inbox(9)] and then hung up at Fetching Summary Information for new messages (85% complete).  "Scanning for changed messages (0% complete)" is also showing on the status bar.

It hung at this point for more than two minutes.

Then it reported:

Error while Opening folder exchange://ees1bk;auth=NTLM@exchange.surrey.ac.uk/personal/Inbox.

Lost connection to Evolution Exchange backend process

No new diagnostics on the terminal window I fired it up on.

OK, any suggestions?  Maybe send me a replacement of the whole source file unless it is the 2.6.0 that is confusing things?

Cheers.

Regards, Bevis.
Comment 7 Sushma Rai 2006-08-01 04:54:26 UTC
Not sure why patch is not applying.
Testing needs to be done after applying the full patch.

your problem is duplicate of 
http://bugzilla.gnome.org/show_bug.cgi?id=344776
(see comment #8)

But I am keeping it open, please try 2.6.3 and 
update the bug.
Comment 8 Bevis King 2006-08-01 16:18:08 UTC
OK, I couldn't find an SRPM for 2.6.3 around, but I did find 2.7.3 - is that what you meant?  Anyway, I compiled up 2.7.3 and it's still very lumpy and crashes quite often when talking to exchange; fine when just running IMAP/S.  I will try and get a crash dump out of 2.7.3 and send it to you tomorrow.

Regards, Bevis.
Comment 9 Sushma Rai 2006-08-02 07:11:54 UTC
No I meant 2.6.3 and it'll be released today.
Comment 10 Bevis King 2006-08-08 14:57:18 UTC
OK, I've grabbed, compiled and installed 2.6.3.  Certainly the problem with it quiting is gone, but it's still not functional.  As new messages arrive, the number in brackets after the Inbox grows ie Inbox (20) but the message index does not update, even after a Send/Recieve.  Neither can next unread CTRL-] display any of the new messages.  Even going into another mailbox and returning to the Inbox doesn't bring up the new messages.

Do you want me to log a new bug about this problem?  Any suggestions on where to look and add debug statements?  No errors are reported to the controlling terminal about this.

Regards, Bevis.
Comment 11 Jeffrey C. Ollie 2006-08-09 15:14:53 UTC
(In reply to comment #10)
> OK, I've grabbed, compiled and installed 2.6.3.  Certainly the problem with it
> quiting is gone, but it's still not functional.  As new messages arrive, the
> number in brackets after the Inbox grows ie Inbox (20) but the message index
> does not update, even after a Send/Recieve.  Neither can next unread CTRL-]
> display any of the new messages.  Even going into another mailbox and returning
> to the Inbox doesn't bring up the new messages.

I see the same problem on FC-5 with the 2.6.3-1.fc5.1 RPMs from FC5 updates-testing.
Comment 12 Sushma Rai 2006-08-10 06:08:19 UTC
Bevis King,

We can change the summary of this bug itself for the new mails issue.
Comment 13 Sushma Rai 2006-08-10 08:43:24 UTC
Created attachment 70622 [details] [review]
Patch committed to head by Varadhan.

Can some one who is observing "fetching new mails issue/hang" test this patch?
Comment 14 Bevis King 2006-08-10 08:44:23 UTC
Please note this bug is also in the RedHat Bugzilla:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=196102
Comment 15 Wiliam Murray 2006-08-10 09:22:23 UTC
  Yes, evo 2.6.3 (as packaged by Fedora ) works nicely for me,
that hang at reading new mail is gone.  
   Bill
Comment 16 Bevis King 2006-08-10 09:39:20 UTC
This patch appears to work perfectly.  New emails are now showing up just fine and a are readable.

Thank you!

Regards, Bevis.
Comment 17 Sushma Rai 2006-08-10 13:14:39 UTC
Cool. I'll be committing this patch to stable branch, so that 2.6.4 will
have it and then closing this bug report.
Comment 18 Sushma Rai 2006-08-10 13:23:12 UTC
2.7.92 and 2.6.4 will have this patch.
Comment 19 Matthew Barnes 2006-08-10 19:37:49 UTC
Actually, it looks like this patch made it into 2.7.91 already.
Comment 20 Michael Steigman 2006-08-11 17:49:16 UTC
I'd like to try the patch until something is released for FC5 but I need evolution-devel in order to recompile the source RPM for the connector. I can't seem to find a 2.6.3 version compatible with the stuff from testing. Can someone tell me where I can grab it?
Comment 21 Matthew Barnes 2006-08-11 18:01:35 UTC
Not sure what you mean by "compatible with the stuff from testing".

Both Evolution 2.6.3 and Evolution-Connector 2.6.3 are in Fedora Test Updates and should be pushed to Fedora Updates very soon.  The source RPMs for both packages are available here:

http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/SRPMS/
Comment 22 Michael Steigman 2006-08-11 18:32:18 UTC
I'm using the 2.6.3 RPMS in updates testing. They (evolution-connector) do not work so their release into updates won't help much. I wanted to try applying the patch in this thread to the connector src but in order to do that, I need evolution-devel:

[root@tain SPECS]# rpmbuild -bb evolution-connector.spec
error: Failed build dependencies:
        evolution-data-server-devel is needed by evolution-connector-2.6.3-1.fc5.1.x86_64
        evolution-devel >= 2.6.3 is needed by evolution-connector-2.6.3-1.fc5.1.x86_64

Comment 23 André Klapper 2006-08-12 14:01:33 UTC
*** Bug 350924 has been marked as a duplicate of this bug. ***
Comment 24 Michael Steigman 2006-08-12 15:52:44 UTC
OK, this was my bad - the mirror I grabbed the 2.6.3 packages from apparently had not synched the -devel package yet. Google wasn't turning up anything yet either.   In any case, I have now rebuilt 2.6.3 with the patch in comment 13 and it appears to have fixed the problem. Sorry for the confusion and thanks!
Comment 25 Sushma Rai 2006-08-17 06:33:01 UTC
*** Bug 350346 has been marked as a duplicate of this bug. ***
Comment 26 Sushma Rai 2006-08-18 11:22:17 UTC
*** Bug 348219 has been marked as a duplicate of this bug. ***
Comment 27 Michael Steigman 2006-08-18 16:09:45 UTC
Not sure if this is related (also commenting on bug 337023, as that looks like the only similar bug) but I am noticing that items added to the calendar from another program or device only show up after restarting Evolution. This is similar to the problem we were all experiencing with email. Let me know if I can provide any further information. Again, this is evolution-connector-2.6.3-1.fc5.1, rebuilt with the patch above.
Comment 28 Sushma Rai 2006-08-21 06:13:22 UTC
*** Bug 351995 has been marked as a duplicate of this bug. ***
Comment 29 lsof 2006-08-21 12:43:06 UTC
I'm using the latest 2.6.3 from FC5, and the _crash_ is fixed for me.

When I get a new e-mail, the new e-mail count in the folder list increases, i.e.
Inbox (3)
But when I go to my Inbox, I cannot see the e-mail. I must restart evo to see it.

I thought this was caused by our firewall being over-zealous with closing idle connections, but this does not explain why the folder list continues to show new e-mail, but the message list cannot.

I am using the 32-bit version.
Comment 30 Lee Dixon 2006-08-21 14:31:05 UTC
I get the same problem.  No more hangups attempting to do a total download of the public folders, but new mail merely increments the number but the email is not visible until I restart evo.  Running the latest FC5 updates (2.6.3-1.fc5.1)  Will gladly test anything that shows up in updates-testing
Comment 31 Sushma Rai 2006-08-22 04:59:19 UTC
*** Bug 352321 has been marked as a duplicate of this bug. ***
Comment 32 Sushma Rai 2006-08-22 06:01:01 UTC
For the comment #29 and #30, Your problem will be solved with the 
patch attached in the comment #13 and this will be availabe in 
2.6.4 and 2.7.92 and above.
Comment 33 Sushma Rai 2006-08-31 08:24:54 UTC
*** Bug 353419 has been marked as a duplicate of this bug. ***
Comment 34 Luis F. Ortiz 2006-09-25 14:09:20 UTC
*** Bug 357096 has been marked as a duplicate of this bug. ***