Activity

1. LuisPicoES commented on Sep 13, 2026

   

   LuisPicoES

   on Sep 13, 2026

   More actions

   I can reproduce this on Ubuntu 24.04 with GNOME Shell 46.0 on X11.

   Environment:

   • Ubuntu 24.04
   • GNOME Shell 46
   • X11
   • ubuntu-appindicators@ubuntu.com 58-1ubuntu24.04.1
   • Docker Desktop 4.90.0

   The AppIndicator extension is enabled and the StatusNotifierWatcher is registered normally. Docker does create org.freedesktop.StatusNotifierItem-<PID>-1, but it does not appear in RegisteredStatusNotifierItems.

   The symptom is exactly as described here: no Docker tray icon, with the three-dot placeholder appearing briefly on some launches.

   I can also reproduce the org.freedesktop.DBus.Error.Failed: error occurred in Get behaviour when accessing /StatusNotifierItem through the unique bus name, while the same property access through the well-known name succeeds.

   Interestingly, ChatGPT's Electron-based tray icon works normally on the same system, so the AppIndicator host itself appears to be functioning.

   This appears to be a useful reproduction on Ubuntu 24.04/GNOME 46/X11 in addition to the newer Ubuntu 26.04/Wayland reports.
2. 0Ky commented on Sep 14, 2026

   

   0Ky

   on Sep 14, 2026

   Last edited by 0Ky

   More actions

   Related to issue #661. It looks like an upstream problem that was suppose to be fixed in electron/electron#53215. Docker Desktop Version 4.91.0 (239619) is bundled with Electron 43.4.0, the fix is in Electron v43.5.0.
3. LuisPicoES commented on Sep 22, 2026

   

   LuisPicoES

   on Sep 22, 2026

   More actions

   Updated to Docker Desktop v4.92.0. Issue is still there, so the underlying issue has not been resolved.
4. 0Ky commented on Sep 22, 2026

   

   0Ky

   on Sep 22, 2026

   More actions

   @LuisPicoES The fix will come when Docker decides to update the bundled Electron to version ≥ 43.5.0. The updated Docker Desktop v4.92.0 is still shipping with Chrome/150.0.7871.224 Electron/43.4.0, an old version of Electron that was released in 12 August, 2026.
5. LuisPicoES commented on Sep 23, 2026

   

   LuisPicoES

   on Sep 23, 2026

   More actions

   @0Ky Yes, I guess that the fix will come when the developers bump the bundled Electron/Chrome. Interesting what they say here. I have been reading about this topic because it affects several apps (Docker, Obsidian, Goose, LM Studio(?)<---not entirely sure about this one, it's been broken for a long time), but not others (AnyDesk, Claude, ChatGPT or Livepatch).

   • Electron <43.3.0 (Claude Desktop, likely ChatGPT if it's on an older build) → unaffected, predates the bug
   • Electron 43.3.0–43.4.x (Docker Desktop, Obsidian, likely Goose and LM Studio) → broken, caught in the regression window
   • Electron ≥43.5.0 or ≥44.1.0 → fixed again, once apps update past it
   • Non-Electron apps entirely (AnyDesk/Qt, LivePatch/native GTK) → never in scope at all
6. haisher commented on Sep 30, 2026

   

   haisher

   on Sep 30, 2026

   More actions

   Hit this too, on Debian 13 (GNOME Shell 48.7, gnome-shell-extension-appindicator 59-4, Docker Desktop 4.93.0). Tray shows the three dots for a second, then the icon disappears. gnome-shell logs error occurred in Get from appIndicator.js.

   I dug through the extension and there are actually two places where it trips over Electron, not one:

   1. RegisterStatusNotifierItem resolves the well-known name to a unique name, and every property read after that fails. This is the one already described above.
   2. Even with that fixed, the icon still ended up hidden. The proxy's initial GetAll also goes to the unique name owner (that's how GDBusProxy works for well-known names), so it fails silently. The extension sets Status to PASSIVE before init and relies on that GetAll to overwrite it. It never does, so the item is "ready" but permanently PASSIVE. Id and Menu come through because they get refreshed separately via the well-known name.

   Quick check that it's the unique-name thing: Get on org.freedesktop.StatusNotifierItem-<pid>-1 works, same call on the :1.xxx name fails.

   Workaround that works for me (icon and menu both fine). Copy the extension to ~/.local/share/gnome-shell/extensions/ so you don't touch the packaged one, then patch two files.

   statusNotifierWatcher.js:

            } else if (service.match(Util.BUS_ADDRESS_REGEX)) {
   -            try {
   -                busName = await Util.getUniqueBusName(invocation.get_connection(),
   -                    service, this._cancellable);
   -            } catch (e) {
   -                logError(e);
   -            }
   +            busName = service;
                objPath = DEFAULT_ITEM_OBJECT_PATH;

   appIndicator.js, in _setupProxy():

                await this._proxy.initAsync(cancellable);
   +            // reload everything via the well-known name, the proxy's own
   +            // GetAll goes to the unique name and fails
   +            try {
   +                await this._proxy.refreshAllProperties();
   +            } catch (e) {
   +                if (e.matches(Gio.IOErrorEnum, Gio.IOErrorEnum.CANCELLED))
   +                    throw e;
   +            }
                this._checkIfReady();

   Then log out and back in (Wayland needs it, and the shell caches the module, so toggling the extension isn't enough).

   Not a proper fix, since it just works around Electron only answering on the well-known name. Whichever side ends up changing, I'd guess Docker Desktop's tray should answer on both names, like other SNI implementations do. Happy to test anything.
7. thaJeztah

   transferred this issue fromdocker/for-linuxon Oct 9, 2026