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 510661 - crash in Tasks:
crash in Tasks:
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 19:18 UTC by Brian L Scipioni
Modified: 2008-01-20 19:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Brian L Scipioni 2008-01-19 19:18:57 UTC
Version: 2.10

What were you doing when the application crashed?



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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 191352832 vsize: 191352832 resident: 62967808 share: 35323904 rss: 62967808 rss_rlim: 4294967295
CPU usage: start_time: 1200770309 rtime: 1085 utime: 830 stime: 255 cutime:23 cstime: 4 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 -1209182496 (LWP 3724)]
[New Thread -1347564656 (LWP 3754)]
[New Thread -1317237872 (LWP 3750)]
[New Thread -1253049456 (LWP 3744)]
[New Thread -1241359472 (LWP 3741)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1347564656 (LWP 3754))

  • #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:3724): e-data-server-WARNING **: Could not open converter for 'iso-3666-8' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-8253-3' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-5599-2' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-7828-0' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-950-6' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-5403-8' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-9324-1' to 'UTF-8' charset
(evolution:3724): e-data-server-WARNING **: Could not open converter for 'iso-7023-2' to 'UTF-8' charset
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-20 19:55:35 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 ***