GNOME Bugzilla – Bug 699610
Extensions inactive after system suspend (App & Workspace indicators)
Last modified: 2021-07-05 14:09:31 UTC
Created attachment 243230 [details] Tweak tool Extentions card Starting up after suspend delivers extentions inactive. Logging out & back in does not help. Only restart does.
It is possible that the extension doesn't properly disable, and thus enters and error state before the suspend. Can you provide the contents of ~/.cache/gdm/session.log / journalctl?
No "gdm" under "~/.cache", neither can I locate "journalctl". I am using lightdm, not gdm, if that is relevant. Is there anything else I can do? (In reply to comment #1) > It is possible that the extension doesn't properly disable, and thus enters and > error state before the suspend. > Can you provide the contents of ~/.cache/gdm/session.log / journalctl?
I believe that lightdm stores the session stderr in ~/.xsession-errors
Created attachment 243289 [details] ~.xsession-errors added
I do not know how, but the problem seams to -in a strange way- affect Unity. If after recreating the problem you log out of Gnome & log into Unity, then Unity starts to behave erraticaly. To such an extend, that it is better to work under Gnome, despite the problems! It is the second time this happens. first time 13.04 was still in beta. Say it did not count. Now though?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab-test.gnome.org/fmuellner/gnome-shell-extensions/issues/102.
Sorry for the noise, I "found" a bug in the migration script: https://gitlab.gnome.org/External/bugzilla-to-gitlab-migrator/issues/2
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.