Bug 1744452

Summary: Enable wayland support for qxl-vga
Product: Red Hat Enterprise Linux 8 Reporter: Guo, Zhiyi <zhguo>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.1CC: ayadav, cfergeau, coli, hdegoede, jkoten, juzhang, kraxel, tpelka, vhumpa
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gdm-3.28.3-25.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1744527 (view as bug list) Environment:
Last Closed: 2020-04-28 16:09:38 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: 1739559, 1744527    

Description Guo, Zhiyi 2019-08-22 08:25:49 UTC
Description of problem:
Enable wayland support for qxl-vga

Version-Release number of selected component (if applicable):
gdm-3.28.3-22.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Currently wayland support has been disabled in gdm for qxl-vga device on rhel 8.1:
# rpm -qf /usr/lib/udev/rules.d/61-gdm.rules 
gdm-3.28.3-22.el8.x86_64

# cat /usr/lib/udev/rules.d/61-gdm.rules 
# disable Wayland on Cirrus chipsets
ATTR{vendor}=="0x1013", ATTR{device}=="0x00b8", ATTR{subsystem_vendor}=="0x1af4", ATTR{subsystem_device}=="0x1100", RUN+="/usr/libexec/gdm-disable-wayland"

# disable Wayland on Matrox chipsets
ATTR{vendor}=="0x102b", ATTR{device}=="0x0522", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0524", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0530", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0532", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0533", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0534", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0536", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x102b", ATTR{device}=="0x0538", RUN+="/usr/libexec/gdm-disable-wayland"

# disable Wayland on aspeed chipsets
ATTR{vendor}=="0x1a03", ATTR{device}=="0x2010", RUN+="/usr/libexec/gdm-disable-wayland"
ATTR{vendor}=="0x1a03", ATTR{device}=="0x2000", RUN+="/usr/libexec/gdm-disable-wayland"

# disable Wayland on legacy QXL virtual machines
ATTR{vendor}=="0x1b36", ATTR{device}=="0x0100", RUN+="/usr/libexec/gdm-disable-wayland"

# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/libexec/gdm-disable-wayland"

# disable Wayland on hybrid graphics setups for now
SUBSYSTEM=="drm", KERNEL=="card[1-9]*", RUN+="/usr/libexec/gdm-disable-wayland"

 
Actual results:
wayland support for qxl-vga has been disabled in gdm

Expected results:
wayland support for qxl-vga is enabled

Additional info:

Comment 1 Gerd Hoffmann 2019-08-22 10:34:21 UTC
Plan: enable early in the 8.2 cycle to give virt QE enough time for a full desktop test run with wayland enabled.

Comment 2 Ray Strode [halfline] 2019-08-23 14:37:13 UTC
have the multihead issues been worked out?

Comment 3 Gerd Hoffmann 2019-08-26 07:21:34 UTC
(In reply to Ray Strode [halfline] from comment #2)
> have the multihead issues been worked out?

Yes, it's sorted and should work fine with the 8.1 kernel.

Virt QE did most 8.1 testing with Xorg not wayland though,
thats why we want flip the switch early in 8.2 ...

Comment 4 Ray Strode [halfline] 2019-12-06 15:30:49 UTC
i'm down for toggling this provided, QE thinks we still have enough runway.  I think we probably do?

Comment 8 Vitezslav Humpa 2020-01-14 09:09:55 UTC
Verified with gdm-3.28.3-28.el8.x86_64, with wayland enabled both greeter and gnome session work as expected. Verified.

Comment 10 errata-xmlrpc 2020-04-28 16:09:38 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/RHSA-2020:1766