Skip to content

fix: Check StatusNotifierWatcher availability when GNOME extensions aren't accessible#150

Open
kenvandine wants to merge 2 commits intoProtonVPN:stablefrom
kenvandine:snap_indicator
Open

fix: Check StatusNotifierWatcher availability when GNOME extensions aren't accessible#150
kenvandine wants to merge 2 commits intoProtonVPN:stablefrom
kenvandine:snap_indicator

Conversation

@kenvandine
Copy link
Copy Markdown

When AppArmor blocks the org.gnome.Shell.Extensions D-Bus call (e.g. in
strict snap confinement), fall back to querying NameHasOwner for
org.kde.StatusNotifierWatcher on the session bus rather than blindly
assuming appindicator support. The SNI watcher is registered by
whichever component provides tray support (GNOME extension host, KDE,
XFCE plugin, etc.), so its presence is a direct, DE-agnostic signal
that AppIndicator3 will work.

…ren't accessible

  When AppArmor blocks the org.gnome.Shell.Extensions D-Bus call (e.g. in
  strict snap confinement), fall back to querying NameHasOwner for
  org.kde.StatusNotifierWatcher on the session bus rather than blindly
  assuming appindicator support.  The SNI watcher is registered by
  whichever component provides tray support (GNOME extension host, KDE,
  XFCE plugin, etc.), so its presence is a direct, DE-agnostic signal
  that AppIndicator3 will work.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant