Marco Trevisan

What application where you running? Some lines there seems to be cut, do you have a full log?

Please report the content of your `journalctl /usr/bin/gnome-shell`

@JumperLuko such extension is only supporting legacy tray icons, which are quite simpler for the shell compared to the appindicators. Mostly because appindicators require quite a lot of dbus chatting...

Some improvements are included in #402 and #405, all the rest of operations are now async, so most we could do should be handled now. Maybe delaying the whole extension...

I've been checking this again, and indeed we've some code that, even if that's fully async, it causes lagging. While there's stuff (like the menu-items initialization) that is basically impossible...

Ok, I've prepared #417 that seems to improve the situation, I've also further ideas, but let's see first with this.

The problem is being able to figure out the application... I've added now some code to get the command line for an indicator, that may be used, but it's definitely...

You can just use classic meson mode... `meson src-path build-path -Dprefix=/usr && ninja -C build-path install`. The local-install is only meant for people installing from git, same for zip-file. If...

I've the feeling that legacy tray icon is causing this not to work properly for you... Can you comment out `TrayIconsManager.TrayIconsManager.initialize();` (and maybe TrayIconsManager.TrayIconsManager.destroy();` in `extension.js` and see if that...

Do you have libappindicator installed or apps are using legacy tray-icons?