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 487422 - crash in Email: ttt
crash in Email: ttt
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-17 08:35 UTC by er
Modified: 2007-10-22 22:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description er 2007-10-17 08:35:27 UTC
Version: 2.10

What were you doing when the application crashed?
ttt


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 138592256 vsize: 138592256 resident: 46739456 share: 29319168 rss: 46739456 rss_rlim: 4294967295
CPU usage: start_time: 1192610019 rtime: 644 utime: 534 stime: 110 cutime:32 cstime: 5 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 -1208744224 (LWP 3101)]
[New Thread -1308623984 (LWP 3114)]
[New Thread -1254098032 (LWP 3109)]
[New Thread -1241613424 (LWP 3107)]
[New Thread -1220240496 (LWP 3104)]
(no debugging symbols found)
0x00bc6402 in __kernel_vsyscall ()

Thread 3 (Thread -1254098032 (LWP 3109))

  • #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:3101): camel-WARNING **: Could not find key entry for word 'мeтодичeского': Invalid or incomplete multibyte or wide character
(evolution:3101): camel-WARNING **: Could not find key entry for word 'прeдприятии': Invalid or incomplete multibyte or wide character
(evolution:3101): camel-WARNING **: Could not find key entry for word 'методичeская': Invalid or incomplete multibyte or wide character
(evolution:3101): camel-WARNING **: Could not find key entry for word 'формирования': Invalid or incomplete multibyte or wide character
(evolution:3101): camel-WARNING **: Could not find key entry for word '流与互动研讨等方式': Invalid argument
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-22 22:49:22 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 ***