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 510656 - crash in Tasks: Verifing my e-mail
crash in Tasks: Verifing my e-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-01-19 18:19 UTC by Rafael Angelo Batista Oneto
Modified: 2008-01-20 19:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Rafael Angelo Batista Oneto 2008-01-19 18:19:57 UTC 
Version: 2.10

What were you doing when the application crashed?
Verifing my e-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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 174141440 vsize: 174141440 resident: 65650688 share: 41426944 rss: 65650688 rss_rlim: 4294967295
CPU usage: start_time: 1200776933 rtime: 1121 utime: 867 stime: 254 cutime:36 cstime: 11 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 -1209178400 (LWP 5895)]
[New Thread -1266877552 (LWP 6005)]
[New Thread -1324004464 (LWP 5947)]
[New Thread -1256383600 (LWP 5927)]
[New Thread -1245893744 (LWP 5921)]
(no debugging symbols found)
0x00abb402 in __kernel_vsyscall ()

+ Trace 185988

Thread 2 (Thread -1266877552 (LWP 6005))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_88
    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 ---------------------
(evolution:5895): camel-WARNING **: Could not find key entry for word '0000000000': Multibyte ou caracter largo inválido
(evolution:5895): camel-WARNING **: Could not find key entry for word '0000000000000': Multibyte ou caracter largo inválido
(evolution:5895): camel-WARNING **: Could not find key entry for word '00000000000': Multibyte ou caracter largo inválido
(evolution:5895): camel-WARNING **: Could not find key entry for word '00000000000000': Multibyte ou caracter largo inválido
warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-20 19:55:26 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 ***