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.
Bug 1213771 - evolution crashed while sending mail
Summary: evolution crashed while sending mail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1174414
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-21 09:15 UTC by Siteshwar Vashisht
Modified: 2019-06-13 08:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
This had been fixed by the rebase. I would not mention it in the Doc Text.
Clone Of:
Environment:
Last Closed: 2015-11-19 07:58:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch to fix 1213771 (2.86 KB, patch)
2015-04-21 09:19 UTC, Siteshwar Vashisht 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2226 0 normal SHIPPED_LIVE evolution bug fix and enhancement update 2015-11-19 08:37:43 UTC

Description Siteshwar Vashisht 2015-04-21 09:15:24 UTC 
Description of problem:

evolution crashed while sending mail with below backtrace :

#0  __GI_____strtoul_l_internal (nptr=nptr@entry=0x0, endptr=endptr@entry=0x0, base=base@entry=10, group=group@entry=0, loc=0x7f370b40d060 <_nl_global_locale>) at ../stdlib/strtol_l.c:298
298	  while (ISSPACE (*s))
(gdb) bt
#0  __GI_____strtoul_l_internal (nptr=nptr@entry=0x0, endptr=endptr@entry=0x0, base=base@entry=10, group=group@entry=0, loc=0x7f370b40d060 <_nl_global_locale>) at ../stdlib/strtol_l.c:298
#1  0x00007f370b08c102 in __GI_strtoul (nptr=nptr@entry=0x0, endptr=endptr@entry=0x0, base=base@entry=10) at ../stdlib/strtol.c:109
#2  0x00007f371237c70d in imapx_job_fetch_new_messages_start (job=0x2d0ce00, is=0x35a6870, cancellable=0x4173550, error=0x7f36b51e0ac0) at camel-imapx-server.c:5678
#3  0x00007f3712373039 in camel_imapx_job_run (job=job@entry=0x2d0ce00, is=is@entry=0x35a6870, error=error@entry=0x7f36b51e0ac0) at camel-imapx-job.c:218
#4  0x00007f37123762e2 in imapx_submit_job (is=is@entry=0x35a6870, job=job@entry=0x2d0ce00, error=error@entry=0x7f36b51e0ac0) at camel-imapx-server.c:3234
#5  0x00007f3712376399 in imapx_server_fetch_new_messages (is=is@entry=0x35a6870, folder=folder@entry=0x2da4950, async=async@entry=0, update_unseen=update_unseen@entry=0, 
    cancellable=cancellable@entry=0x4173550, error=error@entry=0x7f36b51e0ac0) at camel-imapx-server.c:3399
#6  0x00007f3712383ced in imapx_job_refresh_info_start (job=0x293bd30, is=0x35a6870, cancellable=0x4173550, error=0x7f36b51e0ac0) at camel-imapx-server.c:6029
#7  0x00007f3712373039 in camel_imapx_job_run (job=job@entry=0x293bd30, is=is@entry=0x35a6870, error=error@entry=0x7f36b51e0ac0) at camel-imapx-job.c:218
#8  0x00007f37123842ae in camel_imapx_server_refresh_info (is=is@entry=0x35a6870, folder=folder@entry=0x2da4950, cancellable=cancellable@entry=0x4173550, error=error@entry=0x7f36b51e0ac0)
    at camel-imapx-server.c:8014
#9  0x00007f37123703b9 in imapx_refresh_info_sync (folder=0x2da4950, cancellable=0x4173550, error=0x7f36b51e0b60) at camel-imapx-folder.c:817
#10 0x00007f371230a6ac in camel_folder_refresh_info_sync (folder=folder@entry=0x2da4950, cancellable=cancellable@entry=0x4173550, error=error@entry=0x7f36b51e0b60) at camel-folder.c:4147
#11 0x00007f36eda56900 in refresh_folders_exec (m=0x7f36e44170a0, cancellable=0x4173550, error=<optimized out>) at mail-send-recv.c:1049
#12 0x00007f36ee35ee17 in mail_msg_proxy (msg=0x7f36e44170a0) at mail-mt.c:426
#13 0x00007f370b48305c in g_thread_pool_thread_proxy (data=<optimized out>) at gthreadpool.c:307
#14 0x00007f370b4826d5 in g_thread_proxy (data=0x3dc5c50) at gthread.c:764
#15 0x00007f3710b89df5 in start_thread (arg=0x7f36b51e1700) at pthread_create.c:308
#16 0x00007f370b1481ad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Version-Release number of selected component (if applicable):
evolution-data-server-3.8.5-34.el7.x86_64

Additional info:
Upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=732607
Comment 1 Siteshwar Vashisht 2015-04-21 09:19:35 UTC 
Created attachment 1016752 [details]
Patch to fix 1213771

Backported patch from https://git.gnome.org/browse/evolution-data-server/commit/?id=20533b4
Comment 2 Milan Crha 2015-04-21 13:34:59 UTC 
Thanks for a bug report. This might be fixed once the rebase of evolution packages to 3.12.11 release will be done. See bug #1174414 for more information.
Comment 6 errata-xmlrpc 2015-11-19 07:58:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2226.html
Note You need to log in before you can comment on or make changes to this bug.