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 588556 - Crash in camel_folder_summary_load_from_db at camel-folder-summary.c line 1079
Crash in camel_folder_summary_load_from_db at camel-folder-summary.c line 1079
Status: RESOLVED INCOMPLETE
Product: evolution-mapi
Classification: Applications
Component: Mail
0.28.x
Other All
: High critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2009-07-14 16:19 UTC by matip
Modified: 2010-10-01 04:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description matip 2009-07-14 16:19:16 UTC
What were you doing when the application crashed?
just configured connection to exchange 2007


Distribution: openSUSE 11.1 (i586)
Gnome Release: 2.24.1 2009-06-02 (SUSE)
BugBuddy Version: 2.24.1

System: Linux 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 246259712 vsize: 246259712 resident: 28663808 share: 19255296 rss: 28663808 rss_rlim: 18446744073709551615
CPU usage: start_time: 1247588323 rtime: 45 utime: 40 stime: 5 cutime:4 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xa9efbb90 (LWP 5749)]
[New Thread 0xaaefdb90 (LWP 5747)]
[New Thread 0xab6feb90 (LWP 5744)]
[New Thread 0xabeffb90 (LWP 5743)]
[New Thread 0xac8ffb90 (LWP 5742)]
[New Thread 0xad2a5b90 (LWP 5741)]
[New Thread 0xadaa6b90 (LWP 5740)]
[New Thread 0xae2a7b90 (LWP 5738)]
[New Thread 0xaf82fb90 (LWP 5737)]
[New Thread 0xb0030b90 (LWP 5736)]
[New Thread 0xb0831b90 (LWP 5735)]
[New Thread 0xb1032b90 (LWP 5734)]
[New Thread 0xb1833b90 (LWP 5732)]
[New Thread 0xb32feb90 (LWP 5730)]
[New Thread 0xb3affb90 (LWP 5729)]
[New Thread 0xb447db90 (LWP 5727)]
[New Thread 0xb547fb90 (LWP 5724)]
(no debugging symbols found)
0xffffe430 in __kernel_vsyscall ()

Thread 2 (Thread 0xa9efbb90 (LWP 5749))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_89
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 camel_folder_summary_load_from_db
    from /usr/lib/libcamel-provider-1.2.so.14
  • #6 camel_mapi_summary_new
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelmapi.so
  • #7 camel_mapi_folder_new
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelmapi.so
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelmapi.so
  • #9 camel_store_get_folder
    from /usr/lib/libcamel-provider-1.2.so.14
  • #10 mail_tool_uri_to_folder
    from /usr/lib/evolution/2.26/components/libevolution-mail.so
  • #11 get_folder_exec
    from /usr/lib/evolution/2.26/components/libevolution-mail.so
  • #12 mail_msg_proxy
    from /usr/lib/evolution/2.26/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (39 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Initialisi)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Loading th)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Initialisi)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Configured)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Starting t)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 (Software M)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-system-monitor:5645): WARNING **: SELinux was found but is not enabled.
--------------------------------------------------
Comment 1 Akhil Laddha 2009-07-15 04:16:46 UTC
Are you using mapi provider or owa connector ? 

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml2, gtk2, glib2, libsoup, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 Akhil Laddha 2009-08-27 07:44:59 UTC
Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Martin Mai 2009-11-29 10:23:50 UTC
There is a similar trace with all symbols at https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/414634:

Stacktrace: http://launchpadlibrarian.net/30407334/Stacktrace.txt
ThreadStacktrace: http://launchpadlibrarian.net/30407335/ThreadStacktrace.txt

The reporter at launchpad is using the mapi backend.
Comment 4 Akhil Laddha 2009-11-30 06:12:21 UTC
Pasting traces from downstream bug 

  • #0 camel_folder_summary_load_from_db
    at camel-folder-summary.c line 1079
  • #1 camel_mapi_summary_new
    at camel-mapi-summary.c line 155
  • #2 camel_mapi_folder_new
    at camel-mapi-folder.c line 1603
  • #3 mapi_get_folder
    at camel-mapi-store.c line 428
  • #4 camel_store_get_folder
    at camel-store.c line 345
  • #5 mail_tool_uri_to_folder
    at mail-tools.c line 331
  • #6 get_folder_exec
    at mail-ops.c line 1218
  • #7 mail_msg_proxy
    at mail-mt.c line 522
  • #8 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.21.4/glib/gthreadpool.c line 265
  • #9 g_thread_create_proxy
    at /build/buildd/glib2.0-2.21.4/glib/gthread.c line 635
  • #10 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #11 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Comment 5 Milan Crha 2010-06-11 14:00:37 UTC
Thanks for a bug report. I see the ubuntu bug is reported with evolution 2.27.90. I didn't see this myself, and from the trace I see that the folder creation failed for some reason, but it doesn't make much sense, because when memory allocation fails, then the application aborts itself, usually.

The only other thing I can think of right now is something with type registration, but it's quite hard to ensure it, when there is no reproducer, and also because the thread stacktrace doesn't indicate any interleaving in this area.

I would like to ask you, whether you can retest with evolution-mapi 0.30.x and if it'll show you, then also paste here a console output before the crash, whether it'll show some critical warnings or anything similar. Thanks in advance.
Comment 6 Martin Mai 2010-06-11 17:05:33 UTC
For stability reasons, the latest Ubuntu version (10.04) is using evolution* 2.28.* and the development release is currently at 2.28.3, too, so it will take some time until it's possible to test this.

But I will leave a comment downstream and monitor the bug.
Comment 7 Tobias Mueller 2010-07-29 09:06:42 UTC
Hm. You could install Evolution from maverick. And I'm sure that PPAs with recent versions from git exist.
Comment 8 Martin Mai 2010-07-30 09:36:28 UTC
Unfortunately there is no matching PPA (Evolution in maverick is still at 2.30) . If it's about keeping the bug open, you could as well go ahead and close this one as "needinfo". I will update it when possible.

If I had the problem myself I would go ahead and build it from git myself, but that is simply not applicable for the ordinary user.
Comment 9 Tobias Mueller 2010-07-31 11:51:16 UTC
Hm. Well. There are PPAs with evolution-mapi: https://launchpad.net/ubuntu/+ppas?name_filter=mapi i.e. https://launchpad.net/~jacob/+archive/evo230
Comment 10 Martin Mai 2010-08-04 18:15:19 UTC
Ok, I actually found that ppa, but I thought the version is too old because current git master is at 0.31.6 (compared to 0.30.1 in the ppa).

However, I will leave a comment on the launchpad bug and keep an eye on that.
Comment 11 Akhil Laddha 2010-10-01 04:30:01 UTC
Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.32.0 or later, thanks.