Bug 1579257
Summary: | System boots to blank screen when Xinerama enabled with nvidia/nouveau driver | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Divya <dbasant> | ||||||
Component: | mutter | Assignee: | Jonas Ådahl <jadahl> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
Severity: | medium | Docs Contact: | Tomas Capek <tcapek> | ||||||
Priority: | high | ||||||||
Version: | 7.5 | CC: | alanm, dbasant, fmuellner, jadahl, mboisver, mclasen, mkolbas, tpelka, vchoudha, vpakolu | ||||||
Target Milestone: | rc | Keywords: | OtherQA, Regression, ZStream | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | mutter-3.28.3-9.el7 | Doc Type: | Bug Fix | ||||||
Doc Text: |
.System no longer boots to a blank screen when Xinerama is enabled
When the Xinerama extension was enabled in `/etc/X11/xorg.conf` on a system using the nvidia or nouveau driver, the RANDR X extension got disabled. Consequently, login screen failed to start upon boot due to the RANDR X extension being disabled. This bug has been fixed and the login screen now starts properly even with Xinerama enabled.
|
Story Points: | --- | ||||||
Clone Of: | |||||||||
: | 1714959 (view as bug list) | Environment: | |||||||
Last Closed: | 2019-08-06 12:37:16 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: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1714959 | ||||||||
Attachments: |
|
Description
Divya
2018-05-17 09:15:30 UTC
I missed an important piece of information here, i.e With LightDM all worked as expected with Xinerama enabled. could it be, that your monitors.xml file is not setup correctly to end up having your login screen on the wrong display ? Once you logged into your gdm session, configure your monitor setup and copy the monitors.xml file : cp ~/.config/monitors.xml /var/lib/gdm/.config/ I had the same problem and this fixed it. I have a scratch build for 7.5 that tries to somewhat handle the lack of RANDR support in the X server by assuming the whole screen is a single dummy monitor. I can start GNOME Shell with this on a dual monitor setup and it'll work as if all connected monitors were just a single one. Naturally monitor configuration does no longer work with this. Is this something that would work for the customer? The scratch build is available here: http://brew-task-repos.usersys.redhat.com/repos/scratch/jadahl/mutter/3.26.2/18.el7_5/ A scratch build for 7.6 available here: http://brew-task-repos.usersys.redhat.com/repos/scratch/jadahl/mutter/3.28.3/5.el7/ Created attachment 1490887 [details]
Mutter patches for rhel 7.5
Created attachment 1490888 [details]
Mutter patches for rhel 7.6
Here is another scratch build for 7.5. I have tested this on a system with nvidia, with two (separate) monitors using a config similar to the ones in the sosreports. The previous version did indeed crash when using the nvidia driver, but not in the driver as reported reported above, so I cannot verify the same crash is fixed. The new coredump tarball also seems to not have contained any mutter or gnome-shell backtraces, so if the new scratch build still causes a crash, it'd be very useful to have the whole backtrace leading up to the crash. Here is the new scratch build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=18723238 Feedback from the customer with latest scratch build ******* THAT WORKED!!!!!! I did see some core dumps. I didn't always get them when I booted up but I did get a few. They are attached. I tested with Xinerama disabled and enabled, both with 1 screen attached and 2 screens attached. It worked as desired in all 4 cases, but most importantly it worked in the desired case of 2 screens attached with Xinerama enabled. ******* In the attached coredumps, I see, two of them belongs to gnome-shell. Great, thanks a lot for testing! 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-2019:2044 |