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 502551 - crash in Tasks: downloading mail
crash in Tasks: downloading mail
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-08 19:54 UTC by dennis.gimmel
Modified: 2007-12-09 06:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dennis.gimmel 2007-12-08 19:54:51 UTC 
Version: 2.10

What were you doing when the application crashed?
downloading mail


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

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 793714688 vsize: 793714688 resident: 87326720 share: 62377984 rss: 87326720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197143658 rtime: 398 utime: 301 stime: 97 cutime:22 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496432496 (LWP 21569)]
[New Thread 1136945488 (LWP 21595)]
[New Thread 1136679248 (LWP 21594)]
[New Thread 1105209680 (LWP 21589)]
[New Thread 1084229968 (LWP 21586)]
(no debugging symbols found)
0x00000031e8c0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 181257

Thread 3 (Thread 1136679248 (LWP 21594))

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


----------- .xsession-errors ---------------------
(evolution:21569): camel-WARNING **: Could not find key entry for word 'образования': Invalid or incomplete multibyte or wide character
(evolution:21569): camel-WARNING **: Could not find key entry for word 'спецдипозитариев': Invalid argument
(evolution:21569): e-data-server-WARNING **: Could not open converter for 'DEFAULT' to 'UTF-8' charset
(evolution:21569): e-data-server-WARNING **: Could not open converter for 'DEFAULT' to 'UTF-8' charset
(evolution:21569): e-data-server-WARNING **: Could not open converter for 'DEFAULT' to 'UTF-8' charset
(evolution:21569): e-data-server-WARNING **: Could not open converter for 'us-asci8E-' to 'UTF-8' charset
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff75dfd000
--------------------------------------------------
Comment 1 Tobias Mueller 2007-12-09 06:45:29 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 ***