Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2052940

Summary: mutter as a Wayland compositor aborts on hybrid gfx with the NVIDIA proprietary driver
Product: Red Hat Enterprise Linux 9 Reporter: Olivier Fourdan <ofourdan>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED WONTFIX QA Contact: Peter Kopec <pekopec>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: fmuellner, rstrode, tpelka
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-10 07:28:33 UTC Type: Bug
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
gdb backtrace of the abort none

Description Olivier Fourdan 2022-02-10 10:09:05 UTC
Created attachment 1860308 [details]
gdb backtrace of the abort

Description of problem:

On a system with hybrid graphics, using the NVIDIA proprietary driver for the discrete GPU, attaching an external display wired to the discrete GPU will cause GNOME Shell as a Wayland compositor to abort.

Version-Release number of selected component (if applicable):

mutter-40.8-2.el9.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install the NVIDIA proprietary driver on a hybrid graphcs laptop
2. Start a GNOME Shell Wayland session
3. Connect an external display

Actual results:

The user session is terminated as mutter abort.

Expected results:

The session survives.

Additional info:

mutter abort because it fails to allocate the onscreen framebuffer, which in mutter from GNOME 40 is a g_error(), hence the abort.

See attachment for the backtrace.

Also worth noting that mutter from GNOME 41 would not abort in this case, but the external display won't work, but at least the user session is not killed.

Comment 2 Jonas Ådahl 2023-07-11 09:32:16 UTC
> Failed to allocate onscreen framebuffer: Failed to create gbm_surface: Timer expired

So as you say, we can change the abort() to broken behavior. Not sure this should be prioritized since Wayland is disabled for hybrid graphics setups.

Comment 3 RHEL Program Management 2023-08-10 07:28:33 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.