snap logs requires sudo but not journalctl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
Low
|
Unassigned |
Bug Description
In a fresh ubuntu 22 VM
After installing a snap that has a background service, I noticed that the command `snap logs MyApp` does require sudo while using `journalctl -u snap.MyApp.
An example with lxd:
~$ snap logs lxd.activate
error: access denied (try with sudo)
~$ journalctl -u snap.lxd.
May 23 16:02:53 complete-pelican systemd[1]: Starting Service for snap application lxd.activate...
May 23 16:02:53 complete-pelican lxd.activate[533]: => Starting LXD activation
May 23 16:02:53 complete-pelican lxd.activate[533]: ==> Creating missing snap configuration
May 23 16:02:53 complete-pelican lxd.activate[533]: ==> Loading snap configuration
[...]
I believe they inspect the same data, but one require sudo while the other doesn't.
Changed in snapd: | |
importance: | Undecided → Low |
status: | New → Confirmed |