[Touch-packages] [Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure
@Timo,
In bionic mesa (20.0.8-0ubuntu1~18.04.1) it prefer i965 by default over iris.
rules: confflags_GALLIUM += -Dprefer-iris=false
Is it available to enable iris by default in bionic?
--
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 crashed with SIGABRT when under memory pressure
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Released
Status in mesa source package in Hirsute:
Fix Released
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 1554455] Re: "update-initramfs" is executed several times when you remove old kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1554455 Title: "update-initramfs" is executed several times when you remove old kernels Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Here is an example. I had several old kernels: linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic I used apt-get autoremove and here is the result: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: grub-pc-bin linux-headers-3.19.0-49 linux-headers-3.19.0-49-generic linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-image-extra-3.19.0-49-generic linux-image-extra-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic 0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded. After this operation, 502 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 211099 files and directories currently installed.) Removing grub-pc-bin (2.02~beta2-9ubuntu1.7) ... Removing linux-headers-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Removing linux-headers-3.19.0-49 (3.19.0-49.55~14.04.1) ... Removing linux-signed-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-extra-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Generating /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Deleting /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postrm.d
[Touch-packages] [Bug 1938938] Re: apparmor denials for gnutls configuration
Hmm there is also a crypto abstraction too https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor.d/abstractions/crypto - and this is included in the base abstraction so perhaps this *might* be another candidate..? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1938938 Title: apparmor denials for gnutls configuration Status in apparmor package in Ubuntu: New Bug description: gnutls library can be configured using /etc/gnutls/config for example to allow small keys and TLS versions below v1.2 however, if application is confined and has an apparmor profile and uses gnutls it will ignore such file, if it is not allowed to read it. For example: [ 382.586297] audit: type=1400 audit(1628068663.214:162): apparmor="DENIED" operation="open" profile="msmtp" name="/etc/gnutls/config" pid=18621 comm="sendmail" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [25379.358122] audit: type=1400 audit(1628093660.328:163): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/etc/gnutls/config" pid=53262 comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [25460.754092] audit: type=1400 audit(1628093741.726:164): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gnutls/config" pid=53347 comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 How can we allow to read /etc/gnutls/config for all apps that use gnutls? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1938938/+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 1938938] Re: apparmor denials for gnutls configuration
We already have an abstraction (ie a policy fragment) for openssl - https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor.d/abstractions/openssl - perhaps a similar one should be created for gnutls and then this can be #include'd into the profiles for the various applications that wish to use gnutls. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1938938 Title: apparmor denials for gnutls configuration Status in apparmor package in Ubuntu: New Bug description: gnutls library can be configured using /etc/gnutls/config for example to allow small keys and TLS versions below v1.2 however, if application is confined and has an apparmor profile and uses gnutls it will ignore such file, if it is not allowed to read it. For example: [ 382.586297] audit: type=1400 audit(1628068663.214:162): apparmor="DENIED" operation="open" profile="msmtp" name="/etc/gnutls/config" pid=18621 comm="sendmail" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [25379.358122] audit: type=1400 audit(1628093660.328:163): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/etc/gnutls/config" pid=53262 comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [25460.754092] audit: type=1400 audit(1628093741.726:164): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/gnutls/config" pid=53347 comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 How can we allow to read /etc/gnutls/config for all apps that use gnutls? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1938938/+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 1940458] Re: Audio Device not recognized. Problem with sound.
The issue of #3 is a known issue in the pulesaudio. About the hdmi audio can't be detected, maybe it is the graphic driver's issue, do you install the nvidia-drivers after upgrading? -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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/alsa-driver/+bug/1940458/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Changed in: openssl (Ubuntu) Importance: Undecided => Medium ** Changed in: openssl (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: openssl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. As a non-empty reply is incorrect behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940405] Re: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)
** Changed in: dh-python (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1940405 Title: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Status in dh-python package in Ubuntu: New Bug description: Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Disable the nosetests autopkg test. Unmaintained. * Disable the nosetests autopkg test. Unmaintained. * Fix DocTest. -> Those have been fixed by the NMU * Don't run test t301. -> I don't really understand the rationale for disabling this test. While the test case specifies a python version << 3.9 which wouldn't make it fit for current versions of Ubuntu, I believe what is being tested is the ability to specify the version bounds properly, which shouldn't be affected by the default version on the system. Changelog entries since current impish version 4.20201102ubuntu4: dh-python (4.20201102+nmu1) unstable; urgency=medium * Non-maintainer upload * Don't fail tests just because the default python gets hardcoded (Closes: #975536) -- Paul Gevers Sat, 27 Feb 2021 19:51:37 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1940405/+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 1939409] Re: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir
** Summary changed: - merge e2fsprogs 1.46.3-1 from Debian: s390x fails in test f_baddotdir + e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir ** Changed in: e2fsprogs (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1939409 Title: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir Status in e2fsprogs package in Ubuntu: In Progress Bug description: e2fsprogs 1.46.3-1ubuntu1 is in proposed. Architecture s390x fail in test f_baddotdir. The test image was changed with the new release. Next step should be analyzing the error on a s390x virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+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 1921518] Re: OpenSSL "double free" error
It appears that engine is destroyed multiple times. Please see https://github.com/Mellanox/pka/pull/37 which can help to guard against that. Meanwhile I'm continuing to research as to why engine is destroyed multiple times. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
This bug was fixed in the package linux - 5.13.0-14.14 --- linux (5.13.0-14.14) impish; urgency=medium * impish/linux: 5.13.0-14.14 -proposed tracker (LP: #1938565) * Miscellaneous Ubuntu changes - SAUCE: Revert "UBUNTU: SAUCE: random: Make getrandom() ready earlier" - SAUCE: random: properly make getrandom() ready earlier * Miscellaneous upstream changes - seq_buf: Fix overflow in seq_buf_putmem_hex() - bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc - ext4: cleanup in-core orphan list if ext4_truncate() failed to get a transaction handle - ext4: fix kernel infoleak via ext4_extent_header - ext4: fix overflow in ext4_iomap_alloc() - ext4: return error code when ext4_fill_flex_info() fails - ext4: correct the cache_nr in tracepoint ext4_es_shrink_exit - ext4: remove check for zero nr_to_scan in ext4_es_scan() - ext4: fix avefreec in find_group_orlov - ext4: use ext4_grp_locked_error in mb_find_extent -- Andrea Righi Mon, 02 Aug 2021 14:23:08 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1921518] Re: OpenSSL "double free" error
** Changed in: openssl (Ubuntu) Importance: Undecided => Critical ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: New Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1940481] [NEW] dhclient.conf should set send DHCPv6 host-name option
Public bug reported: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Description changed: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); - With this option it causes dhcpy6d's dynamic DNS update (to bind9) to + Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1940481 Title: dhclient.conf should set send DHCPv6 host-name option Status in isc-dhcp package in Ubuntu: New Bug description: Despite the fix in 2012 (bug #991360) the default configuration shipped with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the DHCPv6 hostname option by default. All it needs is: # send host-name with DHCPv6 not just DHCPv4 send fqdn.fqdn = gethostname(); Without this option it causes dhcpy6d's dynamic DNS update (to bind9) to fail because the hostname is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1940481/+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 1939750] Re: Please merge 7.74.0-1.3
Thank you Brian. I will follow up with the close upon migration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1939750 Title: Please merge 7.74.0-1.3 Status in curl package in Ubuntu: Confirmed Status in curl package in Debian: Unknown Bug description: Debian version 7.74.0-1.3 cherry-picks a fix for a command line API breakage that would be unexpected in a minor version release. Please help merge. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064 https://github.com/curl/curl/issues/6321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1939750/+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 1939750] Re: Please merge 7.74.0-1.3
I uploaded this but just now realized that the bug number wasn't in the changelog. Please manually close this after its migrated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1939750 Title: Please merge 7.74.0-1.3 Status in curl package in Ubuntu: Confirmed Status in curl package in Debian: Unknown Bug description: Debian version 7.74.0-1.3 cherry-picks a fix for a command line API breakage that would be unexpected in a minor version release. Please help merge. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064 https://github.com/curl/curl/issues/6321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1939750/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Package changed: ubuntu-meta (Ubuntu) => debian-installer (Ubuntu) ** Summary changed: - Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata + intel-microcode not included 20.04 initrd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1938588 Title: intel-microcode not included 20.04 initrd Status in debian-installer package in Ubuntu: New Status in debian-installer source package in Focal: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1938588/+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 1939750] Re: Please merge 7.74.0-1.3
I'll sponsor this today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1939750 Title: Please merge 7.74.0-1.3 Status in curl package in Ubuntu: Confirmed Status in curl package in Debian: Unknown Bug description: Debian version 7.74.0-1.3 cherry-picks a fix for a command line API breakage that would be unexpected in a minor version release. Please help merge. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064 https://github.com/curl/curl/issues/6321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1939750/+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 1939728] Re: Please merge icu 67.1-7 (main) from Debian unstable
It looks like this got sponsored so I'm unsubscribing the sponsors team. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1939728 Title: Please merge icu 67.1-7 (main) from Debian unstable Status in icu package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1939728/+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 1940458] Re: Audio Device not recognized. Problem with sound.
Attached another screenshot. ** Attachment added: "Screenshoot3.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1940458/+attachment/5518806/+files/Screenshoot3.png -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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/alsa-driver/+bug/1940458/+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 1940458] Re: Audio Device not recognized. Problem with sound.
Attached another screenshot. ** Attachment added: "Screenshoot2.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1940458/+attachment/5518805/+files/Screenshoot2.png -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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/alsa-driver/+bug/1940458/+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 1940458] Re: Audio Device not recognized. Problem with sound.
After last Ubuntu Updates,I can watch now the HDMI/DisplayPort2, but when you go to Ubuntu Settings in Sound options (watch the screenshot attached in this comment), you can watch the HDMI/DisplayPort 2 and the config Salida Digital Estereo (Stereo Digital Output). If you change the config Stereo to HDMI 7.1 (I only have a stereo Speakers not 7.1 speakers), the config setting disappear in the Ubuntu Settings Menu and you can't select it again and you can't change it (check the screenshot). If you try to select HDMI/DisplayPort 2 it doesn't work because the 7.1 sound was selected and I have got a stereo speakers. To fix it I have opened pulse audio (check the other Screenshot attached) and in the top setting, GP102 HDMI Audio set the setting "Stereo Digital Output (HDMI2)". After that the sound was recovered. I don't know if the correct detection of the sound cards when switching on the PC was fixed or not. You will check if this part is fixed now with the last Ubuntu Updates. Thank you. ** Attachment added: "Screenshoot1.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1940458/+attachment/5518804/+files/Screenshoot1.png -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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/alsa-driver/+bug/1940458/+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 1940458] Re: Audio Device not recognized. Problem with sound.
Extra info attached. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1940458/+attachment/5518802/+files/lspcik.txt -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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/alsa-driver/+bug/1940458/+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 1940458] [NEW] Audio Device not recognized. Problem with sound.
Public bug reported: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x: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 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1940458/+attachment/5518796/+files/prevboot.txt -- 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/1940458 Title: Audio Device not recognized. Problem with sound. Status in alsa-driver package in Ubuntu: New Bug description: Hi, after the last Ubuntu updates, I have lost the sound of my screen speakers (yes the monitor has got integrated a speakers), this sound is provided from the GPU via HDMI: [System Product Name, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Sometimes when I reboot the PC, it works and detect the Nvidia GPU 82 HDMI/DP and I can hear the sound of the screen speakers. But a lot of times when I switch on the PC the selected sound card is Digital S/PDIF Family 17h and I can't hear nothing when it happens. If I try to change the sound card, I can't, it doesn't appear in the sound settings options. If I use Pulse Audio, It doesn't appear in it too. Please, fix this bug, It is very annoying to turn on the PC and not hear anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pitx 1733 F pulseaudio /dev/snd/controlC1: pitx 1733 F pulseaudio /dev/snd/controlC0: pitx 1733 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 18 18:46:27 2021 InstallationDate: Installed on 2021-01-14 (215 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourceP
[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot
The attachment "sd-netlink-make-timeout-message-sealed.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: 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/1930738 Title: network configuration failed on reboot Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Bug description: [impact] number of statically defined addresses for an interface in systemd- networkd is limited [test case] Note: this only occurs in a container; this is not reproducable in a VM or bare metal. Configure netplan with the attached yaml file (10-test.yaml) enable debug for systemd-networkd reboot the system and check the journalctl output to see if any errors were reported for systemd-networkd, e.g.: $ journalctl -b -u systemd-networkd | grep 'could not set' Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set address: Connection timed out ... Note that systemd may be able to actually correctly set all addresses, but fails to communicate with netlink to determine the addresses are set, so just checking the output of 'ip a' is not enough, the systemd- networkd debug log should be checked [regression potential] possible failure to correctly apply all statically defined interfaces [scope] TBD, not fully fixed upstream this is needed in f and b this is fixed upstream with commits 628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are included in v246 and later, so this is fixed in h and later [other info] I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as that changes the udev-related behavior of networkd-manager inside a container, which is not appropriate for SRU for this bug, as I don't see any clear bug-related reason to change that behavior. Additionally this requires the typo fix from commit 4934ba2121d76229659939e19ab7d70a89446629 [original 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
[Touch-packages] [Bug 1928989] Re: expiring trust anchor compatibility issue
psqlodbc confuses me, as if clusters fail to create. Seems unrelated to openssl changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1928989 Title: expiring trust anchor compatibility issue Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Trusty: New Status in openssl source package in Xenial: Fix Committed Bug description: [Impact] * openssl fails to talk to letsencrypt website past September 2021, despite trusting the letsencrypt root certificate. [Test Plan] * Import staging cert equivalent to ISRG Root X1 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem * Import expired staging cert equivalen tto DST Root CA X3 https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem * Test connectivity to the expired-root-ca test website https://expired-root-ca-test.germancoding.com setup: apt install openssl ca-certificates wget wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-x1.pem wget https://letsencrypt.org/certs/staging/letsencrypt-stg-root-dst.pem cat letsencrypt-stg-root-x1.pem letsencrypt-stg-root-dst.pem >> ca.pem test case: openssl s_client -connect expired-root-ca-test.germancoding.com:443 -servername expired-root-ca-test.germancoding.com -verify 1 -verifyCAfile ca.pem bad result: connection failed verify depth is 1 CONNECTED(0003) depth=3 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Doctored Durian Root CA X3 verify error:num=10:certificate has expired notAfter=Jan 30 14:01:15 2021 GMT 140672978626200:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1264: good result: connection successful verify depth is 1 CONNECTED(0003) depth=2 C = US, O = (STAGING) Internet Security Research Group, CN = (STAGING) Pretend Pear X1 verify return:1 depth=1 C = US, O = (STAGING) Let's Encrypt, CN = (STAGING) Artificial Apricot R3 verify return:1 depth=0 CN = expired-root-ca-test.germancoding.com verify return:1 --- Certificate chain 0 s:/CN=expired-root-ca-test.germancoding.com i:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 1 s:/C=US/O=(STAGING) Let's Encrypt/CN=(STAGING) Artificial Apricot R3 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 2 s:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Pretend Pear X1 i:/C=US/O=(STAGING) Internet Security Research Group/CN=(STAGING) Doctored Durian Root CA X3 --- Server certificate -BEGIN CERTIFICATE- Connection should be successful and trusted with correctly working openssl s_client that can manage to ignore expired CA, and build a valid trust path using non-expired CA in the chain. [Testcase #2] $ sudo apt install ca-certificates wget faketime # Good connectivity $ wget -O /dev/null https://canonical.com --2021-07-13 11:54:20-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-07-13 11:54:20 (22.3 MB/s) - '/dev/null' saved [30933/30933] # Jump to october to experience failure $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2b, 2001:67c:1360:8001::2c, 91.189.88.181, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2b|:443... connected. ERROR: cannot verify canonical.com's certificate, issued by 'CN=R3,O=Let\'s Encrypt,C=US': Issued certificate has expired. To connect to canonical.com insecurely, use `--no-check-certificate'. # upgrade to new openssl, to see that connectivity is restored, even in october $ dpkg-query -W libssl1.0.0 libssl1.0.0:amd64 1.0.2g-1ubuntu4.20 $ faketime '2021-10-01' wget -O /dev/null https://canonical.com --2021-10-01 00:00:00-- https://canonical.com/ Resolving canonical.com (canonical.com)... 2001:67c:1360:8001::2c, 2001:67c:1360:8001::2b, 91.189.88.180, ... Connecting to canonical.com (canonical.com)|2001:67c:1360:8001::2c|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 30933 (30K) [text/html] Saving to: '/dev/null' /dev/null 100%[>] 30.21K --.-KB/sin 0.001s 2021-10-01 00:00:00 (21.9 MB/s) - '/dev/null' saved [30933/30933] [Where problems could occur] * Changes as to how the trust p
[Touch-packages] [Bug 1937951] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1937951 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- 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/1937951 Title: modules for non-existent hardware are loaded for unknown reason (Ubunntu 20.04, kernel 5.4.0-80-generic) Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: My laptop is Asus X302LA. I removed its HDD and plugged it externally via USB-SATA convertor. To restore the system's bootability, I had to switch from MODULES=dep to MODULES=most in /etc/initramfs-tools/initramfs.conf and regenerate initramfs images by command update-initramfs -u -k all After a successful boot I checked lsmod output and was surprised by a number of loaded modules for seemingly absent hardware. Like, inv_mpu6050 and ak8975. Do I have a way to check this hardware is actually present and is reporting any meaningful data ? If no, do Ubuntu maintainers of linux kernel and initramfs tools have a way to avoid loading these modules when their hardware is absent ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1937951/+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 1940405] [NEW] Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main)
Public bug reported: Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Disable the nosetests autopkg test. Unmaintained. * Disable the nosetests autopkg test. Unmaintained. * Fix DocTest. -> Those have been fixed by the NMU * Don't run test t301. -> I don't really understand the rationale for disabling this test. While the test case specifies a python version << 3.9 which wouldn't make it fit for current versions of Ubuntu, I believe what is being tested is the ability to specify the version bounds properly, which shouldn't be affected by the default version on the system. Changelog entries since current impish version 4.20201102ubuntu4: dh-python (4.20201102+nmu1) unstable; urgency=medium * Non-maintainer upload * Don't fail tests just because the default python gets hardcoded (Closes: #975536) -- Paul Gevers Sat, 27 Feb 2021 19:51:37 +0100 ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1940405 Title: Sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Status in dh-python package in Ubuntu: New Bug description: Please sync dh-python 4.20201102+nmu1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Disable the nosetests autopkg test. Unmaintained. * Disable the nosetests autopkg test. Unmaintained. * Fix DocTest. -> Those have been fixed by the NMU * Don't run test t301. -> I don't really understand the rationale for disabling this test. While the test case specifies a python version << 3.9 which wouldn't make it fit for current versions of Ubuntu, I believe what is being tested is the ability to specify the version bounds properly, which shouldn't be affected by the default version on the system. Changelog entries since current impish version 4.20201102ubuntu4: dh-python (4.20201102+nmu1) unstable; urgency=medium * Non-maintainer upload * Don't fail tests just because the default python gets hardcoded (Closes: #975536) -- Paul Gevers Sat, 27 Feb 2021 19:51:37 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1940405/+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 1918410] Re: isc-dhcp-client denied by apparmor
#4 Does not work for me.
My /etc/apparmor.d/sbin.dhclient partly looks like this:
@{PROC}/[0-9]*/net/ r,
@{PROC}/[0-9]*/net/** r,
# @{PROC}/[0-9]*/task/[0-9]*/comm rw,
@{PROC}/@{pids}*/task/[0-9]*/comm rw,
Maybe I'm missing something?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Triaged
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935051] Re: systemd pid 1 memory leak
Just checked again, bug still exist for latest systemd package on focal. # apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935051 Title: systemd pid 1 memory leak Status in systemd package in Ubuntu: New Bug description: Hi everybody. We've meet a memory leak of pid1 process on the focal release. When we launch chef-client, several systemd .service and .timers are checked for state. Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen on xenial and bionic releases. I straced pid1 when that leak happen and found brk call. On pmap view of pid 1 it's anon memory grow on the same address and all marked as dirty. All that leak memory can be freed by calling systemctl daemon-reexec. Searching in systemd github repo i found this commit https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d - it may be related to this leak. Environment: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 x86_64 Package: systemd: Installed: 245.4-4ubuntu3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677668] Re: no GARPs during ephemeral boot
I'm marking this bug as incomplete for MAAS, since it's not clear what actually needs to be fixed in MAAS. It seems like this needs to be fixed at a lower level. ** Changed in: maas Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1677668 Title: no GARPs during ephemeral boot Status in MAAS: Incomplete Status in cloud-init package in Ubuntu: Incomplete Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Deploys time out with an error on the console that says, "Can not apply stage final, no datasource found! Likely bad things to come!" How to duplicate: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) 1) Rack Controller and Region Controller in different VLANs 2) Use Cisco ASA as the router with "ARP Inspection" enabled 3) Clear the router ARP cache 4) Deploy 2 maas machines with interfaces set to "Static assign" 5) Observe deploys successfully 6) Release both machines and swap IP's. 7) Redeploy the same 2 machines 8) Observe deploy failure with the machine consoles stuck in the "ubuntu login" screen with "Can not apply stage final, no datasource Found! Likely bad things to come!" The root cause is that during ephemeral PXE booting, no GARPs are sent, which in our environment will cause our router (Cisco ASA) to hold on to ARP table entries until it expires (default= 4 hours). Then combined with ASA feature "ARP Inspection" will drop packets from a MaaS machine using the previously used IP from a different MaaS machine. The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily. Running tcpdump on the Rack Controller, showed no GARPs from the deploying MaaS machine. If there were GARPs sent, then the router would refresh its ARP cache thus avoiding the ARP Inspection dropping. [Excerpt from Cisco ASA] http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf When you enable ARP inspection, the ASA compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions: • If the IP address, MAC address, and source interface match an ARP entry, the packet is passed through. • If there is a mismatch between the MAC address, the IP address, or the interface, then the ASA drops the packet. • If the ARP packet does not match any entries in the static ARP table, then you can set the ASA to either forward the packet out all interfaces (flood), or to drop the packet. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1677668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot
** Patch added: "sd-netlink-make-timeout-message-sealed.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5518731/+files/sd-netlink-make-timeout-message-sealed.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/1930738 Title: network configuration failed on reboot Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Focal: Incomplete Bug description: [impact] number of statically defined addresses for an interface in systemd- networkd is limited [test case] Note: this only occurs in a container; this is not reproducable in a VM or bare metal. Configure netplan with the attached yaml file (10-test.yaml) enable debug for systemd-networkd reboot the system and check the journalctl output to see if any errors were reported for systemd-networkd, e.g.: $ journalctl -b -u systemd-networkd | grep 'could not set' Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set address: Connection timed out ... Note that systemd may be able to actually correctly set all addresses, but fails to communicate with netlink to determine the addresses are set, so just checking the output of 'ip a' is not enough, the systemd- networkd debug log should be checked [regression potential] possible failure to correctly apply all statically defined interfaces [scope] TBD, not fully fixed upstream this is needed in f and b this is fixed upstream with commits 628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are included in v246 and later, so this is fixed in h and later [other info] I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as that changes the udev-related behavior of networkd-manager inside a container, which is not appropriate for SRU for this bug, as I don't see any clear bug-related reason to change that behavior. Additionally this requires the typo fix from commit 4934ba2121d76229659939e19ab7d70a89446629 [original 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: C
[Touch-packages] [Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
** Tags added: bot-stop-nagging ** Changed in: ubuntu-z-systems Status: New => 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1932354] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1932354 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1932354 Title: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable) Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz storage PASS networkd-test.py FAIL non-zero exit status 1 build-login FAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. boot-and-servicesFAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. udev FAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. root-unittests FAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. tests-in-lxd SKIP installation fails and skip-not-installable set upstream FAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. boot-smoke FAIL badpkg blame: systemd badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. systemd-fsckdSKIP exit status 77 and marked as skippable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932354/+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 1931725] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1931725 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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
