I uploaded snapd 2.55.5 as a SRU to all the relevant releases. They are
in the "unapproved" queue right now, see e.g.
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- placeholder
+ This is a new version of snapd.
+
+ The changelog is available here
+ https://github.com/snapcore/snapd/blob/2.56/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+ https://github.com/snapcore/snapd/commits/2.56 (note that the
The snapd test change is up in
https://github.com/snapcore/snapd/pull/11810
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in
Public bug reported:
placeholder
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [SRU] 2.55
+ [SRU] 2.56
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fwiw, I tested this also for focal->jammy on my laptop (real machien)
and it worked fine there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and
I ran the spread test in the snapd PR
https://github.com/snapcore/snapd/pull/11702 against this change in
21.10 and 22.04 and the restart behavior is correct: if snapd is
upgraded from a version that does not yet use "dh_systemd --restart-
after-upgrade" still keep running.
** Tags removed:
It seems the above is not an issue on 21.10 at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and update-notifier when snapd package
is being
There is one thing I noticed - when transitioning from
"dh_systemd_start" to "dh_systemd_start --restart-after-upgrade" at
least on 16.04 snapd.service is stopped in the old prerm but when the
new postinst runs it calls "systemctl restart snapd" but that only
restarts a service if it was not
I uploaded a version of snapd with the changes from
https://github.com/snapcore/snapd/pull/11680 and
https://github.com/snapcore/snapd/pull/11287 to the my ppa:mvo/tmp for impish
too.
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt-add-repository ppa:mvo/tmp
$
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt install --no-install--recommends snapd update-notifier
$ sudo snap install canonical-livepatch
$ sudo apt-add-repository ppa:mvo/tmp
$ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list
$ sudo sed -i 's/impish/jammy/'
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt install --no-install--recommends snapd update-notifier
$ sudo snap install canonical-livepatch
$ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list
$ sudo apt update
$ sudo apt full-upgrade -y
and with that I can
I uploaded a cherry pick of Albertos branch with the current jammy snapd
plus the fix to https://launchpad.net/~mvo/+archive/ubuntu/tmp/+packages
and will test once it's build in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This could be the solution
https://gitlab.gnome.org/GNOME/gdm/-/commit/307c683f00e1711973139837992ca0f6f55314a5
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just tested it and and with the attached debdiff I can no longer
reproduce the problem.
** Patch added: "debdiff with the fix"
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1969097/+attachment/5580697/+files/gdm3_42.0-1ubuntu3.debdiff
** Changed in: gdm (Ubuntu)
Status: New =>
** Changed in: snapd (Ubuntu)
Status: Triaged => 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/1792656
Title:
snapd should depend on fuse for snapfuse
To manage notifications
** Summary changed:
- netplan dbus returns "false" in io.netplan.Netplan.Config.Set
+ netplan dbus returns "false" in io.netplan.Netplan.Config.Set with networkd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The deeper reason appears to be:
https://git.launchpad.net/ubuntu/+source/netplan.io/tree/debian/patches/0006-cli-
apply-give-some-extra-time-for-networkctl-
reload.patch?h=applied/ubuntu/focal-updates#n25
It was a bit hard to find because for the "networkctl" calls in strace there
was no
I can also reproduce this on a minimal 20.04 VM image (created with
autopkgtest-buildvm). Running the reproducer script above triggers the
same "false" return so it seems to be related to the renderer. I was not
able to reproduce it on my desktop with network-manager.
--
You received this bug
The (super naive) diff I used to increase the timeout:
"""
diff --git a/src/dbus.c b/src/dbus.c
index 4d9b17a..78cdafe 100644
--- a/src/dbus.c
+++ b/src/dbus.c
@@ -512,8 +512,8 @@ method_try(sd_bus_message *m, void *userdata, sd_bus_error
*ret_error)
// LCOV_EXCL_STOP
/* wait for
Fwiw, it might be interessting to see where this time is actually spend
- 6s is long for a relatively small config, maybe there is a bug hidding
here somewhere that is just masked when we increase the timeout?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
So it looks like the timeout in dbus.c that is hardcoded to 5s is the problem.
I patched dbus.c to use a 15s timeout (values was arbitrary) and run the
reproducer I get:
# time ./repo.sh
+ cut -d" -f2
+ grep object path
+ dbus-send --type=method_call --system --print-reply
Here is a reproducer script
"""
#!/bin/sh
set -ex
objpath=$(dbus-send --type=method_call --system --print-reply
--dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Config | grep
"object path" | cut -d'"' -f2)
dbus-send --type=method_call --system --print-reply
I managed to capture a debug log from netplan when run via the ddbus comments
in #8. It was a bit tricky (bind mounted utils.py and set debug = True there)
because netplan is coming from a RO location and no way to use the environment
to enable debugging. Unfortunately the log gives me not many
Fwiw I was able to reproduce this on core20 via:
"""
$ dbus-send --type=method_call --system --print-reply --dest=io.netplan.Netplan
/io/netplan/Netplan io.netplan.Netplan.Config
[got the /io/netplan/Netplan/config/4ZMNK1 path here]
$ dbus-send --type=method_call --system --print-reply
I was wrong and looked at old code. There is now a case where the dbus Try()
returns "false". It was added in e19441c3 and has:
"""
+/* wait for the /run/netplan/netplan-try.ready stamp file to appear */
+guint poll_timeout = 500;
+if (seconds > 0 && seconds < 5)
+
I'm sorry, my initial comment was wrong - we do have a "false" path in
"Try()" now, I was looking at old code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns
Sergio reported that he sees "systemd-networkd[804]: Could not set
hostname: Permission denied"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967084
Title:
netplan dbus returns "false" in
It's pretty consistent now, here is a strace log from uc20 in google
that shows the calls from dbus: https://paste.ubuntu.com/p/hmjDQYYc9S/
** Also affects: netplan
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
We also observe this behavior now on UC20 systems that run with amd64,
e.g. in this run:
https://github.com/snapcore/snapd/runs/5876437750?check_suite_focus=true
The log looks like this:
"""
2022-04-07T22:28:41.1746417Z Apr 07 22:28:33 apr072148-447340 snapd[3454]:
netplan.go:122: DEBUG: using
Hm, what is super mysterious is that AFAICT from reading
https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/netplan.io/0.104-0ubuntu2~20.04.1/netplan.io_0.104-0ubuntu2~20.04.1.dsc
there is nothing in `method_apply()` code path that could trigger this.
I only see that `sd_bus_error_setf()`
Public bug reported:
As part of our snapd core integration testing we run the spread test for
netplan on a UC20 PI device.
On this device our test fails with:
"""
2022-03-25 14:33:00 Error executing
external:ubuntu-core-20-arm-32:tests/core/netplan-cfg
(external:ubuntu-core-20-arm-32) :
-
** Changed in: shadow (Ubuntu Bionic)
Status: New => In Progress
** Changed in: shadow (Ubuntu Focal)
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/1959375
** Description changed:
Only a single user option (the first one) is taken into consideration
when mounting a new disk regardless of the filesystem.
# mount /dev/sdd1 /mnt/cruizer -onodev,ro,x-gdu.hide,x-gvfs-hide
# findmnt --mtab /mnt/cruizer
TARGET SOURCEFSTYPE OPTIONS
Public bug reported:
When using the netplan-dbus API on Ubuntu Core and the network-manager
renderer the "netplan-dbus" appication will crash. To reproduce take a
UC20 or UC22 system and run:
```
$ sudo snap set system system.network.netplan.network.bridges.br54.dhcp4=true
```
(which in effect
** Patch added: "debdiff for the PPA jammy test upload"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557912/+files/shadow_4.8.1-2ubuntu2~ppa1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Proposed (untested) patch"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557911/+files/shadow-lp1959375.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Currently doing something like:
sudo usermod -a -G snap_microk8s dbeamonte
on a Ubuntu Core system will fail with
usermod: /etc/group.15965: Read-only file system
This is because the existing usermod patches to detect
the extrausers file do not cover this case.
** Description changed:
- Placeholder
+ This is a new version of snapd.
+
+ The changelog is available here
+
https://github.com/snapcore/snapd/blob/2.54.2/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+ https://github.com/snapcore/snapd/commits/2.54.2 (note that
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/1955137
Title:
[SRU] 2.54
To manage
** Also affects: snapd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Also affects: snapd (Ubuntu Bionic)
Fwiw, it looks like the latest core18 edge build that includes
https://launchpad.net/ubuntu/+source/cloud-init/21.4-0ubuntu1~18.04.1
make the problem go away. It seems https://bugs.launchpad.net/cloud-
init/+bug/1946003 is what caused it.
The old code had a udev rule that would call into the
I attached the /run/cloud-init and /var/log/cloud-init logs of the
good/bad run - I looked over the diff via "diff -u <(cut -f 4- -d:
/tmp/cloud-init-good-core18-r2206/cloud-init.log) <(cut -f 4- -d:
/tmp/cloud-init-bad-core18-r2208/cloud-init.log)" but couldn't see
anything standing out there
** Attachment added: "cloud-init logs for the "good" run"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542024/+files/cloud-init-good-core18-r2206.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "cloud-init logs for the "bad" run"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+attachment/5542025/+files/cloud-init-bad-core18-r2208.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I spend a bit more time bisecting the various core18 snaps to see at
what revision the failure started to become reproducible. Interestingly
I found that it started with r2208 AFAICT. It's all a bit annoying
because it's a race so I don't trust it 100% but the previous r2206 got
2 good runs in a
@Dan Thanks, this find about BindsTo is super interesting! It's not
something that snapd writes out, it's curious where this comes from.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
I spend a bit of quality time with this bug today and it seems there is (also?)
a kernel dimension to it. I ran the following:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$ git diff
diff --git
About the question about Focal/hirsute/uc20 - we have not observed the
issue there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in
Fwiw, the patch debian/lp1934147/0001-core-add-a-new-unit-method-
catchup.patch is part of a fairly large patchset
(https://github.com/systemd/systemd/pull/9200/commits) so maybe
something is missing there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just for the record, I also did another run with:
https://storage.googleapis.com/snapd-spread-
tests/snaps/core18_20211102_amd64.snap and that also fails right away:
"""
$ git status
On branch tests-use-core18-from-gce
Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'.
$
Thanks Lukas for providing this revert of
f0831ed2a03fcef582660be1c3b1a9f3e267e656. Using
https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap I can
no longer reproduce the isue.
To make it easier to reproduce what I did:
"""
$ git status
On branch tests-use-core18-from-gce
Your
We created a test PR that uses this core18 snap build in
https://github.com/snapcore/snapd/pull/11015 - we are still running
tests but it seems the error is still there :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hm, maybe I'm holding it wrong (again) but I'm not sure this is fully fixed:
$ apt list netplan.io
netplan.io/now 0.103-0ubuntu5~21.04.2 amd64 [installed,local]
$ $ zcat /usr/share/doc/netplan.io/changelog.Debian.gz |head -n 6
netplan.io (0.103-0ubuntu5~21.04.2) hirsute; urgency=medium
*
I distro patched the impish version of snapd with the fix from Ian and uploaded
a new version:
https://launchpad.net/ubuntu/impish/+queue?queue_state=1_text=snapd
with the fix as 2.53+21.10ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.53/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.53 (note that the debian
changelog is
My apologizes that this totally was not on my radar. I applied the patch
(thank you!) and moved the code from bzr to git, added a gbp.conf and
pushed to GH for now (but maybe this really should go to salsa instead).
I hope I will be able to release a new .16 release with these changes
(and the
** 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/1944988
Title:
[FeatureFreezeException] snapd 2.53~pre1
To manage
This got accepted into impish now.
** 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/1944988
Title:
[FeatureFreezeException] snapd
The build log on impish:
https://launchpad.net/~mvo/+archive/ubuntu/tmp/+build/22111395
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944988
Title:
[FeatureFreezeException] snapd 2.53~pre1
To
Public bug reported:
Snapd needs to be updated to support cgroups v2 and also need to cater
for some changes in libc.
This is why we would like to ask for a feature freeze exception for
snapd to upload 2.53~pre1 and eventually 2.53 into impish.
Unfortunately it's very hard to backport this in
This is now uploaded to impish as
snapd_2.53~pre1.git19b68f708_source.changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To
** Changed in: snapd (Ubuntu)
Status: In Progress => 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/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage
This is merged now in: https://github.com/snapcore/snapd/pull/10524 and
will be part of the next release.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: zmk (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: zmk (Ubuntu)
Status: New => Fix Released
** Changed in: zmk (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the patch! For us it's slightly more complicated because we
want to make sure that snapd keeps building (ideally unchanged) back to
16.04. We will look a bit more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935667
Title:
Please
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
This should also add "assumes: [kernel-assets]" to the meta/snap.yaml so
that the
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.50/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.50 (note that the debian
changelog is
** Package changed: snapd (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920107
Title:
Failed messages of sd-umoun show with reboot/shutdown
To manage notifications
** Also 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/1920107
Title:
Failed messages of sd-umoun show with reboot/shutdown
To
[from-irc]
mvo: hey! There are 2 things here:
- the zfs generator is currently broken in the default setup due to
OpenZFS 2.0 default layout. ubiquity in unapproved since this morning is fixing
this
(people using our default setup will not be impacted by the bug then)
- then, for people
This looks a lot like an issue with zfs-linux to me (and *maybe*
systemd, not sure about this).
The issue is that the snaps are on /var/lib/snapd/snaps and snapd writes
mount units into /etc/systemd/system/ so that the snaps are mounted
under /snap//.
Looking at a zfs-linux system and the
** Also affects: zfs-linux (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/1922293
Title:
Snaps appear broken on 21.04 Beta with ZFS
To manage
Fwiw, the dtbs/ dir:
$ ls pi-kernel-armhf-rev266/dtbs/
bcm2708-rpi-b.dtb bcm2710-rpi-cm3.dtb bcm2835-rpi-zero.dtb
bcm2708-rpi-b-plus.dtbbcm2711-rpi-400.dtb bcm2835-rpi-zero-w.dtb
bcm2708-rpi-b-rev1.dtbbcm2711-rpi-4-b.dtb bcm2836-rpi-2-b.dtb
bcm2708-rpi-cm.dtb
The kernel wants to use:
```
assets:
pidtbs:
update: true
content:
- dtbs/
```
instead of the one suggested above because the pi-kernel on arm64 and
armhf have different dtbs/ dir layout:
arm64: dtbs/broadcom/*.dtb, dtbs/overlays
armhf: dtbs/*.dtb, dtbs/overlays
So the armhf has
** Changed in: snapd (Ubuntu)
Status: In Progress => 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/1920754
Title:
FTBFS and autopkgtest failure in hirsute
To manage
This is in progress now in the snapd and ubuntu-image. This will also
need changes in the gadget/kernel that are tracked here:
https://bugs.launchpad.net/snapd/+bug/1907056
** Changed in: snapd (Ubuntu)
Status: Triaged => In Progress
** Also affects: ubuntu-image (Ubuntu)
Importance:
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
- WE ALSO NEED TO UPDATE THE ASSUMES in the meta/snap.yaml, diff will
- follow shortly.
+
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
+
+ WE ALSO NEED TO UPDATE THE ASSUMES in the meta/snap.yaml, diff will
+ follow shortly.
** Changed in: snapd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Changed in: snapd (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ub
Fwiw, mysql-8.0 is also affected:
$ dpkg -c libmysqlclient21_8.0.23-3_amd64.deb|grep buildd
drwxr-xr-x buildd/buildd 0 2021-02-11 10:32 ./
[many more]
And some more:
$ dpkg -c libqt5xdg3_3.6.0-1ubuntu2_amd64.deb |grep buildd
-rw-r--r-- buildd/buildd 268440 2021-02-11 21:58
This is fixed now.
** Changed in: snapd
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/1878541
Title:
Grub fails to load kernel from squashfs if mem <
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.49/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.49 (note that the debian
changelog is
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
pidtbs:
update: true
content:
-
** Also affects: snapd
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/1907056
Title:
Please add meta/kernel.yaml
To manage notifications about this bug
After discussing this we decided that we will leave cgroups v1 support
for 21.04 because the snapd team will not be able to port all features
to v2 in time. But early in the 21.10 cycle v1 is turned off and snapd
needs to be ported to full v2 support.
--
You received this bug notification
@rbalint Do you have a timeline when you plan this? The changes required
make this most likely something we can only tackle during the 21.10
cycle :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@rbalint Thanks for this heads up. Unfortunately we are not ready for
cgroups v2. Snapd is working on v2 systems but a lot of the
functionality is not ported. AIUI it requires quite a bit of work on our
side and the two are quite different :/
--
You received this bug notification because you are
** Summary changed:
- [SRU] 2.48.1
+ [SRU] 2.48.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906690
Title:
[SRU] 2.48.2
To manage notifications about this bug go to:
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
pidtbs:
update: true
content:
- -
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
- pi-dtbs:
+ pidtbs:
update: true
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
pi-dtbs:
update: true
content:
- -
** Description changed:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
- pi-dtbs:
- update: true
- content:
- -
Public bug reported:
Snapd will soon support to have DTBs in the kernel snap that are
automatically installed on kernel refreshes. To support this, please add
the following file to the pi-kernel:
$ cat meta/kernel.yaml
assets:
pi-dtbs:
update: true
content:
- dtbs
This will allow
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/1906690
Title:
[SRU] 2.48.1
To manage
The travis runs are currently not active, we move to GH actions. The
2.48 release test run is visible at
https://github.com/snapcore/snapd/pull/9685/checks?check_run_id=1443415116
Some isolated test failures on centos/suse but Ubuntu is all green. One
small issue on ubuntu-core-20 with the fsck
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905272
Title:
Can't get h/w video acceleration on rpi4
To manage notifications about this bug
** Also affects: u-boot (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: u-boot (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: u-boot (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: u-boot (Ubuntu Bionic)
Public bug reported:
This is a new version of snapd.
The changelog is available here
https://github.com/snapcore/snapd/blob/2.48/packaging/ubuntu-16.04/changelog,
the raw git changelog is available here:
https://github.com/snapcore/snapd/commits/2.48 (note that the debian
changelog is
Thanks for this! I sponsored the upload, happy to sponsor more!
** Changed in: u-boot (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/1903054
Title:
1 - 100 of 16409 matches
Mail list logo
