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 589181 - crash in Evolution Mail and Calendar: starting evolution (it h...
crash in Evolution Mail and Calendar: starting evolution (it h...
Status: RESOLVED DUPLICATE of bug 588374
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-07-20 21:30 UTC by rostedt
Modified: 2009-07-21 03:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description rostedt 2009-07-20 21:30:15 UTC 
What were you doing when the application crashed?
starting evolution (it has been crashing a lot lately)


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-rc6 #4 SMP PREEMPT Wed May 20 21:50:40 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 158695424 vsize: 158695424 resident: 27328512 share: 19804160 rss: 27328512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1248125358 rtime: 229 utime: 180 stime: 49 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xf6153760 (LWP 700)]
[New Thread 0xefd46b90 (LWP 742)]
[New Thread 0xf15feb90 (LWP 714)]
[New Thread 0xf1dffb90 (LWP 713)]
[New Thread 0xf2fcfb90 (LWP 711)]
[New Thread 0xf37d0b90 (LWP 710)]
[New Thread 0xf3fd2b90 (LWP 709)]
[New Thread 0xf592ab90 (LWP 707)]
0xf7f20425 in __kernel_vsyscall ()

+ Trace 216549

Thread 2 (Thread 0xefd46b90 (LWP 742))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_89
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 segv_redirect
    at main.c line 435
  • #5 <signal handler called>
  • #6 summary_update
    at camel-mbox-summary.c line 600
  • #7 mbox_summary_check
    at camel-mbox-summary.c line 677
  • #8 spool_summary_check
    at camel-spool-summary.c line 315
  • #9 camel_local_summary_check
    at camel-local-summary.c line 277
  • #10 local_refresh_info
    at camel-local-folder.c line 491
  • #11 camel_folder_refresh_info
    at camel-folder.c line 349
  • #12 refresh_folder_exec
    at mail-ops.c line 1664
  • #13 mail_msg_proxy
    at mail-mt.c line 520
  • #14 g_thread_pool_thread_proxy
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gthreadpool.c line 265
  • #15 g_thread_create_proxy
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gthread.c line 635
  • #16 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #17 clone
    from /lib/i686/cmov/libc.so.6 


----------- .xsession-errors (1332878 sec old) ---------------------
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
(evolution:4448): camel-local-provider-WARNING **: Didn't get the next message where I expected (547) got 0 instead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-07-21 03:55:55 UTC 
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 588374 ***