[Touch-packages] [Bug 1936312] Re: nm-online times out, failing autopkgtests
This should have been fixed upstream by: https://github.com/systemd/systemd/pull/18559 Or https://github.com/systemd/systemd/pull/18684 and https://github.com/systemd/systemd/pull/18717 respectively. I wonder why this fix isn't working for network-manager, while it seems to be good for LXD? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1936312 Title: nm-online times out, failing autopkgtests Status in network-manager package in Ubuntu: Fix Released Bug description: The nm-online util does not return successfully as of 1.32.2-0ubuntu1 (currently in impish-proposed). systemd VS network-manager autopkgtests (in LXD) fail, because the autopkgtest-virt-lxd runner tries to wait for "network ready" before it is reconnecting after a reboot. This happens by checking the 'systemctl start network-online.target' command, in turn executing the 'nm-online -s -q' util (via NetworkManager-wait-online.service), in addition to systemd-networkd-wait-online.service (which seems to be working OK). nm-online does not return successfully anymore as of 1.32.2-0ubuntu1, but it times out. That is a regression compared to v1.30. Reproducer: $ lxc launch ubuntu-daily:impish test $ lxc exec test bash # apt install network-manager #(version 1.30.0-1ubuntu4) # time systemctl start network-online.target real 0m0.071s user 0m0.021s sys 0m0.023s # time nm-online -s Connecting... 30s [started] real 0m0.043s user 0m0.027s sys 0m0.006s root@test:~# echo $? 0 Everything is OK up to here. # vim /etc/apt/sources.list #(enable impish-proposed) # apt update && apt install network-manager #(1.32.2-0ubuntu1) # time nm-online -s Connecting...0s [startup-pending] real 0m30.019s user 0m0.021s sys 0m0.014s # time systemctl start network-online.target real 1m0.104s user 0m0.013s sys 0m0.023s # journalctl -u NetworkManager | grep startup Jul 15 09:05:06 test NetworkManager[1912]: [1626339906.6507] manager: startup complete root@test:~# NetworkManager -V 1.32.2 root@test:~# nm-online -s Connecting...0s [startup-pending] root@test:~# echo $? 1 root@test:~# nm-online Connecting...0s [offline] root@test:~# echo $? 1 The journal log contains the "startup completed" line, so 'nm-online -s' should return immediately. But as we can see, nm-online fails (after a timeout) and thus blocks network-online.target, failing the systemd autopkgtests (in LXD). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+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 1791958] Re: iptables-restore is missing -w option
I'm on the same page. Maybe we should leave the package in -update as is and go with the flock() alternative. OR evaluate if, let's say, the Focal's iptables could be backported (if feasible) in bionic-backports. That way, one who wants the 'wait' and 'wait-interval' to be available could rely on -backport, while the rest of our Bionic users could remain on the same old iptables behavior provided in -updates. - Eric -- 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/1791958 Title: iptables-restore is missing -w option Status in iptables package in Ubuntu: Confirmed Bug description: For CRIU we need to have iptables version 1.6.2 which includes the '-w' option in iptables-restore. This is a request to update iptables to 1.6.2 in 18.10 and if possible backport the necessary changes to 18.04. The CRIU project gets right now many bug reports (mostly in the combination LXD + CRIU) due to the missing '-w' option in iptables- restore. Especially as 18.04 will be around for some time it would be good to have iptables-restore available with '-w'. This is one example bug report: https://github.com/checkpoint- restore/criu/issues/551 But not only CRIU would benefit from this change. It seems also problematic with Kubernetes: https://github.com/kubernetes/kubernetes/pull/60978 So if possible, please update iptables to 1.6.2 (or backport changes) to support -w in iptables-restore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1791958] Re: iptables-restore is missing -w option
For backports, a straight build of 1.6.2 would perhaps be enough. Might not seem a version change big enough for backports, but as we have seen, it does introduce a change of behavior that impacts existing firewall scripts. -- 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/1791958 Title: iptables-restore is missing -w option Status in iptables package in Ubuntu: Confirmed Bug description: For CRIU we need to have iptables version 1.6.2 which includes the '-w' option in iptables-restore. This is a request to update iptables to 1.6.2 in 18.10 and if possible backport the necessary changes to 18.04. The CRIU project gets right now many bug reports (mostly in the combination LXD + CRIU) due to the missing '-w' option in iptables- restore. Especially as 18.04 will be around for some time it would be good to have iptables-restore available with '-w'. This is one example bug report: https://github.com/checkpoint- restore/criu/issues/551 But not only CRIU would benefit from this change. It seems also problematic with Kubernetes: https://github.com/kubernetes/kubernetes/pull/60978 So if possible, please update iptables to 1.6.2 (or backport changes) to support -w in iptables-restore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1791958] Re: iptables-restore is missing -w option
I think 'backports' would have been a great place to have this behavior change in Bionic while keep the current one in -updates. I just came across an email about 'backports' about to die (from rbasak). Let's see what is the outcome and rely on the flock() alternative for now. I'll monitor the "-backports" discussion and let's see from there. - Eric -- 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/1791958 Title: iptables-restore is missing -w option Status in iptables package in Ubuntu: Confirmed Bug description: For CRIU we need to have iptables version 1.6.2 which includes the '-w' option in iptables-restore. This is a request to update iptables to 1.6.2 in 18.10 and if possible backport the necessary changes to 18.04. The CRIU project gets right now many bug reports (mostly in the combination LXD + CRIU) due to the missing '-w' option in iptables- restore. Especially as 18.04 will be around for some time it would be good to have iptables-restore available with '-w'. This is one example bug report: https://github.com/checkpoint- restore/criu/issues/551 But not only CRIU would benefit from this change. It seems also problematic with Kubernetes: https://github.com/kubernetes/kubernetes/pull/60978 So if possible, please update iptables to 1.6.2 (or backport changes) to support -w in iptables-restore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Changed in: ubuntu-kernel-tests Status: In Progress => 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1677668] Re: no GARPs during ephemeral boot
This causes problems for me as well during maas re-imaging wiht maas 2.9.2. see https://discourse.maas.io/t/changing-ips-and-lack-of- gratuitous-arp-and-the-pain-it-causes/4800 Ideally when pxebooting, pxelinux.0 should send a gratuitous arp and in theory it should solve the issue. Perhaps I'm mistaken... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1677668 Title: no GARPs during ephemeral boot Status in MAAS: New Status in cloud-init package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Deploys time out with an error on the console that says, "Can not apply stage final, no datasource found! Likely bad things to come!" How to duplicate: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) 1) Rack Controller and Region Controller in different VLANs 2) Use Cisco ASA as the router with "ARP Inspection" enabled 3) Clear the router ARP cache 4) Deploy 2 maas machines with interfaces set to "Static assign" 5) Observe deploys successfully 6) Release both machines and swap IP's. 7) Redeploy the same 2 machines 8) Observe deploy failure with the machine consoles stuck in the "ubuntu login" screen with "Can not apply stage final, no datasource Found! Likely bad things to come!" The root cause is that during ephemeral PXE booting, no GARPs are sent, which in our environment will cause our router (Cisco ASA) to hold on to ARP table entries until it expires (default= 4 hours). Then combined with ASA feature "ARP Inspection" will drop packets from a MaaS machine using the previously used IP from a different MaaS machine. The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily. Running tcpdump on the Rack Controller, showed no GARPs from the deploying MaaS machine. If there were GARPs sent, then the router would refresh its ARP cache thus avoiding the ARP Inspection dropping. [Excerpt from Cisco ASA] http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf When you enable ARP inspection, the ASA compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions: • If the IP address, MAC address, and source interface match an ARP entry, the packet is passed through. • If there is a mismatch between the MAC address, the IP address, or the interface, then the ASA drops the packet. • If the ARP packet does not match any entries in the static ARP table, then you can set the ASA to either forward the packet out all interfaces (flood), or to drop the packet. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1677668/+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 1677668] Re: no GARPs during ephemeral boot
** Also affects: maas Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1677668 Title: no GARPs during ephemeral boot Status in MAAS: New Status in cloud-init package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Deploys time out with an error on the console that says, "Can not apply stage final, no datasource found! Likely bad things to come!" How to duplicate: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) 1) Rack Controller and Region Controller in different VLANs 2) Use Cisco ASA as the router with "ARP Inspection" enabled 3) Clear the router ARP cache 4) Deploy 2 maas machines with interfaces set to "Static assign" 5) Observe deploys successfully 6) Release both machines and swap IP's. 7) Redeploy the same 2 machines 8) Observe deploy failure with the machine consoles stuck in the "ubuntu login" screen with "Can not apply stage final, no datasource Found! Likely bad things to come!" The root cause is that during ephemeral PXE booting, no GARPs are sent, which in our environment will cause our router (Cisco ASA) to hold on to ARP table entries until it expires (default= 4 hours). Then combined with ASA feature "ARP Inspection" will drop packets from a MaaS machine using the previously used IP from a different MaaS machine. The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily. Running tcpdump on the Rack Controller, showed no GARPs from the deploying MaaS machine. If there were GARPs sent, then the router would refresh its ARP cache thus avoiding the ARP Inspection dropping. [Excerpt from Cisco ASA] http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf When you enable ARP inspection, the ASA compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions: • If the IP address, MAC address, and source interface match an ARP entry, the packet is passed through. • If there is a mismatch between the MAC address, the IP address, or the interface, then the ASA drops the packet. • If the ARP packet does not match any entries in the static ARP table, then you can set the ASA to either forward the packet out all interfaces (flood), or to drop the packet. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1677668/+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 1677668] Re: no GARPs during ephemeral boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1677668 Title: no GARPs during ephemeral boot Status in MAAS: New Status in cloud-init package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Deploys time out with an error on the console that says, "Can not apply stage final, no datasource found! Likely bad things to come!" How to duplicate: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) 1) Rack Controller and Region Controller in different VLANs 2) Use Cisco ASA as the router with "ARP Inspection" enabled 3) Clear the router ARP cache 4) Deploy 2 maas machines with interfaces set to "Static assign" 5) Observe deploys successfully 6) Release both machines and swap IP's. 7) Redeploy the same 2 machines 8) Observe deploy failure with the machine consoles stuck in the "ubuntu login" screen with "Can not apply stage final, no datasource Found! Likely bad things to come!" The root cause is that during ephemeral PXE booting, no GARPs are sent, which in our environment will cause our router (Cisco ASA) to hold on to ARP table entries until it expires (default= 4 hours). Then combined with ASA feature "ARP Inspection" will drop packets from a MaaS machine using the previously used IP from a different MaaS machine. The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily. Running tcpdump on the Rack Controller, showed no GARPs from the deploying MaaS machine. If there were GARPs sent, then the router would refresh its ARP cache thus avoiding the ARP Inspection dropping. [Excerpt from Cisco ASA] http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf When you enable ARP inspection, the ASA compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions: • If the IP address, MAC address, and source interface match an ARP entry, the packet is passed through. • If there is a mismatch between the MAC address, the IP address, or the interface, then the ASA drops the packet. • If the ARP packet does not match any entries in the static ARP table, then you can set the ASA to either forward the packet out all interfaces (flood), or to drop the packet. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1677668/+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 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure (Ubuntu) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Invalid Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: Invalid Status in linux-azure source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+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 1936847] [NEW] [amd] Xorg crashed on wakeup from suspend
Public bug reported: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=72a1caf7-a182-459a-b685-43fc66697294 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000BCK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1000BCK:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1000BCK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000BCK dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1936847 Title: [amd] Xorg crashed on wakeup from suspend Status in xorg package in Ubuntu: New Bug description: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK Pr
[Touch-packages] [Bug 1936847] Re: [amd] Xorg crashed on wakeup from suspend
** Description changed: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. + + On a different occasion, my Xorg log file also included (same as bug + 1780677): + + (WW) xf86CloseConsole: KDSETMODE failed: Input/output error + (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error + (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error + (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed - virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed + virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed + virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Renoir [17aa:5081] + Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=72a1caf7-a182-459a-b685-43fc66697294 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000BCK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1000BCK:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1000BCK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000BCK dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1897530. + + This happens when I disconnect dock station after suspend (tested with + Dell WD19s and Lenovo ThinkPad USB-C Dock Gen2). On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Insta
[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif
Working on the problem, I got the idea to move the symlink to another name and so I tried "apt -f install" and the con worked. I perform these steps: $ cd /usr/share/doc/libwind0-heimdal/ $ mv changelog.Debian.gz changelog.Debian.gz.old $ apt -f install RESULT: Reading package lists... Done Building dependency tree... Done Reading status information... Done Fixing dependencies... Done The following packages were installed automatically and are no longer needed: libasn1-8-heimdal:i386 libgssapi3-heimdal:i386 libhcrypto4-heimdal:i386 libheimbase1-heimdal:i386 libheimntlm0-heimdal:i386 libhx509-5-heimdal:i386 libkrb5-26-heimdal:i386 libldap-2.4-2:i386 libroken18-heimdal:i386 libwind0-heimdal:i386 Use 'apt autoremove' to remove them. The following additional packages will be installed: libwind0-heimdal The following packages will be updated: libwind0-heimdal 1 packages updated, 0 new packages installed, 0 to be removed and 19 not updated. 5 packages not fully installed or removed. You need to download 0B/49.1kB of files. After this operation, an additional 0 B of disk space will be used. Do you want to continue? [Y/n] (Reading database ... 365705 files and directories currently installed.) Preparing to unpack .../libwind0-heimdal_7.7.0+dfsg-2build1_amd64.deb ... Unpacking libwind0-heimdal:amd64 (7.7.0+dfsg-2build1) onto (7.7.0+dfsg-2) ... Configuring libwind0-heimdal:amd64 (7.7.0+dfsg-2build1) ... Configuring libwind0-heimdal:i386 (7.7.0+dfsg-2build1) ... Configuring libhx509-5-heimdal:i386 (7.7.0+dfsg-2build1) ... Configuring libkrb5-26-heimdal:i386 (7.7.0+dfsg-2build1) ... Configuring libheimntlm0-heimdal:i386 (7.7.0+dfsg-2build1) ... Configuring libgssapi3-heimdal:i386 (7.7.0+dfsg-2build1) ... Processing triggers for libc-bin (2.33-0ubuntu7) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1934936 Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other instances of package libwind0-heimdal:i386 Status in heimdal package in Ubuntu: Confirmed Bug description: fresh 21.10 install and 1 reboot later it said there was additional updates and while doing so the error popped up ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libwind0-heimdal 7.7.0+dfsg-2build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 8 01:45:16 2021 DuplicateSignature: package:libwind0-heimdal:7.7.0+dfsg-2build1 Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other instances of package libwind0-heimdal:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other instances of package libwind0-heimdal:i386 InstallationDate: Installed on 2021-06-05 (32 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libc6 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.6 SourcePackage: heimdal Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other instances of package libwind0-heimdal:i386 UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1936853] [NEW] package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2
Public bug reported: unknown ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dash 0.5.10.2-6 ProcVersionSignature: Ubuntu 5.4.0-79.88~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-79-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: dash:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 19 22:11:36 2021 ErrorMessage: installed dash package pre-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2021-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: dash Title: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2021-07-19 (0 days ago) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1936853 Title: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2 Status in dash package in Ubuntu: New Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dash 0.5.10.2-6 ProcVersionSignature: Ubuntu 5.4.0-79.88~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-79-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: dash:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 19 22:11:36 2021 ErrorMessage: installed dash package pre-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2021-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: dash Title: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2021-07-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1936853/+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 1936853] Re: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1936853 Title: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2 Status in dash package in Ubuntu: New Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dash 0.5.10.2-6 ProcVersionSignature: Ubuntu 5.4.0-79.88~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-79-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: dash:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 19 22:11:36 2021 ErrorMessage: installed dash package pre-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2021-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: dash Title: package dash 0.5.10.2-6 failed to install/upgrade: installed dash package pre-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2021-07-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1936853/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Hi there, Same model here (Dell XPS 17 9710) with Ubuntu 21.04. I see the exact same stack trace after enabling the Nvidia drivers (replacing Nouveau) advised for the RTX 3060 (Version: 470.57.02 https://www.nvidia.com/Download/driverResults.aspx/177145/en-us) Tried with versions 460 & 465: same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Description changed: + [Impact] + The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which shows as graphical corruption on the desktop apps with certain hardware. + + The fix is to add a commit from upstream staging/21.0 -branch, which + never got released as 21.0.4. + + [Test case] + Install the update, use desktop apps, see that it works correctly now. + + [Where things could go wrong] + The fix adds a single line for an earlier commit that was incomplete. In theory it might regress some other amd hw, but this is highly unlikely. + + -- + Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 ** Changed in: mesa (Ubuntu Focal) Status: New => In Progress ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: In Progress Bug description: [Impact] The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which shows as graphical corruption on the desktop apps with certain hardware. The fix is to add a commit from upstream staging/21.0 -branch, which never got released as 21.0.4. [Test case] Install the update, use desktop apps, see that it works correctly now. [Where things could go wrong] The fix adds a single line for an earlier commit that was incomplete. In theory it might regress some other amd hw, but this is highly unlikely. -- Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1936864] [NEW] Samsung printer can't print after 21.04 update
Public bug reported: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: New Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19
[Touch-packages] [Bug 1858210] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1858210 Title: timedatectl doesn't list all timezones Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] timedatectl list-timezones doesn't show many common timezones that are actually considered 'aliases', such as Europe/Bratislava or US/Eastern. [test case] $ timedatectl list-timezones | grep Eastern $ [regression potential] any regression would likely result in an incorrect list of timezones shown from list-timezones, or failure to correctly set a timezone [scope] this is needed in f and later this is fixed upstream with PR 20066 which was just merged, so this is needed in all releases in ubuntu in bionic, the 'tzdata.zi' file that the new code uses isn't present, so this won't work on bionic, thus marking it wontfix [original description] Is there some filter determining which timezones are displayed by `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing. Even stranger, it can successfully be set by timedatectl. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10 Uname: Linux 5.3.0-1014-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Fri Jan 3 15:36:03 2020 Lspci: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks
This bug was fixed in the package systemd - 246.6-1ubuntu1.5
---
systemd (246.6-1ubuntu1.5) groovy; urgency=medium
[ Kai-Heng Feng ]
* d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e
[ Jeremy Szu ]
* d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d
[ Dan Streetman ]
*
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,
d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321
* d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47
* d/p/lp1858210/0001-time-simplify-get_timezones.patch,
d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542
*
d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch,
d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch,
d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch,
d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch:
Don't rewrite resolv.conf is content unchanged (LP: #1891215)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937
-- Dan Streetman Tue, 06 Jul 2021 14:00:27
-0400
** Changed in: systemd (Ubuntu Groovy)
Status: Fix Committed => 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/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in systemd source package in Impish:
Fix Released
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1931578] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1931578 Title: ActivationPolicy=down causes delay at boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnline=no, then there is a hang at boot waiting for the network to finish coming online. [test case] With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolicy=down and reboot. The boot will be delayed waiting for that interface. [regression potential] any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s). [scope] this is needed for all releases this is proposed upstream in: https://github.com/systemd/systemd/pull/19883 [other info] this is only needed for convenience, as any configuration using ActivationPolicy=down can also easily add RequiredForOnline=no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931578/+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 1932352] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1932352 Title: Fix micmute hotkeys on HP Elite Dragonfly Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [Impact] Mic mute key is no function on HP Elite Dragonfly. [Fix] After confirming with HP, there are two model names for Dragonfly: * HP Elite Dragonfly G2 Notebook PC * HP Elite Dragonfly Max Notebook PC Thus, the commit Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic mute key. [Test] After patching it, the mic mute key could functioned well on my Dragonfly laptop. [Where problems could occur] There is not old rule for Dragonfly dmi string in current hwdb. Which means the Dragonfly is using default HP key map: ``` evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:* KEYBOARD_KEY_81=fn_esc ``` This patch will change the HP machine (if product name contains pnHPEliteDragonfly*) to map 81 to mic mute key. If a machine (pnHPEliteDragonfly*) works good in the past then this patch may cause it's mic mute key become malfunction. However, this rule is confirmed/provided from HP. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932352/+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 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly
This bug was fixed in the package systemd - 246.6-1ubuntu1.5 --- systemd (246.6-1ubuntu1.5) groovy; urgency=medium [ Kai-Heng Feng ] * d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch: - Add ProBook to use micmute hotkey (LP: #1930910) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e [ Jeremy Szu ] * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch: - Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d [ Dan Streetman ] * d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch, d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch, d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch: Adjust default for RequiredForOnline when using ActivationPolicy (LP: #1931578) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321 * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch: Add man page symlink and deprecation notice for systemd-resolve (LP: #1894622) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47 * d/p/lp1858210/0001-time-simplify-get_timezones.patch, d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch, d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch: Parse tzdata.zi so timedatectl list-timezones also lists aliases (LP: #1858210) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542 * d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch, d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch, d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch, d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch: Don't rewrite resolv.conf is content unchanged (LP: #1891215) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937 -- Dan Streetman Tue, 06 Jul 2021 14:00:27 -0400 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => 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/1932352 Title: Fix micmute hotkeys on HP Elite Dragonfly Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [Impact] Mic mute key is no function on HP Elite Dragonfly. [Fix] After confirming with HP, there are two model names for Dragonfly: * HP Elite Dragonfly G2 Notebook PC * HP Elite Dragonfly Max Notebook PC Thus, the commit Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic mute key. [Test] After patching it, the mic mute key could functioned well on my Dragonfly laptop. [Where problems could occur] There is not old rule for Dragonfly dmi string in current hwdb. Which means the Dragonfly is using default HP key map: ``` evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:* KEYBOARD_KEY_81=fn_esc ``` This patch will change the HP machine (if product name contains pnHPEliteDragonfly*) to map 81 to mic mute key. If a machine (pnHPEliteDragonfly*) works good in the past then this patch may cause it's mic mute key become malfunction. However, this rule is confirmed/provided from HP. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932352/+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
This bug was fixed in the package systemd - 246.6-1ubuntu1.5 --- systemd (246.6-1ubuntu1.5) groovy; urgency=medium [ Kai-Heng Feng ] * d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch: - Add ProBook to use micmute hotkey (LP: #1930910) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e [ Jeremy Szu ] * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch: - Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d [ Dan Streetman ] * d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch, d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch, d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch: Adjust default for RequiredForOnline when using ActivationPolicy (LP: #1931578) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321 * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch: Add man page symlink and deprecation notice for systemd-resolve (LP: #1894622) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47 * d/p/lp1858210/0001-time-simplify-get_timezones.patch, d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch, d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch: Parse tzdata.zi so timedatectl list-timezones also lists aliases (LP: #1858210) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542 * d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch, d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch, d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch, d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch: Don't rewrite resolv.conf is content unchanged (LP: #1891215) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937 -- Dan Streetman Tue, 06 Jul 2021 14:00:27 -0400 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => 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/1891215 Title: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] networking changes, like RA events, can cause systemd-resolved to re- write the resolv.conf file, even if the contents didn't change, resulting in unnecessary increased amount of inotify events [test case] see original description for ipv6ra-related reproducer, or simple reproducer here: configure networkd with some config for (e.g.) eth0, but not a config that would result in /etc/resolv.conf changing when the interface goes up/down - for example, use static config with no DNS search domains. Then bring eth0 up/down while observing the md5sum (file content) does not change but the mtime does change. root@lp1891215-h:~# ip l set down dev eth0 root@lp1891215-h:~# md5sum /etc/resolv.conf db23e80078515192c312e5f321ff0340 /etc/resolv.conf root@lp1891215-h:~# stat -t -L /etc/resolv.conf /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216 1625238216 0 4096 root@lp1891215-h:~# ip l set up dev eth0 root@lp1891215-h:~# md5sum /etc/resolv.conf db23e80078515192c312e5f321ff0340 /etc/resolv.conf root@lp1891215-h:~# stat -t -L /etc/resolv.conf /etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226 1625238226 0 4096 [regression potential] regressions would result in incorrect or missing data in the resolv.conf file, possibly resulting in dns failures or errors [scope] this is needed for h and eralier this is (potentially) fixed upstream by f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in v248, so this is needed in hirsute and earlier [original 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 wat
[Touch-packages] [Bug 1894622] Re: Missing manpage for systemd-resolve
This bug was fixed in the package systemd - 246.6-1ubuntu1.5 --- systemd (246.6-1ubuntu1.5) groovy; urgency=medium [ Kai-Heng Feng ] * d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch: - Add ProBook to use micmute hotkey (LP: #1930910) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e [ Jeremy Szu ] * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch: - Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d [ Dan Streetman ] * d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch, d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch, d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch: Adjust default for RequiredForOnline when using ActivationPolicy (LP: #1931578) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321 * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch: Add man page symlink and deprecation notice for systemd-resolve (LP: #1894622) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47 * d/p/lp1858210/0001-time-simplify-get_timezones.patch, d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch, d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch: Parse tzdata.zi so timedatectl list-timezones also lists aliases (LP: #1858210) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542 * d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch, d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch, d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch, d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch: Don't rewrite resolv.conf is content unchanged (LP: #1891215) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937 -- Dan Streetman Tue, 06 Jul 2021 14:00:27 -0400 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => 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/1894622 Title: Missing manpage for systemd-resolve Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] 'man systemd-resolve' fails [test case] $ man systemd-resolve No manual entry for systemd-resolve [regression potential] incorrect man page result for resolvectl or resolvconf, or possibly users using deprecated systemd-resolve longer than they should [scope] this is needed in f and later systemd-resolve was replaced with resolvectl between b and f, so the man page exists in b [other info] the systemd-resolve binary is a symlink to the real binary resolvectl, and users should use resolvectl for all new uses. A patch to the upstream man page was proposed and merged in this PR: https://github.com/systemd/systemd/pull/20064 however that is being discussed and may be reverted in this PR: https://github.com/systemd/systemd/pull/20077 as discussed in the revert PR, it's ok for upstream to elide docs about deprecated tooling; however distros should include deprecation info and thus I believe it's appropriate to include the man page symlink so users trying 'man systemd-resolve' will get the correct 'resolvectl' man page, which includes doc about how they shoudl start using 'resolvectl' instead [original description] On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz This means that man systemd-resolve fails. http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd- resolve.1.html exists and has a link on top to 20.04LTS: it points to http://manpages.ubuntu.com/manpages/focal/en/man1/systemd- resolve.1.html , that however 404's, and one ends up being redirected to Bionic's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+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 1930910] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1930910
Title:
Fix micmute hotkeys on HP ProBooks
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Status in systemd source package in Impish:
Fix Released
Bug description:
[Impact]
Micmute hotkey on many HP ProBooks don't work.
[Fix]
Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the ProBooks I tested.
[Where problems could occur]
The hwdb originally only matches a few ProBooks, the fix changes that to
match all ProBook models. So if there's any ProBook that uses the scancode for
another purpose, there will be a regression.
However, the risk is rather slim because HP explicitly states that all
ProBooks use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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:
Unknown
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Confirmed
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Committed
Bug description:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
see original description for ipv6ra-related reproducer, or simple
reproducer here:
configure networkd with some config for (e.g.) eth0, but not a config
that would result in /etc/resolv.conf changing when the interface goes
up/down - for example, use static config with no DNS search domains.
Then bring eth0 up/down while observing the md5sum (file content) does
not change but the mtime does change.
root@lp1891215-h:~# ip l set down dev eth0
root@lp1891215-h:~# md5sum /etc/resolv.conf
db23e80078515192c312e5f321ff0340 /etc/resolv.conf
root@lp1891215-h:~# stat -t -L /etc/resolv.conf
/etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216
1625238216 0 4096
root@lp1891215-h:~# ip l set up dev eth0
root@lp1891215-h:~# md5sum /etc/resolv.conf
db23e80078515192c312e5f321ff0340 /etc/resolv.conf
root@lp1891215-h:~# stat -t -L /etc/resolv.conf
/etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226
1625238226 0 4096
[regression potential]
regressions would result in incorrect or missing data in the
resolv.conf file, possibly resulting in dns failures or errors
[scope]
this is needed for h and eralier
this is (potentially) fixed upstream by
f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
v248, so this is needed in hirsute and earlier
[original 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-4u
[Touch-packages] [Bug 1894622] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1894622 Title: Missing manpage for systemd-resolve Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] 'man systemd-resolve' fails [test case] $ man systemd-resolve No manual entry for systemd-resolve [regression potential] incorrect man page result for resolvectl or resolvconf, or possibly users using deprecated systemd-resolve longer than they should [scope] this is needed in f and later systemd-resolve was replaced with resolvectl between b and f, so the man page exists in b [other info] the systemd-resolve binary is a symlink to the real binary resolvectl, and users should use resolvectl for all new uses. A patch to the upstream man page was proposed and merged in this PR: https://github.com/systemd/systemd/pull/20064 however that is being discussed and may be reverted in this PR: https://github.com/systemd/systemd/pull/20077 as discussed in the revert PR, it's ok for upstream to elide docs about deprecated tooling; however distros should include deprecation info and thus I believe it's appropriate to include the man page symlink so users trying 'man systemd-resolve' will get the correct 'resolvectl' man page, which includes doc about how they shoudl start using 'resolvectl' instead [original description] On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz This means that man systemd-resolve fails. http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd- resolve.1.html exists and has a link on top to 20.04LTS: it points to http://manpages.ubuntu.com/manpages/focal/en/man1/systemd- resolve.1.html , that however 404's, and one ends up being redirected to Bionic's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+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 1858210] Re: timedatectl doesn't list all timezones
This bug was fixed in the package systemd - 246.6-1ubuntu1.5 --- systemd (246.6-1ubuntu1.5) groovy; urgency=medium [ Kai-Heng Feng ] * d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch: - Add ProBook to use micmute hotkey (LP: #1930910) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e [ Jeremy Szu ] * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch: - Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d [ Dan Streetman ] * d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch, d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch, d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch: Adjust default for RequiredForOnline when using ActivationPolicy (LP: #1931578) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321 * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch: Add man page symlink and deprecation notice for systemd-resolve (LP: #1894622) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47 * d/p/lp1858210/0001-time-simplify-get_timezones.patch, d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch, d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch: Parse tzdata.zi so timedatectl list-timezones also lists aliases (LP: #1858210) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542 * d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch, d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch, d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch, d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch: Don't rewrite resolv.conf is content unchanged (LP: #1891215) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937 -- Dan Streetman Tue, 06 Jul 2021 14:00:27 -0400 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => 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/1858210 Title: timedatectl doesn't list all timezones Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] timedatectl list-timezones doesn't show many common timezones that are actually considered 'aliases', such as Europe/Bratislava or US/Eastern. [test case] $ timedatectl list-timezones | grep Eastern $ [regression potential] any regression would likely result in an incorrect list of timezones shown from list-timezones, or failure to correctly set a timezone [scope] this is needed in f and later this is fixed upstream with PR 20066 which was just merged, so this is needed in all releases in ubuntu in bionic, the 'tzdata.zi' file that the new code uses isn't present, so this won't work on bionic, thus marking it wontfix [original description] Is there some filter determining which timezones are displayed by `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing. Even stranger, it can successfully be set by timedatectl. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10 Uname: Linux 5.3.0-1014-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Fri Jan 3 15:36:03 2020 Lspci: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+subscriptions
[Touch-packages] [Bug 1931578] Re: ActivationPolicy=down causes delay at boot
This bug was fixed in the package systemd - 246.6-1ubuntu1.5 --- systemd (246.6-1ubuntu1.5) groovy; urgency=medium [ Kai-Heng Feng ] * d/p/lp1930910-hwdb-Add-ProBook-to-use-micmute-hotkey.patch: - Add ProBook to use micmute hotkey (LP: #1930910) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=61d8acfdadb856cb408afde99f583142ec31b54e [ Jeremy Szu ] * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch: - Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a635153cbd0542019190380c1f10fd86c12b537d [ Dan Streetman ] * d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch, d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch, d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch: Adjust default for RequiredForOnline when using ActivationPolicy (LP: #1931578) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9496d9934550d842609bf9d4aff8fc93eece1321 * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch: Add man page symlink and deprecation notice for systemd-resolve (LP: #1894622) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=bdcb37e447bf419cc3ff1082aec3427ab9ad0c47 * d/p/lp1858210/0001-time-simplify-get_timezones.patch, d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch, d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch: Parse tzdata.zi so timedatectl list-timezones also lists aliases (LP: #1858210) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a64ac9f1413abd3b7d427560ac6c439ba916e542 * d/p/lp1891215/0001-fs-util-add-conservative_rename-that-suppresses-unne.patch, d/p/lp1891215/0002-resolved-don-t-update-resolv.conf-snippets-unnecessa.patch, d/p/lp1891215/0003-fs-util-rename-conservative_rename-conservative_rena.patch, d/p/lp1891215/0004-fs-util-make-sure-conservative_renameat-properly-det.patch: Don't rewrite resolv.conf is content unchanged (LP: #1891215) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79ff24ba51d2239315d948e7dfb3e39769946937 -- Dan Streetman Tue, 06 Jul 2021 14:00:27 -0400 ** Changed in: systemd (Ubuntu Groovy) Status: Fix Committed => 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/1931578 Title: ActivationPolicy=down causes delay at boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Committed Status in systemd source package in Impish: Fix Released Bug description: [impact] The ActivationPolicy= parameter was backported in bug 1664844, but when this is set to down (or always-down or manual) without also specifying RequiredForOnline=no, then there is a hang at boot waiting for the network to finish coming online. [test case] With the latest systemd, which includes support for ActivationPolicy=, configure an interface with ActivationPolicy=down and reboot. The boot will be delayed waiting for that interface. [regression potential] any regression would likely cause the system to encounter delay at boot, or to boot before configured interface(s) are fully online at boot, or to fail to correctly/fully configure interface(s). [scope] this is needed for all releases this is proposed upstream in: https://github.com/systemd/systemd/pull/19883 [other info] this is only needed for convenience, as any configuration using ActivationPolicy=down can also easily add RequiredForOnline=no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931578/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Please try the latest sof-tgl-h.ri in the https://github.com/thesofproject/sof-bin (like 1.7.x or 1.8.x), this file is at /lib/firmware/intel/sof/ under ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1936847] Re: [amd] Xorg crashed on wakeup from suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: amdgpu ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1936847 Title: [amd] Xorg crashed on wakeup from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, this is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677, but it wasn't fixed in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530. I have created new bug report for Ubuntu 20.04 as suggested in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/comments/14. This happens when I disconnect dock station after suspend (tested with Dell WD19s and Lenovo ThinkPad USB-C Dock Gen2). On a different occasion, my Xorg log file also included (same as bug 1780677): (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 17:31:52 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.10.0-1034-oem, x86_64: installed virtualbox, 6.1.16, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5081] InstallationDate: Installed on 2021-07-08 (11 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20Y1000BCK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=72a1caf7-a182-459a-b685-43fc66697294 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET63W(1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000BCK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR1BET63W(1.32):bd04/12/2021:br1.32:efr1.32:svnLENOVO:pn20Y1000BCK:pvrThinkPadP14sGen1:rvnLENOVO:rn20Y1000BCK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000BCK dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1936847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~to
[Touch-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Tried sof-tgl-h.ri 1.7 and 1.8 signed and RC2 of both. Speakers are still showing dummy output. Still getting: [5.999872] sof-audio-pci :00:1f.3: error: firmware boot failure [5.999879] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [5.999885] sof-audio-pci :00:1f.3: error: status = 0x panic = 0x0211 [5.06] sof-audio-pci :00:1f.3: error: extended rom status: 0x5 0x0 0x211 0x0 0x0 0x0 0x2530509 0x0 [5.10] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [5.11] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -5 [6.001309] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1920836] Re: Show Extended Security Maintenence status
>> Is there a reason why the ua client doesn't do this itself internally, i.e. it gives you fresh json or returns the cached copy if it can't do the update? Currently the only "time" during which ubuntu-advantage-tools (UA client) could perform the logic to exec 'sudo ua status' is during postinst at package install upgrade time. UA client can not perform that status setup during package install for the same timeout reasons you mentioned. It is a potentially long operation. If run during a package install it could delay or prevent other package upgrades if it hits a timeout and/or error. That said, we are working on instrumenting a systemd timer service that can run config change/setup operations out of band of typical APT package installs. So, this case could be handled by that timer-based service. This SRU does represent. This changeset as-is does represent an improvement to existing cases because the Software properties UX demonstrates awareness of ESM (and contract expiry information) properly for attached machines, or unattached machines where `sudo ua status` has been run. Subsequent releases of software-properties will now be able to take advantage of reading "ua status --format=json" output directly as non- root (due to a bug-fix released in 27.2.1). The non-root user will not have to rely anymore on that json file if absent as the --format=json output will render the same JSON dict that would be present on disk for the root user. This is a fix that is under verification in the -proposed queue now for ua-tools and was not available at the time of this original software-properties PR. I'm ok with this approach as-is knowing that we can significantly improve the behavior once ubuntu-advantage- tools 27.2.1 is released to X B F and H -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
If you temporarily remove the sof-tgl-h.ri and bootup, check the dmesg, does the sof-audio-pci looks for sof-tgl-h.ri and fail to find? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openldap (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature, and the intended upstream design is for systemd-logind to talk to systemd-userdb, so that systemd-logind can remain network- sandboxed while systemd-userdb performs any needed network access for user/auth data. However, Debian and Ubuntu don't enable/provide systemd-userdb, so that design does not work for Debian/Ubuntu. this also can cause systemd-udevd failures in some cases as well, apparently (based on upstream and debian discussion comments) For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
Xubuntu-20.04, 20.10 and 21.04 are not usable with ldap authentication - very bad! Not usable for us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature, and the intended upstream design is for systemd-logind to talk to systemd-userdb, so that systemd-logind can remain network- sandboxed while systemd-userdb performs any needed network access for user/auth data. However, Debian and Ubuntu don't enable/provide systemd-userdb, so that design does not work for Debian/Ubuntu. this also can cause systemd-udevd failures in some cases as well, apparently (based on upstream and debian discussion comments) For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+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
