** Description changed:
+ [Impact]
+
+ This bug makes it more difficult for Wayland users to report bugs with
+ apport. When a Wayland user tries to use the -w,--window option, apport
+ fails silently. We do not want users to face a high barrier to
+ submitting bug reports.
+
+ The patch for
** Patch added: "apport-lp-1952947-impish.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561447/+files/apport-lp-1952947-impish.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
This requires a merge because there are changes in the Ubuntu version
not present in the Debian version.
** Affects: procps (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: In Progress
** Changed in: procps (Ubuntu)
Assignee
background).
** Changed in: procps (Ubuntu)
Status: In Progress => Confirmed
** Changed in: procps (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps
** Patch added: "Diff from Debian"
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+attachment/5562751/+files/procps-3.3.17-6-to-3.3.17-6ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps
Oh yes, of course. I will remember next time. Thank you for reviewing
and sponsoring this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1961805
Title:
Please merge
** Tags added: fr-2073
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1961805
Title:
Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
Status in procps
** Description changed:
+ [Impact]
+
+ The systemd shutdown sequence does not honor systemd-system.conf
+ settings when waiting for remaining processes. This means that, for
+ example, if a systemd service specifies KillMode=process and a process
+ remaining from that service does not properly
I tested the -proposed packages on focal (tested apport
2.20.11-0ubuntu27.22) and impish (tested apport 2.20.11-0ubuntu71.1)
using the test plan above. In both cases, the fix worked as expected.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added:
These errors appear to be coming from the udev rules in
/lib/udev/rules.d/66-snapd-autoimport.rules. I also see the errors on my
system, but I have not experienced any other problems as a result.
Jimmy or Jiwei, can you please tell us how you came across these logs?
What other problem(s) did you
After speaking with snapd folks, it was determined that these udev rules
should not be triggered on desktop or server (and in fact, should be
limited to removable media). The proper solution here is to improve the
snapd auto-import udev rules.
Given that, we do not need to make any changes to
I tested systemd 248.3-1ubuntu8.4 from impish-proposed to verify the
fix:
$ systemctl --version
systemd 248 (248.3-1ubuntu8.4)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL
+ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP
-LIBFDISK +PCRE2
In the near term, we could consider tweaking the systemd-oomd defaults
in Ubuntu. According to the commit that added systemd-oomd in Jammy [1],
the current config is based on Fedora's. This includes using the default
value of SwapUsedLimit=90% [2]. However, Fedora has more swap space by
default: a
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a
Public bug reported:
This build log provides an example of the problem:
https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz.
During setup for tests-in-lxd, an attempt is made to purge snapd, but
this fails:
[ ... ]
Purging
** Patch added: "systemd-lp-1967576.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1967576/+attachment/5575869/+files/systemd-lp-1967576.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
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/1966381
Title:
systemd-o
I tested apport 2.20.11-0ubuntu27.23 from focal-proposed using the test
plan above to confirm the fix.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I tested systemd 245.4-4ubuntu3.16 from focal-proposed using the test
plan above. I observed that the loop-ignore-sigterm.service processes
were killed after ~20s on shutdown, which is what I configured in
/etc/systemd/system.conf.
** Tags removed: verification-needed-focal
** Tags added:
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions.
This change is verified by the fact that the systemd
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1955997
Title:
The airplane hotkey has no function on
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1958284
Title:
shutdown hangs at "Waiting for
I tested systemd 245.4-4ubuntu3.16 from focal-proposed using the test
plan above to confirm this fix.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I am not sure (I am not directly involved with snapd), but I can ask
someone to take a look.
--
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/1966203
Title:
Syslog shows
** Tags added: rls-jj-incoming
--
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/1926860
Title:
XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
Status
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1952947
Title:
ubuntu-bug -w (using xprop) doesn't
Hi Jeremy,
Thank you for clarifying how you performed the verification testing.
Since the 248.3-1ubuntu8.5 upload only contained an autopkgtest fix,
your verification against 248.3-1ubuntu8.4 still stands.
** Tags removed: verification-needed verification-needed-impish
** Tags added:
** Package changed: systemd (Ubuntu) => linux (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/2034068
Title:
Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia
The support for deb822 in software-properties is actively being
developed.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The deprecation of systemd-udev-settle.service has been in place since
at least v243[1], and upstream OpenZFS has been tracking this for a few
years[2].
I don't think anything should change in systemd WRT the deprecation
notice.
[1]
> All I am asking is to add the patch/fix to the latest LTS ubuntu
version.
In order to be able to help with that and prioritize this, we need to
know exactly what your trouble is and how to reproduce it.
> For the exact problem statement and steps to reproduce plz use this
ticket
** Changed in: systemd (Ubuntu)
Status: Confirmed => 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/2030505
Title:
on ubuntu 22.04 systemd fails with per
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
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/2033325
Title:
systemd fails to set unit as
We will definitely need to fix this in Jammy, but I am not sure it makes
sense to do so in Mantic given the state of x11 keymap support (see bug
2030788).
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Importance:
We should really address the root of this problem instead of continuing
to patch src:systemd.
--
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/2035122
Title:
Under ubuntu
Okay, so looking again at the diff from 249.11-0ubuntu3.9 to
249.11-0ubuntu3.10[1], the only udev change is a new symlink for nvme
devices. It seems very unlikely that this is related. The only other
change that would be suspicious to me is the systemd.postinst change,
i.e. requesting a reboot for
I have verified the fix on Lunar using 252.5-2ubuntu3.1 from lunar-
proposed:
nr@clean-lunar-amd64:~$ apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3
Candidate: 252.5-2ubuntu3.1
Version table:
252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu
I have verified the fix on Lunar using udev 252.5-2ubuntu3.1 from lunar-
proposed:
ubuntu@ubuntu:~$ apt-cache policy udev
udev:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
*** 252.5-2ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main
I have verified the fix using systemd 249.11-0ubuntu3.10 from jammy-
proposed:
The VM and test networks are already configured on my system:
nr@six:/t/tmp.jTS3wdPdT3$ virsh list
Id NameState
---
8clean-jammy-amd64 running
I have verified the fix using systemd 252.5-2ubuntu3.1 from lunar-
proposed:
The VM and test networks are already configured on my system:
nr@six:/t/tmp.jTS3wdPdT3$ virsh list
Id NameState
---
9clean-lunar-amd64 running
I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:
nr@clean-jammy-amd64:~$ apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.9
Candidate: 249.11-0ubuntu3.10
Version table:
249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu
I have verified the fix using udev 249.11-0ubuntu3.10 from jammy-
proposed:
ubuntu@ubuntu:~$ apt-cache policy udev
udev:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main
I have verified the fix on Lunar using systemd 252.5-2ubuntu3.1 from
lunar-proposed:
root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
*** 252.5-2ubuntu3.1 500
500
Looking at the test history for systemd
(https://autopkgtest.ubuntu.com/packages/systemd), tests-in-lxd is
passing on all arches for 252.5-2ubuntu3.1 (Lunar), and for
249.11-0ubuntu3.10 (Jammy).
** Tags removed: verification-needed verification-needed-jammy
verification-needed-lunar
** Tags
The ppc64el build of systemd 252.5-2ubuntu3.1
(https://launchpad.net/ubuntu/+source/systemd/252.5-2ubuntu3.1/+build/26537841
succeeded), with all built-time tests and fuzzers passing.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done
I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:
root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500
This looks like a user/privileges issue:
Setting up systemd-oomd (249.11-0ubuntu3.9) ...
Your account has expired; please contact your system administrator.
chfn: PAM: Authentication failure
adduser: `/bin/chfn -f systemd Userspace OOM Killer systemd-oom' returned error
code 1. Exiting.
Can you please elaborate on the issue you are experiencing, and provide
steps for someone else to reproduce the problem?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification
I believe this is the relevant part from test-execute:
1739s exec-dynamicuser-statedir.service: About to execute: /usr/bin/sh -x -c
'test $$(find / \( -path /var/tmp -o -path /tmp -o -path /proc -o -path
/dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf -o -path /dev/.lxc \) -prune
-o -type d
The Europe/Kiev symlink is now in tzdata-legacy, so we can just depend
on that for these autopkgtests.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
: systemd (Ubuntu)
Importance: High
Assignee: Nick Rosbrook (enr0n)
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification becau
We are well past feature freeze for Mantic
(https://wiki.ubuntu.com/ManticMinotaur/ReleaseSchedule). We will have
v254 (or potentially v255) for 24.04.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags added: foundations-todo
--
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/1837227
Title:
systemd mount units fail during boot, while file system is correctly
** Tags removed: systemd-sru-next
--
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/2025382
Title:
22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)
Status in systemd
** Changed in: systemd (Ubuntu Mantic)
Status: Confirmed => 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/2038894
Title:
Ubuntu 23.10 cloud images
** Description changed:
+ [Impact]
+
+ In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP
+ listening port 5353.
+
+ By default and by policy, aside from port 22 there should be no other
+ open ports on Ubuntu cloud images. Listening port 5353 is a regression.
+
+ [Test Plan]
The test case with removing kexec-tools before rebooting works for me.
But I can only reproduce the issue by doing that. Can you share more
about your setup so we can understand why exactly you hit this?
I think that having this fallback makes sense, and is fine for an SRU,
but it would be good
** Description changed:
+ [Impact]
+
+ Using systemd-resolved to resolve a hostname which has more than 8 CNAME
+ redirects will fail because of the hard-coded limit. While this case is
+ somewhat rare, the original reporter demonstrated a real-world scenario
+ where this happened (although that
I have verified the fix using systemd-resolved 253.5-1ubuntu6.1 from
mantic-proposed:
root@mantic:~# apt policy systemd-resolved
systemd-resolved:
Installed: 253.5-1ubuntu6.1
Candidate: 253.5-1ubuntu6.1
Version table:
*** 253.5-1ubuntu6.1 500
500 http://security.ubuntu.com/ubuntu
The autopkgtest failures were resolved with retries.
--
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/2038894
Title:
Ubuntu 23.10 cloud images unexpected UDP listening port
** Changed in: systemd (Ubuntu Noble)
Status: New => Fix Committed
--
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/2038894
Title:
Ubuntu 23.10 cloud images
cgroupsv2 has been the default for a few releases now, so it's odd that
you are running cgroupsv1. Can you share /proc/cmdline? I haven't looked
close enough to see if this would actually cause this error, but since
this error seems odd as it is, I wouldn't be surprised.
--
You received this bug
Because upgrades are not enabled yet for mantic -> noble, we still
cannot explicitly verify the XDG_SESSION_TYPE fix for mantic. However,
(a) since this exact patch was verified for lunar -> mantic, (b) this
patch relates to upgrading *from* mantic rather than *to* mantic, and
(c) we do not want
** Also affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2039743
Title:
Intermittent DHCP
** Changed in: systemd (Ubuntu)
Status: New => 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/2038897
Title:
systemd-resolved: not all records flushed when
** 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/1791102
Title:
udev postinst fails because kvm group
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Low
--
I confirmed this issue on 22.04 using the reproducer in the original
description. I agree that [1] looks like the appropriate upstream bug.
In fact, we currently skip a test in Jammy's autopkgtest due to this
issue [2]. Unfortunately, the fix doesn't apply to v249.11 without [3],
and I'm not sure
o this
bug which was uploaded in 1:23.10.11.
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Assignee: Gunnar Hjalmarsson (gunnarhj) => Nick Rosbrook (enr0n)
--
You received this
*** This bug is a duplicate of bug 2036358 ***
https://bugs.launchpad.net/bugs/2036358
** This bug has been marked a duplicate of bug 2036358
systemd wait-online now times out after jammy and lunar upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch
Robert - are you on on desktop or server? If the links are not managed
by systemd-networkd, it seems like you would be running NetworkManager?
What does this show for you?
$ systemctl status systemd-networkd
$ systemctl status NetworkManager
--
You received this bug notification because you are
If you are using NetworkManager, then systemd-networkd.service (and
associated units like systemd-networkd-wait-online.service) should NOT
be enabled. With the caveat that I am not sure why you have systemd-
networkd enabled in the first place, I would recommend that you simply
disable it:
$
for the wwan device), then I recommend that you simply
disable systemd-networkd:
$ systemctl disable --now systemd-networkd.service
This will also disable associated units such as systemd-networkd-wait-
online.target.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbr
Tais - you should not have both services running. For you the solution
should be:
$ systemctl disable --now systemd-networkd.service
This will also disable associated units, including systemd-networkd-
wait-online.service.
** Description changed:
+ [NOTE]
+
+ If you are running a desktop
** Description changed:
[NOTE]
If you are running a desktop system and you see this issue, you should
run:
$ systemctl disable --now systemd-networkd.service
This will disable systemd-networkd and associated units, including
systemd-networkd-wait-online.service.
The issue is that those flags are pretty new, so v253 does not make use
of them. Current upstream systemd will try to use them if available[1].
Since this is just a warning from the kernel[2], and since we are late
in the Mantic cycle, I do not think there is justification to fix this
in systemd.
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Jammy)
Importance:
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Is this affecting your system in any way? Or are you just reporting the
fact that a message is logged?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member
This is a result of us moving PPA sources to deb822 for this cycle. As a
workaround, please use this syntax instead:
$ apt-add-repository ppa:nrbrtx/vte
This is really much nicer than specifying the whole deb line anyways. I
think we should just remove support for the "add by line" syntax since
I believe the remaining autopkgtest failures are unrelated.
For lunar[1], we have ubuntu-drivers-common failing on ppc64el[2]. We
can see the same failure on a different test run without a systemd
trigger[3].
For jammy[4], we have linux-nvidia[5] and linux-nvidia-tegra-igx[6],
each failing
I have uploaded the fix. I am adding block-proposed so that I can do
another test, i.e. do-release-upgrade -d -p, just because the manual way
of testing differs slightly.
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added:
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in
For the near term, I am working on adapting Gunnar's existing work in a
way that we restore the font on the next boot after the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/452304
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
Taking a quick look at the logs for arm64,
https://autopkgtest.ubuntu.com/packages/systemd/mantic/arm64, I only see
this specific failure for newer kernels. Have you tried to reproduce
this locally to see if it is in fact introduced by a kernel change?
--
You received this bug notification
Thanks for your report. We have seen a similar report in bug 2036358.
Before I mark it as duplicate, can you please provide output from the
following commands:
$ networkctl
$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
** Changed in: systemd (Ubuntu)
*** This bug is a duplicate of bug 2036358 ***
https://bugs.launchpad.net/bugs/2036358
Thanks for the additional information. I am going to mark this bug as a
duplicate to consolidate.
** This bug has been marked a duplicate of bug 2036358
systemd wait-online now times out after jammy and
ee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Lunar)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
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.ne
I will work on re-instating the previous patch in some fashion to fix
this bug without regressing 1982218.
--
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/2036358
Title:
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
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/2035778
Title:
upstream autopkgtests fail to build
** Description changed:
+ [Impact]
+
+ When all interfaces "not required for online", e.g. when they are marked
+ "optional: true" in netplan, systemd-networkd-wait-online will timeout.
+ Or, in other words, systemd-networkd-wait-online will timeout even
+ though all interfaces are ignored,
I have verified the fix using systemd 252.5-2ubuntu3.2 in lunar-
proposed:
Creating a fresh container:
nr@six:~$ lxc launch ubuntu-daily:lunar lunar
Creating lunar
Starting lunar
nr@six:~$ lxc exec lunar bash
In the container, after enabling -proposed:
1 - 100 of 823 matches
Mail list logo
