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 479728 - crash in Tasks: clicked on email to view
crash in Tasks: clicked on email to view
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-09-24 07:49 UTC by mahajan.deepak
Modified: 2007-10-01 13:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mahajan.deepak 2007-09-24 07:49:43 UTC
Version: 2.10

What were you doing when the application crashed?
clicked on email to view


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.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 727044096 vsize: 727044096 resident: 155611136 share: 29495296 rss: 155611136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190618823 rtime: 16822 utime: 10778 stime: 6044 cutime:1 cstime: 1 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 46912496337040 (LWP 3167)]
[New Thread 1115699536 (LWP 3332)]
[New Thread 1126189392 (LWP 3248)]
[New Thread 1084229968 (LWP 3189)]
(no debugging symbols found)
0x000000352d20d97f in waitpid () from /lib64/libpthread.so.0

Thread 3 (Thread 1126189392 (LWP 3248))

  • #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 (144 sec old) ---------------------
(evolution:3167): camel-WARNING **: Could not find key entry for word 'sny5hnpu5xf2lpakk0zzqphj8ojpqfj3p': Invalid or incomplete multibyte or wide character
(evolution:3167): camel-WARNING **: Could not find key entry for word 'iptopwq6dju1oleyqvd6sdlywkx3i8yf3r2': Invalid or incomplete multibyte or wide character
(evolution:3167): camel-WARNING **: Could not find key entry for word 'w7vnuh5jnmixcphqhh2wkwzzzudqexr6p': Invalid or incomplete multibyte or wide character
(evolution:3167): camel-WARNING **: Could not find key entry for word 'yxz59lthh6jibpk4rp8ani2o': Invalid or incomplete multibyte or wide character
(evolution:3167): camel-WARNING **: Could not find key entry for word 'ht7m6dci20ijhwwyawjgeqqc8h': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-01 13:35:50 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 ***