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 1441145 - Crash under e_meeting_time_selector_refresh_cb()
Summary: Crash under e_meeting_time_selector_refresh_cb()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 10:04 UTC by Vladimir Benes
Modified: 2017-08-01 12:27 UTC (History)
2 users (show)

Fixed In Version: evolution-3.22.6-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 12:27:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2066 0 normal SHIPPED_LIVE evolution bug fix and enhancement update 2017-08-01 16:05:58 UTC

Description Vladimir Benes 2017-04-11 10:04:28 UTC 
Description of problem:
I don't have proper reproducer but it looks like with heavy clicking you can crash evo.

    (evolution:11345): calendar-gui-CRITICAL **: e_meeting_store_get_num_queries: assertion 'E_IS_MEETING_STORE (store)' failed
     
    Program received signal SIGSEGV, Segmentation fault.
    0x00007fffecf035eb in g_type_check_instance_cast (
        type_instance=0x7fff901e6960, iface_type=76451776) at gtype.c:4057
    4057              is_instantiatable = node && node->is_instantiatable;
    (gdb) bt full
    #0  0x00007fffecf035eb in g_type_check_instance_cast (type_instance=0x7fff901e6960, iface_type=76451776) at gtype.c:4057
            node = 0x700000008
            iface = <optimized out>
            is_instantiatable = <optimized out>
            check = <optimized out>
    #1  0x00007fffbaeee270 in e_meeting_time_selector_refresh_cb ()
        at /usr/lib64/evolution/libevolution-calendar.so
    #2  0x00007fffecc060d7 in g_idle_dispatch (source=0x7fff904ee5d0, callback=0x7fffbaeee1d0 <e_meeting_time_selector_refresh_cb>, user_data=0x9247550)
        at gmain.c:5543
            again = <optimized out>
    #3  0x00007fffecc094c9 in g_main_context_dispatch (context=0x6493d0)
        at gmain.c:3201
            dispatch = 0x7fffecc060c0 <g_idle_dispatch>
            prev_source = 0x0
            was_in_call = 0
            user_data = 0x9247550
            callback = 0x7fffbaeee1d0 <e_meeting_time_selector_refresh_cb>
            cb_funcs = 0x7fffececf920 <g_source_callback_funcs>
            cb_data = 0x7fff9059c910
            need_destroy = <optimized out>
            source = 0x7fff904ee5d0
    ---Type <return> to continue, or q <return> to quit---
            current = 0x686790
            i = 19
    #4  0x00007fffecc094c9 in g_main_context_dispatch (context=context@entry=0x6493d0) at gmain.c:3854
    #5  0x00007fffecc09818 in g_main_context_iterate (context=0x6493d0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3927
            max_priority = 200
            timeout = 0
            some_ready = 1
            nfds = <optimized out>
            allocated_nfds = 4
            fds = 0x35327e0
    #6  0x00007fffecc09aea in g_main_loop_run (loop=0x3532dd0) at gmain.c:4123
            __FUNCTION__ = "g_main_loop_run"
    #7  0x00007fffee7764b5 in gtk_main () at gtkmain.c:1312
            loop = 0x3532dd0
    #8  0x0000000000403de1 in main ()


Version-Release number of selected component (if applicable):
evolution-3.22.6-4.el7.x86_64

How reproducible:
~100%

Steps to Reproduce:
1.heavy click on various calendar items (google cal)

Actual results:
crash after a while

Expected results:
no crash

Additional info:
Comment 1 Milan Crha 2017-04-12 12:45:27 UTC 
Thanks for a bug report. When testing, I realized that it doesn't even require any heavy clicking, the steps are:

a) have a meeting in the agenda (an event with attendees)
b) double-click it, which will open it in an editor
c) close the editor as soon as possible

Shortly after either the application crashes, or you see on console critical warnings like these:

> (evolution:21198): evolution-calendar-CRITICAL **: e_meeting_store_get_num_queries: assertion 'E_IS_MEETING_STORE (store)' failed
>
> (evolution:21198): GLib-GObject-WARNING **: invalid uninstantiatable type '(null)' in cast to 'EMeetingTimeSelectorItem'
>
> (evolution:21198): evolution-calendar-CRITICAL **: e_meeting_time_selector_item_set_normal_cursor: assertion 'IS_E_MEETING_TIME_SELECTOR_ITEM (mts_item)' failed

The underlying object is not freed, but it has nullified its private members, with which the code doesn't count.
Comment 3 Bohdan Milar 2017-06-19 12:40:39 UTC 
Tested manually on x86_64, ppc64le and aarch64 using evolution-3.22.6-10.el7

I used reproducer from C1. Neither crash nor critical warnings happened when I closed the Meeing window (repeated several times).
Comment 4 errata-xmlrpc 2017-08-01 12:27: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://access.redhat.com/errata/RHBA-2017:2066
Note You need to log in before you can comment on or make changes to this bug.