D-Bus slot declaration request: nvbroadcast

[gettharshit]

• name: nvbroadcast
• description: AI-powered virtual camera, microphone enhancement, and local meeting tools for Linux.
• snapcraft: nvidia-broadcast-linux/snap/snapcraft.yaml at v1.4.0 · Hkshoonya/nvidia-broadcast-linux · GitHub
• upstream: GitHub - Hkshoonya/nvidia-broadcast-linux: NV Broadcast — Unofficial NVIDIA Broadcast for Linux and other OS. AI-powered virtual camera with background removal, blur, replacement, video enhancement, and noise cancellation. GPU accelerated. Open source. · GitHub
• upstream-relation: I am the upstream maintainer and registered Snap publisher.
• interfaces:
  • nvbroadcast-dbus (dbus, bus: session, name: com.doczeus.NVBroadcast):
    • request-type: installation (slot declaration)
    • reasoning: NV Broadcast is a GTK/libadwaita Gio.Application and must own its application ID on the session bus for single-instance activation. The same fixed, parameterless application actions are used by the restricted GNOME global-shortcut fallback. The requested name matches the application ID, desktop file, and metainfo. The slot is session-bus only and fixed to one name. No system-bus access, arbitrary D-Bus names, manual connection, or auto-connection is requested.

The current v1.4.0 submissions, amd64 revision 137 and arm64 revision 136, are unassigned and held by declaration-snap-v2_slots_connection. Revision 117 is the existing declaration-review anchor; revisions 136/137 supersede the earlier v1.4 artifacts.

The declared slot is:

nvbroadcast-dbus:
  interface: dbus
  bus: session
  name: com.doczeus.NVBroadcast

[store-requests-bot]

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

[shishirsub10]

Hi @gettharshit,

I have granted the dbus access to the snap. However, I was not able to trigger the automated review. Please reject the revision 117, which should trigger the review for revision 118 and it should be live. Let me know in case of any issues.

[gettharshit]

The signed declaration is now live, and the D-Bus rule looks correct.

The current v1.4.0 uploads are revisions 136 (arm64) and 137 (amd64). Revisions 117 and 118 are older, superseded builds. Before I reject revision 117, can you confirm that doing so will advance the automated review through to 136/137 rather than make revision 118 live? I want to avoid publishing a superseded artifact.

[0xnishit]

yes @gettharshit, it should take new revisions