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 520419 - crash in Tasks: Fetching new mail
crash in Tasks: Fetching new mail
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-04 23:58 UTC by santiago.cardin
Modified: 2008-03-06 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description santiago.cardin 2008-03-04 23:58:39 UTC 
Version: 2.10

What were you doing when the application crashed?
Fetching new mail


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136585216 vsize: 136585216 resident: 43941888 share: 28917760 rss: 43941888 rss_rlim: 4294967295
CPU usage: start_time: 1204675298 rtime: 2639 utime: 2480 stime: 159 cutime:40 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209112864 (LWP 4147)]
[New Thread -1275405424 (LWP 4198)]
[New Thread -1296385136 (LWP 4196)]
[New Thread -1243616368 (LWP 4171)]
[New Thread -1221022832 (LWP 4168)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191324

Thread 3 (Thread -1296385136 (LWP 4196))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #7 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #10 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #11 camel_local_summary_check
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #12 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #13 camel_folder_refresh_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6 


----------- .xsession-errors (33 sec old) ---------------------
(evolution:4147): camel-WARNING **: Could not find key entry for word 'listiddocumentbytypeofstreetid': Invalid or incomplete multibyte or wide character
(evolution:4147): camel-WARNING **: Could not find key entry for word 'textverdana11px000000': Invalid or incomplete multibyte or wide character
(evolution:4147): camel-WARNING **: Could not find key entry for word 'textverdana10px000000': Invalid or incomplete multibyte or wide character
(evolution:4147): camel-WARNING **: Could not find key entry for word 'presentarme': Invalid or incomplete multibyte or wide character
(evolution:4147): camel-WARNING **: Could not find key entry for word 'presentarme': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Tobias Mueller 2008-03-06 16:32:39 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 339602 ***