[Touch-packages] [Bug 1923618] Re: upgrading systemd on groovy terminates sessions
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: Expired Status in systemd source package in Groovy: Expired Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+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 1923618] Re: upgrading systemd on groovy terminates sessions
[Expired for systemd (Ubuntu Groovy) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Groovy) Status: Incomplete => Expired -- 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/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: Expired Status in systemd source package in Groovy: Expired Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+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
Could you please rename sof-tgl-h.ri to sof-tgl.ri, let kernel load this firmware and let us see what error log in the dmesg. -- 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: Confirmed 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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: Confirmed 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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
This bug was fixed in the package alsa-lib - 1.1.3-5ubuntu0.6 --- alsa-lib (1.1.3-5ubuntu0.6) bionic; urgency=medium * d/p/0021-conf-USB-add-Cmedia-Audio-to-USB-Audio.pcm.iec958_de.patch https://github.com/alsa-project/alsa-lib/pull/122 Add "Cmedia Audio" to USB-Audio.pcm.iec958_device, otherwise users will see 2 IEC985 devices from UI, but there is no those physical devices in fact. After adding this patch, those 2 IEC985 devices will not show up in the UI. (LP: #1921452) -- Hui Wang Tue, 22 Jun 2021 10:01:54 + ** Changed in: alsa-lib (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1936974] Re: GNU Guile support is not enabled in GNU Make
** Package changed: gdb (Ubuntu) => make (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1936974 Title: GNU Guile support is not enabled in GNU Make Status in make package in Ubuntu: New Bug description: Hello, Similarly to #1891818, I'd like to request that support for Guile be enabled on in the GNU Make Ubuntu package. Guile is a powerful language and having native support for it to embed Guile fragments in Makefiles can be handy in some situations (where Make portability is not a concern). See: https://www.gnu.org/software/make/manual/html_node/Guile-Example.html for an example. Thank you for your consideration! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/make/+bug/1936974/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead
** Changed in: systemd (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Won't Fix Status in systemd source package in Hirsute: Confirmed Status in systemd source package in Impish: Confirmed Bug description: [impact] suspend-then-hibernate not possible using systemctl [test case] configure a system to allow suspend-then-hibernate but not hybrid- sleep, e.g. by editing /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it: $ sudo systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported [regression potential] failure to correctly enter hybrid-sleep and/or suspend-then-hibernate, or other issues around suspending/hibernating [scope] This is needed in f and later. The bug appears to have been introduced by a typo in the original suspend-then-hibernate commit c58493c00af, and then fixed with larger changes in commit c8cd8ca3986. [other info] note that if hybrid-sleep is allowed/possible, then calling 'systemctl suspend-then-hibernate' does actually perform suspend-then-hibernate; this typo only controls what suspend action logind checks for support of, not what suspend action it actually performs. [original description] ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934981/+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 1936974] [NEW] GNU Guile support is not enabled in GNU Make
Public bug reported: Hello, Similarly to #1891818, I'd like to request that support for Guile be enabled on in the GNU Make Ubuntu package. Guile is a powerful language and having native support for it to embed Guile fragments in Makefiles can be handy in some situations (where Make portability is not a concern). See: https://www.gnu.org/software/make/manual/html_node/Guile-Example.html for an example. Thank you for your consideration! ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1936974 Title: GNU Guile support is not enabled in GNU Make Status in gdb package in Ubuntu: New Bug description: Hello, Similarly to #1891818, I'd like to request that support for Guile be enabled on in the GNU Make Ubuntu package. Guile is a powerful language and having native support for it to embed Guile fragments in Makefiles can be handy in some situations (where Make portability is not a concern). See: https://www.gnu.org/software/make/manual/html_node/Guile-Example.html for an example. Thank you for your consideration! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1936974/+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 1936975] [NEW] `openssl dhparam` cannot validate named group DH parameters
Public bug reported: Identified on Ubuntu 18.04 /etc/os-release: NAME="Ubuntu" VERSION="18.04.5 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.5 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Steps to reproduce: $ openssl dhparam Actual Results: ``` DH Parameters: (8192 bit) prime: 00:ff:ff:ff:ff:ff:ff:ff:ff:ad:f8:54:58:a2:bb: 4a:9a:af:dc:56:20:27:3d:3c:f1:d8:b9:c5:83:ce: 2d:36:95:a9:e1:36:41:14:64:33:fb:cc:93:9d:ce: 24:9b:3e:f9:7d:2f:e3:63:63:0c:75:d8:f6:81:b2: 02:ae:c4:61:7a:d3:df:1e:d5:d5:fd:65:61:24:33: f5:1f:5f:06:6e:d0:85:63:65:55:3d:ed:1a:f3:b5: 57:13:5e:7f:57:c9:35:98:4f:0c:70:e0:e6:8b:77: e2:a6:89:da:f3:ef:e8:72:1d:f1:58:a1:36:ad:e7: 35:30:ac:ca:4f:48:3a:79:7a:bc:0a:b1:82:b3:24: fb:61:d1:08:a9:4b:b2:c8:e3:fb:b9:6a:da:b7:60: d7:f4:68:1d:4f:42:a3:de:39:4d:f4:ae:56:ed:e7: 63:72:bb:19:0b:07:a7:c8:ee:0a:6d:70:9e:02:fc: e1:cd:f7:e2:ec:c0:34:04:cd:28:34:2f:61:91:72: fe:9c:e9:85:83:ff:8e:4f:12:32:ee:f2:81:83:c3: fe:3b:1b:4c:6f:ad:73:3b:b5:fc:bc:2e:c2:20:05: c5:8e:f1:83:7d:16:83:b2:c6:f3:4a:26:c1:b2:ef: fa:88:6b:42:38:61:1f:cf:dc:de:35:5b:3b:65:19: 03:5b:bc:34:f4:de:f9:9c:02:38:61:b4:6f:c9:d6: e6:c9:07:7a:d9:1d:26:91:f7:f7:ee:59:8c:b0:fa: c1:86:d9:1c:ae:fe:13:09:85:13:92:70:b4:13:0c: 93:bc:43:79:44:f4:fd:44:52:e2:d7:4d:d3:64:f2: e2:1e:71:f5:4b:ff:5c:ae:82:ab:9c:9d:f6:9e:e8: 6d:2b:c5:22:36:3a:0d:ab:c5:21:97:9b:0d:ea:da: 1d:bf:9a:42:d5:c4:48:4e:0a:bc:d0:6b:fa:53:dd: ef:3c:1b:20:ee:3f:d5:9d:7c:25:e4:1d:2b:66:9e: 1e:f1:6e:6f:52:c3:16:4d:f4:fb:79:30:e9:e4:e5: 88:57:b6:ac:7d:5f:42:d6:9f:6d:18:77:63:cf:1d: 55:03:40:04:87:f5:5b:a5:7e:31:cc:7a:71:35:c8: 86:ef:b4:31:8a:ed:6a:1e:01:2d:9e:68:32:a9:07: 60:0a:91:81:30:c4:6d:c7:78:f9:71:ad:00:38:09: 29:99:a3:33:cb:8b:7a:1a:1d:b9:3d:71:40:00:3c: 2a:4e:ce:a9:f9:8d:0a:cc:0a:82:91:cd:ce:c9:7d: cf:8e:c9:b5:5a:7f:88:a4:6b:4d:b5:a8:51:f4:41: 82:e1:c6:8a:00:7e:5e:0d:d9:02:0b:fd:64:b6:45: 03:6c:7a:4e:67:7d:2c:38:53:2a:3a:23:ba:44:42: ca:f5:3e:a6:3b:b4:54:32:9b:76:24:c8:91:7b:dd: 64:b1:c0:fd:4c:b3:8e:8c:33:4c:70:1c:3a:cd:ad: 06:57:fc:cf:ec:71:9b:1f:5c:3e:4e:46:04:1f:38: 81:47:fb:4c:fd:b4:77:a5:24:71:f7:a9:a9:69:10: b8:55:32:2e:db:63:40:d8:a0:0e:f0:92:35:05:11: e3:0a:be:c1:ff:f9:e3:a2:6e:7f:b2:9f:8c:18:30: 23:c3:58:7e:38:da:00:77:d9:b4:76:3e:4e:4b:94: b2:bb:c1:94:c6:65:1e:77:ca:f9:92:ee:aa:c0:23: 2a:28:1b:f6:b3:a7:39:c1:22:61:16:82:0a:e8:db: 58:47:a6:7c:be:f9:c9:09:1b:46:2d:53:8c:d7:2b: 03:74:6a:e7:7f:5e:62:29:2c:31:15:62:a8:46:50: 5d:c8:2d:b8:54:33:8a:e4:9f:52:35:c9:5b:91:17: 8c:cf:2d:d5:ca:ce:f4:03:ec:9d:18:10:c6:27:2b: 04:5b:3b:71:f9:dc:6b:80:d6:3f:dd:4a:8e:9a:db: 1e:69:62:a6:95:26:d4:31:61:c1:a4:1d:57:0d:79: 38:da:d4:a4:0e:32:9c:cf:f4:6a:aa:36:ad:00:4c: f6:00:c8:38:1e:42:5a:31:d9:51:ae:64:fd:b2:3f: ce:c9:50:9d:43:68:7f:eb:69:ed:d1:cc:5e:0b:8c: c3:bd:f6:4b:10:ef:86:b6:31:42:a3:ab:88:29:55: 5b:2f:74:7c:93:26:65:cb:2c:0f:1c:c0:1b:d7:02: 29:38:88:39:d2:af:05:e4:54:50:4a:c7:8b:75:82: 82:28:46:c0:ba:35:c3:5f:5c:59:16:0c:c0:46:fd: 82:51:54:1f:c6:8c:9c:86:b0:22:bb:70:99:87:6a: 46:0e:74:51:a8:a9:31:09:70:3f:ee:1c:21:7e:6c: 38:26:e5:2c:51:aa:69:1e:0e:42:3c:fc:99:e9:e3: 16:50:c1:21:7b:62:48:16:cd:ad:9a:95:f9:d5:b8: 01:94:88:d9:c0:a0:a1:fe:30:75:a5:77:e2:31:83: f8:1d:4a:3f:2f:a4:57:1e:fc:8c:e0:ba:8a:4f:e8: b6:85:5d:fe:72:b0:a6:6e:de:d2:fb:ab:fb:e5:8a: 30:fa:fa:be:1c:5d:71:a8:7e:2f:74:1e:f8:c1:fe: 86:fe:a6:bb:fd:e5:30:67:7f:0d:97:d1:1d:49:f7: a8:44:3d:08:22:e5:06:a9:f4:61:4e:01:1e:2a:94: 83:8f:f8:8c:d6:8c:8b:b7:c5:c6:42:4c:ff:ff:ff: ff:ff:ff:ff:ff generator: 2 (0x2) recommended-private-length: 400 bits WARNING: the g value is not a generator ``` Expected Results: ``` DH Parameters: (8192 bit) prime: 00:ff:ff:ff:ff:ff:ff:ff:ff:ad:f8:54:58:a2:bb: 4a:9a:af:dc:56:20:27:3d:3c:f1:d8:b9:c5:83:ce: 2d:36:95:a9:e1:36:41:14:64:33:fb:cc:93:9d:ce: 24:9b:3e:f9:7d:2f:e3:63:63:0c:75:d8:f6:81:b2:
[Touch-packages] [Bug 1925320] Re: Backport packages for 20.04.3 HWE stack
I've checked both my install and daily live image of focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Released Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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: Fix Committed Status in mesa source package in Hirsute: Fix Committed 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 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
This bug was fixed in the package heimdal - 7.7.0+dfsg-2ubuntu1 --- heimdal (7.7.0+dfsg-2ubuntu1) impish; urgency=medium * Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different to i386 resulting in different files on amd64 and i386. LP: #1934936 -- Dimitri John Ledkov Tue, 20 Jul 2021 10:32:53 +0100 ** Changed in: heimdal (Ubuntu) Status: In Progress => Fix Released -- 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: Fix Released 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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Committed Status in mesa source package in Hirsute: Fix Committed 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 1933402] Re: net card set VF and altname display blurred character
** Changed in: kunpeng920/ubuntu-20.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 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/1933402 Title: net card set VF and altname display blurred character Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] When running with the HWE kernel (5.4 didn't support altnames), altnames containing garbage (uninitialized memory) may get assigned to a NIC. This is 100% reproducible on arm64. The upstream commit message suggests that this has been seen to cause segfaults. [Test Case] 1) echo 1 > /sys/class/net/enp189s0f0/device/sriov_numvfs 2) ip a 3) 10: eno1v0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1e:d8:e1:e9:ae:25 brd ff:ff:ff:ff:ff:ff altname @▒ު▒ altname enp125s0f0v0 11: enp189s0f0v0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 76:ea:f4:65:dd:33 brd ff:ff:ff:ff:ff:ff altname ▒b▒ު▒ altname ▒▒ [Fix] There's a one liner upstream fix that simply initializes a variable: https://github.com/systemd/systemd/commit/61fd7d6720c562c88ab79062ff8d131e5e3c7b1b [What Could Go Wrong] The fix itself is innocuous - just initializing a variable to NULL. So the real risk here would seem to be limited to the common risks in updating a core package in the Ubuntu distribution. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933402/+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 - 247.3-3ubuntu3.4 --- systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:38:18 -0400 -- 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers Tue, 20 Jul 2021
07:39:51 -0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910
--
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/1853164
Title:
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
New
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
with systemd-resolved disabled, dhclient doesn't correctly notify
resolvconf about dns server(s)
[test case]
install resolvconf and ifupdown and disable systemd-resolved and
systemd-networkd, use ifupdown to get a dhcp address where the lease
includes a dns nameserver, verify resolvconf is using that dhcp-
provided nameserver
[regression potential]
failure to correctly notify systemd-resolved about new dhclient-
provided nameserver(s)
[scope]
this is needed for f and earlier
in g and later the hook script is moved to the isc-dhcp package, and
edited to correctly check is-enabled systemd-resolved instead of only
checking for the existence of the binary
[original description]
The functionality exists to allow users to revert to the traditional ifupdown
package for network configuration. Alongside this, systemd's often-buggy
resolver can be disabled. However, there's a logic error in the systemd-
supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
from populating /etc/resolv.conf properly when systemd-resolved is disabled.
The issue is here:
if [ -x /lib/systemd/systemd-resolved ] ; then
Instead of checking to see if the systemd-resolved service is enabled or
active, which would be the correct behaviour, this checks for the existence of
a binary, assuming that if it exists it's supposed to be used.
I've not tested this in the absence of resolvconf, but if systemd-resolved
isn't enabled, it's difficult to imagine this code wanting to run. I've tested
this with resolvconf and ifupdown driving dhclient, and it corrects the
behaviour that was broken with the introduction of systemd-resolved.
I'm attaching a patch, and am also including it here for easy access:
*** resolved.broken 2019-11-19 15:01:28.785588838 +
--- resolved2019-11-19 15:08:06.519430073 +
***
*** 14,20
# (D) = master script downs interface
# (-) = master script does nothing with this
! if [ -x /lib/systemd/systemd-resolved ] ; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
--- 14,21
# (D) = master script downs interface
# (-) = master script does nothing with this
! systemctl is-active systemd-resolved > /dev/null 2>&1
! if [ $? -eq 0 ]; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 ** Changed in: systemd (Ubuntu Hirsute) 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers Tue, 20 Jul 2021
07:38:18 -0400
--
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 Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
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
[Touch-packages] [Bug 1894622] Re: Missing manpage for systemd-resolve
This bug was fixed in the package systemd - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 ** Changed in: systemd (Ubuntu Hirsute) 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
This bug was fixed in the package systemd - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers Tue, 20 Jul 2021
07:39:51 -0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910
** Changed in: systemd (Ubuntu Hirsute)
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 Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
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
[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks
This bug was fixed in the package systemd - 247.3-3ubuntu3.4
---
systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers Tue, 20 Jul 2021
07:38:18 -0400
--
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 Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
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 1894622] Re: Missing manpage for systemd-resolve
This bug was fixed in the package systemd - 247.3-3ubuntu3.4 --- systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:38:18 -0400 -- 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly
This bug was fixed in the package systemd - 247.3-3ubuntu3.4 --- systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:38:18 -0400 -- 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot
This bug was fixed in the package systemd - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 -- 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/1928200 Title: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] root fs is not cleanly unmounted on shutdown [test case] create a file in /etc/binfmt.d/TestFormat.conf with the following content: :TestFormat:M::XX::/bin/true:F reboot the system, and then shutdown or reboot again, and watch the serial console for the error message: sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy [regression potential] any regression would likely cause problems on shutdown and/or reboot, or may cause problems with unmounted root fs on shutdown/reboot [scope] this is needed only for f this is fixed upstream with PR 15566 which is included in v246, so this is fixed already in g and later this isn't reproducable on b [original description] On ubuntu 20.04, with latest kernel and systemd, it will show error on ThinkPad X1. sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy systemd 245.4-4ubuntu3.6 kernel: 5.8.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1928200/+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 - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 ** Changed in: systemd (Ubuntu Hirsute) 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1933402] Re: net card set VF and altname display blurred character
This bug was fixed in the package systemd - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 -- 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/1933402 Title: net card set VF and altname display blurred character Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] When running with the HWE kernel (5.4 didn't support altnames), altnames containing garbage (uninitialized memory) may get assigned to a NIC. This is 100% reproducible on arm64. The upstream commit message suggests that this has been seen to cause segfaults. [Test Case] 1) echo 1 > /sys/class/net/enp189s0f0/device/sriov_numvfs 2) ip a 3) 10: eno1v0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1e:d8:e1:e9:ae:25 brd ff:ff:ff:ff:ff:ff altname @▒ު▒ altname enp125s0f0v0 11: enp189s0f0v0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 76:ea:f4:65:dd:33 brd ff:ff:ff:ff:ff:ff altname ▒b▒ު▒ altname ▒▒ [Fix] There's a one liner upstream fix that simply initializes a variable: https://github.com/systemd/systemd/commit/61fd7d6720c562c88ab79062ff8d131e5e3c7b1b [What Could Go Wrong] The fix itself is innocuous - just initializing a variable to NULL. So the real risk here would seem to be limited to the common risks in updating a core package in the Ubuntu distribution. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933402/+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 1925827] Re: [v247] backport routing policy rule fix
This bug was fixed in the package systemd - 247.3-3ubuntu3.4 --- systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:38:18 -0400 ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 -- 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/1925827 Title: [v247] backport routing policy rule fix Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [impact] routing policy rules not correctly configured [test case] more detail in upstream bug linked from original description. configure interface with: [Match] Name = ens3 [Network] Address = 10.0.0.1/32 [RoutingPolicyRule] Family = both IncomingInterface = ens3 Table = 42 Priority = 42 then networkctl reload. then update the network file with: [Route] Table = 42 Destination = 10.0.0.0/24 Gateway = 0.0.0.0 and run networkctl reload again, checking systemd-networkd for error. [regression potential] failure to properly configure networking in general, or policy routes. [scope] this is needed only for h. this is fixed already in i, and this is not reproducable in g. see original descrption for link to specific upstream issue and pr. [original description] The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+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 - 245.4-4ubuntu3.10
---
systemd (245.4-4ubuntu3.10) focal-security; urgency=medium
* SECURITY UPDATE: DoS via DHCP FORCERENEW
- debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW
command in src/libsystemd-network/sd-dhcp-client.c.
- CVE-2020-13529
* SECURITY UPDATE: denial of service via stack exhaustion
- debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path
in src/basic/unit-name.c.
- CVE-2021-33910
-- Marc Deslauriers Tue, 20 Jul 2021
07:39:51 -0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910
** Changed in: systemd (Ubuntu Hirsute)
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 Released
Status in systemd source package in Groovy:
Fix Released
Status in systemd source package in Hirsute:
Fix Released
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] Re: ActivationPolicy=down causes delay at boot
This bug was fixed in the package systemd - 247.3-3ubuntu3.4 --- systemd (247.3-3ubuntu3.4) hirsute-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:38:18 -0400 -- 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1931578] Re: ActivationPolicy=down causes delay at boot
This bug was fixed in the package systemd - 245.4-4ubuntu3.10 --- systemd (245.4-4ubuntu3.10) focal-security; urgency=medium * SECURITY UPDATE: DoS via DHCP FORCERENEW - debian/patches/CVE-2020-13529.patch: tentatively ignore FORCERENEW command in src/libsystemd-network/sd-dhcp-client.c. - CVE-2020-13529 * SECURITY UPDATE: denial of service via stack exhaustion - debian/patches/CVE-2021-33910.patch: do not use strdupa() on a path in src/basic/unit-name.c. - CVE-2021-33910 -- Marc Deslauriers Tue, 20 Jul 2021 07:39:51 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-13529 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33910 ** Changed in: systemd (Ubuntu Hirsute) 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 Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released 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 1932542] Re: Add support for zstd
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.13 --- initramfs-tools (0.130ubuntu3.13) bionic; urgency=medium * Backport zstd and lz4 support from focal. LP: #1932542 -- Dimitri John Ledkov Thu, 01 Jul 2021 14:11:48 +0100 ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1932542 Title: Add support for zstd Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * initramfs-tools in impish has changed default initrd compression to zstd. To allow compressing and uncompressing such initrds on Focal LTS release we should backport zstd support in the mkinitramfs & unmkinitramffs tooling. For example ubuntu-cdimage uses unmkinitramfs tool to unpack and inspect impish initrds on a focal host. * Cherrypicking the feature from 0.138 release, which is also present in Hirsute and Impish. [Test Plan] * Create initrd with zstd $ mkinitramfs -c zstd -o zstd-initrd.img * Uncompress it with $ unmkinitramfs ./zstd-initrd.img zstd-initrd- unpacked * For bionic also repeat the same with lz4. [Where problems could occur] * This adds support for zstd compressed initrd in both mkinitramfs and unmkinitramfs. However our GA kernels do not support zstd compressed initrds. And depends on zstd package is not added either. Meaning one still has to install zstd to gain the unpack support. Changing initramfs.conf to zstd may result in unbootable instance when used with GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1932542/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Impish) Assignee: (unassigned) => Simon Chopin (schopin) -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: In Progress Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: In Progress Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1934221] Re: systemd-resolve segfault
** Patch added: "Hirsute" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512243/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch -- 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/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1933506] Re: ubuntu 20.04 no show cursor in 1 of 3 monitors
** Changed in: gpm (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gpm/+question/698060 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1933506 Title: ubuntu 20.04 no show cursor in 1 of 3 monitors Status in gpm package in Ubuntu: Invalid Bug description: Install Ubuntu 20.04, I have 3 monitors but I can not make the mouse work on the monitor 1, stays stuck on the center monitor and does not pass the cursor. If I use the option on the title bar and press "Move to the screen on the left this works without problem" However, it could not access the window that I sent to that screen. That is to say everything works but the mouse does not pass, and attempting by removing the stickers with "Retouch Editor" but it does not work, also try changing the dock and monitor but the problem with the monitor 1 persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1933506/+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 1936948] Re: Dependency loop via sockets.target
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target Status in dbus package in Ubuntu: New Bug description: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/systemd/+git/systemd-1/+merge/405970 -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: In Progress Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1936948] Re: Dependency loop via sockets.target
i.e. basic.target is too much there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target Status in dbus package in Ubuntu: New Bug description: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+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 1936948] Re: Dependency loop via sockets.target
What the patch was supposed to do is to list Default Dependencies from https://www.freedesktop.org/software/systemd/man/systemd.socket.html# But drop/negate shutdown related ones. Thus it should have been 1) Before= dependency on sockets.target 2) After= and Wants= dependency on sysinit.target Requires=sysinit.target is downgraded to Wants to prevent attempting to stop dbus.service on shutdown. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target Status in dbus package in Ubuntu: New Bug description: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Changed in: systemd (Ubuntu Focal) Status: New => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Simon Chopin (schopin) ** Changed in: systemd (Ubuntu Hirsute) Status: New => In Progress ** Changed in: systemd (Ubuntu Hirsute) Assignee: (unassigned) => Simon Chopin (schopin) -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: In Progress Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1936948] [NEW] Dependency loop via sockets.target
Public bug reported: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target Status in dbus package in Ubuntu: New Bug description: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/systemd/+git/systemd-1/+merge/405966 -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: In Progress Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: In Progress Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1930738] Re: network configuration failed on reboot
Hi,
In our case a backport of the specific commit fixed the issue. I really
do think that this is (a rather difficult to reproduce) problem, which
the above commit fixes.
Cheers
--
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/1930738
Title:
network configuration failed on reboot
Status in systemd package in Ubuntu:
Incomplete
Bug description:
This issue was reported at
https://github.com/systemd/systemd/issues/17012
**Used distribution**
> Ubuntu 20.04.1 LTS
**systemd version the issue has been seen with**
> 245.4-4ubuntu3.2
**Issue details**
I configured 255 IPv4 address (including primary IP) using netplan but when
the server restart, it time out on configuring the interface. If I limit total
IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
**/etc/netplan/10-ens3.yaml**
```
network:
version: 2
renderer: networkd
ethernets:
ens3:
dhcp4: no
addresses:
- 140.XX.XX.XX/23
- 103.XXX.XX.1/24
- 103.XXX.XX.2/24
- CONTINUED IP ADDRESS UPTO BELOW ...
- 103.XXX.XX.254/24
gateway4: 140.XX.XX.X
nameservers:
addresses: [1.1.1.1, 1.0.0.1]
routes:
- to: 169.254.0.0/16
via: 140.XX.XX.X
metric: 100
```
The above config works if I run `netplan apply` but when I reboot, it does
not work.
**networkctl**
```
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutablefailed
2 links listed.
```
**/etc/systemd/system/systemd-networkd.service.d/override.conf**
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
```
**systemctl status systemd-networkd.service**
```
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
enabled-runtime; vendor preset: enabled)
Drop-In: /etc/systemd/system/systemd-networkd.service.d
└─override.conf
Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
Docs: man:systemd-networkd.service(8)
Main PID: 346 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 1074)
Memory: 3.8M
CGroup: /system.slice/systemd-networkd.service
└─346 /lib/systemd/systemd-networkd
Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 7s
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received
before link confirmation timeout
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback
for 'timeout' event.
Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router
Solicitation, next solicitation in 15s
Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed'
failed at src/libsystemd/sd-netlink/netlink-message.c:582, function
netlink_message_read_internal(). Ignoring.
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set
address: Connection timed out
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed:
configuring -> failed
Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal
sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6
Router Solicitation client
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+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 1934221] Re: systemd-resolve segfault
1. No, my skills are just not enough to spot it. I noticed warning in valgrind (but it was once only and not crash), but was not able to trace back reason. Very likely your patch fix that. 2. In my network i have some MDNS devices, and probably some combination of them and their connectivity (power failures, packetloss) triggering this bug from time to time. I run back now valgrind with timestamps and will record all port 53 traffic, maybe i can catch pattern. If you want i can apply your patch and do the same. To find the reason i just disabled systemd-resolved service and run manually valgrind -v /lib/systemd/systemd-resolved. Probably other users complained about resolved segfault messages in dmesg and have it happening more often? 3. I was not able to find way to reproduce bug reliably. And now it might take about a week to spot this remaining bug. -- 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/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Merge proposal linked: https://code.launchpad.net/~schopin/ubuntu/+source/systemd/+git/systemd-1/+merge/405961 -- 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/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode Status in Ubuntu on IBM z Systems: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in netplan.io source package in Focal: New Status in systemd source package in Focal: New Status in netplan.io source package in Hirsute: New Status in systemd source package in Hirsute: New Status in netplan.io source package in Impish: Confirmed Status in systemd source package in Impish: Confirmed Bug description: ---Problem Description--- IPs are not getting assigned for Hipersockets in DHCP mode Contact Information = Asha Shekharappa(ashsh...@in.ibm.com) Sankar(sankar...@in.ibm.com) ---uname output--- 52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Ubuntu 20.04 Netplan with systemd-networkd as renderer Creating ethernet connection on Hipersockets device in DHCP mode fails to assign IPs 1. Configure a Hipersockets device chzdev -e 0.0.8f00 2. Create a .yaml file with the below details network: version: 2 ethernets: enc8f00: dhcp4: yes 3. netplan apply 4. The IP is not assigned as seen below root@M96SANKAR:/etc/netplan# ip a s enc8f00: mtu 32768 qdisc mq state UP group default qlen 1000 link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1934221] Re: systemd-resolve segfault
Thank you for providing a patch! That patch looks straight forward and
(almost) resembles the upstream change, obviously missing the parts that
do not yet exist in systemd v245.
The only other thing I found missing is an upstream change in
src/resolve/resolved-dns-transaction.c:
```
static void dns_transaction_stop_timeout(DnsTransaction *t) {
assert(t);
-t->timeout_event_source =
sd_event_source_unref(t->timeout_event_source);
+t->timeout_event_source =
sd_event_source_disable_unref(t->timeout_event_source);
}
DnsTransaction* dns_transaction_free(DnsTransaction *t) {
```
I've created a new patch for Focal, including this change and also
adopted the patch to Hirsute.
I have a few open questions:
1/ Did you leave that out that resolved-dns-transaction.c change on purpose?
2/ What is the best way to reproduce this issue? Can it somehow be triggerd?
3/ How to test/confirm that the issue is indeed fixed? Is there any way other
than observing for 24 hours?
--
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/1934221
Title:
systemd-resolve segfault
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
New
Status in systemd source package in Hirsute:
New
Status in systemd source package in Impish:
Fix Released
Bug description:
systemd-resolve keep crashing and it is very annoying as sometimes it
severely interrupt normal dns resolving.
Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
Typical error in dmesg:
systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp
7ffe2fd0b758 error 15
apport hints me that problem is related to mdns
#3 0x7f3e903c2f11 in sd_event_dispatch () from
/lib/systemd/libsystemd-shared-245.so
It might be (or not) related that some hosts with mdns in my network
have ipv6 enabled.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
Uname: Linux 5.4.0-75-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 1 08:22:51 2021
InstallationDate: Installed on 2018-12-05 (938 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
dmi.bios.date: 05/12/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1205
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X399-E GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1934221] Re: systemd-resolve segfault
systemd v248 as can be found in Impish already contains the upstream fix. -- 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/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1934221] Re: systemd-resolve segfault
** Patch added: "Focal" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512235/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1936919] Re: Some windows sometimes freeze
** Package changed: ubuntu => xorg (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/1936919 Title: Some windows sometimes freeze Status in xorg package in Ubuntu: New Bug description: Sometimes, some windows freeze - one or several - I am unable to move / resize / close them. In this case, Chrome has frozen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 20 11:36:04 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2070 SUPER] [1462:3860] InstallationDate: Installed on 2021-06-16 (33 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. MS-7B98 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=9cc6efdc-ca4a-4fe2-9769-42599b4e96a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 1:2.10.6-1 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/+bug/1936919/+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 1936919] [NEW] Some windows sometimes freeze
You have been subscribed to a public bug: Sometimes, some windows freeze - one or several - I am unable to move / resize / close them. In this case, Chrome has frozen. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 20 11:36:04 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2070 SUPER] [1462:3860] InstallationDate: Installed on 2021-06-16 (33 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. MS-7B98 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=9cc6efdc-ca4a-4fe2-9769-42599b4e96a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 1:2.10.6-1 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 false-gpu-hang focal freeze ubuntu -- Some windows sometimes freeze https://bugs.launchpad.net/bugs/1936919 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1936922] [NEW] bluetooth devices always show 100% charged battery
Public bug reported: Regardless the true battery charge, any bluetooth connected device (I have tried with headphones, mouse, joystick) report 100% charge: $ upower --dump ... ... Device: /org/freedesktop/UPower/devices/mouse_dev_CC_60_9A_82_E6_F1 native-path: /org/bluez/hci0/dev_CC_60_9A_82_E6_F1 model:Dell WM527 Mouse serial: CC:60:9A:82:E6:F1 power supply: no updated: gio 1 gen 1970, 01:00:00 (1626777065 seconds ago) has history: yes has statistics: no mouse present: yes rechargeable:no state: unknown warning-level: none percentage: 100% icon-name: 'battery-missing-symbolic' ... ... ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jul 20 12:21:31 2021 InstallationDate: Installed on 2019-05-08 (804 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20KH006JIX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-23-generic root=/dev/mapper/kubuntu--vg-root ro noquiet nosplash i915.modeset=1 psmouse.synaptics_intertouch=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2020 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET73W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006JIX 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.20 dmi.modalias: dmi:bvnLENOVO:bvrN23ET73W(1.48):bd04/30/2020:br1.48:efr1.20:svnLENOVO:pn20KH006JIX:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH006JIX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH006JIX dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: D8:F2:CA:B8:F6:95 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:1564009 acl:110206 sco:0 events:3015 errors:0 TX bytes:612997 acl:208 sco:0 commands:2763 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2021-07-20T12:23:28.421672 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1936922 Title: bluetooth devices always show 100% charged battery Status in bluez package in Ubuntu: New Bug description: Regardless the true battery charge, any bluetooth connected device (I have tried with headphones, mouse, joystick) report 100% charge: $ upower --dump ... ... Device: /org/freedesktop/UPower/devices/mouse_dev_CC_60_9A_82_E6_F1 native-path: /org/bluez/hci0/dev_CC_60_9A_82_E6_F1 model:Dell WM527 Mouse serial: CC:60:9A:82:E6:F1 power supply: no updated: gio 1 gen 1970, 01:00:00 (1626777065 seconds ago) has history: yes has statistics: no mouse present: yes rechargeable:no state: unknown warning-level: none percentage: 100% icon-name: 'battery-missing-symbolic' ... ... ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jul 20 12:21:31 2021 InstallationDate: Installed on 2019-05-08 (804 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20KH006JIX ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-23-generic root=/dev/mapper/kubuntu--vg-root ro noquiet nosplash i915.modeset=1 psmouse.synaptics_intertouch=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2020 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET73W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006JIX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[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
** Changed in: heimdal (Ubuntu) Status: Confirmed => In Progress -- 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: In Progress 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Looks like same error with 1.7.x and 1.8.x using sof-tgl.ri [2.993700] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [2.993714] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [2.993959] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.251402] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.387760] sof-audio-pci :00:1f.3: use msi interrupt mode [4.402321] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [4.402952] sof-audio-pci :00:1f.3: Firmware info: version 1:8:0-9e7a8 [4.402954] sof-audio-pci :00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:18:0 [4.402956] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel [4.402963] sof-audio-pci :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [6.520768] sof-audio-pci :00:1f.3: error: firmware boot failure [6.520777] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [6.520783] sof-audio-pci :00:1f.3: error: status = 0x panic = 0x0211 [6.520805] sof-audio-pci :00:1f.3: error: extended rom status: 0x5 0x0 0x211 0x0 0x0 0x0 0x2530509 0x0 [6.520812] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [6.520814] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -5 [6.522883] 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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Test pass on https://certification.canonical.com/hardware/202010-28320/submission/223095/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options .
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
> The snap "dpr-wwan_1.0-wwan-test_amd64.snap" is provided by Lenovo (not published yet) Is there any estimated date when it will be released? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which
[Touch-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Please restore the folder name and try the latest sof-tgl.ri in the 1.7.x and 1.8.x then. -- 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 1925320] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Released Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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
Hello Mateusz, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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: Fix Committed Status in mesa source package in Hirsute: Fix Committed 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 1918855] Re: Xorg xserver got signal 6 to abort
Hello Kai-Chuan, or anyone else affected,
Accepted mesa into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-done verification-done-hirsute
** Tags added: verification-needed verification-needed-hirsute
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Committed
Status in mesa source package in Hirsute:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1925434] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1925434 Title: New bugfix release 21.0.3 Status in mesa package in Ubuntu: Invalid Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925434/+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 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
After enabling the unified cgroups hierarchy in systemd and running some tests, I can confirm that most things are working as expected, except for snapd. https://bileto.ubuntu.com/excuses/4602/impish.html The Bileto autopkgtests show (ignoring two unrelated/flaky failures in universe packages: suricata & mosquitto) that: * The systemd "tests-in-lxd" test fails, for snapd's "WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement" stderr output. If that stderr output is muted/ignored (by modifying autopkgtests itself) the test passes, as tested locally. * The snapd "autopkgtest:adt-local:tests/smoke/sandbox" spread test fails with an "all ubuntu systems must have strict confinement" error message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) Status in lxc: Fix Released Status in lxd: Fix Released Status in snapd: Confirmed Status in docker.io package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in systemd package in Ubuntu: Confirmed Status in lxc package in Debian: Fix Released Status in systemd package in Debian: Fix Released Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest- eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+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 1932311] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1932311 Title: migrate to llvm 12 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. Normally this would be done during the devel series, but this version was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+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
Hello Mateusz, or anyone else affected, Accepted mesa into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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: Fix Committed Status in mesa source package in Hirsute: Fix Committed 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Missing file now. (sof-tgl.ri) [2.977845] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [2.978089] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [2.978153] snd_hda_intel :01:00.1: enabling device ( -> 0002) [2.978583] snd_hda_intel :01:00.1: Disabling MSI [2.978600] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [3.018686] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [3.019131] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver [3.019169] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [3.019977] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [4.278689] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.400440] sof-audio-pci :00:1f.3: use msi interrupt mode [4.413812] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [4.413921] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 [4.413926] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 [4.413931] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [4.414536] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 -- 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
or you temporarily change the folder name of /lib/firmware/intel/sof to /lib/firmware/intel/sof-bak, is there erro about file not found? -- 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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Removed the link for sof-tgl-h.ri in /lib/firmware/intel/sof/. No errors about file not found. Same error as above. -- 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 1936312] Re: nm-online times out, failing autopkgtests
After reading a bit more about this issue, I can see where the conflict happens: 1/ systemd requires any container manager to mount /sys read-only, according to https://systemd.io/CONTAINER_INTERFACE/ in order to make udevd behave properly. 2/ NetworkManager checks for /sys to be read-only in order to decide if it should not be using udev 3/ lxc has a different understanding (and requirements), so it mounts /sys r/w, leading to confusion in NetworkManager. => IMO NetworkManager needs to do an improved check if it is running inside a container (in addition to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/78dc57d8f4af1a230053473f3eb7c18d1eaf0730) as the /sys read-only check is not enough for the LXC environment. Maybe NM could be extended to check for something like "systemd-detect-virt --container == 0" and not use udev in this case? -- 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 1934995] Re: Broken on ppc64el (toolchain bug?)
Ok: A list of things that it appears *not* to be: 1) binutils, valac, gcc versions. A umockdev build with the versions that hirsute's 0.15.4-1 built with. 2) The "debugedit: debian/umockdev/usr/bin/umockdev-record: Unknown DWARF DW_FORM_0x1f20" messages; building an unstripped umockdev doesn't emit this message (as it's no longer invoked by dh_strip), but the built package still results in the Mir tests failing as above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1934995 Title: Broken on ppc64el (toolchain bug?) Status in umockdev package in Ubuntu: New Bug description: umockdev appears to be broken on ppc64el in impish. Running it on one of Mir's umockdev-using tests results in: (impish-ppc64el)root@juju-deb017-porterbox-1:/build/mir-Xn1VqE/umockdev# umockdev-run ../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests MIR_CLIENT_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/client-modules/ MIR_SERVER_PLATFORM_PATH=../mir-2.4.1/build-ppc64el/bin/../lib/server-modules/ LD_LIBRARY_PATH=../mir-2.4.1/build-ppc64el/bin/../lib exec=../mir-2.4.1/build-ppc64el/bin/mir_umock_unit_tests.bin *** stack smashing detected ***: terminated umockdev-run: unable to propagate signal 6 to child 15833: No such process (You can also see this in the Mir 2.4.1-0ubuntu1 build log: https://launchpadlibrarian.net/546972958/buildlog_ubuntu-impish- ppc64el.mir_2.4.1-0ubuntu1_BUILDING.txt.gz ) Installing umockdev 0.15.4-1 and libumockdev0 0.15.4-1 from hirsute results in those tests passing. Strangely, rebuilding umockdev 0.15.4-1 in a hirsute sbuild environment results in packages that do *not* pass those tests, suggesting a toolchain change might be responsible. Unfortunately, I've tried rebuilding umockdev with gcc-9, gcc-11, and vala 0.48.12-1 in Impish and none of these appear to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: umockdev 0.16.1-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 16:04:15 2021 InstallationDate: Installed on 2021-06-26 (11 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: umockdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1934995/+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
