Journald flooded by gnome-shell stack trace messages

My journalctl is constantly flooded by these messages.

nov 08 16:07:06 myhost gnome-shell[2861]: Object St.Button (0x56121db9aef0), has been already deallocated ā€” 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.
nov 08 16:07:06 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:06 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:06 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:06 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:06 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:06 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:06 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:06 myhost gnome-shell[2861]: Object St.Button (0x56121dcb9ac0), has been already deallocated ā€” 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.
nov 08 16:07:06 myhost gnome-shell[2861]: Object St.Button (0x561220121a00), has been already deallocated ā€” 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.
nov 08 16:07:07 myhost gnome-shell[2861]: Object St.Button (0x56121d7c1270), has been already deallocated ā€” 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.
nov 08 16:07:07 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:07 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:07 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:07 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:07 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:07 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:07 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:07 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:07 myhost gnome-shell[2861]: Object St.Button (0x56121db9aef0), has been already deallocated ā€” 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.
nov 08 16:07:07 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:07 myhost gnome-shell[2861]: == Stack trace for context 0x561218dff160 ==
nov 08 16:07:07 myhost gnome-shell[2861]: #0   7ffd67c85370 b   resource:///org/gnome/shell/ui/workspace.js:695 (7ff1ed971160 @ 15)
nov 08 16:07:07 myhost gnome-shell[2861]: #1   7ffd67c85420 b   self-hosted:975 (7ff1eda2e160 @ 392)
nov 08 16:07:07 myhost gnome-shell[2861]: Object St.Button (0x56121dcb9ac0), has been already deallocated ā€” 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.
nov 08 16:07:07 myhost gnome-shell[2861]: Object St.Button (0x561220121a00), has been already deallocated ā€” 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.

Using iotop, systemd-journald is constantly writing to the disk, obviously.

What could be the origin of these messages?

Do you have any gnome-shell extensions installed?

1 Like

Yes, but if Iā€™m not wrong, I tried to disable them all.
The only way to stop such flood is to reboot the system.
But after some hours of work, the problem reappears.

I will need to look better at the logs an see the exact moment when the problem start.

To see what extensions are enabled, run:

gnome-tweaks