*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a
Will be fixed in next systemd upload, in 246.6-1ubuntu1, at least for the
systemd part.
https://github.com/systemd/systemd/issues/16669
** Changed in: systemd (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Groovy)
Importance: Undecided => High
** Bug
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
Will be fixed in next upload, in 246.6-1ubuntu1
https://github.com/systemd/systemd/issues/16669
** Bug watch added: github.com/systemd/systemd/issues #16669
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1890913
init is using 100% of processor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1890913
init is using 100% of processor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Apport keeps reshooting apport-autoreport.service as long as there are
files like /var/crash/*.crash:
# cat /lib/systemd/system/apport-autoreport.path
[Unit]
Description=Process error reports when automatic reporting is enabled (file
watch)
ConditionPathExists=/var/lib/apport/autoreport
[Path]
I've attached the upstream changelog.
The upstream release contains a lot of fixes for nftables but also
rewrites and fixes in other areas.
Landing the merge does have risks, but IMO it would be better ship it in
20.10 than the current version.
I've asked the Security Team in June if they could
** Attachment added: "changes-iptables-1.8.5.txt"
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+attachment/5411820/+files/changes-iptables-1.8.5.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage
** Changed in: systemd (Ubuntu Groovy)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
OK, the next upload passes on s390x, so this will likely be resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1895576
Title:
boot-and-services in tests-in-lxd
@paelzer To correct myself this (s390x) regression is not due to the
snapd seeding issue, but LP: #1895576 which may have been already fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz
...
test_rsyslog (__main__.ServicesTest) ... FAIL
test_tmp_cleanup (__main__.ServicesTest) ... ok
test_tmp_mount
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in
Groovy/s390x, but this is a real regression which is not due to flakiness of
tests-in-lxd.
Please don't reopen this bug, but file a new one or find one already opened. As
I see this is still LP: #1878225. I'm filing a
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1877078
Title:
Please ship empty /etc/fstab in LXD images
** Changed in: iptables (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1893958
Title:
[FFe] Please accept iptables
** Summary changed:
- update alsa/audio realted infomation collection code in apport
+ update alsa/audio related infomation collection code in apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
@laney I've sent the email to ubuntu-devel@ a week ago and it also made
it to
https://www.phoronix.com/scan.php?page=news_item=Ubuntu-20.10-Nftables
so I believe every interested party must be aware of that, but I've now
pinged stgraber on #ubuntu-release.
--
You received this bug notification
switching to nftables (again) is tracked in LP: #1887186
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1843468
Title:
nftables based iptables wrapper break userspace
@oibaf Please open a separate bug for the merge, this one is only for
the switch. I agree that the bug fixes would be better to be merged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
Public bug reported:
The change is a planned change for this development cycle and the fix
has been tested as described in LP: #1887186 and
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html .
Changes:
iptables (1.8.4-3ubuntu3) groovy; urgency=medium
.
* Swap
FFe: LP: #1893958
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1887186
Title:
Please switch to nftables as the default backend
Status in iptables package in Ubuntu:
As I recall the unattended-upgrades package which hit this bug was not
the latest version from bionic-updates. Right?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1893675
Title:
Autopkgtest failure on latest version of initramfs-tools - lack of
We have a few options to fix the issue. The one I'd prefer would be
switching to systemd to depend on chrony as the preferred time-daemon
because timesynd turns back time and that can cause issues like this
one.
An other option is disabling systemd-timesyncd in the test VMs, that
would make the
Who owned /var?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891394
Title:
systemd breaks upgrade
*** This bug is a duplicate of bug 1892358 ***
https://bugs.launchpad.net/bugs/1892358
** This bug has been marked a duplicate of bug 1892358
autopkgtest success rate dropped inhibiting proposed migration
--
You received this bug notification because you are a member of Ubuntu
Touch
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's
comment's about what his plan is after his revert.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
@vorlon What is your plan regarding this fix? The revert may have helped
MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
fstab then MAAS should be fixed and not LXD images should be broken, so
I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
file
This change got reverted in livecd-rootfs and now breaks systemd
autopkgtest.
livecd-rootfs (2.683) groovy; urgency=medium
* Revert the removal of fstab from squashfs images, which has had knock-on
effects and breaks MAAS (ref bug #1890803)
-- Steve Langasek Wed, 12 Aug 2020
11:31:12
Tests-in-lxd fails because LXD images ship invalid /etc/fstab again making
systemd-remount-fs.service fail.
I'm marking systemd-fsckd test as flaky to not block others' work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'm testing the fix in Bileto and will upload it if the tests found no
regression:
https://bileto.ubuntu.com/#/ticket/3801
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Since this affects only upgrades from pre-246 versions the severity
should be High only. I'm testing the fix in Bileto and will upload it if
the tests found no regression:
https://bileto.ubuntu.com/#/ticket/3801
** Changed in: systemd (Ubuntu)
Importance: Critical => High
--
You received
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/101
** Bug watch added: Debian Bug tracker #968589
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968589
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968589
Importance: Unknown
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891716
Title:
Networking broken after systemd update
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790205
Title:
systemd journals take up a lot of space,
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Package changed: systemd (Ubuntu) => zsys (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891867
Title:
zfs not correctly imported at boot
Status in zsys
There are many similar bugs filed against dpkg, is this an APT issue
running dpkg wrong?
** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Since lightdm works OK there is most likely something that GDM could do
differently.
I think this is a duplicate of LP: #1745664 . Does installing ncsd
resolve the issue with gdm3, too?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1882034
Title:
cannot start X session with NIS
Seems like the debconf GTK frontend could not find an icon, needs more
investigation.
** Package changed: unattended-upgrades (Ubuntu) => debconf (Ubuntu)
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886886
Title:
Plymouth 0.9.5 release
Status in plymouth
*** This bug is a duplicate of bug 1871145 ***
https://bugs.launchpad.net/bugs/1871145
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
2.3ubuntu0.1, the
Unattended-upgrades may handle this exception by exiting with failure
and not re-raising it to the top.
** Changed in: unattended-upgrades (Ubuntu)
Status: Opinion => Triaged
** Changed in: unattended-upgrades (Ubuntu)
Importance: Undecided => Low
--
You received this bug
Fastboot is known to cause issues on older CPUs:
https://wiki.archlinux.org/index.php/intel_graphics#Fastboot
If the i915.fastboot=1 option was _not_ set by you manually then please
reopen the bug by settint status to New.
** Changed in: systemd (Ubuntu)
Importance: High => Undecided
**
** Tags added: block-proposed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1890913
Title:
init is
This commit is already present in Focal and later releases.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
**
Is there a reliable way I can reproduce the problem? (I don't face it on my
laptops.)
Is this happening on any Ubuntu-certified model? This could let our
certification team to investigate the issue.
How can the systemd help? killing plymouth earlier?
** Changed in: systemd (Ubuntu)
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug has been marked a duplicate of bug 1805183
systemd-resolved constantly restarts on Bionic upgraded from Xenial
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183
** This bug is no longer a duplicate of bug 1832050
chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)
** This bug has been marked a duplicate of bug 1805183
systemd-resolved
I've added the OEM Solutions Group team for awareness. I'm not sure what
the final fix will be since servers' and desktops'/laptops' ideal
default seem to be different, but most likely the certification tests
should be adjusted if we don't end up restoring the previous behaviour
of the
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a
Verified 2.3ubuntu0.1 on Focal:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/u/unattended-
upgrades/20200722_172955_59a0f@/log.gz :
...
Running ./test_rewind.py with python3
INFO:root:Allowed origins are:
Verified 2.3ubuntu0.1 on Focal (checking reproducibility with buggy
version first):
root@ff-uu-1-verify:~# apt list --upgradable
Listing... Done
open-vm-tools/focal-updates 2:11.1.0-2~ubuntu20.04.1 amd64 [upgradable from:
2:11.0.5-4]
N: There is 1 additional version. Please use the '-a' switch
It is actually APT that triggers the u-u runs, so if there is anything that can
be fixed around timing that can be done on APT.
I agree that it would be desired to download packages even on roaming laptops.
** Package changed: unattended-upgrades (Ubuntu) => apt (Ubuntu)
** Changed in: apt
You seem to be using ZFS on root (which is EXPERIMENTAL AFAIK).
...
update-initramfs: Generating /boot/initrd.img-5.4.0-41-generic
cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu
cryptsetup: WARNING: Couldn't determine root device
...
** Package changed: systemd (Ubuntu) =>
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades
What is the output of:
apt-config dump | grep Reboot
?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Those options can be overridden to match your preference. I for example
enable u-u on metered connections because the plan I use allows enough
traffic for that.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+
+ * Unattended-upgrades crashes when strict whitelist is enabled and
+ there is an update available.
+
+ [Test Case]
+
+ Set up a system with at least one updated package available:
+
+ $ lxc launch ubuntu:focal ff-uu-strict
+ Creating ff-uu-strict
+
** Also affects: unattended-upgrades (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1877769
Title:
The change in SELinux causing the failures:
https://github.com/SELinuxProject/selinux/commit/9eb9c9327563014ad6a807814e7975424642d5b9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
I have a freshly installed 20.10 system running on a 2012 MacBook Air
(MBA 5,2) and it is completely silent and cold when being idle:
rbalint@chaos:~$ sudo cpupower frequency-info
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have
I plan fixing the glibc failure together with other issues early next
week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1887919
Title:
autopkgtest failure with libselinux
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/amd64/g/glibc/20200717_023434_9a6a8@/log.gz
...
x86_64-linux-gnu-gcc-9 nss_files/files-service.c -c -std=gnu11 -fgnu89-inline
-pipe -O2 -g -O3 -Wall
Fixed at upstream at:
https://github.com/systemd/systemd/pull/16424
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Description changed:
The iptables package in Ubuntu already made the switch but it was
reverted in LP: #1843468 due to breaking reverse dependencies and
software not packaged in the Ubuntu Archive.
The switch of the default backend is also a preparation for making the
nftables
IMO this should be fixed in hints handling in autopkgtest-cloud and not
on per package basis. Obsolete tests should not be run.
** Also affects: autopkgtest-cloud
Importance: Undecided
Status: New
** Project changed: autopkgtest-cloud => auto-package-testing
--
You received this bug
And I agree that this is super annoying - for thousands of packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1887191
Title:
autopkgtest always fail on i386 for f
Public bug reported:
The iptables package in Ubuntu already made the switch but it was
reverted in LP: #1843468 due to breaking reverse dependencies and
software not packaged in the Ubuntu Archive.
The switch of the default backend is also a preparation for making the
nftables frontend to be the
I'm also uploading to Groovy so the SRU can be accepted according to the
process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846
Title:
hwdb: Mask rfkill event
Public bug reported:
In LP: #1877078 /etc/fstab has been removed from LXD images and now the
workaround also removing it in the test started failing . :-(
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
@xnox @juliank IMO there is no real need for different boot time and
post-boot governor.
I think where we would like to save power or be less noisy the
(possibly) faster boot does not have huge impact on user satisfaction.
I agree that fans should not be on all the time in laptops/desktops.
If
** Changed in: systemd (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1880258
Title:
Add trailing dot to make
BTW does it work in Core 20?
** Changed in: systemd (Ubuntu Focal)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: systemd (Ubuntu Groovy)
Status: New => Incomplete
--
You received this bug notification because you
Sorry, it may be a valid bug, but may need more triaging.
** Changed in: systemd (Ubuntu Bionic)
Status: Invalid => New
** Changed in: systemd (Ubuntu Focal)
Status: Invalid => New
** Changed in: systemd (Ubuntu Groovy)
Status: Invalid => New
--
You received this bug
So far this was unreproducible in an armhf lxc container running on arm64 host.
Do you have a reproducer for Ubuntu Classic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Works in Ubuntu Classic it seems.
Where are Ubuntu Core bugs tracked? Please reassign this but there.
** Changed in: systemd (Ubuntu Groovy)
Status: New => Invalid
** Changed in: systemd (Ubuntu Focal)
Status: New => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status:
The commit message removing ondemand.service has several bug references, too:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=65f46a7d14b335e5743350dbbc5b5ef1e72826f7
remove Ubuntu-specific ondemand.service
New processors handle scaling/throttling in internal firmware
@raharper I've forwarded the systemd fix for you with minimal tidying of
the commit message https://github.com/systemd/systemd/pull/16317
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: bcache-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-signed (Ubuntu
** Also affects: glibc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: btrfs-progs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu
ols (Ubuntu Groovy)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear
** Changed in: systemd (Ubuntu Focal)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear
I've committed the cherry-picked change to systemd's packaging repo and
it will be available in the next upload, probably in 2-3 weeks.
** Changed in: systemd (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch
Since the m6g-> a1 resizes are IMO not likely when also using btrfs I'm
marking this bug as low.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1883883
Title:
Public bug reported:
... that may prevent rebooting to systems without the same optimization.
This can be observed by on EC2 m6g instances:
$ sudo apt install libc6-lse
$ sudo update-initramfs -k all -u
$ unmkinitramfs /boot/initrd.img i
$ ls i/
bin conf cryptroot etc init lib run sbin
Also with the current fix - which is in itself is correct - only
optimized libpthread libraries end up in initramfs which may prevent
rebooting to systems without the same optimization.
I have opened LP: #1883883 to track that.
--
You received this bug notification because you are a member of
IMO this should go to -security as well because security updates can
trigger it easily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1880853
Title:
libc6-lse
Do you seem to observe https://github.com/systemd/systemd/issues/2941 ?
** Bug watch added: github.com/systemd/systemd/issues #2941
https://github.com/systemd/systemd/issues/2941
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
@panfaust I've already fixed it up and the second version still needs extra
annotation.
https://github.com/mvo5/unattended-upgrades/pull/277
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
The dpkg frontend starting earlier takes the lock until it is finished.
20.04's unattended-upgrades is much faster, BTW.
Unattended-upgrades gracefully stops when it gets the TERM signal, thus
it can be asked to quit, but I think it is not needed in 20.04 because
u-u became fast enough in
@raharper Thanks, I've uploaded the systemd fix to Groovy. Could you
please forward it to upstream?
Also please update bcache-tools since it is Server Team's package and I
also can't upload to Debian until the next keyring refresh.
--
You received this bug notification because you are a member
** Also affects: unattended-upgrades (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: unattended-upgrades (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
We discussed that with @juliank and we agreed that APT should not let
this cross-grading happen without confirmation at least thus the most
generic fix would be in autopkgtest.
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
Maybe APT should not consider crossgrading a package as a removal and
APT should be fixed instead of autopkgtest:
root@gg-libyaml:~# apt install gzip:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
201 - 300 of 1375 matches
Mail list logo
