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 496173 - crash in Evolution Mail:
crash in Evolution Mail:
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-11-12 16:59 UTC by spam
Modified: 2007-11-14 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description spam 2007-11-12 16:59:22 UTC 
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21.1y #2 Wed May 16 13:26:02 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 105353216 vsize: 105353216 resident: 38420480 share: 17428480 rss: 38420480 rss_rlim: 4294967295
CPU usage: start_time: 1194886683 rtime: 2571 utime: 2282 stime: 289 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233102240 (LWP 2851)]
[New Thread -1285555312 (LWP 2944)]
[New Thread -1275278448 (LWP 2942)]
[New Thread -1266889840 (LWP 2935)]
[New Thread -1266140272 (LWP 2917)]
[New Thread -1248011376 (LWP 2915)]
[New Thread -1256879216 (LWP 2913)]
[New Thread -1239585904 (LWP 2907)]
0xb775ab11 in ?? () from /lib/libpthread.so.0

+ Trace 177215

Thread 3 (Thread -1275278448 (LWP 2942))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_88
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 segv_redirect
    at main.c line 436
  • #4 <signal handler called>
  • #5 camel_index_add_name
    at camel-index.c line 183
  • #6 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 1026
  • #7 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 931
  • #8 summary_update
    at camel-mbox-summary.c line 485
  • #9 mbox_summary_check
    at camel-mbox-summary.c line 572
  • #10 camel_local_summary_check
    at camel-local-summary.c line 268
  • #11 local_refresh_info
    at camel-local-folder.c line 476
  • #12 camel_folder_refresh_info
    at camel-folder.c line 298
  • #13 refresh_folder_refresh
    at mail-ops.c line 1585
  • #14 mail_msg_received
    at mail-mt.c line 582
  • #15 thread_dispatch
    at e-msgport.c line 1005
  • #16 start_thread
    from /lib/libpthread.so.0
  • #17 clone
    from /lib/libc.so.6 


----------- .xsession-errors (20 sec old) ---------------------
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-2027-8' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-530-8' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-6581-4' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-8993-1' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-7492-4' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-3806-7' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset
(evolution:2851): e-data-server-WARNING **: Could not open converter for 'iso-5094-0' to 'UTF-8' charset
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-14 00:49:53 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 ***