[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
+1 to Timo to not go for "system nssdb" for the cause of this case here. Also system-wide-trust would be bug 1647285 and is quite a different scope. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does
[Touch-packages] [Bug 1906642] Re: Xorg crashes with abort in iris_dri.so
Any reason why you haven't installed updates? Your mesa is old, there's 20.0.8-0ubuntu1~20.04.1 available since July. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/mesa/+bug/1906642/+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 1906627] Re: adcli fails, can't contact LDAP server
Yes, when --use-ldaps is specified, adcli will make a TLS connection to the domain controller, and speak LDAPS. This works, and is the reason why this bug slipped through our regression testing. I should have tested without the --use-ldaps flag as well. Regardless, this bug seems to be caused by the GSS-SPNEGO implementation in the cyrus-sasl2 package being broken. adcli links to libsasl2 -modules-gssapi-mit, which is a part of cyrus-sasl2, since adcli does not implement GSS-SPNEGO itself, and relies on cyrus-sasl libraries. I downloaded the source package of cyrus-sasl2 2.1.27+dfsg-2 from Focal, and I built it on Bionic, and installed it. I then tried a adcli join, and it worked: https://paste.ubuntu.com/p/R8PyHJMNtT/ Looking at the cyrus-sasl2 source repo, it seems the Bionic version is missing a lot of commits related to GSS-SPNEGO support. Commit 816e529043de08f3f9dcc4097380de39478b0b16 From: Simo Sorce Date: Thu, 16 Feb 2017 15:25:56 -0500 Subject: Fix GSS-SPNEGO mechanism's incompatible behavior Link: https://github.com/cyrusimap/cyrus-sasl/commit/816e529043de08f3f9dcc4097380de39478b0b16 Commit 4b0306dcd76031460246b2dabcb7db766d6b04d8 From: Simo Sorce Date: Mon, 10 Apr 2017 19:54:19 -0400 Subject: Add support for retrieving the mech_ssf Link: https://github.com/cyrusimap/cyrus-sasl/commit/4b0306dcd76031460246b2dabcb7db766d6b04d8 Commit 31b68a9438c24fc9e3e52f626462bf514de31757 From: Ryan Tandy Date: Mon, 24 Dec 2018 15:07:02 -0800 Subject: Restore LIBS after checking gss_inquire_sec_context_by_oid Link: https://github.com/cyrusimap/cyrus-sasl/commit/31b68a9438c24fc9e3e52f626462bf514de31757 This doesn't even seem to be a complete list either, and if we backport these patches to the Bionic cyrus-sasl2 package, it fails to build for numerous reasons. I also found a similar bug report in Debian, which features the above third commit: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917129 >From what I can tell, GSS-SPNEGO in cyrus-sasl2 for Bionic has never worked, and changing it to the default was a bad idea. So, we have a decision to make. If supporting the new Active Directory requirements in ADV190023 [1][2] which adds --use-ldaps for adcli, as a part of bug 1868703 is important, and something the community wants, we need to fix up cyrus-sasl2 to have a working GSS-SPNEGO implementation. [1] https://msrc.microsoft.com/update-guide/en-us/vulnerability/ADV190023 [2] https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows If we don't want --use-ldaps for adcli, then we can revert the patches for adcli on Bionic, and go back to what was working previously, with GSS-API. ** Bug watch added: Debian Bug tracker #917129 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917129 ** Also affects: cyrus-sasl2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: adcli fails, can't contact LDAP server Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: New Status in adcli source package in Bionic: In Progress Status in cyrus-sasl2 source package in Bionic: New Bug description: Package: adcli Version: 0.8.2-1ubuntu1 Release: Ubuntu 18.04 LTS When trying to join the domain with this new version of adcli, it gets to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not do anything for 10 minutes. It will then fail, complaining it can't reach the LDAP server. Logs: Dec 03 01:39:50 example001.domain.com realmd[6419]: * Authenticated as user: domain-join-acco...@domain.com Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1 Dec 03 01:39:50 example001.domain.com realmd[6419]: * Authenticated as user: domain-join-acco...@domain.com Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1 Dec 03 01:39:50 example001.domain.com realmd[6419]: * Using GSS-SPNEGO for SASL bind Dec 03 01:39:50 example001.domain.com realmd[6419]: * Using GSS-SPNEGO for SASL bind Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1 Dec 03 01:55:27 example001.domain.com realmd[6419]: ! Couldn't lookup domain short name: Can't contact LDAP server Dec 03 01:55:27 example001.domain.com realmd[6419]: ! Couldn't lookup domain short name: Can't contact LDAP server Dec 03 01:55:27 example001.domain.com realmd[6419]: * Using fully qualified name: example001.domain.com Dec 03 01:55:27 example001.domain.com realmd[6419]: * Using fully qualified name: example001.domain.com Dec 03 01:55:27 example001.domain.com realmd[6419]: * Using domain name: domain.com Dec 03 01:55:27 example001.domain.com realmd[6419]: * Using domain name: domain.com Dec 03 01:55:27 example001.domain.com realmd[6419]: * Using
[Touch-packages] [Bug 1898204] Re: [Gigabyte Z170-HD3P] No sound
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1898204 Title: [Gigabyte Z170-HD3P] No sound Status in pulseaudio package in Ubuntu: Expired Bug description: no sound after upgrade to Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 2 15:35:55 2020 DistUpgraded: 2020-09-30 09:31:54,933 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: deepin-anything, 0.0, 5.4.0-48-generic, x86_64: installed deepin-anything, 0.0, 5.4.0-49-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-48-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-49-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000] InstallationDate: Installed on 2018-04-15 (900 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. Z170-HD3P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-49-generic root=UUID=8635df37-a190-468b-9472-ccc476db70e3 ro DEEPIN_GFXMODE= SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-09-30 (2 days ago) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22a dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3P-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22a:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3P:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3P dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Oct 2 15:23:59 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898204/+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 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
I also just installed on a pi 4 and had the same issue -- devices worked but would not persist across reboots, and then successive re-adds were... strange, unreliable, etc. Lots of "it appears to work but doesn't." Tried the PPA packages and it worked at first, but was seriously inconsistent at adding and removing devices. I downgraded the PPA packages back to originals and still couldn't reliably add devices. I re-upgraded to PPA packages and the bluetooth was essentially working less than ever. Since it felt like a software issue, like configurations and "sessions" were being munged, I killed BT, searched around and wiped out /var/lib/bluetooth/* (which appeared to have multiple base addresses???) and then I was able to clean out gnome's ui and re-add and things now persist across reboots. To me, this seems like the PPA fixes the issue, but the original packages created a state where there were multiple stale / conflicting states in /var/lib/bluetooth that you must disabled bt, clean, then re-enable / reboot and things work. It almost feels like the original packages had the BT adapter changing addresses each boot or similar. -- 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/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Uninstalling pulseaudio and working only with alsa, the same problem continues. I was playing the audio with the specifications of aplay -l Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 0/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 when the audio stopped and I ran aplay -l and returned: Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 Does anyone know what can it be? -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Uninstalling pulseaudio and working only with alsa, the same problem continues. I was playing the audio with the specifications of aplay -l Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 0/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 when the audio stopped and I ran aplay -l and returned: Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 Does anyone know what can it be? -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
This bug has been closed for 4 years. If you experience any crashes in 18.04 or 20.04 then please open a new bug. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Yakkety: Fix Released Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1906686] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: radeon ** Summary changed: - Xorg freeze + [radeon] Xorg freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => ubuntu ** Summary changed: - [radeon] Xorg freeze + [radeon] Display freeze -- 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/1906686 Title: [radeon] Display freeze Status in Ubuntu: Incomplete Bug description: Hi everyone, when searching for problems with the display, I was siggested, that it it an xorg problem. That is all I understand. I ran into problems with display feezes after upgrading from 18.04 LTS to 20.04. I run the system (a Lenovo K320 Ideacenter) with two screens. Main display connected with HDMI connection and the secondary screen with the classical pin plug (XGA?). I write theis report after booting with recovery mode. Nothing freezes, but the scrren resolution is unsatisfatory and both displays show the same desktop - as expected. My work really requires two screens and for many reasons I prefer this work being performed under Ubuntu and not windows. As I said: No problem under 18.04 with the display freeze. I am using Ubuntu 20.04.1 LTS Release: 20.04 Just in case xorg is the source problem: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status My graphics card is an ATI Radeon. I did not install any drivers. Both 18.04 and 20.04 were 'out of the box' Tnx a lot! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 15:27:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon HD 5450 [1462:2180] InstallationDate: Installed on 2020-11-27 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO IdeaCentre K320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=c0e1bda3-c78d-4f67-9c83-110b714555df ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 5LKT42A dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: 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:bvnLENOVO:bvr5LKT42A:bd06/08/2010:svnLENOVO:pnIdeaCentreK320:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: IdeaCentre K320 dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core:
[Touch-packages] [Bug 1906473] Re: package linux-image-5.4.0-56-generic 5.4.0-56.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1906473 Title: package linux-image-5.4.0-56-generic 5.4.0-56.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: this problem occurs when I'm updating with `sudo apt full-upgrade` ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stchai 1235 F pulseaudio /dev/snd/controlC0: stchai 1235 F pulseaudio CasperMD5CheckResult: skip Date: Wed Dec 2 11:24:21 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b48c Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam Bus 001 Device 005: ID 13d3:3408 IMC Networks Bus 001 Device 002: ID 24ae:1100 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=UUID=a61fc5f1-1f73-4cc2-aa33-b909b5fdd8b6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-56-generic 5.4.0-56.62 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550JX.203:bd04/02/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550JX dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906473/+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 1906642] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg crash + Xorg crashes with abort in iris_dri.so ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/mesa/+bug/1906642/+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 1906642] Re: Xorg crash
The one crash I can see here is incomplete due to missing/incorrect debug symbols: [ 701.646] (EE) Backtrace: [ 701.648] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55cdba58a52c] [ 701.649] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f214374541f] [ 701.650] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f214358218b] [ 701.651] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f2143561859] [ 701.653] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 701.653] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f214177d3a7] [ 701.654] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x2036b7) [0x7f214236fb97] [ 701.654] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x24ee8) [0x7f21417cd608] [ 701.655] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7f2142ee7480] [ 701.656] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 701.656] (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f2142f208f0] [ 701.656] (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x55cdba42d995] [ 701.656] (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x55cdba583ba2] [ 701.656] (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55cdba428cf7] [ 701.657] (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55cdba42cfc4] [ 701.657] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f21435630b3] [ 701.658] (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x55cdba416a2e] -- 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/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/mesa/+bug/1906642/+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 1906642] Re: Xorg crash
** 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/1906642 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906642/+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 1906642] [NEW] Xorg crash
You have been subscribed to a public bug: System is crashing, logging out and i am constantly losing all my work if it's not saved Description:Ubuntu 20.04 LTS (fossa-beric-icl X31) Release:20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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 crash focal ubuntu -- Xorg crash https://bugs.launchpad.net/bugs/1906642 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 1906729] [NEW] Suspend and hibernate work, but hybrid-suspend does not
Public bug reported: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service [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 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET74W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET74W(1.54):bd07/23/2019:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E585 dmi.product.name: 20KVCTO1WW dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585 dmi.product.version: ThinkPad E585 dmi.sys.vendor: LENOVO mtime.conffile..etc.systemd.sleep.conf: 2020-12-03T16:22:33.696671 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Description changed: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. - Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: - [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service - [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 - - 3 overridden configuration files found. + [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service + [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 + + 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET74W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user
** Changed in: apport (Ubuntu Xenial) Status: New => In Progress ** Changed in: apport (Ubuntu Bionic) Status: New => In Progress ** Changed in: apport (Ubuntu Focal) Status: New => In Progress ** Changed in: apport (Ubuntu Groovy) Status: New => Incomplete -- 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/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Status in apport source package in Bionic: In Progress Status in apport source package in Focal: In Progress Status in apport source package in Groovy: Incomplete Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. apport-test-crashes code is here: https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
re: system nssdb; let's not go there anymore, Fedora already moved to openssl system-wide -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 3) Recompile SSSD completely to use libcrypto as backend [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. Behavior should not change, also assuming that upstream dropped NSS support completely in latest release [3], keeping the same functionalities. As per a further review of this by xnox [4], we can safely assume that SSSD does not use libcrypto for operations where its behavior should
[Touch-packages] [Bug 1870876] Re: docker stopped when containerd updated
*** This bug is a duplicate of bug 1870514 *** https://bugs.launchpad.net/bugs/1870514 As a follow-up for the unattended-upgrades problem I've proposed a possible enhancement to protect services by holding back more packages: https://github.com/mvo5/unattended-upgrades/issues/284 ** Bug watch added: github.com/mvo5/unattended-upgrades/issues #284 https://github.com/mvo5/unattended-upgrades/issues/284 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description: Ubuntu 18.04.4 LTS Release: 18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Perhaps the best hope is that Pipewire develops quickly and replaces Pulseaudio: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #249 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
** Attachment added: "successful hirsute build logs" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+attachment/5440683/+files/logrotate_3.17.0-2ubuntu1_amd64-2020-12-01T23%3A18%3A31Z.build ** Changed in: logrotate (Ubuntu) Assignee: Matthieu Clemenceau (mclemenceau) => (unassigned) ** Changed in: logrotate (Ubuntu) Status: In Progress => Confirmed ** Tags added: fr-984 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Confirmed Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
** Patch added: "debdiff between ubuntu 3.17.0-1ubuntu1 and new ubuntu version 3.17.0-2ubuntu1" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+attachment/5440682/+files/logrotate_3.17.0-2_3.17.0-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Confirmed Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
** Patch added: "debdiff between Debian 3.17.0-2 and new ubuntu version 3.17.0-2ubuntu1" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+attachment/5440681/+files/logrotate_3.17.0-2_3.17.0-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: Confirmed Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1906701] [NEW] Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)
Public bug reported: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. ** Affects: logrotate (Ubuntu) Importance: Undecided Assignee: Matthieu Clemenceau (mclemenceau) Status: In Progress ** Changed in: logrotate (Ubuntu) Status: New => In Progress ** Changed in: logrotate (Ubuntu) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1906701 Title: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: In Progress Bug description: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main) At the time of filling this bug, the target debian unstable version is 3.17.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1906701/+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 1906702] [NEW] The boot_delay parameter is not interpreted by the correct boot modude
Public bug reported: Hello. Normal computer booting is no longer possible. However, this computer boots up without any difficulty using recovery mode. A first research shows that the normal boot does not reach the phase of delivery of the trace in the file /var/log/journal. If he did that, it would be possible to recover the trace with a live USB. (Journalctl -b -D /mnt/var/log/journal). It is possible to see the boot traces on the screen. But it ends with a black screen and the cursor blinking. The trace lines run so fast that it is impossible to read them. To solve this problem, I found in a lot of documentations, the "boot-delay" parameter which is described as: boot_delay = Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer ( in https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html?highlight=kernel%20parameters) So I modified the /boot/grub/grub.cfg file (Ubuntu 20.04.1) to put this setting in a place that I think is good (line 167) Here is its current content linux /boot/vmlinuz-5.4.0-56-generic root = UUID = ec732fcc-7338-46a2-91e0-1c883e26d0f9 ro nomodeset debug ignore_loglevel nomodeset boot_delay=180 But the boot is absolutely not going the way I wanted! With the value 0, the start-up delay is 2 seconds. With the value 60, the start delay is 85 seconds. With the value 120, the start delay is 185 seconds. With the value 180, the start delay is 275 seconds. I had not considered this delay at the start. When the start is done, the lines continue to scroll at full speed. My wish was to set the value 9876. But after 4 hours, the start-up still had not taken place. Thank you for dealing with the problem as best as possible: Software or documentation correction? Good week. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/boot/grub/grub.cfg" https://bugs.launchpad.net/bugs/1906702/+attachment/5440680/+files/grub.cfg -- 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/1906702 Title: The boot_delay parameter is not interpreted by the correct boot modude Status in initramfs-tools package in Ubuntu: New Bug description: Hello. Normal computer booting is no longer possible. However, this computer boots up without any difficulty using recovery mode. A first research shows that the normal boot does not reach the phase of delivery of the trace in the file /var/log/journal. If he did that, it would be possible to recover the trace with a live USB. (Journalctl -b -D /mnt/var/log/journal). It is possible to see the boot traces on the screen. But it ends with a black screen and the cursor blinking. The trace lines run so fast that it is impossible to read them. To solve this problem, I found in a lot of documentations, the "boot-delay" parameter which is described as: boot_delay = Milliseconds to delay each printk during boot. Values larger than 10 seconds (1) are changed to no delay (0). Format: integer ( in https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html?highlight=kernel%20parameters) So I modified the /boot/grub/grub.cfg file (Ubuntu 20.04.1) to put this setting in a place that I think is good (line 167) Here is its current content linux /boot/vmlinuz-5.4.0-56-generic root = UUID = ec732fcc-7338-46a2-91e0-1c883e26d0f9 ro nomodeset debug ignore_loglevel nomodeset boot_delay=180 But the boot is absolutely not going the way I wanted! With the value 0, the start-up delay is 2 seconds. With the value 60, the start delay is 85 seconds. With the value 120, the start delay is 185 seconds. With the value 180, the start delay is 275 seconds. I had not considered this delay at the start. When the start is done, the lines continue to scroll at full speed. My wish was to set the value 9876. But after 4 hours, the start-up still had not taken place. Thank you for dealing with the problem as best as possible: Software or documentation correction? Good week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1906702/+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 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
I'm having a similar errors, I think it has something to do with the latest kernel updates. In my case, the kernel modules were updated on Dec 1. From the apt history.log: Start-Date: 2020-12-01 07:41:57 Commandline: aptdaemon role='role-commit-packages' sender=':1.297' Install: linux-image-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56:amd64 (5.4.0-56.62, automatic), linux-modules-extra-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-modules-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), linux-libc-dev:amd64 (5.4.0-54.60, 5.4.0-56.62), linux-image-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), snapd:amd64 (2.47.1+20.04, 2.48+20.04), linux-generic:amd64 (5.4.0.54.57, 5.4.0.56.59) End-Date: 2020-12-01 07:43:16 I didn't restart my computer at the time, but shut it down overnight and restarted in the morning of December 2, and that's when I started having very similar issues as described in the original submission. The biggest difference is that the time period of WiFi network disconnects is longer - normally it'll work for a half hour or more, but eventually I'll get disconnected and prompted for a password on a network that I've been connecting to for years. Might have something to do with Realtek wireless adapters: allan ~ $ lspci | grep -i WiFi 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook
[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Affects me on Kubuntu 20.04. Somehow it didn't before I upgraded from 18.04. But now I have session crashes once per few hours. Meaning, I'm thrown back to the login screen. No VPN here. I did have to uninstall pavucontrol-qt (it segfaulted) and installed pavucontrol instead, though. No idea if it might have to do with pavucontrol? My drain isn't a headphone, but a Bose Solo 5. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Yakkety: Fix Released Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1905735] Re: ubuntu-image autopkgtests failing since python-debian 0.1.38
This is fixed from our POV, shouldn't be a problem anymore. ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1905735 Title: ubuntu-image autopkgtests failing since python-debian 0.1.38 Status in python-debian package in Ubuntu: Fix Committed Status in ubuntu-image package in Ubuntu: Fix Released Status in python-debian package in Debian: Unknown Bug description: In the tests it seems that since some - yet to be found - change ~20th Nov the tests of ubuntu-image fail. Tests all list those three sub-tests as failing: unittests.sh FAIL non-zero exit status 1 qa FAIL non-zero exit status 1 coverage.sh FAIL non-zero exit status 1 Fails all seem to be related to some python/pytest/py* change that might have slipped in without gating on this test. Ubuntu-image itself also isn't new - still the same as in groovy ubuntu-image | 1.10+20.10ubuntu2 | groovy | source, all ubuntu-image | 1.10+20.10ubuntu2 | hirsute| source, all == log start === Obtaining file:///tmp/autopkgtest.ZuL7Da/build.chY/src ERROR: Command errored out with exit status 1: command: /tmp/autopkgtest.ZuL7Da/build.chY/src/.tox/py38-nocov/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"'; __file__='"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-yaplrymq cwd: /tmp/autopkgtest.ZuL7Da/build.chY/src/ Complete output (5 lines): Traceback (most recent call last): File "", line 1, in File "/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py", line 49, in __version__ = str(Changelog(infp).get_version()) AttributeError: 'Changelog' object has no attribute 'get_version' ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. === log end The issue reproducible in local KVM-autopkgtest against hirsute-proposed and hirsute-release for me (I mistyped before). Example: sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --apt-pocket=proposed --shell-fail ubuntu-image_1.10+20.10ubuntu2.dsc --testname=qa -- qemu --qemu-options='-cpu host' --ram-size=1536 --cpus 2 ~/work/autopkgtest-hirsute-amd64.img In terms of similar bug signatures I found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973227 Fixed by: https://gitlab.kitware.com/debian/dh-cmake/-/commit/3337c8e0e9ebd109490d3c40f0bd5c1e367bedc8 Looking for the same issue in ubuntu-image has shown an entry in setup.py setup.py:49:__version__ = str(Changelog(infp).get_version()) And now that we know all that we see https://launchpad.net/ubuntu/+source/python-debian/+publishinghistory New version in since 2020-11-20 02:23:27 CET That is a perfect match to our bug. $ diff -Naur python-debian-0.1.3[78]/lib/debian/changelog.py ... -def get_version(self): -# type: () -> Version +def _get_version(self): +# type: () -> Optional[Version] """Return a Version object for the last version""" -return self._blocks[0].version +return self._blocks[0].version # type: ignore ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1905735/+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 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Description changed: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 + 3) Recompile SSSD completely to use libcrypto as backend + [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: - $ p11-kit list-modules + $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca- certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable - crypto backend for PKCS#11 operations. And behavior should not change - (if not improved), also assuming that upstream dropped NSS support - completely in latest release, keeping the same functionalities. + crypto backend for PKCS#11 operations. Behavior should not change, also + assuming that upstream dropped NSS support completely in latest release + [3], keeping the same functionalities. - The only binary that is really affected in its behavior is p11_child. + As per a further review of this by xnox [4], we can safely assume that + SSSD does not use libcrypto for operations where its behavior should + differ from NSS. As it's needed only for certificates handling. - And I'm confident this will break only those setup (if there are any, - given that smartcard access is currently not supported by ubuntu) that -
[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent
** Tags added: fr-980 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1906078 Title: Whoopsie sends bug reports automatically without consent Status in whoopsie package in Ubuntu: New Bug description: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1906078/+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 1906688] [NEW] [SRU] Update evolution, evolution-data-server & evolution-ews to 3.36.5 in Focal
Public bug reported: * Impact That's the current GNOME 3.36 stable updates, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution/-/blob/gnome-3-36/NEWS Evolution 3.36.5 2020-08-07 --- Bug Fixes: - "Time" portion of calendar entries not scaling with font (Stefan Paul Noack) - ECompEditor: Error when save-only (all instances) of a recurring event (Milan Crha) - Calendar: SEQUENCE not changed when modifying All Instances (Milan Crha) - Calendar: Event non-libical time zone reset to UTC on edit (Milan Crha) Miscellaneous: - EContactEditor: Other mailing address has stored incorrect address label (Milan Crha) - help: Mailing List filter criterion checks numerous mail headers (Andre Klapper) Translations: Jordi Mas (ca) Jwtiyar Nariman (ckb) Yuri Chornoivan (uk) https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/gnome-3-36/NEWS Evolution-Data-Server 3.36.5 2020-08-07 --- Bug Fixes: - Uses LC_ADDRESS unconditionally in libphonenumber code (Milan Crha) - IMAPx: Disable move to real junk/trash in server-side virtual folders (Milan Crha) Miscellaneous: - Fix a memory leak in ebmb_gather_photos_local_filenames() (Milan Crha) - ESoupSession: Provided SoupAuth might not be always used by libsoup (Milan Crha) https://gitlab.gnome.org/GNOME/evolution-ews/-/blob/gnome-3-36/NEWS Evolution-EWS 3.36.5 2020-08-07 --- Miscellaneous: - Provided SoupAuth might not be always used by libsoup (Milan Crha) * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - Check that evolution works correctly with different emails server and with online calendars. - Check that calendar events show in gnome-shell's calendar menu. - Check that calendar events show in gnome-calendar (when installed). * Regression potential There is no specific change or feature to test in that update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 17:08:35 2020 InstallationDate: Installed on 2020-04-26 (221 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Affects: evolution-ews (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Also affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Also affects: evolution-ews (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1906688 Title: [SRU] Update evolution, evolution-data-server & evolution-ews to 3.36.5 in Focal Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: New Status in evolution-ews package in Ubuntu: New Bug description: * Impact That's the current GNOME 3.36 stable updates, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution/-/blob/gnome-3-36/NEWS Evolution 3.36.5 2020-08-07 --- Bug Fixes: - "Time" portion of calendar entries not scaling with font (Stefan Paul Noack) - ECompEditor: Error when save-only (all instances) of a recurring event (Milan Crha) - Calendar: SEQUENCE not changed when modifying All Instances (Milan Crha) - Calendar: Event non-libical time zone reset to UTC on edit (Milan Crha) Miscellaneous: - EContactEditor: Other mailing address has stored incorrect address label (Milan Crha) - help: Mailing List filter criterion checks numerous mail headers (Andre Klapper) Translations: Jordi Mas (ca) Jwtiyar Nariman (ckb) Yuri Chornoivan (uk) https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/gnome-3-36/NEWS Evolution-Data-Server 3.36.5 2020-08-07 --- Bug Fixes: - Uses LC_ADDRESS unconditionally in libphonenumber code (Milan Crha) - IMAPx: Disable move to real junk/trash in server-side virtual folders (Milan Crha) Miscellaneous: - Fix a memory leak in ebmb_gather_photos_local_filenames() (Milan Crha) - ESoupSession: Provided SoupAuth might not be always used by libsoup (Milan Crha)
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I understood that they need to deal with new codec inclusion, via GStreamer o other libs, and that writing code and manage a community is not a simple task. Said that, IMHO there are three big question with bluetooth and PulseAudio: 1. in these days we (probably most of us) are always on web conferencing and we need good audio quality in both direction, mic and speaker. Current bluetooth headsets are capable of using Bluetooth Profile HFP 1.6 with mSBC 16kHz audio encoding, this standard permit high quality voice conferencing and It was made in 2011...9 year ago. 2. Bluetooth Profile A2DP for listening only (music...) There are a lot of codec for high quality listen audio, es. SBC-XQ, aptX-LL, aptX-HD, aptX Voice and FastStream 3. Support for new version of Bluetooth / Profile. Ex #1 BT 5.3 with LC3 (Low Complexity Communications Coded (LC3)) codec. Ex #2 BT Profile HFP 1.8 with codec selection and Enhanced Voice Recognition Activation. My two cents -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1906686] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1906686 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hi everyone, when searching for problems with the display, I was siggested, that it it an xorg problem. That is all I understand. I ran into problems with display feezes after upgrading from 18.04 LTS to 20.04. I run the system (a Lenovo K320 Ideacenter) with two screens. Main display connected with HDMI connection and the secondary screen with the classical pin plug (XGA?). I write theis report after booting with recovery mode. Nothing freezes, but the scrren resolution is unsatisfatory and both displays show the same desktop - as expected. My work really requires two screens and for many reasons I prefer this work being performed under Ubuntu and not windows. As I said: No problem under 18.04 with the display freeze. I am using Ubuntu 20.04.1 LTS Release: 20.04 Just in case xorg is the source problem: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status My graphics card is an ATI Radeon. I did not install any drivers. Both 18.04 and 20.04 were 'out of the box' Tnx a lot! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 15:27:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon HD 5450 [1462:2180] InstallationDate: Installed on 2020-11-27 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO IdeaCentre K320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=c0e1bda3-c78d-4f67-9c83-110b714555df ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 5LKT42A dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: 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:bvnLENOVO:bvr5LKT42A:bd06/08/2010:svnLENOVO:pnIdeaCentreK320:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: IdeaCentre K320 dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906686/+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 1906565] Re: traceback when running apport as non-root user
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Groovy: New Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. apport-test-crashes code is here: https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1906681] Re: packagekitd crashed with SIGSEGV in pk_dbus_get_uid()
*** This bug is a duplicate of bug 1906546 *** https://bugs.launchpad.net/bugs/1906546 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1906546, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1906681/+attachment/5440622/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440624/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440627/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440628/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440629/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440630/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1906681/+attachment/5440631/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1906546 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1906681 Title: packagekitd crashed with SIGSEGV in pk_dbus_get_uid() Status in packagekit package in Ubuntu: New Bug description: This error report is generated after the moment of log in. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: packagekit 1.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 Date: Mon Nov 30 13:10:46 2020 ExecutablePath: /usr/libexec/packagekitd ProcCmdline: /usr/libexec/packagekitd ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x558293594eb1 : mov 0x8(%rax),%r8 PC (0x558293594eb1) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%r8" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: pk_dbus_get_uid () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: packagekitd crashed with SIGSEGV in pk_dbus_get_uid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1906681/+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 1906686] [NEW] Xorg freeze
You have been subscribed to a public bug: Hi everyone, when searching for problems with the display, I was siggested, that it it an xorg problem. That is all I understand. I ran into problems with display feezes after upgrading from 18.04 LTS to 20.04. I run the system (a Lenovo K320 Ideacenter) with two screens. Main display connected with HDMI connection and the secondary screen with the classical pin plug (XGA?). I write theis report after booting with recovery mode. Nothing freezes, but the scrren resolution is unsatisfatory and both displays show the same desktop - as expected. My work really requires two screens and for many reasons I prefer this work being performed under Ubuntu and not windows. As I said: No problem under 18.04 with the display freeze. I am using Ubuntu 20.04.1 LTS Release:20.04 Just in case xorg is the source problem: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status My graphics card is an ATI Radeon. I did not install any drivers. Both 18.04 and 20.04 were 'out of the box' Tnx a lot! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 15:27:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon HD 5450 [1462:2180] InstallationDate: Installed on 2020-11-27 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO IdeaCentre K320 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=c0e1bda3-c78d-4f67-9c83-110b714555df ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 5LKT42A dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: 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:bvnLENOVO:bvr5LKT42A:bd06/08/2010:svnLENOVO:pnIdeaCentreK320:pvrLenovoProduct:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: IdeaCentre K320 dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO 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 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1906686 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 1906565] Re: traceback when running apport as non-root user
apport (2.20.11-0ubuntu55) hirsute; urgency=medium * data/apport: only drop supplemental groups if the user is root. -- Brian Murray Wed, 02 Dec 2020 14:40:29 -0800 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1906565 Title: traceback when running apport as non-root user Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Focal: New Status in apport source package in Groovy: New Bug description: [Impact] The apport-test-crashes package, which is used to test the Error Tracker deployments, fails produce crash files for binary applications since "various security hardening fixes" were included in apport. The problematic change is the dropping of supplemental groups in data/apport. This results in a PermissionError as it is not the root user who is calling /usr/share/apport/apport. [Test Case] The least convulted test case involves using the generate-sigsegv-crash.py script from apport-test-crashes. This ends up using a command similar to '/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < /tmp/20.10-gnome-calculator.core' which then will encounter the Traceback. 1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary as we are not running as root) 2) Put a copy of generate-sigsegv-crash.py on disk. 3) Run 'python3 /tmp/generate-sigsegv-crash.py cat' 4) Observe the following Traceback: Traceback (most recent call last): File "/tmp/tmpvkt5d266/apport", line 599, in drop_privileges(True) File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges os.setgroups([]) PermissionError: [Errno 1] Operation not permitted With the version of apport from -proposed you'll receive no such Traceback. [Regression Potential] If there is an error in the python code we code see a new traceback for any and all crashes being generated, so ensure regular crash generation works too. apport-test-crashes code is here: https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1906565/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Time to get a Macbook or Chromebook or whatever -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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
Re: [Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
So, what IS the solution exactly On Thu, Dec 3, 2020 at 8:01 AM Josja Van Bever <1871...@bugs.launchpad.net> wrote: > The crash mentioned in previous comment could (most probably?) be > attributed to a (very small?) hardware failure of the usb stick used. > Though, the same stick was used earlier in the same conditions to > install ubuntu 18. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871268 > > Title: > Installation fails due to useless immediate configuration error when > "Install Third-Party Drivers" is selected > > Status in Ubuntu CD Images: > Fix Released > Status in apt package in Ubuntu: > Fix Released > Status in apt source package in Bionic: > Confirmed > Status in apt source package in Focal: > Triaged > Status in apt source package in Groovy: > Triaged > Status in apt package in Debian: > Unknown > > Bug description: > [Impact] > Installations that really succeeded would then fail because APT could > not immediately configure a package. Which is a pointless way to fail at > that point, because everything did work out anyway. > > So what we do is change that to a warning. > > [Test case] > Not available right now. Issues can flare up and then disappear again. > > [Regression potential] > It's imaginable that we missed something somewhere and some path that > checked for a set error doesn't check it anymore, and we report success > when we hit an error, but it seems unlikely. > > Behavior of --simulate changes. This used to fail before as well, and > will now only produce a warning. We don't believe that is a reason of > concern. > > [Groovy SRU] > The groovy SRU is a sync of the 2.1.11 micro release from Debian > unstable which also incorporates changes to the documentation: A typo fix, > replacing focal with groovy in examples, and minor Dutch manual pages > translation updates. > > We do not have test cases for the documentation changes, and we do not > consider there to be a huge regression potential. As long as they > build, they should be readable - maybe some words are wrong in the > translation, who knows. > > [Original bug report] > Test Case > 1. Install Ubuntu Desktop on hardware with an nVidia card and select to > install 3rd party drivers > 2. Proceed with installation > > The following error message is displayed in /var/log/syslog > /plugininstall.py: Verifying downloads ... > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: > "Version: '4.4.10-10ubuntu4' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: > '1.2.11.dfsg-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: > '1.0.9-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: > "Version: '1.1.3-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: > '1.3.4-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: > "Version: '3.6.0-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: > "Version: '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: > '1.1.5-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: > '5.0.3-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: > "Version: '1.1.4-1build1' not found." > /plugininstall.py: Downloads verified successfully > ubiquity: Error in function: install > /plugininstall.py: Exception during installation: > /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , > E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see > man 5 apt.conf under APT::Immediate-Configure for
Re: [Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
> This does raise a question as to why we don't provide a system nssdb. I > think we should. I wonder if libnss or libnss3-tools could ship ca- > certificates hook to provide a system nssdb certificate store. I don't think it makes much sense at this point as most of the tools that were depending on NSS are leaving it anyways (curl, sssd...) and even Fedora is trying to get rid the usage of libnss completely and only support one crypto backend. So, I was thinking of doing that and it could be a possibility, but wouldn't still be a futurable solution as we'd regress in next LTS, and so we'd end up providing a solution for this LTS (for something that we didn't support so far) that is going to be broken in the next version. And I don't think it's a professional thing to ask our users to setup something and reconfigure it at next mayor update when we can start with the right foot now. > If we are changing backends, and certs were provided for the nss > backend, imho we should automatically convert them and keep them active > for the openssl backend. However unlikely it is that somebody made nss- > based p11_child work. Yeah, as I said isn't hard to do... The only problem I see is that the postinst script for NSS should depend on libnss3-tools (if we don't write us something in C that is shipped with SSSD) in order to read the certs and export them to the OpenSSL chain. As you said, it's quite unlikely, but could happen. > Actually, I don't see sssd at all using TLS connections, does it? It > seems that to perform ldaps connections, it uses libldap from openldap > which in turn uses GnuTLS. And any and all TLS LDAPS options are simply > passed through to the libldap. I had this feeling too, both looking at the code and at the various logs I found around, where I noticed that connection was handled differently, but not being the maximum expert here, I preferred not to talk. So happy you say so. > Inspecting all sssd binary packages I can see that only p11_child is the > only one using libssl and that does not do TLS. Yeah, exactly... It does only certs management basically. > Thus changing nss => openssl backend should be immaterial to what sssd > uses from them. Ok, good to hear. > I don't know how to configure p11_child but I do have > smartcard reader and multiple smartcards so happy to test things =) I wrote a bit of hints in this document, should help: https://hackmd.io/@3v1n0/ubuntu-smartcard-login -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a
[Touch-packages] [Bug 1906653] Re: Backport systemd to make uevents "sticky"
** Description changed: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). + An example causing by this issue, I had a usb printer (non-ippusbxd) + which connected to my laptop, but after unplugging it from my laptop, + the .device unit were still present, if a different printer gets plugged + to the same USB port then, it won't be configured correctly. + [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files -- 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/1906653 Title: Backport systemd to make uevents "sticky" Status in systemd package in Ubuntu: New Bug description: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). An example causing by this issue, I had a usb printer (non-ippusbxd) which connected to my laptop, but after unplugging it from my laptop, the .device unit were still present, if a different printer gets plugged to the same USB port then, it won't be configured correctly. [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+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
Re: [Touch-packages] [Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support for p11_child
>> Soo... Given we prefer to stay conservative and not change SSSD crypto > > I didn't say that! I know, I'm not saying that you took a decision on that but I was speaking in plural form as I recognize what you say in the sense that indeed there may be cases which we don't think of that we could break. >> backend fully (to be clear, I would have preferred it to follow >> upstream, not to provide a solution that will change in next LTS no >> matter what, and avoid having "frankensteins", but wasn't a strong >> requirement for me) I've been exploring ways to get only the component >> we care (p11_child) to use p11-kit and openssl. > > This is certainly a valuable angle to look at - thanks! > >> Robie, this would be better SRU approach? > > I think you misunderstand me. I'm not saying that your upload *has* to > be narrow. I've not formed an opinion that yet. What I'm saying is that > whatever size of scope you choose, there must be a regression analysis > that covers that scope. I understood this, reason why I thought that, given we have the chance to make it a narrower scope, then I tried to get that done. > But the analysis is still necessary and must not be skipped. Sure, not trying to do that, I'm just saying that I can't over all the cases myself. > I appreciate that sometimes it's harder or riskier to narrow the scope, > so I'm still open to widening the scope - *if* there is an appropriate > justification *and* full regression analysis of that wider scope > provided. Problem is that I'm quite sure we can't cover all the cases in a such complicated piece of software that may be configured in so many ways. Thus the reason I thought narrowing the scope was a better idea. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
Actually, I don't see sssd at all using TLS connections, does it? It seems that to perform ldaps connections, it uses libldap from openldap which in turn uses GnuTLS. And any and all TLS LDAPS options are simply passed through to the libldap. Inspecting all sssd binary packages I can see that only p11_child is the only one using libssl and that does not do TLS. libsss-certmap0 uses libcrypto.so.1.1 only for certificate parsing but not for TLS. Thus changing nss => openssl backend should be immaterial to what sssd uses from them. The only concern from me is to migrate custom certs that p11_child trusts, if there are any configured, and migration is needed between the backends. I don't know how to configure p11_child but I do have smartcard reader and multiple smartcards so happy to test things =) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Disappointing. I've just ordered a 1mii B10 USB Bluetooth 5.0 Audio Transmitter as a workaround... -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1906653] [NEW] Backport systemd to make uevents "sticky"
Public bug reported: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. - So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not - be removed from the device again until the device itself is removed (i.e. unplugged). - + So in this PR [1] which minimize issues resulting from this kernel + change (but not avoid them entirely) by make uevent "sticky", meaning + that once a tag is assigned to a device it will not be removed from the + device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files -- 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/1906653 Title: Backport systemd to make uevents "sticky" Status in systemd package in Ubuntu: New Bug description: Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and "unbind" to the Linux device model which resulted in a number of software issues. So in this PR [1] which minimize issues resulting from this kernel change (but not avoid them entirely) by make uevent "sticky", meaning that once a tag is assigned to a device it will not be removed from the device again until the device itself is removed (i.e. unplugged). [0] https://lwn.net/Articles/837033/ [1] https://github.com/systemd/systemd/pull/16853/files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
The crash mentioned in previous comment could (most probably?) be attributed to a (very small?) hardware failure of the usb stick used. Though, the same stick was used earlier in the same conditions to install ubuntu 18. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Confirmed Status in apt source package in Focal: Triaged Status in apt source package in Groovy: Triaged Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
If we want to change the main sssd backend from nss to openssl, imho it would be prudent enough to use http://manpages.ubuntu.com/manpages/hirsute/en/man3/SSL_set_security_level.3ssl.html APIs to set_security_level to 1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. And behavior should not change (if not improved), also assuming that upstream dropped NSS support completely in latest release, keeping the same functionalities. The only binary that is really affected in its
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
This does raise a question as to why we don't provide a system nssdb. I think we should. I wonder if libnss or libnss3-tools could ship ca- certificates hook to provide a system nssdb certificate store. If we are changing backends, and certs were provided for the nss backend, imho we should automatically convert them and keep them active for the openssl backend. However unlikely it is that somebody made nss- based p11_child work. In nss, we do set minimum TLS version TLSv1.2 but we do not enforce 112 bits of security like we do with OpenSSL. Specifically that is 2k RSA minimum key size, nor prohibit SHA1/MD5 cert hashes, and any cipher suites that use RC4. These changes in minimum requirements do not affect p11_child, but would affect sssd itself when talking over ldaps. I would be worried that an LDAP server has a lowish sized key in their cert, and suddenly an upgrade of sssd, once caches expire, prevent logins. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID
[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child
** Also affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child Status in ca-certificates package in Ubuntu: New Status in sssd package in Ubuntu: Fix Released Status in ca-certificates source package in Focal: New Status in sssd source package in Focal: New Bug description: [ Impact ] SSSD supports in 20.04 two security backends: NSS and OpenSSL (speaking in past tense as upstream dropped NSS support completely). Those two backends are used for various generic crypto features (so they are interchangeable), but also for the management of the PKCS#11 modules for smart cards. In this case, the main problem is that by using NSS it also relies on the presence of a "system NSS" database [1] that is something present in Fedora and RHEL, but not in ubuntu or generic Linux distributions. In order to make SSSD to find a smart card module, we would then need to create a such database that mentions a p11kit proxy that will eventually load the p11-kit module and then add the card CA certificate to the same DB (see more details in [2]). And even in such case... It will not work at login phase. This is making support for Smart-card based authentication in 20.04 quite complicated, and hard to implement in professional environments (see bug #1865226). As per this, recompiling SSSD's p11_child to use OpenSSL (as it already happens starting from 20.10) would be enough to make the this tool (the one in charge for smartcard authentications and certificate matching) to be able to get the smartcard devices from p11-kit allowed modules and to check their certificate using CA certificates in the ubuntu system ca certificate files (or other configured file). One more mayor reason to do this, is also that if we fix 20.04 now to use the "proper" method, people who will configure smartcard access there via SSSD (not easily possible right now) won't be affected by future migrations. [ Proposed Implementations ] 1) Use p11-kit and openssl for p11_child, by changing the build/test system (preferred) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child 2) Build both versions and package things accordingly (hackish) https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1 [ Test case ] With a smartcard reader available (and with a card in its slot) as reported by: $ p11-kit list-modules launch: $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \ --nssdb=/etc/ssl/certs/ca-certificates.crt The tool should find your card: (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module List: (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common name: [p11-kit-trust]. (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so]. (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): Description [/etc/ssl/certs/ca-certificates.crt PKCS#11 Kit ] Manufacturer [PKCS#11 Kit ] flags [1] removable [false] token present [true]. (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common name: [opensc-pkcs11]. (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): Description [VMware Virtual USB CCID 00 00 VMware ] Manufacturer [VMware ] flags [7] removable [true] token present [true]. (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found [MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so]. Then the tool might fail if the card certificate is not added to the ca-certificates.crt, but this is outside the scope of the test case. What it matters is that the card is found. [ Regression potential ] While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend for PKCS#11 operations. And behavior should not change (if not improved), also assuming that upstream dropped NSS support completely in latest release, keeping the same functionalities. The only binary that is really affected in its behavior is p11_child. And I'm confident this will break only those setup (if there are any, given that smartcard access is currently
[Touch-packages] [Bug 1768755] Re: Missing links to libGL.so and libglapi.so
libglvnd-dev only provide libGL.so, but not libapi.so! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1768755 Title: Missing links to libGL.so and libglapi.so Status in mesa package in Ubuntu: Invalid Bug description: In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain the symbolic links libGL.so and libglapi.so. Thus, it is not possible to use the -lGL option to compile a program... System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768755/+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 1718927] Re: No HDMI sound after suspend/resume
A workaround that worked for me was `pulseaudio -k`; having to do this almost every time I need audio is a big PITA though. -- 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/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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