Describe the bug
This happens since a recent update of the extension from extensions.gnome.org
Sep 18 10:17:02 gnome-shell[2222]: Object St.Label (0x5651f9bad080), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 18 10:17:02 gnome-shell[2222]: == Stack trace for context 0x5651f8252190 ==
Sep 18 10:17:02 gnome-shell[2222]: #0 7fff02e9b120 b /home/poncho/.local/share/gnome-shell/extensions/ShutdownTimer@deminder/lib/MenuItem.js:272 (233ebb681600 @ 393)
Sep 18 10:17:02 gnome-shell[2222]: #1 7fff02e9b830 b self-hosted:1178 (3b63c44b0a10 @ 398)
Sep 18 10:17:02 gnome-shell[2222]: #2 5651fab19018 i /home/poncho/.local/share/gnome-shell/extensions/ShutdownTimer@deminder/lib/Convenience.js:128 (233ebb67cba0 @ 77)
Sep 18 10:17:02 gnome-shell[2222]: clutter_text_get_editable: assertion 'CLUTTER_IS_TEXT (self)' failed
Sep 18 10:17:02 gnome-shell[2222]: clutter_text_get_text: assertion 'CLUTTER_IS_TEXT (self)' failed
Sep 18 10:17:02 gnome-shell[2222]: clutter_text_set_text: assertion 'CLUTTER_IS_TEXT (self)' failed
Does the bug only occur in with an additional gnome shell extension enabled or with only the "Shutdown Timer" extension enabled ?
With only the "Shutdown Timer" extension enabled
To Reproduce
Enable the extension, lock and unlock the screen
Describe the bug This happens since a recent update of the extension from extensions.gnome.org
To Reproduce Enable the extension, lock and unlock the screen
Expected behavior No errors spamming the journal
System