Public bug reported:
When I try to execute `do-release-upgrade -d` on a 20.04 system, the
following fatal error occured.
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-yqb1e837/jammy", line 8, in
sys.exit(main())
File
FYI, a possible regression for 20.10.x:
https://github.com/moby/moby/issues/41831
** Bug watch added: github.com/moby/moby/issues #41831
https://github.com/moby/moby/issues/41831
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925827
Title:
[v247] backport routing policy rule fix
To manage notifications about this
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925827
Title:
[v247] backport routing policy rule fix
To manage notifications about this
Per my testing, restart systemd-networkd is also affected.
Debian maintainer refused to apply my backport due to patch size.
https://github.com/systemd/systemd-stable/pull/96
That’s fair.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> I'm able to reproduce this on hirsute, but not groovy, so this seems to
> affect only hirsute; please correct me if that's wrong.
That’s correct.
> only 'networkctl reload' doesn't work, normal systemd-networkd startup works
`systemctl restart systemd-networkd` doesn’t work either.
--
You
Public bug reported:
The original issue can be found at
https://github.com/systemd/systemd/issues/18107.
I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96)
against v247-stable branch, which got merged and released in v247.4.
However due to the freezing state of Debian
Public bug reported:
When I look at the dbx revocation database for amd64 architecture, I
noticed that the dbxupdate shipped by Ubuntu is significantly smaller
than dbxupdate downloaded from UEFI forum website.
The revocation list (2020-10-12) published on UEFI forum website
contains the
The patch for this issue is already shipped in 4.3-3. However there is
no binary release for groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902490
Title:
systemtap not usable on groovy
To
Public bug reported:
Same issue as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972247
It seems that Ubuntu released a new version of systemtap for hirsute
only. Groovy is also affected.
** Affects: systemtap (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
And https://github.com/systemd/systemd/pull/16881
Not available in systemd-stable v246 yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897365
Title:
RoutingPolicyRule not applied on reconfigure
Public bug reported:
I noticed some error message from systemd-networkd in log journal.
systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring:
AF_INETpriority=28fwmark=28/0
This appears to be a known issue at
https://github.com/systemd/systemd/issues/16784
Fix is available at
Public bug reported:
I ran into this issue when doing AES decryption. Decrypted content
cannot be garbage-collected.
Upstream issue: https://github.com/Legrandin/pycryptodome/issues/372
Upstream fix:
https://github.com/Legrandin/pycryptodome/commit/05979c919430139810e5a113bb9f611332db51e5
**
workaround: install python3-cffi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876059
Title:
memory leak
To manage notifications about this bug go to:
filed an upstream issue
** Bug watch added: github.com/systemd/systemd/issues #13882
https://github.com/systemd/systemd/issues/13882
** Changed in: systemd
Status: Fix Released => Unknown
** Changed in: systemd
Remote watch: github.com/systemd/systemd/issues #12886 =>
kernel log is not needed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847946
Title:
initramfs contains modprobe blacklist
Public bug reported:
# lsinitramfs /boot/initrd.img-5.3.0-18-generic | fgrep usr/lib/modprobe.d
usr/lib/modprobe.d
usr/lib/modprobe.d/aliases.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-13-generic.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-17-generic.conf
For my installation, I found that dnsmasq is running with -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new arguments.
/etc/dnsmasq.d/libvirt-daemon specified bind-interfaces, causing dnsmasq
trying to bind to each interface on startup, which was unfortunately not
available yet.
Comment out the
This issue also affects 18.04 LTS with systemd 237-3ubuntu10.29
A VLAN interface with LinkLocalAddressing=no configured is not honored
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845909
Title:
After upgraded to Ubuntu 19.10 with systemd 242-6ubuntu1, the issue I
encountered disappeared.
```
# ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever
I'm running Ubuntu 19.04 with systemd 240-6ubuntu5.7
systemd-networkd configuration:
```
# eno1.network
[Match]
Name=eno1
[Link]
Multicast=no
[Network]
LinkLocalAddressing=no
Address=192.168.50.249/24
Gateway=192.168.50.1
DNS=192.168.50.1
VLAN=pppoe
# pppoe.netdev
[NetDev]
Name=pppoe
Kind=vlan
Emm, I think the issue I referenced above is an incorrect one.
https://github.com/systemd/systemd/issues/9890
&
https://github.com/systemd/systemd/pull/11423
I think `debian/patches/networkd-honour-LinkLocalAddressing.patch` might
be an incorrect backport of this upstream bug.
** Bug watch
Public bug reported:
upstream issue: https://github.com/systemd/systemd/issues/12886
upstream patch: https://github.com/systemd/systemd/pull/13565
The upstream fix will be available in systemd 244.
Backport please. Thanks.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status:
This bug still exists in 19.04 Disco. Please fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692353
Title:
systemd-fsckd : useless CR displayed on console
To manage notifications about this
I'm expecting the documented behavior. Please refer Bug #889936
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760140
Title:
HOME environmental variable no long preserved with sudo by default
To
25 matches
Mail list logo
