** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: snappy
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620560
Title:
Actually fixed with this PR: https://github.com/snapcore/snapd/pull/1868
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a membe
Pull request: https://github.com/snapcore/snapd/pull/1864
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620560
Title:
Revert command doesn't reset the right apparmor profile
To manage notification
Ok, this is caused by restoring previous profile in enforcing mode, not
"complain" on revert as we don't restore the flags. This is incorrect
and will be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Ok, reproduced easily with Didier's snaps. Investigating.
** Changed in: snappy
Status: In Progress => Confirmed
** Changed in: snapd (Ubuntu)
Status: In Progress => Confirmed
** Changed in: snapd (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification
Followed up on IRC with the snap files.
** Changed in: snappy
Status: Incomplete => New
** Changed in: snapd (Ubuntu)
Status: Incomplete => In Progress
** Changed in: snappy
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Hi Didier, I couldn't reproduce this issue with my local test snap;
could you please attach your snapcraft yaml so that I can test same
thing?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
** Changed in: snappy
Status: New => Incomplete
--
You received this bug notificat
** Changed in: snappy
Assignee: Zygmunt Krynicki (zyga) => (unassigned)
** Changed in: snappy
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620560
Title:
Rev
Quick analysis shows that we do setup snap security. Perhaps the
SnapSetup object that is used as the root of the decision tree is stale
and is not updated accordingly. Investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Description changed:
Tested with and without devmode:
foo snap is using:
plugs: [camera]
opening /dev/video0
snap install foo_1.0.snap
-> Access to /dev/video0 is given in x1
snap install foo_2.0.snap
-> Access to /dev/video0 is still given in x2 (same if reinstalling
** Changed in: snappy
Status: New => In Progress
** Changed in: snappy
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
** Changed in: snappy
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
Tested with and without devmode:
foo snap is using:
- plugs: [camera]
+ plugs: [camera]
opening /dev/video0
-
snap install foo_1.0.snap
-> Access to /dev/video0 is given in x1
snap install foo_2.0.snap
-> Access to /dev/video0 is still given in
12 matches
Mail list logo
