Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Thanks for a bug report. There is one exactly same bug report [1] filled upstream, though it didn't get its fix and is closed as incomplete. Fortunately we have this filled here already, thus I'm marking this as a duplicate of it.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=595968
*** This bug has been marked as a duplicate of bug 602667 ***
Description of problem: segfault in camel_msgport_try_pop during check of folders after startup Version-Release number of selected component (if applicable): evolution-2.28.3-25.2.el6.x86_64 How reproducible: happened just once. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Interesting part of the backtrace: Thread 1 (Thread 0x7f959e44f940 (LWP 3227)): #0 camel_msgport_try_pop (msgport=0x72929292929299e) at camel-msgport.c:402 msg = <value optimized out> __PRETTY_FUNCTION__ = "camel_msgport_try_pop" #1 0x000000336f844644 in camel_operation_cancel_check (cc=0x560c440) at camel-operation.c:405 msg = <value optimized out> cancelled = <value optimized out> #2 0x00007f95933d7ae1 in regen_list_done (m=0x82be0c0) at message-list.c:4232 No locals. #3 0x00007f959314b871 in mail_msg_idle_cb () at mail-mt.c:502 msg = 0x82be0c0 __PRETTY_FUNCTION__ = "mail_msg_idle_cb" #4 0x0000003359c38f0e in g_main_dispatch (context=0xe9dda0) at gmain.c:1960 dispatch = 0x3359c37070 <g_idle_dispatch> was_in_call = 0 user_data = 0x0 callback = 0x7f959314b770 <mail_msg_idle_cb> cb_funcs = 0x3359ee4150 cb_data = 0x78a5420 current_source_link = {data = 0x4184400, next = 0x0} need_destroy = <value optimized out> source = 0x4184400 current = 0xf0f890 i = <value optimized out> #5 IA__g_main_context_dispatch (context=0xe9dda0) at gmain.c:2513 No locals.