** Description changed:
We're getting this stack-trace.
This is because the dock may be still tracked when destroyed
(gnome-shell:4085779): GNOME Shell-CRITICAL **: 16:41:06.538: Invalid
work id 3: Error: Invalid work id 3
Stack trace:
queueDeferredWork@resource:///org/gnome/shell/ui/main.js:994:18
_queueRedisplay@resource:///org/gnome/shell/ui/dash.js:486:14
_queueRedisplay@file:///data/GNOME/JHBUILD_HOME/.local/share/gnome-shell/extensions/[email protected]/dash.js:354:52
_enable/</<@file:///data/GNOME/JHBUILD_HOME/.local/share/gnome-shell/extensions/[email protected]/docking.js:1636:63
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:277:14
+
+ ---
+ External link: https://warthogs.atlassian.net/browse/UDENG-10125
** Tags added: udeng-10125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2148339
Title:
DashToDock: On screen / unlock changes it may try to access to
destroyed dock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2148339/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
