Hi :),
I uploaded the first two revisions of my snap “hinata” today and both are sitting in the manual review queue. The upload output said:
“human review required due to ‘deny-connection’ constraint (interface attributes)”
Revision 1 is arm64, revision 2 is amd64, both version 10.1.0. Neither can be released to a channel right now (the dashboard shows a warning on both, and releasing from the CLI fails with resource-not-ready).
I think the trigger is the dbus slot. The snapcraft.yaml declares:
slots: dbus-hinata: interface: dbus bus: session name: com.ahmadre.hinata
Hinata is a desktop client for a self hosted issue tracker. The Linux build is a GTK 3 app whose runner is a unique GApplication with G_APPLICATION_HANDLES_COMMAND_LINE. It needs to own that well known name for two reasons. First, starting it twice should not open a second window, it should hand the arguments to the window that is already running. Second, the app registers the hinata:// URI scheme, so when someone clicks a link to an issue the URI travels the same way and the running window navigates to it. Without the name the app cannot register and neither of those works.
The name matches the app id we already use everywhere else, including the desktop entry and the AppStream metainfo, so nothing else should be trying to claim it.
Everything else is plain strict confinement. The full plug list is network, home, desktop, desktop-legacy, gsettings, opengl, wayland, x11, audio-playback, audio-record and password-manager-service. The last two do not auto connect and I am not asking for that here, users can connect them themselves and the app explains how when they are missing.
Could you clear the two revisions and grant a declaration for the dbus slot so future uploads go through automatically?
Source and packaging:
The recipe is at packaging/linux/snap/snapcraft.yaml (symlinked to snap/).
Thanks
