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 481982 - crash in Tasks: Open evolution. "Storin...
crash in Tasks: Open evolution. "Storin...
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-30 20:19 UTC by huixquic
Modified: 2007-10-01 13:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description huixquic 2007-09-30 20:19:53 UTC 
Version: 2.10

What were you doing when the application crashed?
Open evolution.  "Storing folder (69% complete)"  and boom !!!
same thing happens every time.   Just updated evo to latest version for Fedora 7.



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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 173764608 vsize: 173764608 resident: 58265600 share: 30654464 rss: 58265600 rss_rlim: 4294967295
CPU usage: start_time: 1191183506 rtime: 1852 utime: 1501 stime: 351 cutime:52 cstime: 13 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 -1209100576 (LWP 3659)]
[New Thread -1264522352 (LWP 3690)]
[New Thread -1308337264 (LWP 3687)]
[New Thread -1253639280 (LWP 3678)]
[New Thread -1232659568 (LWP 3675)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166694

Thread 2 (Thread -1264522352 (LWP 3690))

  • #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 (15 sec old) ---------------------
(evolution:3659): camel-WARNING **: Could not find key entry for word 'применение': Invalid or incomplete multibyte or wide character
(evolution:3659): camel-WARNING **: Could not find key entry for word 'согласовании': Invalid or incomplete multibyte or wide character
(evolution:3659): camel-WARNING **: Could not find key entry for word 'формирования': Invalid or incomplete multibyte or wide character
(evolution:3659): camel-WARNING **: Could not find key entry for word 'другими': Invalid or incomplete multibyte or wide character
(evolution:3659): camel-WARNING **: Could not find key entry for word 'проектирования': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-01 13:37:16 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.

Could give detailed instructions on how to reproduce this bug in bug 339602? Thanks in advance :)

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