That was because of an error where libusb was throwing “unable to initialize libusb: -99”. There was a bug on launchpad somewhere which suggested adding the network-control interface and after I did that the error went away. Unable to find that link now…
Can you snap disconnect that interface and try to reproduce, then add any policy violations from journalctl/syslog? I suspect you only need network and not network-control.
You can plug the mount-observe interface for some of these. hardware-observe would cover many of the others. I suspect what network-control is giving you is access to some AF_NETLINK sockets. I suggest removing network-control and trying network and if that doesn’t work, network-observe might (but I would still ask why gphoto2 needs to observe the network).
If network doesn’t work, can you install your snap in devmode (snap install --dangerous --devmode /path/to/you/snap then do snap run --strace gphoto2-eberkund... and exercise your snap then put the output of this command somewhere so I can review what it is doing?
I’m +1 to auto-connect camera, raw-usb, mount-observe, hardware observe (and home, but that does already, surely)
I don’t understand why -1 on removable-media. If I put an SD card from my DSLR in my PC, can gphoto2 see that without jumping through hoops to connect it? I’d expect that to work.
I tend to not vote to auto-connect removable-media unless it is core functionality. I’m happy to hear others on this point. I was thinking about the SD card scenario and that is very valid. I’ll adjust my vote.
We don’t have the ability to rename snaps in the store (AIUI) so you’d need to upload a new snap as gphoto2 rather than the current name with the suffix. Unless you’re requesting gphoto2 as an alias in your current snap? I’d certainly prefer the former than the latter. I’m not a fan of namespaced snaps where no existing snap exists for the non-namespaced name.
Sorry for missing the request for the gphoto2 name(space). Registering the gphoto2 snap name and then republishing your snap there is the way to go - we don’t typically service registration requests for reserved names via the forum.
You’ll need to find a way to tell users of gphoto2-eberkund to switch to the other snap (which might involve data loss - you need to research this and provide a procedure for them to migrate the data), unless you plan to keep publishing updates to gphoto2-eberkund (not recommended).
Try to register it normally, you’re likely to get a “Request reserved name XXX in the Global store” page which looks a bit scary - just document your rationale for claiming the name in the comment box and the store reviewers will evaluate the request.
Once registered, you can simply publish your snap there and close all channels for gphoto2-eberkund.
Last time I tried that it said the namespace was taken, but as far as I can see it’s not actually in use (but still reserved). If that namespace could be deleted then I would be able to upload a new snap with the correct name.
How long ago was this? I just tried registering gphoto2 and got:
The name ‘gphoto2’ is reserved.
Here’s what you can do:
Choose an alternative name that people can associate with you, for example ‘roadmr-gphoto2’.
Request this name to be manually reviewed: please enter a rationale in the ‘Comment’ box and click the ‘Request reserved name’ button below.
I don’t see mention of it being taken - “reserved” is something else (it means it can’t just be registered by anyone, since it’s a well-known application name we want to ensure the registrant has a good claim and rationale to the name).
Let me know if you see something different. If you do not, the thing to do would be indeed : “enter a rationale in the ‘Comment’ box and click the ‘Request reserved name’ button below.”
But yes, I would like to request that name which is why I made this thread. I am just packaging the official deb package from the repos so I think it should be okay.