Good day,

No, it is not related to an extension. Even with all extensions disable, I have 
the syslog flooded with this bug:
(All extensions disabled, changing with Ctrl Alt Arrow).

Object .Gjs_ui_workspaceAnimation_MonitorGroup (0x5780a5299930), has been 
already disposed — impossible to access it. This might be caused by the object 
having been destroyed from C code using something such as destroy(), dispose(), 
or remove() vfuncs.
                                             == Stack trace for context 
0x578098a58ad0 ==
                                             #0   7ffd216c9a50 b   
resource:///org/gnome/shell/ui/workspaceAnimation.js:256 (3db5da405380 @ 246)
                                             #1   578098b4c160 i   
resource:///org/gnome/shell/ui/environment.js:206 (103e75660830 @ 827)
                                             #2   578098b4c0b8 i   
resource:///org/gnome/shell/ui/environment.js:290 (2bd464816600 @ 25)
                                             #3   578098b4bfd8 i   
resource:///org/gnome/shell/ui/workspaceAnimation.js:438 (3db5da4059c0 @ 849)
                                             #4   578098b4bf38 i   
resource:///org/gnome/shell/ui/windowManager.js:1638 (2bd4648e8e20 @ 134)
                                             #5   578098b4bea8 i   
resource:///org/gnome/shell/ui/windowManager.js:1853 (2bd4648e9380 @ 80)
                                             #6   578098b4bdc8 i   
resource:///org/gnome/shell/ui/windowManager.js:1830 (2bd4648e92e0 @ 1866)
                                             #7   578098b4bd38 i   
resource:///org/gnome/shell/ui/init.js:21 (3c6680c70c90 @ 48)

It happens whatever the method used to change the workspace.

If I disconnect HDMI monitor, there is no more these errors.

Thanks

** Changed in: ubuntu
       Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078431

Title:
  Object .Gjs_ui_workspaceAnimation_MonitorGroup, has been already
  disposed — impossible to access it. This might be caused by the object
  having been destroyed from C code using something such as destroy(),
  dispose(), or remove() vfuncs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2078431/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to