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 1836153 - Crash on meeting with empty attendee
Summary: Crash on meeting with empty attendee
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-15 09:26 UTC by Michal Odehnal
Modified: 2020-09-29 20:26 UTC (History)
2 users (show)

Fixed In Version: evolution-3.28.5-9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 20:26:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backtrace of the crash (17.58 KB, text/plain)
2020-05-15 09:26 UTC, Michal Odehnal
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3995 0 None None None 2020-09-29 20:26:29 UTC

Description Michal Odehnal 2020-05-15 09:26:45 UTC
Created attachment 1688846 [details]
backtrace of the crash

Description of problem:
Creating an empty attendee on a new Meeting will crash evolution any time I left/right click on the event. 

Version-Release number of selected component (if applicable):
evolution-data-server-debuginfo-3.28.5-5.el7.x86_64
evolution-ews-3.28.5-6.el7.x86_64
evolution-langpacks-3.28.5-8.el7.noarch
evolution-data-server-3.28.5-5.el7.x86_64
evolution-3.28.5-8.el7.x86_64
evolution-debuginfo-3.28.5-8.el7.x86_64
evolution-ews-langpacks-3.28.5-6.el7.noarch
evolution-data-server-langpacks-3.28.5-5.el7.noarch


How reproducible:


Steps to Reproduce:
1. Create Meeting
2. Have an empty user as attendee.
3. Save the Meeting
4. Click on the Meeting.

Actual results:
Crash of evolution

Expected results:
Evolution will not crash

Additional info:

Comment 2 Milan Crha 2020-05-15 09:49:10 UTC
A meeting with attendees like this:

ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;LANGUAGE=en:user
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;
 RSVP=TRUE;LANGUAGE=en:

can cause the crash. This is partly related to bug #1721543.

Comment 6 Michal Odehnal 2020-05-19 07:19:47 UTC
Unable to reproduce with evolution-3.28.5-9

Comment 8 errata-xmlrpc 2020-09-29 20:26:20 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 (evolution-data-server bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:3995


Note You need to log in before you can comment on or make changes to this bug.