GNOME Bugzilla – Bug 580414
Crash in camel_internet_address_add at camel-internet-address.c line 306
Last modified: 2010-09-13 10:38:05 UTC
What were you doing when the application crashed? Evolution mapi issue getting folders from the 2003 exchange server Distribution: Fedora release 10.92 (Rawhide) Gnome Release: 2.26.1 2009-04-13 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.29.1-102.fc11.x86_64 #1 SMP Mon Apr 20 15:33:38 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10601000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 1868562432 vsize: 1868562432 resident: 161333248 share: 29229056 rss: 161333248 rss_rlim: 18446744073709551615 CPU usage: start_time: 1240820801 rtime: 20307 utime: 19424 stime: 883 cutime:0 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fc62d390910 (LWP 11743)] [New Thread 0x7fc622bfd910 (LWP 11741)] [New Thread 0x7fc6235fe910 (LWP 11740)] [New Thread 0x7fc62ebfd910 (LWP 11738)] [New Thread 0x7fc62ffff910 (LWP 11664)] [New Thread 0x7fc62f5fe910 (LWP 11605)] [New Thread 0x7fc63da62910 (LWP 11603)] [New Thread 0x7fc63d061910 (LWP 11477)] [New Thread 0x7fc63f5fe910 (LWP 11476)] [New Thread 0x7fc66aa09910 (LWP 4620)] [New Thread 0x7fc63ffff910 (LWP 4619)] [New Thread 0x7fc65abfd910 (LWP 2849)] [New Thread 0x7fc65b5fe910 (LWP 2846)] [New Thread 0x7fc65bfff910 (LWP 2845)] [New Thread 0x7fc668fbf910 (LWP 2842)] [New Thread 0x7fc66a372910 (LWP 2839)] [New Thread 0x7fc66bde2910 (LWP 2836)] [New Thread 0x7fc671c9d910 (LWP 2835)] 0x0000003aad80ea5d in __libc_waitpid (pid=11757, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); Current language: auto; currently minimal
+ Trace 214843
Thread 2 (Thread 0x7fc62d390910 (LWP 11743))
---- Critical and fatal warnings logged during execution ---- ** camel **: camel_provider_get: assertion `url_string != NULL' failed ** camel **: camel_provider_get: assertion `url_string != NULL' failed ** camel **: camel_provider_get: assertion `url_string != NULL' failed ** camel **: camel_provider_get: assertion `url_string != NULL' failed ** camel **: camel_data_wrapper_set_mime_type: assertion `mime_type != NULL' failed ** camel **: camel_data_wrapper_set_mime_type: assertion `mime_type != NULL' failed ** camel **: camel_data_wrapper_set_mime_type: assertion `mime_type != NULL' failed ** camel **: camel_data_wrapper_set_mime_type: assertion `mime_type != NULL' failed ** GLib **: g_utf8_collate: assertion `str1 != NULL' failed ----------- .xsession-errors --------------------- Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/5c/a7f89ad3e78369dffe894f8708470e9a3970b3.debug warning: "/usr/lib/debug/usr/lib64/gconv/libJIS.so.debug": The separate debug info file has no debug info warning: "/usr/lib/debug/usr/lib64/gconv/libGB.so.debug": The separate debug info file has no debug info warning: "/usr/lib/debug/usr/lib64/gconv/libKSC.so.debug": The separate debug info file has no debug info Missing separate debuginfo for /usr/lib64/libglade/2.0/libgnome.so Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/1b/0b462ef104087d14a7b3866a9f01b17b53f4ea.debug Missing separate debuginfo for /usr/lib64/libglade/2.0/libbonobo.so Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/38/1fa7a769b3e402f723b7d37e00861ab63caf31.debug Missing separate debuginfo for /usr/lib64/libtrackerclient.so.0 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/75/e99b833ede5dbd36a6fda7983a9f972cd4adc0.debug Missing separate debuginfo for /usr/lib64/evolution-data-server-1.2/camel-providers/libcamelmapi.so Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/0a/4e540c8dac4cda70c99bc19172e86653d75fdd.debug --------------------------------------------------
Evolution 2.26 on Fedora 11 evolution-2.26.1-2.fc11.x86_64 evolution-data-server-2.26.1-1.fc11.x86_64 evolution-data-server-debuginfo-2.26.1-1.fc11.x86_64 evolution-data-server-devel-2.26.1-1.fc11.x86_64 evolution-data-server-doc-2.26.1-1.fc11.noarch evolution-debuginfo-2.26.1-2.fc11.x86_64 evolution-devel-2.26.1-2.fc11.x86_64 evolution-exchange-2.26.1-1.fc11.x86_64 evolution-mapi-0.26.1-1.fc11.x86_64
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 565237 ***
How is this a dupe? I can't see any similarity to the crash dump and I'm not using IMAP.
I also don't see anything similar here. Fabio, can you please explain?
look this: http://bugzilla.gnome.org/show_bug.cgi?id=578332 i am sure this is dup of this bug, and #578332 was market as dup of #565237
Thread 10 in bug 578332 has a imap_sync when the signal handler is called - this bug does not have.
ooooops i dont see this thread.... only see the start thread and the thread 1, so they declare dup well, is true imap_sync is call.... sorry again... :-)
I'm pretty sure this bug is triggered from mapi. I have the old evo connector enabled and used day to day and it runs fine. I configured and enabled evolution-mapi and it seems this happens right at the end of the retrieving the folder list. I had two crashes at the same point as did a colleague of mine, the only difference between his and my setup is that I run Fedora 11, he runs the new release of Ubuntu.
*** Bug 582652 has been marked as a duplicate of this bug. ***
This version is no longer maintained, which means that it will not receive any further security or bug fix updates. The current stable GNOME and Evolution version is 2.30. Can you please check again whether this issue still happens in Evolution 2.30 and update this report by adding a comment and changing the "Version" field? Thanks a lot. Again thank you for reporting this bug and we are sorry it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE in 6 weeks.