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.

With the latest 7.2 packages, mutter sometimes crashes when plugging in monitors:

Program received signal SIGSEGV, Segmentation fault.
meta_monitor_manager_xrandr_read_current (manager=manager@entry=0x17332a0) at backends/x11/meta-monitor-manager-xrandr.c:612
612		  meta_output->preferred_mode = meta_output->modes[0];
(gdb) bt
#0  meta_monitor_manager_xrandr_read_current (manager=manager@entry=0x17332a0) at backends/x11/meta-monitor-manager-xrandr.c:612
#1  0x00007fe870f2dc73 in meta_monitor_manager_xrandr_handle_xevent (manager_xrandr=0x17332a0, event=0x7ffcbf492c10)
    at backends/x11/meta-monitor-manager-xrandr.c:1157
#2  0x00007fe870f2b483 in x_event_source_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>)
    at backends/x11/meta-backend-x11.c:212
#3  0x00007fe86cb3879a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#4  0x00007fe86cb38ae8 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0
#5  0x00007fe86cb38dba in g_main_loop_run () from /lib64/libglib-2.0.so.0
#6  0x00007fe870f52bc8 in meta_run () at core/main.c:473
#7  0x0000000000402455 in main ()


There are two related bugs filed upstream about this:
https://bugzilla.gnome.org/show_bug.cgi?id=756796
https://bugzilla.gnome.org/show_bug.cgi?id=756660

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-2216.html