Bug 1724302

Summary: Include the Gnome GUI in RHEL 8 AARCH64
Product: Red Hat Enterprise Linux 8 Reporter: Joe Wright <jwright>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact: Gabriela Nečasová <gnecasov>
Priority: unspecified    
Version: 8.2CC: alanm, fmuellner, jadahl, jeischma, jkoten, jwboyer, klember, lmanasko, mclasen, mkolbas, msuchane, pasik, sbarcomb, tpelka, tpopela, vanhoof
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: 8.0Flags: gnecasov: needinfo? (fmuellner)
Hardware: aarch64   
OS: Linux   
Fixed In Version: Doc Type: Technology Preview
Doc Text:
.GNOME Desktop on ARM is available as a Technology Preview The GNOME Desktop is now available as a Technology Preview on the 64-bit ARM architecture. Users who require a graphical session to configure and manage their servers can now connect to a remote graphical session running GNOME Desktop using VNC.
Story Points: ---
Clone Of: 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:
Bug Depends On:    
Bug Blocks: 1746605, 1745633    

Description Joe Wright 2019-06-26 17:23:12 UTC
What is the nature and description of the request?  
- Customer would like Gnome included in the ARM release of RHEL 8
Why does the customer need this? (List the business requirements here)  
- graphical applications, including gedit, among others
How would the customer like to achieve this? (List the functional requirements here)  
- Gnome is available for ARM
Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
- RHEL 8

List any affected packages or components.  
- gnome-* gdm

Comment 19 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.