@Paweł and @Zygmunt, was it really fixed?
I have the latest update from xenial-updates (2.13), and I can still reproduce
the bug.
Actually, "apt-cache policy snapd" reports 2.13:
snapd:
Installed: 2.13
Candidate: 2.13
While "snap --version" reports 2.12:
snap2.12
snapd 2.12
series
** Also affects: snappy
Importance: Undecided
Status: New
** Changed in: snappy
Milestone: None => 2.13
** Changed in: snappy
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It was fixed on 2016-07-31 and included in recently released snapd 2.13
(I just made a quick test with latest version and can't reproduce).
Marking as fixed.
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
