This appears to be the source of the problem:
Snap run attempts to create a separate scope (a cgroup actually) for the application by talking to org.freedesktop.systemd1.Manager over session bus. In your case, the session bus is unavailable, so a separate cgroup cannot be created thus it is not possible to set up device access rules or identify processes belonging to a snap.
Hwoever, it does appear that the process was in /user.slice/user-1000.slice/session-1.scope
cgroup, what suggest that the session was at least partially set up by systemd. Can you check whether DBUS_SESSION_BUS_ADDRESS is set in your environment? (and in the terminal you execute the command). Does /run/user/1000/bus
exist and is it a socket?