[Touch-packages] [Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Seems its not "low importance" bug. 洛 Updating systemd package can trigger such bug, and if you have a unattended-upgrade it's gonna cause a network flap on that host. Easy to reproduce it with: # apt install --reinstall systemd -- Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy systemd 249 (249.11-0ubuntu3.9) -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028191] Re: curl breaks by installing libcurl4-openssl-dev=7.81.0-1ubuntu1.11
** Changed in: curl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2028191 Title: curl breaks by installing libcurl4-openssl-dev=7.81.0-1ubuntu1.11 Status in curl package in Ubuntu: Fix Released Bug description: On a brand new Ubuntu 22.04 server, running: sudo apt install curl libcurl4-openssl-dev will install curl version "7.81.0-1ubuntu1.11" and libcurl4-openssl-dev version "7.81.0-1ubuntu1.11". Installing libcurl4-openssl-dev version "7.81.0-1ubuntu1.11" breaks curl. Once that package is installed, curl no longer works against https endpoints. For example: # curl https://raw.githubusercontent.com curl: (60) SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. This problem is not exhibited in the previous version, "7.81.0-1ubuntu1.10". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcurl4-openssl-dev 7.81.0-1ubuntu1.11 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 19 19:20:21 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028191] Re: curl breaks by installing libcurl4-openssl-dev=7.81.0-1ubuntu1.11
Same issue https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028170 Seems to fixed in curl (7.81.0-1ubuntu1.13). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2028191 Title: curl breaks by installing libcurl4-openssl-dev=7.81.0-1ubuntu1.11 Status in curl package in Ubuntu: Confirmed Bug description: On a brand new Ubuntu 22.04 server, running: sudo apt install curl libcurl4-openssl-dev will install curl version "7.81.0-1ubuntu1.11" and libcurl4-openssl-dev version "7.81.0-1ubuntu1.11". Installing libcurl4-openssl-dev version "7.81.0-1ubuntu1.11" breaks curl. Once that package is installed, curl no longer works against https endpoints. For example: # curl https://raw.githubusercontent.com curl: (60) SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. This problem is not exhibited in the previous version, "7.81.0-1ubuntu1.10". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcurl4-openssl-dev 7.81.0-1ubuntu1.11 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jul 19 19:20:21 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
Same problem here but with strange behaviour with bond interface. All slaves was release from bond and after reloading bond stay without any slave links. dmesg logs bond-xe2: (slave eth4): Releasing backup interface bond-xe2: (slave eth5): Removing an active aggregator bond-xe2: (slave eth5): Releasing backup interface # cat /proc/net/bonding/bond-xe2 Ethernet Channel Bonding Driver: v5.19.0-35-generic Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer3+4 (1) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info LACP active: on LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: da:74:dc:e2:48:b4 bond bond-xe2 has no active aggregator After running networkctl reload, bond enslave links and all start working correct. -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
@brian-murray Hi. Tested that build, all seems fine, still no memory leak. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status Test was performed like i was describe at original post, i run chef- client and it start checking for all .service and .timers units, and it cause memory leak, after upgrade no mem leak. ** 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] pid1 leaks memory when rebuilding unit path cache [test case] see original description. also, the patch contains an example of how to reproduce: $ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service ~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user start test$(printf %04d $i).service;done [regression] any problems would occur when rebuilding the path cache, possibly resulting in memory leaks or pid1 crashes. [scope] this is needed only in f fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is included in v246, so fixed in h and later the code in b is very different and doesn't appear to have the leak, per original report [original description] Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
Yep, i checked on friday and no memory leak since then. Version of package and source repository: # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.12 Candidate: 245.4-4ubuntu3.12 Version table: *** 245.4-4ubuntu3.12 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages Test was performed like i was describe at original post, i run chef- client and it start checking for all .service and .timers units, and it cause memory leak, after upgrade no mem leak. ** 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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] pid1 leaks memory when rebuilding unit path cache [test case] see original description. also, the patch contains an example of how to reproduce: $ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service ~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user start test$(printf %04d $i).service;done [regression] any problems would occur when rebuilding the path cache, possibly resulting in memory leaks or pid1 crashes. [scope] this is needed only in f fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is included in v246, so fixed in h and later the code in b is very different and doesn't appear to have the leak, per original report [original description] Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
Thanks for answering! Yep, that build fixed leak for me. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.12~202108090622~ubuntu20.04.1 This build will be used for official systemd-245.4-4ubuntu3.12 package ? -- 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/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
Just checked again, bug still exist for latest systemd package on focal. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.11 -- 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/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
** Attachment added: "pmap_pid1_focal" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+attachment/5509911/+files/pmap_pid1_focal ** Description changed: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. + All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. - + Environment: - Distributor ID: Ubuntu - Description:Ubuntu 20.04.2 LTS - Release:20.04 - Codename: focal - Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 + Distributor ID: Ubuntu + Description:Ubuntu 20.04.2 LTS + Release:20.04 + Codename: focal + Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: - systemd: - Installed: 245.4-4ubuntu3.7 + systemd: + Installed: 245.4-4ubuntu3.7 ** Tags added: pid1 -- 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/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] [NEW] systemd pid 1 memory leak
Public bug reported: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: pid1 systemd ** Attachment added: "pid1 strace focal" https://bugs.launchpad.net/bugs/1935051/+attachment/5509910/+files/pid1_strace_focal -- 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/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp