Marco Trevisan

Please, try latest master and let me know if this has been addressed.

Mh, weird... Could you maybe run gnome-shell with `G_MESSAGES_DEBUG=all` env set and attach the `journalctl /usr/bin/gnome-shell -b0` result when virt-manager causes this? Also not familiar with that, is it virtual-manager...

Oh, so it's the menu addition that causes problems... Maybe having a dump of that dbus-menu could be useful to be able to reproduce the issue. However, if it's not...

Will try to replicate this again, but it's a bit hard so far.. I need a way to easily populate my virt-manager with lots of images it seems :)

Could you please check if applying this improves the things? It should be just enough to change it to the files you've installed in `/usr/share/gnome-shell/extensions/` or in `~/.local/share/gnome-shell/extensions` ```diff diff...

Mh, try with this? ```diff diff --git a/appIndicator.js b/appIndicator.js index 46c2d41..5808ed8 100644 --- a/appIndicator.js +++ b/appIndicator.js @@ -179,6 +179,7 @@ var AppIndicator = class AppIndicators_AppIndicator { } _onProxySignal(_proxy, _sender, signal,...

Mh, still trying to figure out, as I can't get that in my-stress-test indicator... However, a part the errors, the CPU usage is still high, right?

I'd look also in virt-manager itself though, as for what I see it disposes and recreates the same indicator multiple times, and this doesn't look correct.

It may be related to the findings of this (very interesting) thread from @mildsunrise in https://twitter.com/mild_sunrise/status/1458739604098621443

Cleaned up the long lines and squashed the commits, we should be ready to go! Thanks