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 444939 - evolution crashed shortly after opening
evolution crashed shortly after opening
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 506999 535708 540302 569159 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-07 00:07 UTC by Eric Harney
Modified: 2010-05-10 04:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
command line output from "CAMEL_DEBUG=all evolution" (178.02 KB, text/plain)
2007-06-07 00:08 UTC, Eric Harney
Details

Description Eric Harney 2007-06-07 00:07:48 UTC
Steps to reproduce:
1. Open evolution
2. Doesn't always crash, but I'm getting it rather frequently.  Seems to always crash while "Storing folder" and downloading new mail from an account. 


Stack trace:
(Bug Buddy failed to submit this itself.)

Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 686493696 vsize: 686493696 resident: 63275008 share: 18100224 rss: 63275008 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181174465 rtime: 1044 utime: 774 stime: 270 cutime:52 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034hUsing host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496365152 (LWP 4301)]
[New Thread 1136679248 (LWP 4331)]
[New Thread 1115699536 (LWP 4329)]
[New Thread 1147435344 (LWP 4316)]
[New Thread 1126189392 (LWP 4312)]
[New Thread 1094719824 (LWP 4309)]
[New Thread 1105209680 (LWP 4307)]
[New Thread 1084229968 (LWP 4305)]
0x000000316a80d89f in __libc_waitpid (pid=4339, stat_loc=0x7fff786bd4fc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 6 (Thread 1094719824 (LWP 4309))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 <signal handler called>
  • #4 memset
    from /lib64/libc.so.6
  • #5 e_memchunk_alloc0
    at /usr/include/bits/string3.h line 96
  • #6 camel_message_info_new
    at camel-folder-summary.c line 2703
  • #7 message_info_new_from_header
    at camel-folder-summary.c line 1716
  • #8 message_info_new_from_header
    at camel-local-summary.c line 627
  • #9 message_info_new_from_header
    at camel-mbox-summary.c line 277
  • #10 message_info_new_from_parser
    at camel-mbox-summary.c line 356
  • #11 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 1000
  • #12 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 920
  • #13 summary_update
    at camel-mbox-summary.c line 485
  • #14 mbox_summary_check
    at camel-mbox-summary.c line 575
  • #15 mbox_summary_sync
    at camel-mbox-summary.c line 847
  • #16 local_sync
    at camel-local-folder.c line 498
  • #17 camel_folder_sync
    at camel-folder.c line 273
  • #18 camel_filter_driver_filter_folder
    at camel-filter-driver.c line 1302
  • #19 em_filter_folder_element_filter
    at mail-ops.c line 140
  • #20 fetch_mail_fetch
    at mail-ops.c line 325
  • #21 mail_msg_proxy
    at mail-mt.c line 484
  • #22 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #23 g_thread_create_proxy
    at gthread.c line 591
  • #24 start_thread
    at pthread_create.c line 296
  • #25 clone
    from /lib64/libc.so.6


----------- .xsession-errors (334 sec old) ---------------------
(evolution:3559): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3559): e-data-server-WARNING **: Could not open converter for 'UNKNOWN' to 'UTF-8' charset
(evolution:3559): e-data-server-WARNING **: Could not open converter for '136' to 'UTF-8' charset
(evolution:3559): e-data-server-WARNING **: Could not open converter for '134' to 'UTF-8' charset
Loading "fastestmirror" plugin
Loading "installonlyn" plugin
Loading mirror speeds from cached hostfile
Loading mirror speeds from cached hostfile
--------------------------------------------------

Other information:
Will attach file from CAMEL_DEBUG=all
Comment 1 Eric Harney 2007-06-07 00:08:29 UTC
Created attachment 89521 [details]
command line output from "CAMEL_DEBUG=all evolution"
Comment 2 Eric Harney 2007-06-07 17:02:52 UTC
I should revise my "Doesn't always crash" statement - this is currently happening every time I start evolution.  I can apply any additional debugging techniques which would be useful in diagnosing this crash.  
Comment 3 Milan Crha 2008-02-20 17:20:33 UTC
*** Bug 506999 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2008-02-20 17:35:41 UTC
Can you still reproduce this please? I would like to investigate more on this.
Can I ask you what kind of accounts you're using? It would be interesting to know what is on the console of evolution-data-server and evolution itself in time of the crash, maybe something useful, I hope.
Comment 5 Eric Harney 2008-02-23 17:37:41 UTC
That system has since been upgraded to evolution 2.12 and I haven't seen it happen.

It was using a couple of (3?) POP accounts.
Comment 6 Milan Crha 2008-02-25 09:16:29 UTC
Thanks for your info. I will close this as working in actual stable version, but please feel free to reopen if you face it again. 
Comment 7 Milan Crha 2008-09-23 16:25:23 UTC
*** Bug 540302 has been marked as a duplicate of this bug. ***
Comment 8 Milan Crha 2008-09-23 16:25:48 UTC
*** Bug 535708 has been marked as a duplicate of this bug. ***
Comment 9 Milan Crha 2008-09-23 16:29:35 UTC
Reopening and changing version from 2.10 to 2.22, because the above duplicates come from there.
Comment 10 Akhil Laddha 2009-08-27 07:39:51 UTC
*** Bug 569159 has been marked as a duplicate of this bug. ***
Comment 11 Akhil Laddha 2009-08-27 07:40:21 UTC
last dupe in 2.24.x
Comment 12 Akhil Laddha 2010-03-26 05:24:51 UTC
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.30.

Can you please check again whether this issue still happens in Evolution 2.28
or 2.30 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 13 Akhil Laddha 2010-05-10 04:27:42 UTC
Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.30.0 or later, thanks.