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 476604 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-13 15:44 UTC by Jon Day
Modified: 2007-09-29 01:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jon Day 2007-09-13 15:44:27 UTC
Version: 2.10

What were you doing when the application crashed?



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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 148410368 vsize: 148410368 resident: 46096384 share: 28512256 rss: 46096384 rss_rlim: 4294967295
CPU usage: start_time: 1189698253 rtime: 528 utime: 438 stime: 90 cutime:30 cstime: 7 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 -1208584480 (LWP 3383)]
[New Thread -1336935536 (LWP 3414)]
[New Thread -1324794992 (LWP 3413)]
[New Thread -1283478640 (LWP 3407)]
[New Thread -1262498928 (LWP 3404)]
[New Thread -1219298416 (LWP 3400)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 3 (Thread -1324794992 (LWP 3413))

  • #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 ---------------------
(evolution:3383): camel-WARNING **: Could not find key entry for word 'гороховый': Invalid or incomplete multibyte or wide character
(evolution:3383): camel-WARNING **: Could not find key entry for word '3весенний': Invalid or incomplete multibyte or wide character
(evolution:3383): camel-WARNING **: Could not find key entry for word '3драники': Invalid or incomplete multibyte or wide character
(evolution:3383): camel-WARNING **: Could not find key entry for word 'отбивная': Invalid or incomplete multibyte or wide character
(evolution:3383): camel-WARNING **: Could not find key entry for word 'картофель': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-29 01:53:16 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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