As for the questions of xnox:
"""
ubuntu@autopkgtest:~$ sudo systemd-run --unit=check-env /usr/bin/env
Running as unit: check-env.service
ubuntu@autopkgtest:~$ sudo journalctl --no-pager -u check-env
-- Logs begin at Mon 2018-07-23 18:30:47 CEST, end at Sun 2019-02-03 13:25:21
CET. --
Feb 03
The SRU validation is done now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811233
Title:
[SRU] 2.37.1
To manage notifications about this bug go to:
** Summary changed:
- [SRU] 2.37
+ [SRU] 2.37.1
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
** Also affects: snapd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Bionic)
Public bug reported:
placeholder
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811233
Title:
[SRU] 2.37
To manage
This is now fixed upstream: https://github.com/shadow-
maint/shadow/pull/119 - so the next shadow release should have it. This
makes me also wonder if we should simply cherry pick it for disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: snapd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791587
Title:
snapd ignores proxy settings set via core snap
To manage
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because
** Changed in: snapd
Status: New => 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/1772844
Title:
snapd didn't initialize all the seeded snaps
To manage notifications about this
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631514
Title:
snap doesnt work. error: cannot communicate with server
To manage notifications
Closing the ubuntu task (as this is a debian bug :) - the other part of
course is still valid.
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is being worked on in https://github.com/snapcore/snapd/pull/5845
** Changed in: snapd
Status: Confirmed => In Progress
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Some work has been done to make connections after in
https://github.com/snapcore/snapd/pull/5469 - this will be part of the
upcoming 2.36 release which will most likely not be ready before cosmic
though :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Dan! Thats really helpful. So from the log you provided it looks
like the follow happend:
Boot time went from up by 8s (from 15s to 23s):
- "graphical.target reached after 15.614s in userspace" (before)
- "graphical.target reached after 23.527s in userspace" (after)
Seeding time went up
@Dan could we get the same data (plot + output of snap changes/tasks)
for the image *before* lxd was seeded as well? This way we can more
easily compare.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your reply @doko.
Let me clarify what my position:
- we would like to stop supporting gccgo in snapd
- this will mean a regression in xenial where we currently have a buildable
snapd on powerpc
- we would like to add the exception to powerpc to
https://wiki.ubuntu.com/SnapdUpdates to
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.36/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.36 (note that the debian
changelog is
I am much in favour of stop supporting powerpc in snapd. If we can make
that official in the SRU page we have one worry less (in practical terms
powerpc was never really fully supported because we don't build a core
snap for powerpc).
--
You received this bug notification because you are a
** Changed in: snapd (Ubuntu Cosmic)
Status: In Progress => 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/1791691
Title:
PATH broken in systemd units
To manage notifications
Removing block-promote tag as this is fixed in 2.35.2+18.10 now (well,
"fixed" it will do nothing if there is no PATH).
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: snapd (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791691
We found the root cause now and work on a fix. sorry for the trouble -
Note that this is a "cosmic" specific issue. I'm exploring workarounds
now to unblock you.
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
Hey Alex first, sorry for the trouble you have! We do run ~2800 tests
which each branch merged or release. This includes an automatic upgrade
test. Unfortunately the hang is not reproducible for everyone it seems,
neither our automatic tests nor I in a VM have managed to trigger this
hang. But we
What we see in the ps output is that for some reason it seems like
systemctl prompts for a password. Which is unusual because apt/dpkg runs
as root so there should be no need for this. Any further hints for us?
Are these desktop or server installs?
--
You received this bug notification because
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791087
Title:
Thanks for your bugreport. The output of "ps afx" when this hangs would
be great to get an idea why the dpkg process blocks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776622
Title:
snapd on
Thanks for your bugreport.
If you can reproduce this and/or still have the machine in this state it
would be great if you could attached the output of "ps afx" (run from a
terminal) to this bugreport. I wonder what is blocking the dpkg progress
here.
--
You received this bug notification
This is being worked on in https://github.com/snapcore/snapd/pull/5736
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771858
Title:
/snap/bin not in default PATH for units, snapd should ship
@sil2100 sorry for that, I updated the description now.
** Description changed:
- placeholder
+ This is a new version of snapd.
+
+ The changelog is available here
+ https://github.com/snapcore/snapd/blob/2.35/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+
On classic systems snapd will honor the system proxy settings via
http_proxy (and friends). However it does not (yet) respect the internal
settings. The following PR changes this:
https://github.com/snapcore/snapd/pull/5699
--
You received this bug notification because you are a member of Ubuntu
** Also affects: snapd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
placeholder
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786438
Title:
[SRU] 2.35
To manage
The above image was build by manually adding the patched util-linux
libuuid.so to the initramfs. The kernel (snap) build system does not use
-proposed so the initrd had to be updated this way to test this on core.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When doing: "(parted) p" to print the partitions UUIDs will be generated
internally when there are GPT disk labels. This is usually no problem.
However recently the kernel became more strict about getting randomness
from getrandom() and for reading from /dev/urandom. The
Thanks for your careful review Robie! As far as security is concerned, upstream
comments on this in edc1c90cb972fdca1f66be5a8e2b0706bd2a4949:
"""
Note that we do not use random numbers for security sensitive things
like keys or so. It's used for random based UUIDs etc.
"""
I looked at the
Public bug reported:
The current version of libuuid is using getrandom() without the
GRND_NONBLOCK flag. This means that in early boot the boot is blocked
until the crng is initialized to "level=1" which on virtual machines may
take some time.
Upstream fixed this in
** Summary changed:
- [SRU] 2.34
+ [SRU] 2.34.2
** Description changed:
This is a new version of snapd.
The changelog is available here
-
https://github.com/snapcore/snapd/blob/2.34.1/packaging/ubuntu-16.04/changelog,
+
** Description changed:
- placeholder
+ This is a new version of snapd.
+
+ The changelog is available here
+
https://github.com/snapcore/snapd/blob/2.34.1/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+ https://github.com/snapcore/snapd/commits/2.34.1 (note that
I looked over the failures:
# snapcraft:
network related failures AFAICT in their integration tests, e.g.
```
/home/ubuntu/autopkgtest_tmp/tmpyiuc3lb5/parts/rust-subdir/rust/bin/cargo fetch
--manifest-path
/home/ubuntu/autopkgtest_tmp/tmpyiuc3lb5/parts/rust-subdir/src/Cargo.toml
Exited with
** Summary changed:
- Boot delays with 4.15.0-24 based kernels
+ Boot delays with 4.15.0-24 based kernels in cloud
** Summary changed:
- Boot delays with 4.15.0-24 based kernels in cloud
+ Boot delays with 4.15.0-24 based kernels in images
--
You received this bug notification because you are
I suspect this is entropy related, i.e. something in the entropy
handling changed which causes things that use random numbers during the
boot to slow down. The snapd team is also affected by this bug (snapd
startup during boot became slow but when people press keys, move mouse
things get better).
Public bug reported:
placeholder
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779403
Title:
[SRU] 2.34
To manage
This got fixed in the cosmic seeds in https://git.launchpad.net/~ubuntu-
core-dev/ubuntu-
seeds/+git/ubuntu/commit/?id=764ab69745c53d8009b7cf9317df1fd9e26bbca2
and in bionic with https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
** Patch added: "systemd_237-3ubuntu10.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5157097/+files/systemd_237-3ubuntu10.2.debdiff
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
The 16.04 version of systemd had a patch to support the read-only etc.
For core18 we will also need this change because core18 is still not on
a fully writable etc.
I will attach a debdiff against the current bionic version of systemd.
** Affects: systemd (Ubuntu)
Any chance this can be fixed for 18.04.1 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776218
Title:
New style hook support not robust on removal
To manage notifications about this bug go to:
Thanks, its slightly mysterious why these files are truncated. I added
https://github.com/snapcore/snapd/pull/5402 and
https://github.com/snapcore/snapd/pull/5404 with better error checking
and extra canary checks to get to the bottom of this.
--
You received this bug notification because you
I pushed https://github.com/snapcore/snapd/pull/5390 which should fix
this with the next snapd release. It will drop in a systemd environment
configuration file that adds /snap/bin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I pushed a slightly modified version of this to https://github.com
/shadow-maint/shadow/pull/119
** Bug watch added: Debian Bug tracker #833256
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833256
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fwiw, I looked at the code of "su.c" from util-linux (because
debian/ubuntu may switch to it, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=833256) and it looks like the bug is not present
there. The su-common.c:modify_environment() code will first
setenv_path() from login.defs and then
Public bug reported:
Bugreport here so that we can SRU dosfstools with the fix:
On Ubuntu Core system we found a bug with fsck.vfat. When it repairs a
file that has a long filename it may rename it to FSCK.000 - however
it does not rename/replace the long-filename. Which means that the vfat
Public bug reported:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt ||
** Description changed:
- PLACEHOLDER
+ This is a new version of snapd.
+
+ The changelog is available here
+ https://github.com/snapcore/snapd/blob/2.33/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+ https://github.com/snapcore/snapd/commits/2.33 (note that the
I discussed this with Gustavo on the standup today. It seems like he
prefers to not add a new feature but just use "snap list | awk '{print
$1"|"$2}'|tail +2". Would that work for you? Or do you needs bits that
are not visible via "snap list"?
--
You received this bug notification because you
This is being worked on in https://github.com/snapcore/snapd/pull/5234
** Changed in: snapd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773842
Title:
https://github.com/snapcore/snapd/pull/5226 <- contians a PR for this
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771858
Title:
/snap/bin not in default PATH for units, snapd should ship
Public bug reported:
PLACEHOLDER
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773118
Title:
[SRU] 2.33
To manage
Hey Chen, could you please try to reoder the seed.yaml so that gtk-
common-themes is listed before all the application snaps, i.e. before
gnome-calculator?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [SRU] 2.32.8
+ [SRU] 2.32.9
** Description changed:
This is a new version of snapd.
The changelog is available here
-
https://github.com/snapcore/snapd/blob/2.32.8/packaging/ubuntu-16.04/changelog,
+
** Summary changed:
- [SRU] 2.32.7
+ [SRU] 2.32.8
** Description changed:
This is a new version of snapd.
The changelog is available here
-
https://github.com/snapcore/snapd/blob/2.32.7/packaging/ubuntu-16.04/changelog,
+
** Summary changed:
- [SRU] 2.32.6
+ [SRU] 2.32.7
** Description changed:
This is a new version of snapd.
The changelog is available here
-
https://github.com/snapcore/snapd/blob/2.32.6/packaging/ubuntu-16.04/changelog,
+
This is uploaded now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767833
Title:
[SRU] 2.32.6
To manage notifications about this bug go to:
** Description changed:
+ [Impact]
+ * Usability of snap recommendations degrated
+
+ [Test Case]
+ 1. Remove /snap/bin from PATH
+ 2. snap install corebird
+ 3. run "corebird"
+ 4. observe command-not-found suggesting to install corebird
+
+ 5. install fixed c-n-f
+ 6. observe that
Public bug reported:
When the user installs a snap (like slack) but does not have /snap/bin in PATH
the message is very confusing:
```
$ sudo snap install slack
...
$ slack
Command 'slack' not found, but can be installed with:
sudo apt install slack
```
The fix is that /snap/bin
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Artful)
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.32.6/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.32.6 (note that the debian
changelog is
Note that this "fix" is incomplete issofar that the options should also
escape the "=" char.
** Patch added: "Possible naive fix"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1763266/+attachment/5126430/+files/0001-bcachefs-escape-special-characters-in-option-strings.patch
--
You
The first bit of the diff is wrong, but should not matter for the test,
the bch2_scnprint_string_list() is what I suspect needs the escaping.
** Changed in: snapd (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I looked into this some more and I think this is a bcachefs bug. It does not do
any escaping for the mountinfo options. This is done by other filesystems like
ext4. The following might fix it:
"""
diff --git a/fs/bcachefs/opts.c b/fs/bcachefs/opts.c
index 8db8096e5ed4..4ebe557dfbaf 100644
---
I looked into this issue and pushed a fix here:
https://github.com/snapcore/snapd/compare/master...mvo5:lp-1763266?expand=1
However this looks like a bcachefs bug to me, most filesystems use
"seq_show_option" to display stuff in mountinfo. And seq_show_options()
will seq_escape() spaces:
** Changed in: snapd (Ubuntu)
Status: Fix Committed => 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/1762218
Title:
Snap apps not working anymore
To manage notifications about
*** This bug is a duplicate of bug 1765090 ***
https://bugs.launchpad.net/bugs/1765090
** This bug has been marked a duplicate of bug 1765090
[SRU] 2.32.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for your bugreport. We improved the robustness of this code path
- can you please try with snapd 2.32.5 which is available in bionic now.
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.32.5/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.32.5 (note that the debian
changelog is
** Tags removed: verification-needed verification-needed-artful
verification-needed-bionic verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-bionic verification-done-trusty verification-done-xenial
--
You received
Just a quick question: we have three cases where we use "" right
now. I assume we change all three (for consistency):
"""
sudo snap install aws-cli-compat # version 0.1
sudo apt install aws # version 1.0
-See 'snap info ' for additional versions.
+See 'snap info ' for additional
** Description changed:
- Placeholder
+ This is a new version of snapd. It supersedes the pending snapd releases
+ in -proposed.
+
+ The changelog is available here
+
https://github.com/snapcore/snapd/blob/2.33.3.1/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+
Thanks for your bugreport.
Do you have some more information about this issue? What is the output
of: "systemctl status -l snapd.service"? Could you paste this data to
this bugreport please? Does "sudo snap install --reinstall snapd" change
anything?
** Changed in: snapd (Ubuntu)
Status:
command-not-found (18.04.0~pre2) bionic; urgency=medium
* add versionized dependencies from command-not-found on
command-not-found-data and python3-commandnotfound
* update changelog to the latest agreement
-- Michael Vogt <michael.v...@ubuntu.com> Wed, 07 Mar 2018 14:58:22
The version number information is WIP - the server side(s) need tweaks
for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754839
Title:
CNF recommends 'snap info ' instead of 'snap info '
To
This is fixed in bionic with 18.04.0~pre6 now:
```
$ aws
Command 'aws' not found, but can be installed as:
sudo snap install aws-cli
sudo apt install awscli
See 'snap info aws-cli' for additional versions.
```
** Changed in: command-not-found (Ubuntu)
Status: In Progress => Fix
Thanks for your bugreport? Is this reproducible? I looked at the code
and the dependencies and its a bit unclear how this can happy.
** Changed in: command-not-found (Ubuntu)
Status: New => Incomplete
** Information type changed from Private to Public
--
You received this bug
** Summary changed:
- [SRU] 2.31.1
+ [SRU] 2.31.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745217
Title:
[SRU] 2.31.2
To manage notifications about this bug go to:
Public bug reported:
Placeholder
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: snapd
** Changed in: command-not-found (Ubuntu)
Status: New => In Progress
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Critical
** Changed in: command-not-found (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notificatio
** Changed in: command-not-found (Ubuntu)
Status: New => Triaged
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The new command-not-found extractor uses hints from the binary packages.
The attached fix adds renaming for python2.7-minimal -> python2.7. We
probably want the same for python3.6,3.7.
** Affects: python2.7 (Ubuntu)
Importance: Undecided
Status: New
** Patch
Public bug reported:
The new command-not-found in bionic supports hints from the package now.
To make command-not-found suggest "python3" on top if a user types
"python" (when that is not installed) the attached debdiff is needed.
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
The current output (in lp:command-not-found) looks like this:
Mixed snaps/debs:
"""
$ jq
The command 'jq' can be installed as:
snap jq
deb jq (1.5+dfsg-2)
See 'snap info jq' for additional versions.
"""
Single snap:
"""
$ spotify
The command 'spotify' can be installed from the following
** Also affects: command-not-found
Importance: Undecided
Status: New
** Changed in: command-not-found
Status: New => In Progress
** Changed in: command-not-found
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs,
https://github.com/snapcore/snapd/pull/4718
** Changed in: snapd (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750856
Title:
snapd on s390x tried
We are working on improving this currently. Right now c-n-f has no
version concept for the apt backend (easy for snaps). But we have a plan
how to fix that (some work though).
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => Critical
** Changed in: command-not-found (Ubuntu)
** Also affects: snapd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because
** Summary changed:
- [SRU] 2.31
+ [SRU] 2.31.1
** Description changed:
- placeholder
+ This is a new version of snapd.
+
+ The changelog is available here
+
https://github.com/snapcore/snapd/blob/2.31.1/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+
Unfortunately we need to revert this again because the display name can
be changed in arbitrary ways by the developer. So it could be used to
present misleading information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: command-not-found (Ubuntu)
Status: New => In Progress
** Changed in: command-not-found (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Proposed fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1749000/+attachment/5054232/+files/systemd_237-1ubuntu4.debdiff
** Patch removed: "possible fix"
** Patch added: "possible fix"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1749000/+attachment/5054183/+files/systemd_237-1ubuntu4.debdiff
** Patch removed: "possible fix"
Public bug reported:
There was a recent change in apparmor
(https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb) that
breaks snapd. The fix is simply to add the
++AssumedApparmorLabel=unconfined line to the service file so that
activation works again.
Attached is a debdiff with a
301 - 400 of 16460 matches
Mail list logo
