Bug 1539425

Summary: [abrt] evolution: g_ascii_strncasecmp(): evolution killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Sergio Basto <sergio>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: alexl, brick.and.blade, caillon+fedoraproject, francois.perriot, lucilanga, mcrha, rhughes, rstrode, sandmann, two.oes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4a3eb3a103ee8708ae443c1269e7769b9736f00d
Whiteboard: abrt_hash:f48c7ea90b691ffbbcba868a13dc7999eff197f6;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 21:59:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Sergio Basto 2018-01-28 21:01:36 UTC
Description of problem:
began last week , maybe related with apointment in  calendar 

Version-Release number of selected component:
evolution-3.24.6-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/evolution
crash_function: g_ascii_strncasecmp
executable:     /usr/bin/evolution
journald_cursor: s=9e157fce474744aa84f03bc7e7ca0d08;i=83444;b=fc2e47dbc6254934a03a01928bf7b39e;m=57f85b5eb7;t=563af09a0c644;x=73745c1962611ecb
kernel:         4.14.13-200.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_ascii_strncasecmp at gstrfuncs.c:1841
 #1 itip_strip_mailto at /usr/src/debug/evolution-3.24.6/src/calendar/gui/itip-utils.c:645
 #2 itip_view_init_view at /usr/src/debug/evolution-3.24.6/src/modules/itip-formatter/itip-view.c:6009
 #3 web_extension_proxy_created_cb at /usr/src/debug/evolution-3.24.6/src/modules/itip-formatter/itip-view.c:1862
 #4 g_task_return_now at gtask.c:1145
 #5 g_task_return at gtask.c:1203
 #6 init_second_async_cb at gdbusproxy.c:1808
 #7 g_task_return_now at gtask.c:1145
 #8 g_task_return at gtask.c:1203
 #9 async_init_data_set_name_owner at gdbusproxy.c:1499

Potential duplicate: bug 1502776

Comment 1 Sergio Basto 2018-01-28 21:01:43 UTC
Created attachment 1387345 [details]
File: backtrace

Comment 2 Sergio Basto 2018-01-28 21:01:44 UTC
Created attachment 1387346 [details]
File: cgroup

Comment 3 Sergio Basto 2018-01-28 21:01:47 UTC
Created attachment 1387347 [details]
File: core_backtrace

Comment 4 Sergio Basto 2018-01-28 21:01:48 UTC
Created attachment 1387348 [details]
File: cpuinfo

Comment 5 Sergio Basto 2018-01-28 21:01:51 UTC
Created attachment 1387349 [details]
File: dso_list

Comment 6 Sergio Basto 2018-01-28 21:01:53 UTC
Created attachment 1387350 [details]
File: environ

Comment 7 Sergio Basto 2018-01-28 21:01:55 UTC
Created attachment 1387351 [details]
File: exploitable

Comment 8 Sergio Basto 2018-01-28 21:01:56 UTC
Created attachment 1387352 [details]
File: limits

Comment 9 Sergio Basto 2018-01-28 21:01:59 UTC
Created attachment 1387353 [details]
File: maps

Comment 10 Sergio Basto 2018-01-28 21:02:01 UTC
Created attachment 1387354 [details]
File: open_fds

Comment 11 Sergio Basto 2018-01-28 21:02:03 UTC
Created attachment 1387355 [details]
File: proc_pid_status

Comment 12 Sergio Basto 2018-01-28 21:02:05 UTC
Created attachment 1387356 [details]
File: var_log_messages

Comment 13 Milan Crha 2018-01-29 08:26:58 UTC
Thanks for a bug report. If I read the backtrace properly, then this happened when you've selected certain meeting invitation mail. I have several meeting invitation mails and none causes this crash, thus I'm wondering what the cause could be. Does it happen for every meeting invitation mail you have, or only any of them?

Comment 14 Milan Crha 2018-02-27 09:32:15 UTC
*** Bug 1549311 has been marked as a duplicate of this bug. ***

Comment 15 François Perriot 2018-03-18 21:09:24 UTC
*** Bug 1557801 has been marked as a duplicate of this bug. ***

Comment 16 Ben Cotton 2018-11-27 15:11:41 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Ben Cotton 2018-11-30 21:59:09 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.