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 491866 - crash in Evolution Mail: I've just started the ap...
crash in Evolution Mail: I've just started the ap...
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-30 21:26 UTC by felixrubiodalmau
Modified: 2007-10-31 21:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description felixrubiodalmau 2007-10-30 21:26:39 UTC
What were you doing when the application crashed?
I've just started the application, I've got no time to do anything yet :s


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 105230336 vsize: 105230336 resident: 28364800 share: 16523264 rss: 28364800 rss_rlim: 4294967295
CPU usage: start_time: 1193779556 rtime: 188 utime: 167 stime: 21 cutime:1 cstime: 2 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68906b0 (LWP 3164)]
[New Thread 0xb2686b90 (LWP 3220)]
[New Thread 0xb2f2eb90 (LWP 3219)]
[New Thread 0xb389bb90 (LWP 3218)]
[New Thread 0xb489db90 (LWP 3188)]
[New Thread 0xb50feb90 (LWP 3187)]
[New Thread 0xb58ffb90 (LWP 3186)]
[New Thread 0xb626fb90 (LWP 3183)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb2f2eb90 (LWP 3219))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_86
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
  • #11 ??
  • #12 <signal handler called>
  • #13 camel_index_add_name
    from /usr/lib/libcamel-1.2.so.10
  • #14 camel_folder_summary_info_new_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #15 camel_folder_summary_add_from_parser
    from /usr/lib/libcamel-provider-1.2.so.10
  • #16 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
  • #17 ??
  • #18 ??
  • #19 ??


----------- .xsession-errors ---------------------
(evolution:3164): camel-WARNING **: Could not find key entry for word 'устанавливаем': Invalid or incomplete multibyte or wide character
(evolution:3164): camel-WARNING **: Could not find key entry for word 'сoздание': Invalid or incomplete multibyte or wide character
(evolution:3164): camel-WARNING **: Could not find key entry for word 'парктроник': Invalid or incomplete multibyte or wide character
(evolution:3164): camel-WARNING **: Could not find key entry for word 'круизконтроль': Invalid or incomplete multibyte or wide character
(evolution:3164): camel-WARNING **: Could not find key entry for word 'йпсхгйнмрпнкэ': Invalid or incomplete multibyte or wide character
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-31 21:55:58 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 ***