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 1897045 - gnome-shell-3.28.3-31.el7 Causes Gnome Session to Fail to Start
Summary: gnome-shell-3.28.3-31.el7 Causes Gnome Session to Fail to Start
Keywords:
Status: CLOSED DUPLICATE of bug 1897063
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.9
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-12 07:42 UTC by Johnray Fuller
Modified: 2020-11-12 15:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-12 15:04:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
journal (3.57 KB, text/plain)
2020-11-12 08:25 UTC, Michal Odehnal
no flags Details

Description Johnray Fuller 2020-11-12 07:42:10 UTC
Description of problem:

I upgraded my RHEL 7.9 packages today and when gnome-shell was updated from gnome-shell-3.28.3-30.el7.x86_64 to version gnome-shell-3.28.3-31.el7.x86_64, I could no longer get Gnome to start at all.

This was even true for a freshly created user.

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

gnome-shell-3.28.3-31.el7.x86_64

How reproducible:

Always

Steps to Reproduce:
1. With a system that is using gnome-shell-3.28.3-30.el7.x86_64 or earlier, validate that gnome works.
2. dnf or yum upgrade to gnome-shell-3.28.3-31.el7.x86_64.
3. Gnome will either not fully start (no desktop picture or anything) or if it does start, no top bar or window boxes will appear, but the "desktop" files may appear if you have any files on the desktop.

Actual results:

gnome-shell fails to initialize.

Expected results:

A normal gnome environment.

Additional info:

Comment 2 Tomas Pelka 2020-11-12 07:50:35 UTC
Would it be possible to attache some logs when gnome-shell failed?

Comment 3 bugreports2005 2020-11-12 07:54:54 UTC
We noticed the same. Gnome Classic works, as does rolling back RHBA-2020:5048.

Comment 4 Michal Odehnal 2020-11-12 08:25:59 UTC
Created attachment 1728649 [details]
journal

These are the journal entries upon start.

Comment 5 Tomas Pelka 2020-11-12 08:31:15 UTC
(In reply to Michal Odehnal from comment #4)
> Created attachment 1728649 [details]
> journal
> 
> These are the journal entries upon start.

As Michal pointed out seems like dup of https://bugzilla.redhat.com/show_bug.cgi?id=1897063

Comment 6 Ray Strode [halfline] 2020-11-12 15:04:47 UTC

*** This bug has been marked as a duplicate of bug 1897063 ***


Note You need to log in before you can comment on or make changes to this bug.