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 353730 - Evolution crashes after half a minute
Evolution crashes after half a minute
Status: RESOLVED DUPLICATE of bug 456003
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-08-31 20:05 UTC by Sebastien Bacher
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sebastien Bacher 2006-08-31 20:05:51 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/evolution/+bug/58316

"Since this morning (20060831) I get a crash every 30 seconds, just by simply browsing the email.
...
(evolution-2.6:8294): camel-WARNING **: Could not find key entry for word '损益表的阅读与分析': Invalid or incomplete multibyte or wide character

(evolution-2.6:8294): camel-WARNING **: Could not find key entry for word '损益表的阅读与分析': Invalid or incomplete multibyte or wide character

(evolution-2.6:8294): camel-WARNING **: Could not find key entry for word '损益表的阅读与分析': Invalid or incomplete multibyte or wide character

(evolution-2.6:8294): camel-WARNING **: Could not find key entry for word '损益表的阅读与分析': Invalid or incomplete multibyte or wide character

Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 8304)

  • #0 camel_index_add_name
    at camel-index.c line 183
  • #1 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 951
  • #2 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 856
  • #3 summary_update
    at camel-mbox-summary.c line 467
  • #4 mbox_summary_check
    at camel-mbox-summary.c line 554
  • #5 camel_local_summary_check
    at camel-local-summary.c line 268
  • #6 local_refresh_info
    at camel-local-folder.c line 476
  • #7 camel_folder_refresh_info
    at camel-folder.c line 298
  • #8 refresh_folder_refresh
    at mail-ops.c line 1584
  • #9 mail_msg_received
    at mail-mt.c line 570
  • #10 thread_dispatch
    at e-msgport.c line 974

Comment 1 Karsten Bräckelmann 2006-08-31 20:47:57 UTC
Matches the gdb stacktrace in bug 339602 comment 1.


*** This bug has been marked as a duplicate of 339602 ***
Comment 2 Sebastien Bacher 2006-09-01 08:58:09 UTC
I don't think that's a duplicate, comment #1 on that other bug should be a different issue than the bug description and should have been a new bug, not a comment on an another issue, reopening that one
Comment 3 Simos Xenitellis 2007-05-02 19:33:57 UTC
I have the same problem. 
Using Ubuntu 6.10 on x86, and a rather big evolution mailbox (>1GB)
When starting evolution, it crashes after a few seconds. The console shows about 50 lines of the type

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'vfs': Success

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'mounts': Success

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'mount': Success

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'kernel': Success

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'proxy': Success

(evolution-2.8:5492): camel-WARNING **: Could not find key entry for word 'pure': Success


and about 15 lines of the type


(evolution-2.8:5492): camel-local-provider-WARNING **: Could not open/create index file: Bad file descriptor: indexing not performed

(evolution-2.8:5492): camel-local-provider-WARNING **: Could not open/create index file: Bad file descriptor: indexing not performed

(evolution-2.8:5492): camel-local-provider-WARNING **: Could not open/create index file: Bad file descriptor: indexing not performed


I believe this might be related to an earlier problem I had; the file descriptors of the kernel would get consumed and no new files could be opened. Evolution would fail to create new index files and freeze. Apparently the file handles where somehow consumed by beagle which I have now uninstalled.

I get the problem even when I run "evolution --offline".

To restart evolution, I do "evolution --force-shutdown".

To make matters worse, evolution sometimes crashes early enough not to show any of the error messages above.
Comment 4 Simos Xenitellis 2007-05-02 19:56:47 UTC
Ok, I set CAMEL_DEBUG=all and run evolution on the command line.
I now get to see which where I get the messages 

(evolution-2.8:5492): camel-local-provider-WARNING **: Could not open/create
index file: Bad file descriptor: indexing not performed

and I enter and delete the *index* files for the specific folders.

After I completed that, evolution appeared to work ok once. However, subsequent runs would crash, and I end up with the same error for folders that I have already erased the *index* files. As if the threads were creating the index files but die prematurely before completing their work.

Comment 5 Simos Xenitellis 2007-07-03 02:37:55 UTC
I still have the problem of evolution crashing during the start.
This is Evolution 2.8.1 on Edgy.

Now I get the warning 
(evolution-2.8:14242): camel-local-provider-WARNING **: Could not open/create index file: Bad file descriptor: indexing not performed

though I am not sure if it is actually related to the crashes.

My screen resolution is 1024x786 and it appears that evolution cannot fit all the elements in the window when it is maximised. Especially, when I use the Greek locale, the text messages are wider than the English ones, requiring even more horizontal space for the vertical layout of Evolution. I can get evolution to crash rather consistently when I use the Greek locale and I get the window be maximised while it loads. Once Evo has loaded, I do not get crashes. When I start Evo with --offline, it appears to help sometimes.
Comment 6 palfrey 2007-07-12 11:34:32 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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