Bug 1762048

Summary: gnome activities panel and gnome search broken by upgrade to RHEL 7.8 Beta
Product: Red Hat Enterprise Linux 7 Reporter: Lenny Szubowicz <lszubowi>
Component: gnome (assorted, untriaged)Assignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.8CC: csoriano, debarshir, dking, fmuellner, mboisver, mclasen, otaylor, skpaul, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 07:22:59 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
gnome desktop after Super key pressed none

Description Lenny Szubowicz 2019-10-16 00:29:47 UTC
Created attachment 1626217 [details]
gnome desktop after Super key pressed

Description of problem:

Immediately after doing a yum update from RHEL 7.7 GA to RHEL 7.8 Beta and rebooting I noticed that the gnome activities panel no longer works.

Pressing the Super key causes the windows to get arranged on the desktop, but the activities panel is not displayed on the left and the text search entry box is not displayed. A screen shot is attached.

To test if this was somehow related to my personal account settings, I created a new test user account with no customization. The test user account exhibits the same behavior. Yet I also know that the problem is not universal because I have a workstation that is running RHEL 7.8 nightly builds and the gnome activities panel does appear to function correctly on that workstation.

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

RHEL 7.8 Beta, Gnome 3.28.2

Comment 2 Tomas Pelka 2019-10-16 07:22:59 UTC
This is actually because of new "more classic" classic session.

See https://bugzilla.redhat.com/show_bug.cgi?id=1720286

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

Comment 3 Michael Boisvert 2019-10-16 13:23:31 UTC
Lenny, to re-enable the overview follow these steps:

1. Modify the following file as root: /usr/share/gnome-shell/modes/classic.json
2. Change "hasOverview": false to "hasOverview": true
3. Restart the session.

Comment 4 Lenny Szubowicz 2019-10-17 13:51:46 UTC
(In reply to Michael Boisvert from comment #3)
> Lenny, to re-enable the overview follow these steps:
> 
> 1. Modify the following file as root:
> /usr/share/gnome-shell/modes/classic.json
> 2. Change "hasOverview": false to "hasOverview": true
> 3. Restart the session.

Thank you for the above, which does work for me.

Thanks also for the reference to BZ 1720286. I didn't realize that this was tied to GNOME Classic. I think I'll give the newer GNOME non-classic session UI a try.

                                 -Lenny.

Comment 5 Michael Boisvert 2019-10-17 17:19:30 UTC
(In reply to Lenny Szubowicz from comment #4)
> (In reply to Michael Boisvert from comment #3)
> > Lenny, to re-enable the overview follow these steps:
> > 
> > 1. Modify the following file as root:
> > /usr/share/gnome-shell/modes/classic.json
> > 2. Change "hasOverview": false to "hasOverview": true
> > 3. Restart the session.
> 
> Thank you for the above, which does work for me.
> 
> Thanks also for the reference to BZ 1720286. I didn't realize that this was
> tied to GNOME Classic. I think I'll give the newer GNOME non-classic session
> UI a try.
> 
>                                  -Lenny.

Ah, I see. Some of our customers voiced a desire for a simplified classic session, so we answered the call.

Comment 6 Skip Paul 2020-04-01 15:09:04 UTC
(In reply to Michael Boisvert from comment #3)
> Lenny, to re-enable the overview follow these steps:
> 
> 1. Modify the following file as root:
> /usr/share/gnome-shell/modes/classic.json
> 2. Change "hasOverview": false to "hasOverview": true
> 3. Restart the session.

worked for me.  Thanks so much!