Dbus slot declaration request: rustconn (dbus)

store-requests privileged-interfaces
1
  • name: rustconn
  • description: GTK4/libadwaita connection manager for Linux — SSH, RDP, VNC, SPICE, Telnet, Serial, Kubernetes, and Zero Trust protocols with embedded Rust clients
  • snapcraft: RustConn/snap/snapcraft.yaml at main · totoshko88/RustConn · GitHub
  • upstream: GitHub - totoshko88/RustConn: Modern connection manager for Linux with GTK4/Wayland-native interface. · GitHub
  • upstream-relation: I am the upstream author and sole maintainer
  • interfaces:
    • dbus-rustconn (dbus, bus: session, name: io.github.totoshko88.RustConn):
      • request-type: installation
      • reasoning: The GTK4/GApplication app owns its well-known D-Bus name on the session bus, matching the app ID and desktop file (io.github.totoshko88.RustConn) as registered by g_application_register. Under strict confinement a snap may only own D-Bus names derived from the snap name, so a slot declaration is required to grant AppArmor permission to own the app-ID name. Without it the app fails to register on the session bus (“not allowed to own the service … due to AppArmor policy”). This is the standard single-instance/activation mechanism for GTK/GApplication apps. The providing snap is auto-granted ownership, so no manual connection or auto-connection is needed — only the slot declaration (installation). Since moving from a custom core26 setup back to core24 with the gnome extension (rev 149+), this slot is declared in snapcraft.yaml:
slots:
  dbus-rustconn:
    interface: dbus
    bus: session
    name: io.github.totoshko88.RustConn

Previous interface request: Privileged interfaces request: rustconn (personal-files, system-files)

2

This request has been added to the queue for review by the @reviewers team.

3

Done as per Dbus slot declaration request for rustconn

4

@jslarraz Thank you for granting the dbus slot. However revisions r174/r175 (0.16.7), uploaded after the grant, are still held (resource-not-ready: Revision is not approved). Local review-tools shows the only outstanding constraint is:

declaration-snap-v2:slots_connection:dbus-rustconn:dbus
  human review required due to 'deny-connection' constraint (interface attributes)

It looks like the declaration grants allow-installation but the slot connection is still denied. Could you please also add allow-connection (and allow-auto-connection) for the dbus-rustconn slot with attribute name: io.github.totoshko88.RustConn on bus session? The personal-files grants are working fine. Thanks!

5

I can confirm that the newest version of the snap #180 passes review with the current snap declaration. I guess you will need to reject blocking revision manually to trigger new reviews.

1 Like