[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Description changed: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. + + To SRU to focal: + + [Impact] + + * for OEM project, lts is been used. And collect log is important. +With built-in tool to get acpidump, we don't need to install +extra tool in the end-customer's machine. That make it much +easier for the oem process. + + * By call built-in utility, we no lounger need to install extra +tools to collect data that's both complete and convenient for +HWE people to work on. + + [Test Case] + + * before this applied, run oem-getlog without install acpidump. +we can't get the dump data. After this applied, we can just dump +the data HWE need. + + * test step: install the new package, run + +sudo -E oem-getlogs [-c case_id] to get the + +use apport-unpack to unpack the apport file. + +check the acpidump file. HWE people know much better on check +the acpidump file. Give the dump_acpi_tables.py just updated and SRUed +by HWE/ACPI/UEFI expert, it's pretty safe to do so. + + [Regression Potential] + + * Given the modification change the way to collect log, even it +failed, it won't break apport itself. Just the collected log +might contain data not so valid. + + * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they +just reviewed and updated the dump_acpi_tables.py script, I +believe it will have good quality. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1893728] [NEW] Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive
Public bug reported: Information in shows that krb5 versions before 1.17 are vulnerable to CVE-2018-20217. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Based on Debian bug report, this is already fixed in 1.16.2 version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917387 Ubuntu 20.04 LTS (Focal Fossa) includes version krb5 1.17.6: https://launchpad.net/ubuntu/focal/+source/krb5 Ubuntu CVE Tracker page shows that Ubuntu 20.04 LTS (Focal Fossa) doesn't have a package where CVE-2018-20217 is fixed. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Steps to reproduce: This was found when examining AWS Elastic Container Registry Vulnerability scanning results for a Docker image based on latest Ubuntu 20.04: Here is the complete line from the report: krb5:1.17-6ubuntu4 MEDIUM A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. It can be seen from the scan that the Docker image included krb5 bversion 1.17-6. Expected: No vulnerability finding. Actual: krb5 bversion 1.17-6ubuntu4 is reported as vulnerable to CVE-2018-20217. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1893728 Title: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive Status in krb5 package in Ubuntu: New Bug description: Information in shows that krb5 versions before 1.17 are vulnerable to CVE-2018-20217. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Based on Debian bug report, this is already fixed in 1.16.2 version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917387 Ubuntu 20.04 LTS (Focal Fossa) includes version krb5 1.17.6: https://launchpad.net/ubuntu/focal/+source/krb5 Ubuntu CVE Tracker page shows that Ubuntu 20.04 LTS (Focal Fossa) doesn't have a package where CVE-2018-20217 is fixed. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Steps to reproduce: This was found when examining AWS Elastic Container Registry Vulnerability scanning results for a Docker image based on latest Ubuntu 20.04: Here is the complete line from the report: krb5:1.17-6ubuntu4 MEDIUM A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. It can be seen from the scan that the Docker image included krb5 bversion 1.17-6. Expected: No vulnerability finding. Actual: krb5 bversion 1.17-6ubuntu4 is reported as vulnerable to CVE-2018-20217. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1893728/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891461/+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 1893704] Re: Very slow execution of boot and other tasks on an Atom N270
There's a large number of possible reasons for the slowness here. Indeed maybe try a lighter version like: http://cdimage.ubuntu.com/xubuntu/releases/18.04.5/release/xubuntu-18.04.5-desktop-i386.iso ** Summary changed: - very slow execution of boot and other tasks + Very slow execution of boot and other tasks on an Atom N270 ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893704 Title: Very slow execution of boot and other tasks on an Atom N270 Status in Ubuntu: Won't Fix Bug description: problems with time taken to execute tasks, perhaps as a result of cumulative updates over several lts editions.i am a complete novice, sorry I cannot provide more specific information.With more recent updates,a lot of time seemed to be spent loading? generic files one after another,for no apparent reason,{just watching update details in progress window}what I think is needed is a clean install, but I do not know how to do that and maintain data etc.The computer is a small netbook,Medion E1210.,probably needs a lighter version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 31 22:47:07 2020 DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express Integrated Graphics Controller [1462:0110] Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1462:0110] MachineType: MEDION E1210 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago) dmi.bios.date: 07/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E1210 dmi.board.vendor: MEDION dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001: dmi.product.family: To be filled by O.E.M. dmi.product.name: E1210 dmi.product.version: Ver.001 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 26 22:14:29 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1220 vendor CPT xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893704/+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 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
** Description changed: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in - /etc/syslog and the load spikes. + /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc /update-motd.d). This only started on the system in question after a recent set of system updates were in stalled. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non-interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then - # Fall back to using the very slow lsb_release utility - DISTRIB_DESCRIPTION=$(lsb_release -s -d) + # Fall back to using the very slow lsb_release utility + DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" ** Description changed: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc /update-motd.d). This only started on the system in question after a - recent set of system updates were in stalled. + recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non-interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in openssh package in Ubuntu: New Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login
[Touch-packages] [Bug 1893686] Re: [nvidia] Some apps show semi-random corruption
Thanks for the bug report. Are you able to provide a screenshot of the full desktop showing corrupt and non-corrupt apps side by side? ** Summary changed: - Some apps show semi-random corruption + [nvidia] Some apps show semi-random corruption ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps show semi-random corruption Status in gtk+3.0 package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: NVidia drivers in Ubuntu 20.04 show corruption in certain applications. Most egregious bug appears to be "Ubuntu Software Center" which is almost completely transparent and unusable. Also see occasional corruption in window decorations in other apps, namely Gnome Tweaks as a prime example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 13:33:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7] NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729] InstallationDate: Installed on 2020-06-25 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.12 dmi.board.name: 02XRCM dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R8 dmi.product.sku: 08F7 dmi.product.version: 1.0.12 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+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 1893655] Re: Headphones connect but don't appear as audio output
Even if it's not that bug, please try the same workaround. Just delete your personal audio config: cd ~/.config rm -rf pulse and then log out and in again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1893655 Title: Headphones connect but don't appear as audio output Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893655/+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 1893716] [NEW] scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
Public bug reported: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /etc/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc /update-motd.d). This only started on the system in question after a recent set of system updates were in stalled. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non-interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in openssh package in Ubuntu: New Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /etc/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were in stalled. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1893716/+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 1893655] Re: Headphones connect but don't appear as audio output
Do you mean they don't appear in the audio device list at all, or they just don't get used even when they're selected from the list? Either way, bug 1866194 might be the answer and a fix for that should arrive in 20.04 in the coming weeks. ** Package changed: bluez (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1893655 Title: Headphones connect but don't appear as audio output Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893655/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Would this bug cause a gnome-session initialization delay? My logs have this error and technically everything "works" correctly but initialization of the user session takes > 1 min. The greeter isn't exactly fast either but definitely more tolerable. My systemd analysis looks fine too. Really hoping this bug is the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Confirmed Status in pam source package in Groovy: Confirmed Status in pam package in Debian: New Bug description: Hello, after upgrading to focal I found the following in my journalctl output: Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory The login package stopped packaging this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 and now forcibly removes the file: https://paste.ubuntu.com/p/myh9cGWrHD/ However, the pam package's pam_unix.so module has not yet been adapted to ignore this file: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25 Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 24 23:35:33 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1893704] Re: very slow execution of boot and other tasks
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893704 Title: very slow execution of boot and other tasks Status in xorg package in Ubuntu: New Bug description: problems with time taken to execute tasks, perhaps as a result of cumulative updates over several lts editions.i am a complete novice, sorry I cannot provide more specific information.With more recent updates,a lot of time seemed to be spent loading? generic files one after another,for no apparent reason,{just watching update details in progress window}what I think is needed is a clean install, but I do not know how to do that and maintain data etc.The computer is a small netbook,Medion E1210.,probably needs a lighter version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 31 22:47:07 2020 DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express Integrated Graphics Controller [1462:0110] Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1462:0110] MachineType: MEDION E1210 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago) dmi.bios.date: 07/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E1210 dmi.board.vendor: MEDION dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001: dmi.product.family: To be filled by O.E.M. dmi.product.name: E1210 dmi.product.version: Ver.001 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 26 22:14:29 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1220 vendor CPT xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893704/+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 1893704] [NEW] very slow execution of boot and other tasks
You have been subscribed to a public bug: problems with time taken to execute tasks, perhaps as a result of cumulative updates over several lts editions.i am a complete novice, sorry I cannot provide more specific information.With more recent updates,a lot of time seemed to be spent loading? generic files one after another,for no apparent reason,{just watching update details in progress window}what I think is needed is a clean install, but I do not know how to do that and maintain data etc.The computer is a small netbook,Medion E1210.,probably needs a lighter version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 31 22:47:07 2020 DistUpgraded: 2020-08-27 12:21:54,637 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GSE Express Integrated Graphics Controller [1462:0110] Subsystem: Micro-Star International Co., Ltd. [MSI] Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1462:0110] MachineType: MEDION E1210 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=38a83982-ae1b-4b05-bf17-ca55d6630e0a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-08-27 (4 days ago) dmi.bios.date: 07/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E1210 dmi.board.vendor: MEDION dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd07/16/2008:svnMEDION:pnE1210:pvrVer.001:rvnMEDION:rnE1210:rvrVer.001:cvnMEDION:ct3:cvrVer.001: dmi.product.family: To be filled by O.E.M. dmi.product.name: E1210 dmi.product.version: Ver.001 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Aug 26 22:14:29 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1220 vendor CPT xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- very slow execution of boot and other tasks https://bugs.launchpad.net/bugs/1893704 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I was having this issue, didn't gather much info on in, but I was on Ubuntu 18.x LTS, my Dell Vostro was detecting 3 mics, when I actually had only 1. I reinstalled Ubuntu, 20.04 now. At first glance it was detecting the same mics and some buzz noise, same with the 18.x, but then after the initial update, I restarted my pc and now it's all working, and it only detects 1 mic -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891224 Title: [Hyper-V] VSS and File Copy daemons intermittently fails to start Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in systemd source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in systemd source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in systemd source package in Groovy: Invalid Bug description: [Impact] We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago. From the journal : Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_vss.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon. Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job hv-vss-daemon.service/start failed with result 'dependency'. Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai> Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_fcopy.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon. We've seen problems in the past with KVP daemons that looked very similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 [Test Case] There two main scenarios that need to be tested: 1. Azure instances: - Just start an azure instance using our Ubuntu images and check the the status of the hv-vss-daemon and hv-fcopy-daemon services using systemctl. - If the issue is solved they shouldn't be listed as failed. 2. Local Hyper-V VM: - Create a local Hyper-V instance and enable the two systemd services if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot. - You can change the integration services that are enable to the guest. 1. With desktop integration and the backup feature disabled, the hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be listed as failed. 2. With the same features enabled the services should start without errors. [Regression Potential] The major risk with a potential regression is that those systemd service units are shipped by a package produced by our generic kernels and not the linux-azure kernel. So in case of a regression we might need to re-spin the generic kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891224/+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 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1891224 Title: [Hyper-V] VSS and File Copy daemons intermittently fails to start Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in systemd source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in systemd source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in systemd source package in Groovy: Invalid Bug description: [Impact] We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago. From the journal : Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start tim> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_vss.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon. Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-daemon.service: Job hv-vss-daemon.service/start failed with result 'dependency'. Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_vss.device: Job sys-devices-virtual-misc-vmbus\x21hv_vss.device/start fai> Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_fcopy.device: Job sys-devices-virtual-misc-vmbus\x21hv_fcopy.device/start> Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-virtual-misc-vmbus\x21hv_fcopy.device. Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon. We've seen problems in the past with KVP daemons that looked very similar : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063 [Test Case] There two main scenarios that need to be tested: 1. Azure instances: - Just start an azure instance using our Ubuntu images and check the the status of the hv-vss-daemon and hv-fcopy-daemon services using systemctl. - If the issue is solved they shouldn't be listed as failed. 2. Local Hyper-V VM: - Create a local Hyper-V instance and enable the two systemd services if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot. - You can change the integration services that are enable to the guest. 1. With desktop integration and the backup feature disabled, the hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be listed as failed. 2. With the same features enabled the services should start without errors. [Regression Potential] The major risk with a potential regression is that those systemd service units are shipped by a package produced by our generic kernels and not the linux-azure kernel. So in case of a regression we might need to re-spin the generic kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891224/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils
Could you please add some SRU information to the bug description to facilitate the SRU process? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1893695] [NEW] package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
Public bug reported: All I know is that it states that I must install libx264-155:amd64 before proceeding with any further installation. This is a new installations, but I have completed to date five other upgrades without too much issue. Not sure why it is causing problems this time as things seem to be installing fine. One observation is that i noted the software centre is short of packages to start. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx264-155:amd64 2:0.155.2917+git0a84d98-2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 31 21:38:05 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: x264 Title: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: x264 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to x264 in Ubuntu. https://bugs.launchpad.net/bugs/1893695 Title: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in x264 package in Ubuntu: New Bug description: All I know is that it states that I must install libx264-155:amd64 before proceeding with any further installation. This is a new installations, but I have completed to date five other upgrades without too much issue. Not sure why it is causing problems this time as things seem to be installing fine. One observation is that i noted the software centre is short of packages to start. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx264-155:amd64 2:0.155.2917+git0a84d98-2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 31 21:38:05 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: x264 Title: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1893695/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here. Ubuntu 20.04 LTS and Ubuntu 18.04 LTS JBL Reflect Flow Dell Latitude 3400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1893686] Re: Some apps show semi-random corruption
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: Some apps show semi-random corruption Status in xorg package in Ubuntu: New Bug description: NVidia drivers in Ubuntu 20.04 show corruption in certain applications. Most egregious bug appears to be "Ubuntu Software Center" which is almost completely transparent and unusable. Also see occasional corruption in window decorations in other apps, namely Gnome Tweaks as a prime example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 13:33:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7] NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729] InstallationDate: Installed on 2020-06-25 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.12 dmi.board.name: 02XRCM dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R8 dmi.product.sku: 08F7 dmi.product.version: 1.0.12 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893686/+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 1893686] [NEW] Some apps show semi-random corruption
You have been subscribed to a public bug: NVidia drivers in Ubuntu 20.04 show corruption in certain applications. Most egregious bug appears to be "Ubuntu Software Center" which is almost completely transparent and unusable. Also see occasional corruption in window decorations in other apps, namely Gnome Tweaks as a prime example. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 13:33:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell UHD Graphics 630 (Desktop 9 Series) [1028:08f7] NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] [10de:1e87] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU104 [GeForce RTX 2080 Rev. A] [1028:3729] InstallationDate: Installed on 2020-06-25 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Alienware Alienware Aurora R8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=c80a6058-31c8-4117-a747-3193e765eff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.12 dmi.board.name: 02XRCM dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.12:bd02/20/2020:svnAlienware:pnAlienwareAuroraR8:pvr1.0.12:rvnAlienware:rn02XRCM:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R8 dmi.product.sku: 08F7 dmi.product.version: 1.0.12 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- Some apps show semi-random corruption https://bugs.launchpad.net/bugs/1893686 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
note there is only one xenial reverse-dep autopkgtest failure, for nfs- utils on s390x, and that test has always failed and can be ignored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Committed Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.2ubuntu0.1 amd64converts RPC program numbers into universal addresses ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:927 *:* 13471/rpcbind same default behavior after upgrade: ubuntu@lp304393-x:~$ dpkg -l|grep rpcbind ii rpcbind 0.2.3-0.2ubuntu0.16.04.1 amd64converts RPC program numbers into universal addresses ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:625 *:* 14441/rpcbind with parameter added, random port disabled: ubuntu@lp304393-x:~$ cat /etc/default/rpcbind RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc ubuntu@lp304393-x:~$ with parameter commented, default behavior restored: ubuntu@lp304393-x:~$ cat /etc/default/rpcbind #RPCBIND_RMTCALL_DEFAULT_DISABLED=1 ubuntu@lp304393-x:~$ sudo systemctl restart rpcbind ubuntu@lp304393-x:~$ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 *:660 *:* 14476/rpcbind ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Committed Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the
[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Patch added: "focal_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5406228/+files/focal_initramfs_lp1879980_V2.debdiff -- 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/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reproduce this, one must boot a system (virtual machine is good) with the wrong console set on kernel command-line through the "console=" parameter *and* not pass the "quiet" parameter. * Also, e2fsck tool shouldn't be present in the initrd - for that, the 6th field of /etc/fstab (fs_passno) should be 0 and initrd must be recreated after that. This is the default in Ubuntu, though. [Regression Potential] * The regression potential is small, we're just returning 0 after a printf that is executed in error paths, so I don't expect any issues from that. But in case something bad happens after this change, I expect a more friendly" breakage, like an initramfs panic (drop to a shell), not a silent failure or boot-loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP #1893675) - it's non-related with the fixes proposed here, but we need to make autopkgtest happy or we cannot get the package released, so here goes the V2 of the initramfs-tools debdiffs. Notice the SRU is mainly driven in this LP and/or LP #1879987. ** Patch added: "groovy_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5406229/+files/groovy_initramfs_lp1879980_V2.debdiff -- 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/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: In Progress Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: In Progress Status in initramfs-tools source package in Groovy: In Progress Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Regression potential] * There are potential for regressions, since this is a change in 2 boot components. The patches were designed in a way to keep the regular case working, it changes the failure case which is not currently working anyway. * A modification in the behavior of cryptsetup was introduced: right now, if we fail the password 3 times (the default maximum attempts), the script doesn't "panic" and drop to a shell immediately; instead it runs once more (or twice, if mdadm is installed) before failing. This is a minor change given the benefit of the being able to mount rootfs in a degraded RAID1 scenario. * Other potential regressions could show-up as boot problems, but the change in initramfs-tools specifically is not invasive, it just may delay boot time a bit, given we now run cryptsetup multiple times on local-block, with 1 sec delays between executions. To manage notifications about this bug go
[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Worth to notice that the cryptsetup release is blocked on LP #1891473 - there's a failure on building this package from source introduced by a recent PPA builder upgrade (from Xenial to Bionic). -- 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/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: In Progress Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: In Progress Status in initramfs-tools source package in Groovy: In Progress Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Regression potential] * There are potential for regressions, since this is a change in 2 boot components. The patches were designed in a way to keep the regular case working, it changes the failure case which is not currently working anyway. * A modification in the behavior of cryptsetup was introduced: right now, if we fail the password 3 times (the default maximum attempts), the script doesn't "panic" and drop to a shell immediately; instead it runs once more (or twice, if mdadm is installed) before failing. This is a minor change given the benefit of the being able to mount rootfs in a degraded RAID1 scenario. * Other potential regressions could show-up as boot problems, but the change in initramfs-tools specifically is not invasive, it just may delay boot time a bit, given we now run cryptsetup multiple times on local-block, with 1 sec delays between executions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
** Patch added: "focal_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/mdadm/+bug/1879980/+attachment/5406230/+files/focal_initramfs_lp1879980_V2.debdiff -- 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/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: In Progress Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: In Progress Status in initramfs-tools source package in Groovy: In Progress Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Regression potential] * There are potential for regressions, since this is a change in 2 boot components. The patches were designed in a way to keep the regular case working, it changes the failure case which is not currently working anyway. * A modification in the behavior of cryptsetup was introduced: right now, if we fail the password 3 times (the default maximum attempts), the script doesn't "panic" and drop to a shell immediately; instead it runs once more (or twice, if mdadm is installed) before failing. This is a minor change given the benefit of the being able to mount rootfs in a degraded RAID1 scenario. * Other potential regressions could show-up as boot problems, but the change in initramfs-tools specifically is not invasive, it just may delay boot time a bit, given we now run cryptsetup multiple times on local-block, with 1 sec delays between executions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+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 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
An issue on initramfs-tools autopkgtest was found in Groovy and Focal (see LP #1893675) - it's non-related with the fixes proposed here, but we need to make autopkgtest happy or we cannot get the package released, so here goes the V2 of the initramfs-tools debdiffs. Notice the SRU is mainly driven in this LP and/or LP #1879980. ** Patch added: "groovy_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+attachment/5406227/+files/groovy_initramfs_lp1879980_V2.debdiff -- 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/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reproduce this, one must boot a system (virtual machine is good) with the wrong console set on kernel command-line through the "console=" parameter *and* not pass the "quiet" parameter. * Also, e2fsck tool shouldn't be present in the initrd - for that, the 6th field of /etc/fstab (fs_passno) should be 0 and initrd must be recreated after that. This is the default in Ubuntu, though. [Regression Potential] * The regression potential is small, we're just returning 0 after a printf that is executed in error paths, so I don't expect any issues from that. But in case something bad happens after this change, I expect a more friendly" breakage, like an initramfs panic (drop to a shell), not a silent failure or boot-loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
Although the debdiffs are being hereby attached, the SRU track is ongoing in LPs #1879987 and #1879980. ** Patch added: "groovy_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406203/+files/groovy_initramfs_lp1879980_V2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. [See the Rectification below] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Description changed: + SRU Description + + [Impact] + data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. + This SRU for xenial and bionic based on the work made in cosmic enabled proper handling of named argument. + Note that this is disabled for now on ALL series + + [Test Case] + No real test here since apport general behavior should be unchanged Just to check that the feature is disable, /proc/sys/kernel/core_pattern + content should remain unchanged : + + $> cat /proc/sys/kernel/core_pattern + |/usr/share/apport/apport %p %s %c %d %P %E + + [Regression Potential] + The new feature is not enabled so the regression risk is fairly low. this will take place in a future coordinated SRU across all LTS but in the meanwhile we can make sure that there's no regression by running apport with various + + End SRU Description + data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. Here's something of an example: 347 # Normal startup 348 if len(sys.argv) not in (5, 6): 349 try: 350 print('Usage: %s [global pid]' % sys.argv[0]) 351 print('The core dump is read from stdin.') We could not maintain backwards compatibility because "global pid" is an optional argument and "dump mode" was a new argument. So if there were five arguments its possible the last one was "dump mode" (no global pid) or "global pid" (no support for dump mode). Its possible to use strings in /proc/sys/kernel/core_pattern so we could use those and have apport accept named arguments e.g: $ cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d --global-pid=%P ['/home/bdmurray/source-trees/apport/artful/data/apport', '--pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-pid=5870'] Tyler said "that's probably a nice cleanup to make no matter what because the magic arg ordering is dangerous". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Won't Fix Status in apport source package in Xenial: In Progress Status in apport source package in Bionic: In Progress Status in apport source package in Cosmic: Won't Fix Status in apport source package in Disco: Fix Released Bug description: SRU Description [Impact] data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. This SRU for xenial and bionic based on the work made in cosmic enabled proper handling of named argument. Note that this is disabled for now on ALL series [Test Case] No real test here since apport general behavior should be unchanged Just to check that the feature is disable, /proc/sys/kernel/core_pattern content should remain unchanged : $> cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport %p %s %c %d %P %E [Regression Potential] The new feature is not enabled so the regression risk is fairly low. this will take place in a future coordinated SRU across all LTS but in the meanwhile we can make sure that there's no regression by running apport with various End SRU Description data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. Here's something of an example: 347 # Normal startup 348 if len(sys.argv) not in (5, 6): 349 try: 350 print('Usage: %s [global pid]' % sys.argv[0]) 351 print('The core dump is read from stdin.') We could not maintain backwards compatibility because "global pid" is an optional argument and "dump mode" was a new argument. So if there were five arguments its possible the last one was "dump mode" (no global pid) or "global pid" (no support for dump mode). Its possible to use strings in /proc/sys/kernel/core_pattern so we could use those and have apport accept named arguments e.g: $ cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport --pid=%p
[Touch-packages] [Bug 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
** Patch added: "focal_initramfs_lp1879980_V2.debdiff" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+attachment/5406204/+files/focal_initramfs_lp1879980_V2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. [See the Rectification below] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. [See the Rectification below] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893569] Re: The mouse freezes
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893569 Title: The mouse freezes Status in xorg package in Ubuntu: New Bug description: The mouse freezes in the middle of work. I connected others and the same thing happens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:44:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation HD Graphics 5500 [1179:f920] Subsystem: Toshiba Corporation Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1179:f923] InstallationDate: Installed on 2020-06-15 (76 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: TOSHIBA SATELLITE L50-B ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sr_RS SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8f2dae7e-98af-440c-adfc-c31f5c18bb4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTQE-00500DY4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.sku: INVALID dmi.product.version: PSKTQE-00500DY4 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
** Description changed: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] - * Build initramfs-tools in PPA and observe the failure in AMD64 - the signature of the failure is as discussed in the Impact section above. + * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has - no support for VMs, and this test requires that. + no support for VMs, and this test requires that. [See the Rectification + below] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Run the autopkgtest suite in the initramfs-tools package and observe the failure aforementioned. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. [See the Rectification below] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893675] Re: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
Rectification of my statement in the description: the net test is not present in Debian, only in Ubuntu (Focal and subsequent releases), added in order to perform network parsing test, especially for netplan. ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: Undecided Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Build initramfs-tools in PPA and observe the failure in AMD64 - the signature of the failure is as discussed in the Impact section above. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893675] [NEW] Autopkgtest failure on latest version of initramfs-tools - lack of partprobe
Public bug reported: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Build initramfs-tools in PPA and observe the failure in AMD64 - the signature of the failure is as discussed in the Impact section above. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Tags: seg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1893675 Title: Autopkgtest failure on latest version of initramfs-tools - lack of partprobe Status in initramfs-tools package in Ubuntu: In Progress Bug description: [Impact] * Currently the initramfs-tools autopkgtest fails for at least AMD64, with the following signature: "mount: /tmp/autopkgtest.K1r92h/build.zdS/src/mnt: special device /dev/loop0p1 does not exist." * The reason for that is the test trying immediately to use that partition on the loop device, but kernel may not have a partition re- read ioctl issued, so the test may fail as observing a nonexistent partition. * The fix proposed here is just to manually run "partprobe" before using the new to-be-discovered loop partition in the net autopkgtest. [Test Case] * Build initramfs-tools in PPA and observe the failure in AMD64 - the signature of the failure is as discussed in the Impact section above. [Regression Potential] * Extremely low potential, we are just introducing a partition re-read/probe operation during autopkgtest phase, in order to keep the partition table of loop devices consistent before the test uses it. * The only potential issue I see with that is if for some reason we don't have partprobe in the autopkgtest environment, but that shouldn't happen since parted package is on ubuntu-standard. * Notice that this test is not executed in Debian CI given that CI has no support for VMs, and this test requires that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1893675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892108] Re: ping prints ip address octets backwards on host redirect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iputils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1892108 Title: ping prints ip address octets backwards on host redirect Status in iputils package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Just noticed a weird thing with ping on Ubuntu 20.04, which I recently updated to. This is what I get when pinging a host on my network: user@ubuntu2004:~$ ping 10.156.0.63 PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data. From 10.15.0.1 icmp_seq=2 Redirect Host(New nexthop: 2.0.15.10) The ubuntu2004 machine is located in the 10.15.0.x network. 10.15.0.1 is a DSL router. 10.15.0.2 is a firewall between multiple networks. 10.156.0.63 is a machine on a different local network. All traffic not destined for the internet is routed from 10.15.0.1 to 10.15.0.2, so I would expect the printout to read "New nexthop: 10.15.0.2". However, as you can see this is not the case. Instead the octets are printed in reverse order. To verify this I tried the same on another machine in the same network, running Ubuntu 18.04: user@ubuntu1804:~$ ping 10.156.0.63 PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data. From 10.15.0.1: icmp_seq=2 Redirect Host(New nexthop: 10.15.0.2) As you can see, the printout is correct here: "New nexthop: 10.15.0.2" I further verified the discrepancy by using tcpdump to interpret the ICMP packets on the ubuntu2004 machine, and there seems to be no problem for tcpdump to display the correct IP address. My assumption is that there is something wrong in the print function which displays the IP address for a host redirect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1892108/+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 1659719] Re: ssh can't call a binary from a snap without the full path
** Changed in: openssh (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: openssh (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: openssh (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: Won't Fix Status in pam source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: Won't Fix Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: Won't Fix Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1835660] Re: initramfs unpacking failed
Ubuntu put it at lz4 by default, so my gut tells me that'll give the fastest boot time. I didn't change lz4 to anything, just ran this command to get rid of the error: sudo update-initramfs -c -k $(uname -r) I believe you have to run this command everytime certain packages are updated. Runnning: Ubuntu 20.04.1 -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1879177] Re: Sound cuts off and back on randomly during online streaming of videos
*** This bug is a duplicate of bug 1879182 *** https://bugs.launchpad.net/bugs/1879182 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879177 Title: Sound cuts off and back on randomly during online streaming of videos Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound cuts off and comes back on every 10 or so minutes. I have tried the usual stuff like purging and removing alsa and pulseaudio and restarting, forcing alsa reload, killing pulseaudio and starting again, etc. Here is the output from cat /var/log/syslog* | grep -i pulse gnome-shell[7674]: [8240:8240:0516/223421.641830:ERROR:pulse_util.cc(300)] pa_operation is nullptr. I have attached alsa information also as an attachment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879177/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
assigning pcsc-lite back to sarnold for the decision if you really need/want it for "pcscd" or not. ** Changed in: pcsc-lite (Ubuntu) Assignee: (unassigned) => Seth Arnold (seth-arnold) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs,
[Touch-packages] [Bug 1893655] [NEW] Headphones connect but don't appear as audio output
Public bug reported: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1893655 Title: Headphones connect but don't appear as audio output Status in bluez package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+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 1889217] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.6 --- pulseaudio (1:13.99.1-1ubuntu3.6) focal; urgency=medium [ Kai-Heng Feng ] * d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch: - recognize USB jack mixer to support jack detection (LP: #1891461) * d/p/0002-module-alsa-card-Set-a-minimum-profile-priority-if-i.patch: - resolve an issue when headset gets unplugged, HDMI audio is choosen instead of internal speaker (LP: #1891461) [ Hui Wang ] * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch - Make the AMD acp sound card skipped in the PA, then the ucm could link it to other sound cards, it is easy for gnome to support AMD Renoir sound driver after this change. (LP: #1889217) -- Kai-Heng Feng Thu, 13 Aug 2020 18:53:08 +0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2 --- alsa-lib (1.2.2-2.1ubuntu2) focal; urgency=medium * d/p/0001-conf-add-snd_config_is_array-function.patch * d/p/0001-Enabled-extended-namehints-in-alsa.conf.patch * d/p/0002-topology-use-snd_config_is_array-function.patch * d/p/0003-ucm-merge-the-array-items-from-the-condition-blocks.patch * d/p/0004-ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch * d/p/0005-ucm-execute-SectionDefaults-lately-when-the-first-ve.patch * d/p/0006-ucm-handle-set-_once-command.patch * d/p/0007-ucm-handle-set-_defaults-command.patch * d/p/0008-ucm-initialize-mgr-once_list.patch * d/p/0009-ucm-fix-SectionOnce-comment.patch * d/p/0010-ucm-fix-compilation-error-in-set_defaults_user.patch * d/p/0011-ucm-rename-SectionOnce-to-BootSequence.patch * d/p/0012-ucm-rename-_once-command-to-_boot-command.patch * d/p/0013-ucm-configuration-implement-in-place-Include.patch * d/p/0014-ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch * d/p/0015-ucm-config-substitute-File-string-to-allow-variables.patch * d/p/0016-ucm-configuration-allow-to-define-the-configuration-.patch * d/p/0017-ucm-configuration-add-DefineRegex.patch * d/p/0018-ucm-substitute-arguments-in-sequences.patch * d/p/0019-ucm-allow-syntax-version-3.patch * d/p/0020-ucm-config-change-the-in-place-include-evaluation-or.patch * d/p/0021-ucm-allow-to-specify-the-toplevel-directory-using-as.patch * d/p/0022-ucm-substitute-also-value-strings.patch * d/p/0023-ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch * d/p/0024-ucm-String-condition-implement-Empty.patch * d/p/0025-ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch * d/p/0026-ucm-substitute-OpenName.patch * d/p/0027-ucm-substitute-CardNumber.patch * d/p/0028-ucm-implement-the-toplevel-ucm-configuration-file-pa.patch * d/p/0029-ucm-substitute-device-modifier-names-too.patch * d/p/0030-ucm-substitute-device-strings-in-the-device-lists.patch * d/p/0031-ucm-substitute-component-sequence-string.patch * d/p/0032-ucm-substitute-verb-name-and-file-field.patch * d/p/0033-ucm-substitute-Comment-in-Transition-and-Device.patch * d/p/0034-ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch * d/p/0035-ucm-substitute-arguments-in-sequences-only-for-synta.patch * d/p/0036-ucm-shuffle-code-in-compound_merge.patch * d/p/0037-ucm-implement-CardIdByName-substitution.patch * d/p/0038-ucm-allow-to-ignore-errors-for-the-value-substitutio.patch * d/p/0039-ucm-allow-to-use-the-defined-variables-in-the-substi.patch * d/p/0040-ucm-implement-CardNumberByName-substitution.patch * d/p/0041-ucm-fix-the-possible-buffer-overflow-substitution.patch * d/p/0042-ucm-simplify-get_by_card-in-parser.c.patch * d/p/0043-ucm-implement-AlwaysTrue-Condition.Type.patch * d/p/0044-ucm-Allow-empty-strings-in-var-.-substitutions.patch * d/p/0045-ucm-substitution-remove-duplicate-allow_empty-assign.patch * d/p/0046-ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch * d/p/0047-ucm-substitute-the-merged-tree-completely.patch * add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control * add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu2 in the d/libasound2.symbols - enable sound on AMD Renoir machines (LP: #1889217) [ Kai-Heng Feng ] * d/p/0048-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch - Disable IEC958 on Lenovo ThinkStation P620 (LP: #1891461) -- Hui Wang Mon, 10 Aug 2020 15:09:30 +0800 ** Changed in: alsa-lib (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.2 --- alsa-ucm-conf (1.2.2-1ubuntu0.2) focal; urgency=medium * d/p/0003-ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch * d/p/0004-ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch * d/p/0005-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch * d/p/0006-ucm.conf-add-support-for-the-kernel-module-name-tree.patch * d/p/0007-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch * d/p/0008-sof-soundwire-initial-UCM2-version.patch * d/p/0009-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch * d/p/0010-sof-soundwire-rewrite-for-syntax-3.patch * d/p/0011-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch * d/p/0012-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch * d/p/0013-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch * d/p/0014-amd-renoir-acp-add-syntax-in-the-Linked.patch * d/p/0015-HDA-Intel-only-bind-the-acp-dmic-to-the-soundcard-wi.patch * d/p/0016-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch enable sound on AMD Renoir machines (LP: #1889217) [ Kai-Heng Feng ] * d/p/0017-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch Add proper stream and jack assignment to Lenovo ThinkStation P620 (LP: #1891461) -- Hui Wang Mon, 10 Aug 2020 15:05:02 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch
[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.2 --- alsa-ucm-conf (1.2.2-1ubuntu0.2) focal; urgency=medium * d/p/0003-ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch * d/p/0004-ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch * d/p/0005-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch * d/p/0006-ucm.conf-add-support-for-the-kernel-module-name-tree.patch * d/p/0007-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch * d/p/0008-sof-soundwire-initial-UCM2-version.patch * d/p/0009-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch * d/p/0010-sof-soundwire-rewrite-for-syntax-3.patch * d/p/0011-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch * d/p/0012-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch * d/p/0013-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch * d/p/0014-amd-renoir-acp-add-syntax-in-the-Linked.patch * d/p/0015-HDA-Intel-only-bind-the-acp-dmic-to-the-soundcard-wi.patch * d/p/0016-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch enable sound on AMD Renoir machines (LP: #1889217) [ Kai-Heng Feng ] * d/p/0017-Add-support-for-Lenovo-ThinkStation-P620-Main-Audio.patch Add proper stream and jack assignment to Lenovo ThinkStation P620 (LP: #1891461) -- Hui Wang Mon, 10 Aug 2020 15:05:02 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: pulseaudio (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other
[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.6 --- pulseaudio (1:13.99.1-1ubuntu3.6) focal; urgency=medium [ Kai-Heng Feng ] * d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch: - recognize USB jack mixer to support jack detection (LP: #1891461) * d/p/0002-module-alsa-card-Set-a-minimum-profile-priority-if-i.patch: - resolve an issue when headset gets unplugged, HDMI audio is choosen instead of internal speaker (LP: #1891461) [ Hui Wang ] * d/p/0034-alsa-adjust-ucm-sink-source-priority-according-to-po.patch * d/p/0035-ucm-add-possibility-to-skip-the-UCM-card-completely-.patch * d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch - Make the AMD acp sound card skipped in the PA, then the ucm could link it to other sound cards, it is easy for gnome to support AMD Renoir sound driver after this change. (LP: #1889217) -- Kai-Heng Feng Thu, 13 Aug 2020 18:53:08 +0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If
[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2 --- alsa-lib (1.2.2-2.1ubuntu2) focal; urgency=medium * d/p/0001-conf-add-snd_config_is_array-function.patch * d/p/0001-Enabled-extended-namehints-in-alsa.conf.patch * d/p/0002-topology-use-snd_config_is_array-function.patch * d/p/0003-ucm-merge-the-array-items-from-the-condition-blocks.patch * d/p/0004-ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch * d/p/0005-ucm-execute-SectionDefaults-lately-when-the-first-ve.patch * d/p/0006-ucm-handle-set-_once-command.patch * d/p/0007-ucm-handle-set-_defaults-command.patch * d/p/0008-ucm-initialize-mgr-once_list.patch * d/p/0009-ucm-fix-SectionOnce-comment.patch * d/p/0010-ucm-fix-compilation-error-in-set_defaults_user.patch * d/p/0011-ucm-rename-SectionOnce-to-BootSequence.patch * d/p/0012-ucm-rename-_once-command-to-_boot-command.patch * d/p/0013-ucm-configuration-implement-in-place-Include.patch * d/p/0014-ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch * d/p/0015-ucm-config-substitute-File-string-to-allow-variables.patch * d/p/0016-ucm-configuration-allow-to-define-the-configuration-.patch * d/p/0017-ucm-configuration-add-DefineRegex.patch * d/p/0018-ucm-substitute-arguments-in-sequences.patch * d/p/0019-ucm-allow-syntax-version-3.patch * d/p/0020-ucm-config-change-the-in-place-include-evaluation-or.patch * d/p/0021-ucm-allow-to-specify-the-toplevel-directory-using-as.patch * d/p/0022-ucm-substitute-also-value-strings.patch * d/p/0023-ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch * d/p/0024-ucm-String-condition-implement-Empty.patch * d/p/0025-ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch * d/p/0026-ucm-substitute-OpenName.patch * d/p/0027-ucm-substitute-CardNumber.patch * d/p/0028-ucm-implement-the-toplevel-ucm-configuration-file-pa.patch * d/p/0029-ucm-substitute-device-modifier-names-too.patch * d/p/0030-ucm-substitute-device-strings-in-the-device-lists.patch * d/p/0031-ucm-substitute-component-sequence-string.patch * d/p/0032-ucm-substitute-verb-name-and-file-field.patch * d/p/0033-ucm-substitute-Comment-in-Transition-and-Device.patch * d/p/0034-ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch * d/p/0035-ucm-substitute-arguments-in-sequences-only-for-synta.patch * d/p/0036-ucm-shuffle-code-in-compound_merge.patch * d/p/0037-ucm-implement-CardIdByName-substitution.patch * d/p/0038-ucm-allow-to-ignore-errors-for-the-value-substitutio.patch * d/p/0039-ucm-allow-to-use-the-defined-variables-in-the-substi.patch * d/p/0040-ucm-implement-CardNumberByName-substitution.patch * d/p/0041-ucm-fix-the-possible-buffer-overflow-substitution.patch * d/p/0042-ucm-simplify-get_by_card-in-parser.c.patch * d/p/0043-ucm-implement-AlwaysTrue-Condition.Type.patch * d/p/0044-ucm-Allow-empty-strings-in-var-.-substitutions.patch * d/p/0045-ucm-substitution-remove-duplicate-allow_empty-assign.patch * d/p/0046-ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch * d/p/0047-ucm-substitute-the-merged-tree-completely.patch * add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control * add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu2 in the d/libasound2.symbols - enable sound on AMD Renoir machines (LP: #1889217) [ Kai-Heng Feng ] * d/p/0048-conf-USB-Audio-Disable-IEC958-on-Lenovo-ThinkStation.patch - Disable IEC958 on Lenovo ThinkStation P620 (LP: #1891461) -- Hui Wang Mon, 10 Aug 2020 15:09:30 +0800 ** Changed in: alsa-lib (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb
[Touch-packages] [Bug 1891461] Update Released
The verification of the Stable Release Update for alsa-lib has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to:
[Touch-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Here is a diff working vs non-working: https://www.diffchecker.com/WW0VL687 -- 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/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+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 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Logging in and out works. So I imagine the headphones just need to be plugged in pre login. -- 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/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
While looking at pcsc-tools and pcscs-perl (only needed for the dependency from pcscs-tools) I have found that these are not really depended on by anything important. This matches the statement in the request that says: "This package provides general utilities for smartcards; it's possible that we do not strictly need this package for our use case." Use case wise it contains: - /usr/bin/ATR_analysis Tool to analyze the raw ATR answer from a smart card - debugging tool at best and no common use case - /usr/bin/scriptor + /usr/bin/gscriptor Send scripts to a smartcard, that might be a developer or debugging feature but doesn't sound an end user thing for the enterprise desktop you have in mind. - /usr/bin/pcsc_scan This is the one end-user useful tool in this toolset showing the available cards that are inserted. But honestly you want to integrate things in an enterprise desktop and there I'd expect a UI-thing for it and not this cmdline tool. At the same time nothing in gnome or anywhere else related depends on it. IMHO we should not promote packages to main we have no real use and integration of. If there is a good case how this plays a role in the envisioned "Enterprise Desktop smartcard integration" then I'm more than happy to review and process this (in that case also say why/why-not pcscd is important - see above). MIR Team Nack to pcsc-tools and pcscs-perl for the (currently) given dependencies and reasoning. ** Changed in: pcsc-perl (Ubuntu) Status: New => Invalid ** Changed in: pcsc-tools (Ubuntu) Status: New => Invalid ** Changed in: pcsc-perl (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: pcsc-tools (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: pcsc-lite (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance]
[Touch-packages] [Bug 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Here is the alsa-info.txt when they are NOT plugged in pre-boot and do not show up in the settings: http://alsa-project.org/db/?f=afd99b1656c7317e16fbc52b460299f7ec484195 -- 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/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+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 1893566] Re: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl
Sorry for the poor description. Basically, if my headphones are not plugged pre-boot I cannot get them to register (I think I got them to work post boot by reinstalling pulseaudio and trashing the config but not am not certain). Here is the alsa-info.txt when they are plugged in pre-boot: http://alsa-project.org/db/?f=86bf2f9c23ca1a730c413524ec17ea7b05f19766 -- 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/1893566 Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone not plugged in on bootl Status in alsa-driver package in Ubuntu: New Bug description: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails if headphone is not plugged in on boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mea1935 F pulseaudio /dev/snd/pcmC1D0c: mea1935 F...m pulseaudio /dev/snd/controlC0: mea1935 F pulseaudio /dev/snd/controlC2: mea1935 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 12:29:20 2020 InstallationDate: Installed on 2020-07-17 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: Aug 30 11:07:51 mea-MS-7A40 dbus-daemon[908]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=1178 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [MS-7A40, Realtek ALC887-VD, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd11/12/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893566/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
I asked about it in comment #2 already. pcsc-lite was MIRed in bug 250245 but pcscd explcitly excluded. One either needs to: 1. step up and say "yes we want to own it" (in that case please add a request to the description) 2. say this isn't needed for what you want to achieve (Essentially providing a Windows(R) SCard interfce - which chances are you won't need). In the case of #2 please modify "opensc" in Ubuntu to reduce the "Recommends" dependency on pcscd to just a "Suggests". Marking the task as incomplete and not doing a full review on pcscd until really requested. ** Changed in: pcsc-lite (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: Incomplete Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging.
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
This bug was fixed in the package pam - 1.3.1-5ubuntu4.1 --- pam (1.3.1-5ubuntu4.1) focal; urgency=medium * debian/libpam-modules.postinst: Add /snap/bin to $PATH in /etc/environment. (LP: #1659719) -- Michael Hudson-Doyle Wed, 22 Jul 2020 11:30:44 +1200 ** Changed in: pam (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: New Status in pam source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: New Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: New Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
[Summary] This looks mostly ok from a MIR POV, I've listed remaining that would help to get this improved below. Those are rather minor, MIR Ack under the condition to have them handled. Please update the bug once you have done so. Specific binary packages to be promoted to main: libpam-pkcs11 Required TODOs: - some testing for the overall context of smartcard usage as outlined in the ccid review - please look into the odd file path of the pam .so file if that is ok - please subscribe the team to the bug right away (too easy to be missed later and gives a preview about the bug influx) Recommended TODOs: - n/a [Duplication] In addition to opensc-pkcs11 this seems like "the same". But while opensc-pkcs11 is about providing pkcs#11 for pkcs#15 cards this lib here libpam-pkcs11 is a subproject to opensc - there are pam_p11 (simpler) and pam-pkcs#11 (this one). This lib here is about integrating pkcs#11 into pam with extended features like name mapping and cert chain verification. See - https://github.com/OpenSC/OpenSC/wiki#sub-projects - https://github.com/OpenSC/pam_pkcs11 => Despite the name similarity duplication isn't an issue here [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not parse data formats - does not open a port - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop Problems: - does deal with system authentication (eg, pam), etc) => This needs an security evaluation [Common blockers] OK: - does not FTBFS currently - no translation present, but none needed for this case (user visible)? - not a python/go package, no extra constraints to consider int hat regard Problems: - does have a test suite that runs at build time - does have a test suite that runs as autopkgtest (I have mentioned the overall testing before, applies here as well. - The package has a team bug subscriber [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking is not in place (but this is only a pam plugin) - d/watch is present and looks ok - Upstream update history is slow (but gladly seems only to be stable updates) - Debian/Ubuntu update history is sporadic (e.g. 2 year gap) - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - Does not have Built-Using Problems: - the shared objects have odd pathing /lib/pam_pkcs11/ldap_mapper.so /lib/pam_pkcs11/opensc_mapper.so /lib/pam_pkcs11/openssh_mapper.so /lib/security/pam_pkcs11.so While everything else pam'y is in /lib/x86_64-linux-gnu/security/ Does this have x86 only limitations (or a multiarch violation) we need to solve? [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as I can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - no embedded source copies - not part of the UI for extra checks ** Changed in: pam-pkcs11 (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: New Status in pcsc-tools package in Ubuntu: New Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution.
[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
[Summary] This package needs some cleanup for better tests, symbols tracking and things like lintian/dh_missing. No show stoppers thou, MIR Team kind-of-Ack under the condition to try to improve these weak spots before promotion. Please report here what has been done for that and summarize the new and improved state of warnings and bugs to reduce concerns to get the final MIR Ack. While the above isn't a full Ack yet it isn't too bad either. We don't have to wait and block on it atm, this does needs a security review, so I'll assign ubuntu-security now already. Secuity manages MIR reviews via the subscription, to reflect that work is needed in any case I'll set the state to incomplete also. To be promoted to main: opensc + opensc-pkcs11 Required TODOs: - some testing for the overall topic of smartcard usage as outlined in the ccid review - subscribe a team to the bug (better now than later) - plenty of libs, some seem internal, but still - please add symbols tracking where applicable to detect incompatibilities early - check and resolve dh_missing - too many crash bugs left, please do a bug squash and help to improve quality. Also see the suggestions below of "splitting the package" and "defined set of supported cards" to make this more manageable Recommended TODOs: - The tests at build time skip 3/4 subtests. Please evaluate if that can be improved. - This package consists of many small tools, supporting (and thereby testing, recreating issues, ...) all of them can be hard. For supportability and install footprint it could be useful to check all these binaries and split some of them into an -extra package that will not be promoted. [Duplication] PKCS#15 card support providing PKCS#11 to the upper layers is the core piece of opensc, this is the only SW doing that in the archive - no duplication. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning (many CVEs), but under control (all closed) - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop Problems: - does parse data formats (from/to cards pkcs#15 and from/to higher layers pkcs#11) - does deal with system authentication (eg, pam), etc) pam-pkcs#11 is directly involved with auth => It will need a security review [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - no translation present, but none needed for this case (user visible)? - not a python/go package, no extra constraints to consider in that regard - no new python2 dependency Problems: - the self tests it has at build time are mostly skipped - does have a test suite that runs as autopkgtest (as discussed in ccid) - The package has a team bug subscriber Do it early please! [Packaging red flags] OK: - Ubuntu does not carry a delta - d/watch is present and looks ok - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - d/rules is rather clean - Does not have Built-Using Problems: - symbols tracking is not in place (some libs are reported without version at all - but that might be internal only libs) W: opensc-pkcs11: shared-library-lacks-version usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so onepin-opensc-pkcs11.so W: opensc-pkcs11: shared-library-lacks-version usr/lib/x86_64-linux-gnu/opensc-pkcs11.so opensc-pkcs11.so W: opensc-pkcs11: shared-library-lacks-version usr/lib/x86_64-linux-gnu/pkcs11-spy.so pkcs11-spy.so - no massive Lintian warnings A few (see above) and in addition some dh_missing and missing man page warnings that should be looked after. [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as I can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no dependency on webkit, qtwebkit, seed or libgoa-* - no embedded source copies - not part of the UI for extra checks Problem: - many open bugs (even crashers, etc) in Debian or Ubuntu https://bugs.launchpad.net/ubuntu/+source/opensc https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=yes=opensc There are plenty of bugs even segfaults, and from reading through them it might come back to what I predicted with the problem of various hardware. Again it might be worth to split the package and support only a subset. Also again please consider declaring somewhere formally a defined set of "supported cards" that
[Touch-packages] [Bug 1892559] Re: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite
[Summary] >From the MIR POV the package is mostly ok. The overall topic of smartcard usage will need some QA testing to be supportable. Only a bit can be done in autopkgtest due to the special HW requirements but it would be worth to try that as well as setting up a test lab with the most common respective HW. This does need a security review, so I'll assign ubuntu-security Binaries to promote: libccid TODOs: Recommended: - Tests: - Special HW - In general and I guess this is true for all packages here. Canonical should get a set of the common (=the want to be supported) devices and document those somewhere to make it clear what is regularly tested / supported vs what is on "hopefully it works" level. - Also please try at least if with vsmartcard-vpicc + vsmartcard-vpcd some autopkgtest time testing could be added to some of these packages. (I'm not going to repeat this request on all reviews, but overall it is important for QA on such a new topic.) - Add symbols tracking (this is a bit vice versa, it is a lib providing a driver to be used in ps/sc, but still auto-detect if things change is good) Required: - Please subscribe to the package (usually good to be done now already) [Duplication] libccid is used to communicate though PC/SC (also on this MIR) with smart cards. https://wiki.debian.org/Smartcards holds a nice overview, there are a bunch of special drivers in other packages (not part of this MIR), but ccid covers the majority of devices listed. [Dependencies] OK: - no other Dependencies to MIR due to this (libc6, libusb-1.0-0) - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop Problems: - does parse data formats The ccid protocol - if ever exploited - would be a very great angle of attack - does deal with system authentication (eg, pam), etc) Smartcards can and commonly are used to do auth - This will need a security review on top of the MIR review [Common blockers] OK: - does not FTBFS currently - no translation present, but none needed for this case (user visible)? - not a python/go package, no extra constraints to consider int hat regard Problems: - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a test suite that runs as autopkgtest => Tests of special HW are hard at build time anyway, but a bit more than nothing would be great. I suggested an overall test with a set of meant to be supported cards exercising all the components of this MIR. - The package has a team bug subscriber This needs a Team subscriber still, Desktop was mentioned to be that, but it isn't yet. From experience this is easy to be forgotten later. Also subscribing now will help to see the influx of bugs on the topic and therefore help to be sure if you want to own this. [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok - Upstream update history is good (regular and only stable updates) - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - Does not have Built-Using Problems: - symbols tracking is not place [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as I can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - no embedded source copies - not part of the UI for extra checks ** Changed in: ccid (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid libpam-pkcs1 libpcsc-perl opensc pcsc-tools pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: New Status in pcsc-tools package in Ubuntu: New Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to
[Touch-packages] [Bug 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9
** Bug watch added: github.com/pypa/pip/issues #5599 https://github.com/pypa/pip/issues/5599 ** Also affects: pip via https://github.com/pypa/pip/issues/5599 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775457 Title: /usr/bin/pip3:ImportError:/usr/bin/pip3@9 Status in pip: Unknown Status in apport package in Ubuntu: New Status in python-pip package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding python-pip. This problem was most recently seen with package version 9.0.1-2.3~ubuntu1, the problem page at https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1775457/+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 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.
This problem is triggered by incorrect "/var/lib/snapd/seed/seed.yaml" files. At various points during the development cycles they were incorrect and that has (almost) no effect on the live-cd or the installed system. However on the next snapd refresh it would trigger the hang people are experiencing. The hang is caused by services waiting for "snapd" to finish seeding but that never happens because the seed.yaml is incorrect. The best workaround is to $ sudo mv /var/lib/snapd/seed/seed.yaml /var/lib/snapd/seed/seed.yaml .disabled and re-run the upgrade. Versions of snapd from ~April 2020 will do this automatically for you if they detect a broken seed. So I will close this bug as fixed because there is an automatic workaround in snapd now. The tooling around the livecd got also improved AIUI so that incorrect seed.yaml should be much harder to create now. ** Changed in: snapd Status: Confirmed => Fix Released ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1776622 Title: snapd updates on focal never finish installing. Can't install any other updates. Status in snapd: Fix Released Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
after pacmd --list, when the system has woken from sleep, and now is on the wrong sound output. note that it's not going to the internal sound card at the moment, but the other hdmi device. even though looking at the diff, it thinks the default sync hasn't changed, it actually is now going to the wrong output, and i have to manually switch it to the other hdmi/dp in the sound settings. ** Attachment added: "after.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406021/+files/after.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
before pacmd --list, with the input correctly selected as 5.1 surround on HDMI / DisplayPort 2. ** Attachment added: "before.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406020/+files/before.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1882547] Re: systemd-resolved dumps core all the time
Can most rapidly reproduce with a config like: [Resolve] Domains=domaina domainb DNSSEC=yes And querying a "hostc" that exists under "domainb" only. Will reliably fail after about 5-20 invocations of "resolvectl query hostc". -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882547] Re: systemd-resolved dumps core all the time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882547] Re: systemd-resolved dumps core all the time
Seeing this frequently too after adding multiple entries to "Domains" in "/etc/systemd/resolved.conf" -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: Confirmed Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
If not going for marking the subtest flaky as in groovy, I have prepared force-reset-test as alternatives in: - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005 - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390004 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the