JS ERROR: TypeError: workspace is undefined [in _getSpacing]

Bug #2037538 reported by Dan Ringhiser
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Shell
New
Unknown
gnome-shell (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 22.04.3 LTS

gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x555e5db5c350] is on because it needs an allocation.
gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x555e5fe0d310] is on because it needs an allocation.
gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x555e5fe106d0] is on because it needs an allocation.
gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x555e5db5c350] is on because it needs an allocation.
gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x555e5fe0d310] is on because it needs an allocation.
gnome-shell[3218]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x555e5fe106d0] is on because it needs an allocation.
gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018

Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change.
JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60
gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[3218]: == Stack trace for context 0x555e5d657170 ==
gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10)
gnome-shell[3218]: == Stack trace for context 0x555e5d657170 ==
gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36)
gnome-shell[3218]: == Stack trace for context 0x555e5d657170 ==
gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77)
gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 27 07:19:09 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-15 (42 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.9-0ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dan Ringhiser (ringhidb) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also check to see if the freeze is related to switching workspaces (bug 2000644).

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also try deleting locally installed extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then reboot.

Revision history for this message
Dan Ringhiser (ringhidb) wrote :

Daniel,

Attached are the files from the two journal commands.

I have 2 .crash files in /var/crash:
_usr_bin_evolution.1000.crash
_usr_bin_nm-connection-editor.1000.crash

Is it worth doing the ubuntu-bug command on any/all of those?
I do see 50 error reports at https://errors.ubuntu.com/user/ID. Clicking any of the "received" links says "Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access."

Is it safe to post my whoopsie ID here for you to see the list?

I do not have the symptoms of the workspace dots staying active as described in #2000644. I have had my system set to fixed, 10 workspaces since installation.

There are no files in ~/.local/share/gnome-shell/extensions/

Revision history for this message
Dan Ringhiser (ringhidb) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Are any of the reports at https://errors.ubuntu.com/user/ID from gnome-shell? That's the important one if the screen has frozen but the cursor keeps moving.

Revision history for this message
Dan Ringhiser (ringhidb) wrote :

No, only one that even has gnome in the name is network-manager-gnome.

I haven't had any freezing issue the last couple days, but will run and post the journal commands next time it happens.

Still getting JS Error workspace is undefined and stack traces every time I exit "activities" if my mouse cursor is hovering over an application window on a monitor other than my primary display, and can't' update stage views actor any time I resize any application on any monitor, with the exception of using the application controls to maximize (not full screen).

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
summary: - GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but
- can't click.
+ JS ERROR: TypeError: workspace is undefined [in _getSpacing]
Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed
Changed in gnome-shell:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.