Gnome Shell Freezes when Chrome fullscreen is toggled

[Chris Andrew]

I can't put Chrome on fullscreen because it freezes the system. Actually the system just seems to be frozen, but I can't use it because it only show a static blueish screen (as the hue were changed to blue) from Chrome on top of everything.

The problem doesn't occur when using Opera.

I am able to resume normal use after restarting Gnome Shell (inputting r after pressing Ctrl+F2).

System info:

- Ubuntu 17.04 64-bit (dev branch)
- GNOME Shell 3.24.0
- NVIDIA 378.13
- Google Chrome 58.0.3029.54 beta

More details: https://askubuntu.com/questions/903272/ubuntu-gnome-freezes-when-i-switch-chrome-to-fullscreen

[Jeremy Bícha (jbicha)]

Does this also happen if you use chromium-browser instead of Chrome?

Does it happen when you make any other app full screen?

[Chris Andrew (chrisandrew.cl)]

No, I've just checked: toggling full screen on Chromium does not trigger this behavior.

For now I've only experienced this with Chrome (stable/beta).

As another user pointed out, it seems to also occur toggling full screen in Shotwell.

After disabling the "Hide Top Bar" the full screen works again, but there are still a hue change to bluish during the full screen toggle (this also occur in Chromium).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel Sloof (danslo)]

I can also confirm this issue. Works when disabling 'Hide top bar'.

Upstream bug report:
https://github.com/mlutfy/hidetopbar/issues/132

[Daniel Sloof (danslo)]

Some further info:
I doubt this bug has to do with 'Hide top bar'. Disabling this extension does in fact solve the problem on my main monitor. But my secondary monitor (which gnome3 by default doesn't show a top bar for) does the exact same thing regardless of the extension.

[Herbert Spaul (herbert.spaul)]

To my understanding the bug is caused by the animations from gnome-shell ui. I would guess the connection to the hide top bar extension has to do with the extra space that becomes available that causes some animation to run into a exception or something because it does not expect the top space to be available.
As I have pointed out at askubuntu I was able to fix the freeze when going back from fullscreen by simply commenting out the animation in the hide top bar extension source.
Now the freeze when going full screen has a different cause. The animation is built in the PanelBox of gnome-shell.

The relevant code that causes the freeze in the hide top bar extension is simply removing and readding the PanelBox:

https://github.com/mlutfy/hidetopbar/blob/master/panelVisibilityManager.js#L42
{{{
Main.layoutManager.removeChrome(PanelBox);
        Main.layoutManager.addChrome(PanelBox, {
            affectsStruts: false,
            trackFullscreen: true
});
}}}

Now, if you change the "affectsStruts" to true (the default I guess), the freeze will not occur but the top bar will no longer hide.

Maybe this points someone with more insight into the right direction.

[gsmetal (gsmetal)]

>But my secondary monitor (which gnome3 by default doesn't show a top bar for) does the exact same thing regardless of the extension.

Same here! I don't use 'Hide top bar' extension and chrome freezes and bluish on fullscreen on secondary monitor without panel. But it works well on primary monitor with panel.

[Daniel Sloof (danslo)]

In addition, this only happens when Chrome is already filling the entire screen. If you drag the Chrome window to be smaller, and then go fullscreen (youtube video for example), it'll work without issue.

[Daniel Sloof (danslo)]

So for completeness, steps to reproduce:

1) Either
   a) Install 'Hide top bar' extension and maximize chrome on main monitor, or;
   b) Hook up a secondary monitor and maximize chrome on secondary monitor

2) Trigger a full-screen animation (press F11, press fullscreen on a youtube video, etc).

[Stefan L (stefan-loewen)]

I am also affected by this bug.

System info:
- Ubuntu GNOME 17.04
- gnome-shell 3.24.0
- Google Chrome 58.0.3029.81 (64-bit)
- Intel Graphics (driver=i915)

Details:
- The freeze only occurs on screens without a top-panel and only when Chrome is maximized when activating fullscreen.
- Disabling hardware acceleration in Chrome does not prevent the freeze.
- The freeze can be prevented by unmaximizing Chrome beforehand, by using the main screen (which has a top bar) or by using the "Multi Monitors Add-On" extension [1] to add a top bar to each screen.
    - With these workarounds there still is a short flash of inverted colors when activating fullscreen. This flash does not appear when using Firefox.

[1] https://extensions.gnome.org/extension/921/multi-monitors-add-on/

[Policratus (policratus)]

I'm having the same issue described. Every time I try to put Google Chrome on full screen, Gnome 3.24.0 completely freezes and it's confirmed that is Hide Top Bar extension is causing this.

[Herbert Spaul (herbert.spaul)]

The freeze problem has been solved for me with one of the updates (openSUSE Tumbleweed latest):
 Gnome 3.24.1
 Kernel 4.10.12-1
 Intel Graphics (driver=i915)

[Daniel Sloof (danslo)]

Looks like us Ubuntu users will have to have some more patience. Even the GNOME3 staging PPA does not include gnome-shell/mutter 3.24.1 yet:
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging?field.series_filter=zesty

Just for reference, this bug exists in <=3.24.0.

[Jeremy Bícha (jbicha)]

Daniel, that's because the gnome-shell/mutter update is going through the Stable Release Update process. I think the update will be released this week.

https://people.canonical.com/~ubuntu-archive/pending-sru.html

[Jeremy Bícha (jbicha)]

The gnome-shell/mutter update is being pushed out today.

[Chris Andrew (chrisandrew.cl)]

I've just upgraded to gnome-shell 3.24.1, but sadly the problem still occurs...

[Charles Masucci (chuckmasucci)]

Seems to be fixed for me. Going fullscreen on a web video on my 2nd monitor no longer glitches out and works as expected.

[Daniel Sloof (danslo)]

Can confirm, after a dist-upgrade everything works fine again!

[Chris Andrew (chrisandrew.cl)]

It seems that after also updating mutter to 3.24.1 the issue is solved.

Great work! Thank you!

[elhassen (l2b)]

The pkg genome shell is not installed in my computer even though i experience the problem