[Touch-packages] [Bug 1890913] Re: init is using 100% of processor
*** 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 member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890913 Title: init is using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
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 watch added: github.com/systemd/systemd/issues #16669 https://github.com/systemd/systemd/issues/16669 -- 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 apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process
[Touch-packages] [Bug 1890913] Re: init is using 100% of processor
*** 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 https://github.com/systemd/systemd/issues/16669 -- 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 using 100% of processor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+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 1895293] Re: After last upgrade systemd uses 100% CPU
*** 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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895293 Title: After last upgrade systemd uses 100% CPU Status in systemd package in Ubuntu: New Bug description: I'm not sure, but none of the already reported bugs seems to fit. At shutdown I get for a moment many messages concerning "automatic report enabled but not possible" (roughly) and after showing these the shutdown lasts about one Minute. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: openafs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 11 14:30:32 2020 InstallationDate: Installed on 2020-09-01 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=8d55d30d-adfe-4f99-9e71-193677d1ec1e ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.asset.tag: CZC4123JXT dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC4123JXT dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895293/+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 1895631] Re: systemd at 100% handling apport failures
*** 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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895631 Title: systemd at 100% handling apport failures Status in systemd package in Ubuntu: Confirmed Bug description: systemd is pegged at 100% after booting Groovy Desktop. Seems like an apport-report.service issue: Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 15 08:01:50 lenovo systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 15 08:01:50 lenovo systemd[1]: apport-autoreport.service: Start request repeated too quickly. I removed apport to resolve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895631/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
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] PathExistsGlob=/var/crash/*.crash [Install] WantedBy=paths.target # cat /lib/systemd/system/apport-autoreport.service [Unit] Description=Process error reports when automatic reporting is enabled ConditionPathExists=/var/lib/apport/autoreport Wants=whoopsie.service After=whoopsie.service [Service] Type=oneshot ExecStart=/usr/share/apport/whoopsie-upload-all If the service succeeds there is no reason for systemd to not restart it. IMO apport should check the files once after the boot finised and monitor /var/crash/ for _changes_ only while the system is running. I still check if something could be done on systemd side. -- 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 apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated
[Touch-packages] [Bug 1894195] Re: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)
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 merge the new upstream from Debian, but they could not find time for that AFAIK. I\m +1 on the FFe, but someone still needs to actually do the merge and landing. -- 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/1894195 Title: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main) Status in iptables package in Ubuntu: New Bug description: Please merge iptables 1.8.5-3 (main) from Debian sid (main) Explanation of FeatureFreeze exception: Current iptables is using the same upstream version in focal, which had problems with the nft backend and was then reverted to the legacy backend. 1.8.5 has many fixes for the nft backend. For example these Debian bugs are fixed in 1.8.5: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961117 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968457 Please merge it. Changelog entries since current groovy version 1.8.4-3ubuntu3: iptables (1.8.5-3) unstable; urgency=medium * [2d587e5] src:iptables: bump build-dep version on libnftnl to 1.1.6 -- Arturo Borrero Gonzalez Tue, 25 Aug 2020 11:56:55 +0200 iptables (1.8.5-2) unstable; urgency=medium [ Alberto Molina Coballes ] * [d90516d] d/control: modify breaks and replaces fields (Closes: #949576) * [4754a45] d/not-installed: arch independ files * [780330f] d/tests/control: Run iptables-legacy-* tests explicitly [ Arturo Borrero Gonzalez ] * [6fb6557] d/patches: add -upstream-fix-xtables-translate.patch (Closes: #962724) -- Arturo Borrero Gonzalez Wed, 24 Jun 2020 10:56:19 +0200 iptables (1.8.5-1) unstable; urgency=medium [ Debian Janitor ] * [c3deeb3] Wrap long lines in changelog entries: 1.8.2-1, 1.8.0-1~exp1, 1.6.0-1. * [214468e] Update standards version to 4.5.0, no changes needed. [ Arturo Borrero Gonzalez ] * [eb1d7c5] New upstream version 1.8.5 (Closes: #950535) * [7a119db] d/patches: drop all patches * [ec63c87] libxtables12.symbols: add new symbol * [4056ce6] iptables: bump debhelper-compat to 13 -- Arturo Borrero Gonzalez Thu, 04 Jun 2020 13:33:22 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+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 1894195] Re: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)
** 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 iptables in Ubuntu. https://bugs.launchpad.net/bugs/1894195 Title: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main) Status in iptables package in Ubuntu: New Bug description: Please merge iptables 1.8.5-3 (main) from Debian sid (main) Explanation of FeatureFreeze exception: Current iptables is using the same upstream version in focal, which had problems with the nft backend and was then reverted to the legacy backend. 1.8.5 has many fixes for the nft backend. For example these Debian bugs are fixed in 1.8.5: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961117 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968457 Please merge it. Changelog entries since current groovy version 1.8.4-3ubuntu3: iptables (1.8.5-3) unstable; urgency=medium * [2d587e5] src:iptables: bump build-dep version on libnftnl to 1.1.6 -- Arturo Borrero Gonzalez Tue, 25 Aug 2020 11:56:55 +0200 iptables (1.8.5-2) unstable; urgency=medium [ Alberto Molina Coballes ] * [d90516d] d/control: modify breaks and replaces fields (Closes: #949576) * [4754a45] d/not-installed: arch independ files * [780330f] d/tests/control: Run iptables-legacy-* tests explicitly [ Arturo Borrero Gonzalez ] * [6fb6557] d/patches: add -upstream-fix-xtables-translate.patch (Closes: #962724) -- Arturo Borrero Gonzalez Wed, 24 Jun 2020 10:56:19 +0200 iptables (1.8.5-1) unstable; urgency=medium [ Debian Janitor ] * [c3deeb3] Wrap long lines in changelog entries: 1.8.2-1, 1.8.0-1~exp1, 1.6.0-1. * [214468e] Update standards version to 4.5.0, no changes needed. [ Arturo Borrero Gonzalez ] * [eb1d7c5] New upstream version 1.8.5 (Closes: #950535) * [7a119db] d/patches: drop all patches * [ec63c87] libxtables12.symbols: add new symbol * [4056ce6] iptables: bump debhelper-compat to 13 -- Arturo Borrero Gonzalez Thu, 04 Jun 2020 13:33:22 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** 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 apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.s
[Touch-packages] [Bug 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x
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 autopkgtest fails in groovy on s390x Status in systemd package in Ubuntu: New Bug description: 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 (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@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. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to:
[Touch-packages] [Bug 1895576] [NEW] boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x
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 (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- 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 autopkgtest fails in groovy on s390x Status in systemd package in Ubuntu: New Bug description: 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 (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@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 hint for it for now. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We
[Touch-packages] [Bug 1877078] Re: Please ship empty /etc/fstab in LXD images
** 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 Status in livecd-rootfs package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: Systemd boots degraded because of the invalid content of /etc/fstab: $ lxc shell gg-test root@gg-test:~# systemctl is-system-running degraded root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 1 loaded units listed. root@gg-test:~# cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 root@gg-test:~# echo "" > /etc/fstab root@gg-test:~# reboot Session terminated, killing shell... ...killed. rbalint@yogi:~$ lxc shell gg-test root@gg-test:~# systemctl is-system-running running root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. Not shipping is also fixing the issue, but some programs (such as systemd autopkgtes) reads fstab and a missing fstab should be special-cased, thus that would cause more breakages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1877078/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
** 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 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: Fix Released Bug description: 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 alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1893899] Re: update alsa/audio related infomation collection code in apport
** 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. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio related infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
@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 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 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: 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 alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1843468] Re: nftables based iptables wrapper break userspace
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 Status in iptables package in Ubuntu: Fix Released Bug description: iptables just got replaced by the nftables wrappers, effectively changing all Ubuntu systems to using nftables rather than regular iptables/ip6tables/ebtables. Unfortunately those wrappers aren't perfect and don't convert every option properly, nor know about some of the available plugins for those commands. This means that unless the software using those commands are aware that those are wrappers and adapt their use, they may break at some random point in time. While nftables is clearly the way forward, just silently switching the existing native tools with the compat wrappers will lead to widespread breakage both from packages in the archive, snaps and a variety of scripts our users may be running. So far, looking around, known breakages post-nft are expected with at least Docker, Kubernetes and LXD but the same may be true with the many other packages we have that call iptables, ip6tables, ebtables or arptables today. A migration should include a proper audit of all in-archive users, see if they have a plan/patch for native nft interaction and if not, validate their use of the tools is compatible with the wrappers. We should also extend that to popular snaps / those we ship by default. Snaps make things worse as they use the tools from their base snap, which in LXD's case is currently 16.04 (soon to switch to 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1843468/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
@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. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: 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 alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1893958] [NEW] [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
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 alternative priority and prefer nftables backend over legacy (LP: #1887186) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Attachment added: "iptables_1.8.4-3ubuntu3.diff" https://bugs.launchpad.net/bugs/1893958/+attachment/5407008/+files/iptables_1.8.4-3ubuntu3.diff ** Description changed: 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 alternative priority and prefer nftables backend over legacy + (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/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: 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 alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1887186] Re: Please switch to nftables as the default backend
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: Confirmed Bug description: 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 preferred tool for interfacing the Netfilter framework, thus please Recommend: it. Inclusion of the nftables package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+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 1893889] Re: unattended-upgrade of nova-common failure due to conffile prompt
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, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1893889 Title: unattended-upgrade of nova-common failure due to conffile prompt Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: unattended-upgrades attempted to upgrade nova from 2:17.0.9-0ubuntu1 to 2:17.0.10-0ubuntu2.1 (bionic-security), however nova-common contains a modified conffile (/etc/nova/nova.conf) which prompts during upgrade and leaves apt/dpkg in a permanent error state requiring manual intervention. It also prevents other automated apt install operations from working while in this state. I understand that this conffile prompt is a generally known problem and that unattended-upgrades specifically attempts to skip upgrades that have such a conffile prompt, however that did not work on this case. I am filing this bug to try and identify and resolve the cause and this affected multiple systems in an Ubuntu OpenStack deployment. rbalint advised that this is very likely a more complex interaction with the exact upgrades that were being staged at the time and hence more logs would be needed, indeed attempting to reproduce this very simply with a downgrade of nova packages to 2:17.0.0-0ubuntu1 results in it being skipped, as expected: root@juju-c21ec6-bionic-nova-7:/home/ubuntu# unattended-upgrade Package nova-common has conffile prompt and needs to be upgraded manually And from the unattended-upgrades log we can see that 179 packages in total were scheduled to upgrade together during this run. Attaching the following logs files: /var/log/unattended-upgrades/* /var/log/dpkg* dpkg_-l (As at 2020-04-27 16:22, the same time period as the unattended-upgrades logs, but the dpkg.log* files were taken later but also cover the full time period from before 2019-12-28 and after 2020-04-27). The first instance of the failure is in unattended-upgrades.log.4.gz Line 161 "2019-12-28 06:15:29,837 Packages that will be upgraded: amd64-microcode... [truncated, 179 packages total]" That relates to the output in unattended-upgrades-dpkg.log.4.gz Line 791 "Log started: 2019-12-28 06:25:56" Which relates to the output of dpkg.log.6.gz Line 392 "2019-12-28 06:25:56 upgrade nova-compute-kvm:all 2:17.0.9-0ubuntu1 2:17.0.10-0ubuntu2.1" It fails many times after that as anytime you attempt to install a package, it attempts to configure nova.conf again and exits with an error again. But that is the original failure. But note that various package upgrades happened by unattended-upgrades (and possibly other sources) in the intervening 4 months and so I guess reproducing the situation may require reverse engineering the original package list from the dpkg logs. I have not currently attempted to do that with the hopes intimate knowledge of the unattended-upgrades code and logs will make that process faster. A full sosreport from the system is available if more information is required that will include other log files, and various other command outputs. It is not uploaded initially for privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+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 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
** 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 partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. [See the Rectification below] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+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 1880839] Re: Clock skew on testbeds
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 tests more reproducible but less similar to real installations's behavour. -- 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/1880839 Title: Clock skew on testbeds Status in Auto Package Testing: New Status in systemd package in Ubuntu: New Bug description: Clock stepped backward on a testbed: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/amd64/b/boost1.71/20200501_151103_1e387@/log.gz ... context FAIL stderr: make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future autopkgtest [13:55:37]: test context: - - - - - - - - - - stderr - - - - - - - - - - make[2]: Warning: File '/tmp/tmp.qPfGPM84a1/src/demo2.cpp' has modification time 0.52 s in the future make[2]: warning: Clock skew detected. Your build may be incomplete. .. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1880839/+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 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root
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 with useless error if /var is not owned by root Status in systemd package in Ubuntu: Incomplete Bug description: I just upgraded from 16.04 to 18.04. The upgrade broke. The error, from systemd, was: "Unsafe symlinks encountered in /var/log/journal, refusing." That directory was empty. The fix was "chmod root:root /var". Yes, it's weird that my /var wasn't owned by root, but upgrade breaking errors should say something useful. panic:~# chown darxus:darxus /var panic:~# dpkg-reconfigure systemd Unsafe symlinks encountered in /var/spool/rsyslog, refusing. Unsafe symlinks encountered in /var/lib/colord, refusing. Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Unsafe symlinks encountered in /var/cache/man, refusing. Unsafe symlinks encountered in /var/run/opendkim, refusing. Unsafe symlinks encountered in /var/lib/systemd, refusing. Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Unsafe symlinks encountered in /var/log/wtmp, refusing. Unsafe symlinks encountered in /var/log/btmp, refusing. Unsafe symlinks encountered in /var/log/lastlog, refusing. Unsafe symlinks encountered in /var/log, refusing. Unsafe symlinks encountered in /var/log/auth.log, refusing. Unsafe symlinks encountered in /var/log/mail.err, refusing. Unsafe symlinks encountered in /var/log/mail.log, refusing. Unsafe symlinks encountered in /var/log/kern.log, refusing. Unsafe symlinks encountered in /var/log/syslog, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing. panic:~# chown root:root /var panic:~# dpkg-reconfigure systemd I found the fix here: https://askubuntu.com/a/1095796 Showing that I'm not the only one encountering this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 Uname: Linux 5.6.14-x86_64-linode135 x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 Date: Wed Aug 12 15:58:33 2020 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro devtmpfs.mount=1 ProcModules: SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+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 1892130] Re: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22
*** 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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892130 Title: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz The testcase systemd-fsckd is falling with several kernels in Focal: == FAIL: test_fsck_with_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 100, in test_fsck_wi th_failure self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false == FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest) Ensure that a failing systemd-fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 114, in test_systemd_fsck_with_failure self.assertProcessKilled() File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 204, in assertProcessKilled self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892130/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@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 Title: autopkgtest success rate dropped inhibiting proposed migration Status in glib2.0 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in ntpsec package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1892358/+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 1877078] Re: Please ship empty /etc/fstab in LXD images
@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 which is not particularly beautiful, but not invalid at least. -- 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 Status in livecd-rootfs package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Bug description: Systemd boots degraded because of the invalid content of /etc/fstab: $ lxc shell gg-test root@gg-test:~# systemctl is-system-running degraded root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 1 loaded units listed. root@gg-test:~# cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 root@gg-test:~# echo "" > /etc/fstab root@gg-test:~# reboot Session terminated, killing shell... ...killed. rbalint@yogi:~$ lxc shell gg-test root@gg-test:~# systemctl is-system-running running root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. Not shipping is also fixing the issue, but some programs (such as systemd autopkgtes) reads fstab and a missing fstab should be special-cased, thus that would cause more breakages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1877078/+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 1877078] Re: Please ship empty /etc/fstab in LXD images
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 -0700 IMO LXD images should not contain invalid fstab and MAAS should be fixed. ** Changed in: livecd-rootfs (Ubuntu) Status: Fix Released => Triaged ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1877078 Title: Please ship empty /etc/fstab in LXD images Status in livecd-rootfs package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Bug description: Systemd boots degraded because of the invalid content of /etc/fstab: $ lxc shell gg-test root@gg-test:~# systemctl is-system-running degraded root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 1 loaded units listed. root@gg-test:~# cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 root@gg-test:~# echo "" > /etc/fstab root@gg-test:~# reboot Session terminated, killing shell... ...killed. rbalint@yogi:~$ lxc shell gg-test root@gg-test:~# systemctl is-system-running running root@gg-test:~# systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. Not shipping is also fixing the issue, but some programs (such as systemd autopkgtes) reads fstab and a missing fstab should be special-cased, thus that would cause more breakages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1877078/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in systemd package in Ubuntu: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892358/+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 1886886] Re: Plymouth 0.9.5 release
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, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886886 Title: Plymouth 0.9.5 release Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress Bug description: Plymouth 0.9.5 release: https://www.freedesktop.org/software/plymouth/releases/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1891716] Re: Networking broken after systemd update
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 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 Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: Unknown Bug description: # Description: After this upgrade in groovy, networking stopped working: Start-Date: 2020-08-14 17:02:50 Commandline: apt-get dist-upgrade --assume-yes Requested-By: ubuntu (1000) Install: motd-news-config:amd64 (11ubuntu11, automatic) Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. $ systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 2745 (code=exited, status=1/FAILURE) Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network
[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update
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 Status: Unknown -- 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 Status in systemd package in Ubuntu: In Progress Status in systemd package in Debian: Unknown Bug description: # Description: After this upgrade in groovy, networking stopped working: Start-Date: 2020-08-14 17:02:50 Commandline: apt-get dist-upgrade --assume-yes Requested-By: ubuntu (1000) Install: motd-news-config:amd64 (11ubuntu11, automatic) Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. $ systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 2745 (code=exited, status=1/FAILURE) Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 17:03:01 fulfilling-hornet
[Touch-packages] [Bug 1891716] Re: Networking broken after systemd update
** 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 Status in systemd package in Ubuntu: In Progress Bug description: # Description: After this upgrade in groovy, networking stopped working: Start-Date: 2020-08-14 17:02:50 Commandline: apt-get dist-upgrade --assume-yes Requested-By: ubuntu (1000) Install: motd-news-config:amd64 (11ubuntu11, automatic) Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. $ systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 2745 (code=exited, status=1/FAILURE) Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service. Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Stopped Network Service. Aug 14 17:03:01 fulfilling-hornet systemd[1]:
[Touch-packages] [Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
** 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, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Invalid Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+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 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
** 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 /run/systemd/resolve/*resolv.conf for every IPv6 RA received Status in systemd package in Ubuntu: New Bug description: # Issue description: On 2 Linode VMs that are used as lxd hosts, we noticed that /run/systemd/resolve/*resolv.conf were re-created quite frequently (~ once per second). We noticed because of the log noise from lxd's dnsmasq instance using inotify to watch the target of /etc/resolv.conf (which points to the stub-resolv.conf in our case). This was (wrongly) reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until it became apparent it was more likely to be a problem with systemd(-resolved)?. The log noise is the observable problem that would be nice to see addressed: root@lxd02:~# uptime 17:55:48 up 9:52, 1 user, load average: 0.18, 0.11, 0.05 root@lxd02:~# journalctl -b0 | grep -cF dnsmasq 158609 Upon further investigation, it seems that systemd-resolved re-creates the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is received. 1) One can observe that by setting systemd-resolved's service in debug mode: $ sudo systemctl edit systemd-resolved and in the editor that is opened, add and save this content: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then restart systemd-resolved and watch the logs scroll by with: $ journalctl -fu systemd-resolved 3) In another terminal, watch the files be recreated with: watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf 3) In yet another terminal, run a packet capture and watch "ICMP6, router advertisement" messages come by: sudo tcpdump -ni eth0 icmp6 You will see that every time a RA packet comes in, resolved's journal will log this: Aug 11 17:33:55 lxd02 systemd-resolved[15368]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/resolve1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=244 reply_cookie=0 signature=sa{sv}as error-name=n/a error- message=n/a And the stat monitoring terminal will blink to highlight the new inode and timestamps of the freshly replaced stub-resolv.conf file. # Additional information: root@lxd02:~# lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 root@lxd02:~# apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@lxd02:~# uname -a Linux lxd01 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891215/+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 1891527] Re: systemd unit tests need updates for Linux 5.8 and later
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1891527 Title: systemd unit tests need updates for Linux 5.8 and later Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Bug description: Linux 5.8 allows unprivileged creation of whiteout devices, causing a couple of test failures in systemd: == test-fs-util === /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, function test_touch_file(). Aborting. FAIL: test-fs-util (code: 134) ... == test-stat-util === Assertion 'stat(path, ) >= 0' failed at src/test/test-stat-util.c:126, function test_device_path_make_canonical_one(). Aborting. FAIL: test-stat-util (code: 134) test-fs-util succeeds in making a character device with major/minor 0,0, and thus assumes it will be able to create other devices, but it cannot. test-stat-util assumes that because /run/systemd/inaccessible/chr exists /run/systemd/inaccessible/blk should also exist, but it does not for the same reason. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1891527/+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 1891716] Re: Networking broken after systemd update
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update Status in systemd package in Ubuntu: New Bug description: # Description: After this upgrade in groovy, networking stopped working: Start-Date: 2020-08-14 17:02:50 Commandline: apt-get dist-upgrade --assume-yes Requested-By: ubuntu (1000) Install: motd-news-config:amd64 (11ubuntu11, automatic) Upgrade: libaudit-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. $ systemctl status systemd-networkd.service ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 2745 (code=exited, status=1/FAILURE) Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service. Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. Aug 14 17:03:01 fulfilling-ho
[Touch-packages] [Bug 1891867] Re: zfs not correctly imported at boot
** 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 package in Ubuntu: New Bug description: On a fresh and up-to-date Ubuntu 20.04 amd64 installation I configured two encrypted partitions on the same hdd. On these I created a stripped zpool. After login I can import and mount the pool without problems, but the at-boot import fails after the first partitions is available and never tried again. zpool version: zfs-0.8.3-1ubuntu12.2 zfs-kmod-0.8.3-1ubuntu12.2 uname -a: Linux hostname 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux systemd --version systemd 245 (245.4-4ubuntu3.2) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Relevant logs: Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write Protect is off Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 17 07:12:25 hostname kernel: sdb: sdb1 sdb2 Aug 17 07:12:25 hostname kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found ordering cycle on cryptsetup.target/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found dependency on systemd-cryptsetup@vol\x2dswap_crypt.service/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found dependency on systemd-random-seed.service/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found dependency on zfs-mount.service/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found dependency on zfs-import.target/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Found dependency on zfs-import-cache.service/start Aug 17 07:12:25 hostname systemd[1]: zfs-import-cache.service: Job cryptsetup.target/start deleted to break ordering cycle starting with zfs-import-cache.service/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:12:25 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for sdb1_crypt... Aug 17 07:12:26 hostname systemd[1]: Starting Cryptography Setup for sdb2_crypt... Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:12:26 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:12:32 hostname systemd[1]: Finished Cryptography Setup for sdb2_crypt. Aug 17 07:12:32 hostname systemd[1]: Reached target Block Device Preparation for /dev/mapper/sdb2_crypt. Aug 17 07:12:32 hostname zpool[1887]: cannot import 'sdb': no such pool or dataset Aug 17 07:12:32 hostname zpool[1887]: Destroy and re-create the pool from Aug 17 07:12:32 hostname zpool[1887]: a backup source. Aug 17 07:12:32 hostname systemd[1]: zfs-import-cache.service: Main process exited, code=exited, status=1/FAILURE Aug 17 07:12:32 hostname systemd[1]: zfs-import-cache.service: Failed with result 'exit-code'. Aug 17 07:12:34 hostname systemd[1]: Finished Cryptography Setup for sdb1_crypt. Aug 17 07:12:34 hostname systemd[1]: Reached target Block Device Preparation for /dev/mapper/sdb1_crypt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1891867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1891663] Re: package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade: package systemd-timesyncd is already installed and configured
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. https://bugs.launchpad.net/bugs/1891663 Title: package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade: package systemd-timesyncd is already installed and configured Status in apt package in Ubuntu: New Bug description: This is my first linux experience, I am a totally Newbee. I tried to update my language System, but it did not work. I would like to change from QWERTY to QWERTZ... ;-) Thank you! :-) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd-timesyncd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 600:120:125:37:2020-08-14 02:43:47.659610329 +0200:2020-08-14 02:43:47.659610329 +0200:/var/crash/_usr_bin_gnome-shell.1000.uploaded 664:1000:125:0:2020-08-14 02:43:41.139536887 +0200:2020-08-14 02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.upload 640:1000:125:30803273:2020-08-14 02:43:39.603530645 +0200:2020-08-14 02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 600:0:125:315407:2020-08-14 16:26:15.810850381 +0200:2020-08-14 16:26:16.810850381 +0200:/var/crash/systemd.0.crash 600:0:125:315427:2020-08-14 16:26:15.790850400 +0200:2020-08-14 16:26:16.790850400 +0200:/var/crash/systemd-timesyncd.0.crash Date: Fri Aug 14 16:26:16 2020 DuplicateSignature: package:systemd-timesyncd:245.4-4ubuntu3.2 Setting up cups (2.3.1-9ubuntu1.1) ... Log started: 2020-08-14 16:26:16 dpkg: error processing package systemd-timesyncd (--configure): package systemd-timesyncd is already installed and configured ErrorMessage: package systemd-timesyncd is already installed and configured InstallationDate: Installed on 2020-08-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade: package systemd-timesyncd is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1891663/+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 1882034] Re: cannot start X session with NIS account
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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882034 Title: cannot start X session with NIS account Status in gdm3 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+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 1882034] Re: cannot start X session with NIS account
** 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 account Status in gdm3 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+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 1891641] Re: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit sta
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 subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1891641 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 Status in debconf package in Ubuntu: New Bug description: This occured while upgrading from Ubuntu 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 14 16:32:44 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-08-07 (7 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-14 (0 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "7"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2020-08-14T15:42:52.692116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1891641/+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 1886886] Re: Plymouth 0.9.5 release
** 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 package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Confirmed Bug description: Plymouth 0.9.5 release: https://www.freedesktop.org/software/plymouth/releases/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1891332] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:clear:/usr/bin/unattended-upgrade@2514:main:run:calculate_upgradable_pkg
*** 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 problem page at https://errors.ubuntu.com/problem/a16ab8014a871a4f125fcf1b5f1412bd338f9b5c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 1705, in try_to_upgrade + cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) + File "/usr/bin/unattended-upgrade", line 440, in mark_upgrade_adjusted + self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) + File "/usr/bin/unattended-upgrade", line 399, in call_adjusted + self.clear() + File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear + self._depcache.init() + apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. + + During handling of the above exception, another exception occurred: + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 2514, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1985, in main + res = run(options, rootdir, mem_log, logfile_dpkg, + File "/usr/bin/unattended-upgrade", line 2157, in run + pkgs_to_upgrade = calculate_upgradable_pkgs(cache, options) + File "/usr/bin/unattended-upgrade", line 1746, in calculate_upgradable_pkgs + try_to_upgrade(pkg, + File "/usr/bin/unattended-upgrade", line 1716, in try_to_upgrade + rewind_cache(cache, pkgs_to_upgrade) + File "/usr/bin/unattended-upgrade", line 1334, in rewind_cache + cache.clear() + File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear + self._depcache.init() + apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. ** This bug has been marked a duplicate of bug 1871145 apt.Cache.clear() -> apt.Cache._depcache.init() raises Error -- 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/1891332 Title: /usr/bin/unattended- upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:clear:/usr/bin /unattended- upgrade@2514:main:run:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:clear Status in unattended-upgrades package in Ubuntu: New Bug description: 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 problem page at https://errors.ubuntu.com/problem/a16ab8014a871a4f125fcf1b5f1412bd338f9b5c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1705, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 440, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 399, in call_adjusted self.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2514, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1985, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2157, in run pkgs_to_upgrade = calculate_upgradable_pkgs(cache, options) File "/usr/bin/unattended-upgrade", line 1746, in calculate_upgradable_pkgs try_to_upgrade(pkg, File "/usr/bin/unattended-upgrade", line 1716, in try_to_upgrade rewind_cache(cache, pkgs_to_upgrade) File "/usr/bin/unattended-upgrade", line 1334, in rewind_cache cache.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. To manage notifications about this bug go to:
[Touch-packages] [Bug 1871145] Re: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871145 Title: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error Status in python-apt package in Ubuntu: Opinion Status in unattended-upgrades package in Ubuntu: Triaged Bug description: Unattended-upgrades 2.1 triggers the following crash in python-apt: File "/usr/bin/unattended-upgrade", line 1706, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 438, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 397, in call_adjusted self.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package intellij-idea-ultimate needs to be reinstalled, but I can't find an archive for it. I think .clear() should not raise an error, but if it should u-u can catch that. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/798f1ab5a4a2784a0fadd6034a875901345682f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871145/+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 1890913] Re: init is using 100% of processor
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 ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Package changed: systemd (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Tags removed: block-proposed -- 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 using 100% of processor Status in linux package in Ubuntu: Invalid Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890913/+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 1890913] Re: init is using 100% of processor
** 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 using 100% of processor Status in systemd package in Ubuntu: New Bug description: the `sbin/init splash` process is using more than 100% of processor after boot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-12.13-generic 5.8.0-rc7 Uname: Linux 5.8.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Aug 8 22:14:37 2020 InstallationDate: Installed on 2019-11-01 (280 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2349KEG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-12-generic root=/dev/mapper/vgubuntu-root ro i915.fastboot=1 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349KEG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349KEG:pvrThinkPadT430:rvnLENOVO:rn2349KEG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349KEG dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-08T22:11:41.151132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890913/+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 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers
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 ** Also affects: systemd (Ubuntu Bionic) 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/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: Fix Released Bug description: Recent Linux kernels introduced a number of new syscalls ending in _time64 to fix Y2038 problem; it appears recent glibc, including the version in focal, test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) doesn't know about these so blocks them by default. It seems however glibc isn't expecting an EPERM, causing numerous programs to fail. In particular, running do-release-upgrade to focal in an nspawn container hosted on bionic will break as soon as the new libc has been unpacked. Solution (tested here) is to cherrypick upstream commit https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2 A newer libseccomp is also needed but this is already being worked on, see bug #1876055. It's a pretty trivial fix one the new libseccomp lands, and there is precedent for SRU-ing for a similar issue in bug #1840640. https://patchwork.kernel.org/patch/10756415/ is apparently the upstream kernel patch, which should give a clearer idea of which architectures are likely to be affected - I noticed it on armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+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 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it
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) 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/1871641 Title: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Boot process freezes at the splash screen and nothing happens after that. The computer can be suspended and it is able to return from suspend. Boot is possible by pressing escape early in the process to bypass plymouth. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Wed Apr 8 14:30:13 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 7469A23 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7469A23 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X200s dmi.product.name: 7469A23 dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1832050] Re: chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr)
*** 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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1832050 Title: chrony autopkgtest "time-sources-from-dhcp-servers" fails (produces stderr) Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Eoan: Confirmed Bug description: iproute2 fix in -proposed (https://launchpad.net/ubuntu/+source/iproute2/4.18.0-1ubuntu3) has showed regressions in chrony autopkgtest (object of this bug report). From autopkgtest output: """ Generating /etc/default/isc-dhcp-server... Created symlink /etc/systemd/system/multi-user.target.wants/isc-dhcp-server.service → /lib/systemd/system/isc-dhcp-server.service. Created symlink /etc/systemd/system/multi-user.target.wants/isc-dhcp-server6.service → /lib/systemd/system/isc-dhcp-server6.service. Setting up autopkgtest-satdep (0) ... Processing triggers for systemd (240-6ubuntu9) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.29-0ubuntu2) ... (Reading database ... 62774 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [20:50:33]: test time-sources-from-dhcp-servers: [--- Preparing the dummy network interface and dhcpd configuration… md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-dummy0.conf: No such file or directory Done! Check if the NTP server is made available to chronyd… SUCCESS! Release the current lease and check if the NTP server has been correctly removed… SUCCESS! """ It is likely that the stdout from md5sum coming out of the dhclient command caused the "regression". I have reproduced the issue by hand doing: $ apt-get install isc-dhcp-server $ modprobe dummy $ ip link add name dummy0 type dummy $ ip address add 192.168.1.1/24 dev dummy0 $ ip link set dev dummy0 up cat < /etc/dhcp/dhcpd.conf default-lease-time 600; max-lease-time 7200; authorative; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option broadcast-address192.168.1.255; option ntp-servers 192.168.1.50; range 192.168.1.42 192.168.1.100; } EOF $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc- dhcp-server and $ systemctl restart isc-dhcp-server $ dhclient dummy0 <- problem happens here It could be a "isc-dhcp-client"problem, but I'll keep this bug linked to another bug if that is the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832050/+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 1832053] Re: systemd dhclient hook is causing md5sum cmds in inexistent files
*** 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 constantly restarts on Bionic upgraded from Xenial -- 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/1832053 Title: systemd dhclient hook is causing md5sum cmds in inexistent files Status in systemd package in Ubuntu: In Progress Status in systemd source package in Eoan: In Progress Bug description: I have discovered this issue by doing investigation for the BUG: https://bugs.launchpad.net/ubuntu/+bug/1832050 """ I have reproduced the issue by hand doing: $ apt-get install isc-dhcp-server $ modprobe dummy $ ip link add name dummy0 type dummy $ ip address add 192.168.1.1/24 dev dummy0 $ ip link set dev dummy0 up cat < /etc/dhcp/dhcpd.conf default-lease-time 600; max-lease-time 7200; authorative; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option broadcast-address 192.168.1.255; option ntp-servers 192.168.1.50; range 192.168.1.42 192.168.1.100; } EOF $ sed -i 's/INTERFACESv4=""/INTERFACESv4="dummy0"/' /etc/default/isc- dhcp-server and $ systemctl restart isc-dhcp-server $ dhclient dummy0 <- problem happens here """ When trying a simple dhclient running on a bridge called "teste": (c)inaddy@eoanchrony:~/work/sources/ubuntu/chrony/debian/tests$ sudo dhclient teste md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-teste.conf: No such file or directory md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-teste.conf: No such file or directory The problem is caused by the hook script: /etc/dhcp/dhclient-enter-hooks.d/resolved In the following line: md5sum $statedir/isc-dhcp-v4-$interface.conf $statedir/isc- dhcp-v6-$interface.conf &> $oldstate I believe commit +systemd (240-6ubuntu9) eoan; urgency=medium caused this issue with a patch to file "debian/extra/dhclient-enter- resolved-hook" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832053/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
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 ondemand.service unconditionally. The latest LTS release, 20.04 is not affected so the certification test changes are probably not very urgent. -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Released Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
** 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 member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Fix Released Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU
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: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.063s OK ... ** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1877769 Title: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Focal: Fix Committed Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades consumes excessive amount of CPU when rewinding cache trying to mark packages to upgrade or install even when they are already marked to be upgraded or installed. This can be triggered by packages held back. [Test Case] * Run test_rewind.py: -Fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.022s OK - Not fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies . -- Ran 1 test in 0.024s (Note the extra "DEBUG:root:falling back to adjusting" ... lines) [Regression Potential] * Minimal. The very small change fixes how call_checked() verifies that the package to be upgrades/installed is indeed marked to either being installed or upgraded. In the worst case, if call_checked() erroneously returns success for a package as a result of a regression, unattended-upgrades does not fall back to adjusting packages to make marking successful. Later unattended-upgrades finds out that the package could not be marked and should be treated as kept back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1877769/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
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 to see it root@ff-uu-1-verify:~# unattended-upgrade root@ff-uu-1-verify:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist root@ff-uu-1-verify:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}' >> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist root@ff-uu-1-verify:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 330, in open self.apply_pinning(self.pinning_from_config()) File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config and policy.get_candidate_ver(pkg) > -1: # type: ignore TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' root@ff-uu-1-verify:~# sed -i 's/backports/proposed/' /etc/apt/sources.list root@ff-uu-1-verify:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-proposed InRelease [265 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages [42.9 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main Translation-en [19.5 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 c-n-f Metadata [1308 B] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/restricted amd64 Packages [3684 B] Get:9 http://archive.ubuntu.com/ubuntu focal-proposed/restricted Translation-en [1252 B] Get:10 http://archive.ubuntu.com/ubuntu focal-proposed/restricted amd64 c-n-f Metadata [116 B] Get:11 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages [40.9 kB] Get:12 http://archive.ubuntu.com/ubuntu focal-proposed/universe Translation-en [22.5 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 c-n-f Metadata [1688 B] Get:14 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse amd64 Packages [672 B] Get:15 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse Translation-en [3492 B] Get:16 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse amd64 c-n-f Metadata [188 B] Fetched 403 kB in 2s (179 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 17 packages can be upgraded. Run 'apt list --upgradable' to see them. root@ff-uu-1-verify:~# apt install unattended-upgrades Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 16 not upgraded. Need to get 48.7 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 unattended-upgrades all 2.3ubuntu0.1 [48.7 kB] Fetched 48.7 kB in 0s (135 kB/s) Preconfiguring packages ... (Reading database ... 31266 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_2.3ubuntu0.1_all.deb ... Unpacking unattended-upgrades (2.3ubuntu0.1) over (2.3) ... Setting up unattended-upgrades (2.3ubuntu0.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.2) ... seroot@ff-uu-1-verify:~# sed -i 's/proposed/backports/' /etc/apt/sources.list root@ff-uu-1-verify:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f Metadata [112 B] Get:6 http://archive.ubuntu.com/ubuntu focal-backports/restricted amd64 c-n-f Metadata [116 B] Get:7 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [3096 B] Get:8 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops
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 (Ubuntu) Status: Invalid => Opinion ** Changed in: apt (Ubuntu) Status: Opinion => 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/1886161 Title: UU should work on roaming laptops Status in apt package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1888442] Re: upgrade did not go well
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) => zfs-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/1888442 Title: upgrade did not go well Status in zfs-linux package in Ubuntu: New Bug description: Hello, I had some problems during my most recent apt upgrade. A confounding factor to these problems was removing my laptop from its docking station a few minutes earlier. $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic linux-image-5.4.0-42-generic linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic python3-click python3-colorama The following packages will be upgraded: base-files libnss-mymachines libnss-systemd libpam-systemd libpulse-mainloop-glib0 libpulse0 libpulsedsp libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic linux-headers-generic linux-image-generic pulseaudio pulseaudio-utils python3-distupgrade sudo systemd systemd-container systemd-journal-remote systemd-sysv systemd-timesyncd ubuntu-drivers-common ubuntu-release-upgrader-core udev 34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/184 MB of archives. After this operation, 360 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 11ubuntu5.1 [60.1 kB] Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.2 [95.6 kB] Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB] Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.2 [1,363 kB] Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.2 [78.9 kB] Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB] Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 6.0.0-0ubuntu8.2 [343 kB] Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB] Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB] Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB] Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 6.0.0-0ubuntu8.2 [1,444 kB] Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 6.0.0-0ubuntu8.2 [404 kB] Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines amd64 245.4-4ubuntu3.2 [131 kB] Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 2.4.3-1ubuntu3.20.04.3 [42.4 kB] Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container amd64 245.4-4ubuntu3.2 [317 kB] Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB] Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.2 [10.3 kB] Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.2 [28.0 kB] Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.2 [186 kB] Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.2 [3,796 kB] Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.2 [271 kB] Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB] Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 1:13.99.1-1ubuntu3.5 [21.7 kB] Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils amd64 1:13.99.1-1ubuntu3.5 [55.0 kB] Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 1:13.99.1-1ubuntu3.5 [815 kB] Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 1:13.99.1-1ubuntu3.5 [263 kB] Get:27 http://wopr.domain/ubuntu focal/main
[Touch-packages] [Bug 1872215] Re: There should be a GUI option to install non-security packages too
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1872215 Title: There should be a GUI option to install non-security packages too Status in unattended-upgrades package in Ubuntu: Opinion Bug description: The Software & Updates program lacks the option for the user to allow Ubuntu to automatically install non-security packages. It only supports security packages. I know Unattended-upgrades supports automatic upgrading of other packages but it might be too complicated for new users. There should be an easier way. Consider that Windows also deals with software updates "unattended" by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1872215/+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 1887655] Re: unattended-upgrades triggers reboot despite configuration
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. https://bugs.launchpad.net/bugs/1887655 Title: unattended-upgrades triggers reboot despite configuration Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: I've been having problems with my Ubuntu machine suddenly rebooting without any warning. To my knowledge Ubuntu Desktop is not supposed to reboot without warning by default. I believe this is being triggered by unattended-upgrades unattended-upgrades 2.3 (amd64) Ubuntu Desktop: Description: Ubuntu 20.04 LTS Release: 20.04 One pattern that emerges is that the reboot happens right after unattended-upgrades completes successfully. There are multiple examples in my /var/log/syslog, but all show "unattended- upgrades.service: Succeeded." the same second everything begins to shut down, with nothing for a minute or two prior. Example: Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new release of Ubuntu... Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500] Jul 15 11:17:22 pc check-new-release-gtk[71843]: /usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk' , '3.0') before import to ensure that the right version gets loaded. Jul 15 11:17:22 pc check-new-release-gtk[71843]: from gi.repository import Gtk Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout reached, exiting Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded. Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new release of Ubuntu. Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper: assertion 'node != NULL' failed Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500] Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded. Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip. Jul 15 11:18:03 pc systemd[1]: Removed slice system-clean\x2dmount\x2dpoint.slice. Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice. Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice. Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for /dev/mapper/ubuntu. Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session (session: gnome). From memory I've never edited the contents of /etc/apt/apt.conf.d/ and the configuration for unattended upgrades claims to be default (NOT to reboot): $ grep -irnC4 reboot /etc/apt/apt.conf.d/ /etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of unused packages after the upgrade /etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get autoremove) /etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies "false"; /etc/apt/apt.conf.d/50unattended-upgrades-91- /etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT CONFIRMATION* if /etc/apt/apt.conf.d/50unattended-upgrades:93:// the file /var/run/reboot-required is found after the upgrade /etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot "false"; /etc/apt/apt.conf.d/50unattended-upgrades-95- /etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if there are users currently logged in /etc/apt/apt.conf.d/50unattended-upgrades:97:// when Unattended-Upgrade::Automatic-Reboot is set to true /etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; /etc/apt/apt.conf.d/50unattended-upgrades-99- /etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is enabled and needed, reboot at the specific /etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately /etc/apt/apt.conf.d/50unattended-upgrades-102-// Default: "now" /etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time "02:00"; /etc/apt/apt.conf.d/50unattended-upgrades-104- /etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit feature, this example limits the download /etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec /etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70"; journalctl -u unattended-upgrades Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown. Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded. -- Reboot -- Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown. Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service:
[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops
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 member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in unattended-upgrades package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1883082] Re: Crash when using Package-Whitelist-Strict
** 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 + Starting ff-uu-strict + $ lxc shell ff-uu-strict + root@ff-uu-strict:~# apt update + ... + root@ff-uu-strict:~# 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 to see it + + Set up strict whitelist not covering the package: + + root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist + root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}' >> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist + + Run unattended-upgrades: + root@ff-uu-strict:~# unattended-upgrade + + The fixed version does not crash here, the not fixed one does. + + + [Regression Potential] + + Minimal. The fix adds only one extra check to not crash dereferencing + None. + + [Original Bug Text] + + Hi, I'm trying to use unattended-upgrades only with a few packages from a list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua file: - root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua - Unattended-Upgrade::Package-Whitelist-Strict "true"; + root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua + Unattended-Upgrade::Package-Whitelist-Strict "true"; Unattended-Upgrade::Package-Whitelist { "firefox"; "bash"; "openssh-server"; } When running unattended-upgrades in dry run mode I get this crash: root@focal-ua:~# unattended-upgrade --debug --dry-run Running on the development release Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security, o=UbuntuESM,a=focal-security - Initial blacklist: + Initial blacklist: Initial whitelist (strict): firefox bash openssh-server Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin An error occurred: '>' not supported between instances of 'apt_pkg.Version' and 'int' Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1983, in main - res = run(options, rootdir, mem_log, logfile_dpkg, - File "/usr/bin/unattended-upgrade", line 2124, in run - cache = UnattendedUpgradesCache(rootdir=rootdir) - File "/usr/bin/unattended-upgrade", line 171, in __init__ - apt.Cache.__init__(self, rootdir=rootdir) - File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__ - self.open(progress) - File "/usr/bin/unattended-upgrade", line 330, in open - self.apply_pinning(self.pinning_from_config()) - File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config - and policy.get_candidate_ver(pkg) > -1: # type: ignore - TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' - Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11 09:38:25 - Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 2512, in - sys.exit(main(options)) - File "/usr/bin/unattended-upgrade", line 1983, in main -
[Touch-packages] [Bug 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU
** 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: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Focal: New Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades consumes excessive amount of CPU when rewinding cache trying to mark packages to upgrade or install even when they are already marked to be upgraded or installed. This can be triggered by packages held back. [Test Case] * Run test_rewind.py: -Fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.022s OK - Not fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies . -- Ran 1 test in 0.024s (Note the extra "DEBUG:root:falling back to adjusting" ... lines) [Regression Potential] * Minimal. The very small change fixes how call_checked() verifies that the package to be upgrades/installed is indeed marked to either being installed or upgraded. In the worst case, if call_checked() erroneously returns success for a package as a result of a regression, unattended-upgrades does not fall back to adjusting packages to make marking successful. Later unattended-upgrades finds out that the package could not be marked and should be treated as kept back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1877769/+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 1887919] Re: autopkgtest failure with libselinux 3.1
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. https://bugs.launchpad.net/bugs/1887919 Title: autopkgtest failure with libselinux 3.1 Status in glibc package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: 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 -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF
[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
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 their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 2.80 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 2.80 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 915 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes 2600 MHz max turbo 4 active cores 2600 MHz max turbo 3 active cores 2600 MHz max turbo 2 active cores 2800 MHz max turbo 1 active cores @seb128, @juliank I'm not sure if there is anything to fix in the user space, but please report which laptops you experienced issues with. Those may need firmware/kernel fixes. ** Changed in: systemd (Ubuntu Groovy) 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1887919] Re: autopkgtest failure with libselinux 3.1
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 3.1 Status in glibc package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: 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 -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF lsm/.deps/liblxc_la-selinux.Tpo -c lsm/selinux.c -fPIC -DPIC -o
[Touch-packages] [Bug 1887919] [NEW] autopkgtest failure with libselinux 3.1
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 -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fPIC -fcf-protection -U_FORTIFY_SOURCE -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -I../include -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss -I/tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -isystem /tmp/autopkgtest.p9VjWR/build.CPS/src/debian/include -D_LIBC_REENTRANT -include /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=libnss_files -include ../include/libc-symbols.h -DPIC -DSHARED -DTOP_NAMESPACE=glibc -o /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os -MD -MP -MF /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os.dt -MT /tmp/autopkgtest.p9VjWR/build.CPS/src/build-tree/amd64-libc/nss/files-service.os makedb.c: In function ‘set_file_creation_context’: makedb.c:849:3: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] 849 | security_context_t ctx; | ^~ makedb.c:863:3: error: ‘matchpathcon’ is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | ^~ In file included from makedb.c:50: /usr/include/selinux/selinux.h:500:12: note: declared here 500 | extern int matchpathcon(const char *path, |^~~~ ... https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20200717_015751_af18d@/log.gz ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -fPIC -DPIC -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -pthread -g -O2 -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Wvla -std=gnu11 -Werror -MT lsm/liblxc_la-selinux.lo -MD -MP -MF lsm/.deps/liblxc_la-selinux.Tpo -c lsm/selinux.c -fPIC -DPIC -o lsm/.libs/liblxc_la-selinux.o [01m[Klsm/selinux.c:[m[K In function ‘[01m[Kselinux_process_label_get[m[K’: [01m[Klsm/selinux.c:35:2:[m[K [01;31m[Kerror: [m[K‘[01m[Ksecurity_context_t[m[K’ is deprecated [[01;31m[K-Werror=deprecated-declarations[m[K] 35 | [01;31m[Ksecurity_context_t[m[K ctx; | [01;31m[K^~[m[K cc1: all warnings being treated as errors make[3]: Leaving
[Touch-packages] [Bug 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
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) -- 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: In Progress Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1887186] Re: Please switch to nftables as the default backend
** 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 frontend to be the preferred tool for interfacing the Netfilter framework, thus please Recommend: it. - Inclusion of the netfilter package in main is traced at LP: #1887187. + Inclusion of the nftables package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. -- 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: Confirmed Bug description: 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 preferred tool for interfacing the Netfilter framework, thus please Recommend: it. Inclusion of the nftables package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+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 1887191] Re: autopkgtest always fail on i386 for f and later
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 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 and later Status in Auto Package Testing: New Status in systemd package in Ubuntu: New Bug description: [impact] all autopkgtest runs fail for i386 arch for focal and later, since i386 is no longer a fully supported arch; the test run fails due to missing test deps. this is super annoying. [test case] run autopkgtest for i386 for f or g or later. [regression potential] as this only disables/skips all testing on i386 for f and later, any regression would likely cause incorrectly failed or skipped autopkgtests for non-i386 archs. [scope] this is needed for f and later. i386 is a fully supported arch for b and earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1887191/+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 1887191] Re: autopkgtest always fail on i386 for f and later
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 and later Status in Auto Package Testing: New Status in systemd package in Ubuntu: New Bug description: [impact] all autopkgtest runs fail for i386 arch for focal and later, since i386 is no longer a fully supported arch; the test run fails due to missing test deps. this is super annoying. [test case] run autopkgtest for i386 for f or g or later. [regression potential] as this only disables/skips all testing on i386 for f and later, any regression would likely cause incorrectly failed or skipped autopkgtests for non-i386 archs. [scope] this is needed for f and later. i386 is a fully supported arch for b and earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1887191/+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 1887186] [NEW] Please switch to nftables as the default backend
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 preferred tool for interfacing the Netfilter framework, thus please Recommend: it. Inclusion of the netfilter package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** 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 frontend to be the preferred tool for interfacing the Netfilter framework, thus please Recommend: it. - Inclusion of the netfilter package in main is traced at LP: #XXX. + Inclusion of the netfilter package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. -- 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: New Bug description: 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 preferred tool for interfacing the Netfilter framework, thus please Recommend: it. Inclusion of the netfilter package in main is traced at LP: #1887187. I've prepared a Bileto ticket for staging and testing the packages which need to be changed: https://bileto.ubuntu.com/#/ticket/4044 The updated package break any package or project, please mark them affected and/or leave a commend in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
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 from intel-hid on HP platforms Status in HWE Next: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Committed Bug description: [Impact] Press wireless hotkey on HP's latest generation laptops generate two rfkill events, prevent airplane mode from turning off. One event is from intel-hid and the other one is from hp-wireless. [Fix] Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use rfkill from hp-wireless. [Test] With the one-liner fix, press wireless hotkey only generate one rfkill event, hence airplane mode works as expected. [Regression Potential] Low, use hp-wireless over intel-hid is anticipated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1886430] [NEW] debian/tests/tests-in-lxd fails when /etc/fstab is missing from the LXC container
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 of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886430 Title: debian/tests/tests-in-lxd fails when /etc/fstab is missing from the LXC container Status in systemd package in Ubuntu: New Bug description: In LP: #1877078 /etc/fstab has been removed from LXD images and now the workaround also removing it in the test started failing . :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886430/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@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 we agree that there is no need for separate boot time and post-boot governor then I think the proper place to set the right default is the kernel. I'd love to hear the Kernel Team's opinion on the matter because there were quite of lot of discussions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 . -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
** 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 connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Focal: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
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 are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
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. https://bugs.launchpad.net/bugs/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18
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: 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/1885901 Title: timedatectl reports wrong status for timesyncd in core18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Bug description: when calling timedatectl in Ubuntu Core 18 the tool reports the status of the systemd-timesyncd.service ... sadly it does report it wrongly (the tool reports it inactive while the service is actually running): ogra@pi4:~$ timedatectl Local time: Wed 2020-07-01 10:52:48 UTC Universal time: Wed 2020-07-01 10:52:48 UTC RTC time: n/a Time zone: n/a (UTC, +) System clock synchronized: yes systemd-timesyncd.service active: no RTC in local TZ: no ogra@pi4:~$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago Docs: man:systemd-timesyncd.service(8) Main PID: 779 (systemd-timesyn) Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) CGroup: /system.slice/systemd-timesyncd.service └─779 /lib/systemd/systemd-timesyncd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
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 (e.g. intel_pstate), and do not require OS config. Additionally, nobody else does this, not even Debian. And finally, this has caused problems for years, e.g.: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1497375 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773 https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012 https://bugs.launchpad.net/charm-sysconfig/+bug/1873028 IMO the kernel is a better place for setting the default governor properly and can even set different governors in cloud-specific kernels. If the decision is to control the governor in user space in Ubuntu I'd prefer a solution shipped in an other package because systemd does too many things already. -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@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. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** 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 Bionic) 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
** 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 Bionic) Status: New => Invalid ** Changed in: btrfs-progs (Ubuntu Bionic) Status: New => Invalid -- 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 lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Bionic: Invalid Status in glibc source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Reopening against bcache-tools according to @raharper's comment about preferring a different fix. https://bugs.launchpad.net/ubuntu/groovy/+source/bcache-tools/+bug/1861941/comments/28 ** Changed in: bcache-tools (Ubuntu Groovy) Status: Fix Released => Triaged ** Changed in: bcache-tools (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 after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** 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 after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms Status in HWE Next: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Committed Bug description: [Impact] Press wireless hotkey on HP's latest generation laptops generate two rfkill events, prevent airplane mode from turning off. One event is from intel-hid and the other one is from hp-wireless. [Fix] Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use rfkill from hp-wireless. [Test] With the one-liner fix, press wireless hotkey only generate one rfkill event, hence airplane mode works as expected. [Regression Potential] Low, use hp-wireless over intel-hid is anticipated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1883883] Re: Only libraries optimized for the running system end up in initramfs
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: Only libraries optimized for the running system end up in initramfs Status in initramfs-tools package in Ubuntu: New Bug description: ... 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 scripts usr var $ cd i/ $ find . -name *pthread* ./usr/lib/aarch64-linux-gnu/atomics/libpthread.so.0 ./usr/lib/aarch64-linux-gnu/atomics/libpthread-2.31.so Luckily btrfs-progs does not play a role in rebooting, thus m6g instances can still be resized to a1 instance types, and I observed no failure when trying to do so. Follow-up for LP: #1880853. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1883883/+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 1883883] [NEW] Only libraries optimized for the running system end up in initramfs
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 scripts usr var $ cd i/ $ find . -name *pthread* ./usr/lib/aarch64-linux-gnu/atomics/libpthread.so.0 ./usr/lib/aarch64-linux-gnu/atomics/libpthread-2.31.so Luckily btrfs-progs does not play a role in rebooting, thus m6g instances can still be resized to a1 instance types, and I observed no failure when trying to do so. Follow-up for LP: #1880853. ** Affects: initramfs-tools (Ubuntu) Importance: Low Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => 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: Only libraries optimized for the running system end up in initramfs Status in initramfs-tools package in Ubuntu: New Bug description: ... 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 scripts usr var $ cd i/ $ find . -name *pthread* ./usr/lib/aarch64-linux-gnu/atomics/libpthread.so.0 ./usr/lib/aarch64-linux-gnu/atomics/libpthread-2.31.so Luckily btrfs-progs does not play a role in rebooting, thus m6g instances can still be resized to a1 instance types, and I observed no failure when trying to do so. Follow-up for LP: #1880853. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1883883/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
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 Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
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 lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+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 1882034] Re: cannot start X session with NIS account
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 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 account Status in systemd package in Ubuntu: Incomplete Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882034/+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 1883082] Re: Crash when using Package-Whitelist-Strict
@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. https://bugs.launchpad.net/bugs/1883082 Title: Crash when using Package-Whitelist-Strict Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Focal: New Bug description: Hi, I'm trying to use unattended-upgrades only with a few packages from a list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua file: root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua Unattended-Upgrade::Package-Whitelist-Strict "true"; Unattended-Upgrade::Package-Whitelist { "firefox"; "bash"; "openssh-server"; } When running unattended-upgrades in dry run mode I get this crash: root@focal-ua:~# unattended-upgrade --debug --dry-run Running on the development release Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security, o=UbuntuESM,a=focal-security Initial blacklist: Initial whitelist (strict): firefox bash openssh-server Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin An error occurred: '>' not supported between instances of 'apt_pkg.Version' and 'int' Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 330, in open self.apply_pinning(self.pinning_from_config()) File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config and policy.get_candidate_ver(pkg) > -1: # type: ignore TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11 09:38:25 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir)
[Touch-packages] [Bug 1883338] Re: unattended-upgrades blocks apt
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 typical cases. ** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Invalid -- 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/1883338 Title: unattended-upgrades blocks apt Status in unattended-upgrades package in Ubuntu: Invalid Bug description: Version: Ubuntu 18.04 and all prior versions that include unattended- upgrades Buggy behavior: I boot a laptop that has been off for a while with the intent to install linux updates. I type apt-get update; apt full-upgrade and it fails, finding that unattended upgrades is running in the background for an extended period of time, but not actually running dpkg at all, just holding the lock, preventing me from running updates. Expected behavior: apt full-upgrade, the graphical update manager, and related commands should either 1) Immediately (and silently?) abort whatever unattended-upgrades is doing and proceed with running updates in the foreground 2) Display progress of updates currently running in the background, waiting for them to finish, and then proceed with running additional updates in the foreground Note that it may be necessary to implement both behaviors, depending if unattended-upgrades is just spinning or if it has actually started running upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1883338/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@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 of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1883082] Re: Crash when using Package-Whitelist-Strict
** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1883082 Title: Crash when using Package-Whitelist-Strict Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Focal: New Bug description: Hi, I'm trying to use unattended-upgrades only with a few packages from a list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua file: root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua Unattended-Upgrade::Package-Whitelist-Strict "true"; Unattended-Upgrade::Package-Whitelist { "firefox"; "bash"; "openssh-server"; } When running unattended-upgrades in dry run mode I get this crash: root@focal-ua:~# unattended-upgrade --debug --dry-run Running on the development release Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security, o=UbuntuESM,a=focal-security Initial blacklist: Initial whitelist (strict): firefox bash openssh-server Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin Marking not allowed with -32768 pin An error occurred: '>' not supported between instances of 'apt_pkg.Version' and 'int' Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 330, in open self.apply_pinning(self.pinning_from_config()) File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config and policy.get_candidate_ver(pkg) > -1: # type: ignore TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11 09:38:25 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir)
[Touch-packages] [Bug 1881504] Re: cross-testing essential packages fails
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 member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1881504 Title: cross-testing essential packages fails Status in apt package in Ubuntu: Won't Fix Status in autopkgtest package in Ubuntu: New Status in gzip package in Ubuntu: New Bug description: Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz ... autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1 autopkgtest [19:51:38]: build not needed autopkgtest [19:51:38]: test simple-gzip: preparing testbed Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: gzip The following NEW packages will be installed: build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0 libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22 libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1 linux-libc-dev WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. E: Failed to process build dependencies ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 1881504] Re: cross-testing essential packages fails
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 installed: gcc-10-base gcc-10-base:i386 libatomic1 libc6:i386 libcc1-0 libcrypt-dev libcrypt1 libcrypt1:i386 libgcc-s1 libgcc-s1:i386 libgomp1 libidn2-0:i386 libitm1 liblsan0 libquadmath0 libstdc++6 libtsan0 libubsan1 libunistring2 libunistring2:i386 Suggested packages: glibc-doc:i386 locales:i386 The following packages will be REMOVED: gzip The following NEW packages will be installed: gcc-10-base:i386 gzip:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: gcc-10-base libatomic1 libcc1-0 libcrypt-dev libcrypt1 libgcc-s1 libgomp1 libitm1 liblsan0 libquadmath0 libstdc++6 libtsan0 libubsan1 libunistring2 WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 14 upgraded, 7 newly installed, 1 to remove and 121 not upgraded. Need to get 5303 kB of archives. After this operation, 15.2 MB of additional disk space will be used. You are about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!' ?] Abort. ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1881504 Title: cross-testing essential packages fails Status in apt package in Ubuntu: New Status in autopkgtest package in Ubuntu: New Status in gzip package in Ubuntu: New Bug description: Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz ... autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1 autopkgtest [19:51:38]: build not needed autopkgtest [19:51:38]: test simple-gzip: preparing testbed Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: gzip The following NEW packages will be installed: build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0 libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22 libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1 linux-libc-dev WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. E: Failed to process build dependencies ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 1882596] Re: systemd.unit(5) incorrectly refers to systemd.syntax(5)
** 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. https://bugs.launchpad.net/bugs/1882596 Title: systemd.unit(5) incorrectly refers to systemd.syntax(5) Status in systemd package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually systemd.syntax(7). "See systemd.syntax(5) for a general description of the syntax." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882596/+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