Bug 1719279

Summary: JS ERROR: TypeError: this._workspacesViews[i] is undefined
Product: Red Hat Enterprise Linux 8 Reporter: Martin Krajnak <mkrajnak>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: jadahl, jan.public, jkoten, modehnal, tpelka
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-shell-3.32.2-6.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:14:05 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: 1678350    

Description Martin Krajnak 2019-06-11 12:04:09 UTC
Description of problem:
I have 3 monitor setup, when I toggle the gnome-shell overview I always get the following error in journal.

Jun 11 14:02:33 localhost.localdomain gnome-shell[19145]: JS ERROR: TypeError: this._workspacesViews[i] is undefined
                                                          _updateWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:714:13
                                                          setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:704:9
                                                          setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/viewSelector.js:293:9
                                                          _updateWorkspacesGeometry@resource:///org/gnome/shell/ui/overviewControls.js:456:9
                                                          vfunc_allocate@resource:///org/gnome/shell/ui/overviewControls.js:389:9
                                                          _updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:637:13
                                                          show@resource:///org/gnome/shell/ui/workspacesView.js:557:9
                                                          show@resource:///org/gnome/shell/ui/viewSelector.js:268:9
                                                          _animateVisible@resource:///org/gnome/shell/ui/overview.js:527:9
                                                          show@resource:///org/gnome/shell/ui/overview.js:513:9
                                                          toggle@resource:///org/gnome/shell/ui/overview.js:636:13
                                                          _initializeUI/<@resource:///org/gnome/shell/ui/main.js:190:13


Version-Release number of selected component (if applicable):
gnome-shell-3.32.2-2.el8.x86_64

How reproducible:
always


This is happening both via keyboard and top left corner.

Comment 3 Martin Krajnak 2019-06-11 12:50:48 UTC
This is also being mentioned upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1065

Comment 4 Martin Krajnak 2019-06-11 13:27:09 UTC
Also, the error goes away when I switch to built-in laptop monitor only. (Detached from dock station)

Comment 5 Tomas Pelka 2019-07-12 12:17:13 UTC
*** Bug 1729487 has been marked as a duplicate of this bug. ***

Comment 6 Florian Müllner 2019-07-12 16:31:12 UTC
It is not entirely clear what is going on (code that has existed for years somehow now triggers a spurious allocation call that results in those warnings), but the following upstream commit silences them:

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/625

Comment 8 Martin Krajnak 2019-07-15 11:12:11 UTC
No more errors with: gnome-shell-3.32.2-6.el8.x86_64

Comment 10 errata-xmlrpc 2019-11-05 22:14:05 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-2019:3553