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 597557 - crash in Evolution Mail and Calendar: opened a large mailing l...
crash in Evolution Mail and Calendar: opened a large mailing l...
Status: RESOLVED DUPLICATE of bug 588374
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-06 14:34 UTC by rostedt
Modified: 2009-10-07 00:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description rostedt 2009-10-06 14:34:57 UTC 
What were you doing when the application crashed?
opened a large mailing list


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

System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 21:08:31 UTC 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: 180412416 vsize: 180412416 resident: 31244288 share: 20176896 rss: 31244288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254839643 rtime: 430 utime: 370 stime: 60 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 0xeed14b90 (LWP 32126)]
[New Thread 0xf0efeb90 (LWP 32071)]
[New Thread 0xefdaab90 (LWP 32070)]
[New Thread 0xf05abb90 (LWP 32069)]
[New Thread 0xf3133b90 (LWP 32066)]
[New Thread 0xf3934b90 (LWP 32060)]
[New Thread 0xf4135b90 (LWP 32059)]
[New Thread 0xf5165b90 (LWP 32054)]
[New Thread 0xf5966b90 (LWP 32051)]
0xf7f23425 in __kernel_vsyscall ()

+ Trace 218099

Thread 2 (Thread 0xeed14b90 (LWP 32126))

  • #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.22.0-1-i386-YCLGRR/glib2.0-2.22.0/glib/gthreadpool.c line 265
  • #15 g_thread_create_proxy
    at /build/buildd-glib2.0_2.22.0-1-i386-YCLGRR/glib2.0-2.22.0/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 (2246719 sec old) ---------------------
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:6219): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-10-07 00:38:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 588374 ***