[Touch-packages] [Bug 1952489] [NEW] [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while
Public bug reported: As soon as some playback goes through my integrated speakers it doesn't take long for them to halt. After poking around in PavuControl, I realized that when I have my earbuds connected, the audio profile shows up as integrated speakers. As soon as I disconnect the earbuds, the profile jumps back to "Headphones (plugged in)". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jrios 5967 F pulseaudio /dev/snd/controlC1: jrios 5967 F pulseaudio /dev/snd/pcmC1D0p: jrios 5967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 18:30:13 2021 InstallationDate: Installed on 2021-11-26 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, ATAPI Symptom_Type: Sound works for a while, then breaks Title: [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.release: 1.90 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:br1.90:efr1.30:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00W00C:skuPSKK6U:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite S55-A dmi.product.sku: PSKK6U dmi.product.version: PSKK6U-00W00C dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "This is when I have NOTHING connected to my audio jack." https://bugs.launchpad.net/bugs/1952489/+attachment/5543707/+files/Screenshot%20from%202021-11-26%2018-39-06.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1952489 Title: [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: As soon as some playback goes through my integrated speakers it doesn't take long for them to halt. After poking around in PavuControl, I realized that when I have my earbuds connected, the audio profile shows up as integrated speakers. As soon as I disconnect the earbuds, the profile jumps back to "Headphones (plugged in)". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jrios 5967 F pulseaudio /dev/snd/controlC1: jrios 5967 F pulseaudio /dev/snd/pcmC1D0p: jrios 5967 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 18:30:13 2021 InstallationDate: Installed on 2021-11-26 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, ATAPI Symptom_Type: Sound works for a while, then breaks Title: [Satellite S55-A, IDT 92HD99BXX, Speaker, ATAPI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.release: 1.90 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10S dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:br1.90:efr1.30:svnTOSHIBA:pnSatelliteS55-A:pvrPSKK6U-00W00C:skuPSKK6U:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite S55-A dmi.product.sku: PSKK6U dmi.product.version: PSKK6U-00W00C dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.n
[Touch-packages] [Bug 1952477] [NEW] unable to compile gtk+3.0-3.24.30 on 21.10
Public bug reported: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile sudo apt-get update sudo apt-get build-dep apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' Making check in application8 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application8' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application8' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
The issue is fixed with 3.42 in the current Ubuntu serie, I'm working on backporting the change to impish, later series will also need to be fixed ** Description changed: + * Impact + The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown + + * Testcase + - use evolution + - add a google account + - go the contacts section + + The contacts stored on the google account should be listed, no error + should be displayed + + * Regression potential + The patch changes the google contact backend so any potential issue is likely to be with contacts integration. + + + I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? - [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a ** Changed in: evolution (Ubuntu) Status: New => Fix Committed ** Changed in: evolution (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Released -- 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/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952191] Re: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952191 Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: Confirmed Bug description: Crash on do-release-upgrade 21.04->21.10 ProblemType: Package DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Uname: Linux 5.13.19-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Nov 25 08:28:24 2021 DuplicateSignature: package:systemd:248.3-1ubuntu8 Installing new version of config file /etc/systemd/user.conf ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.19-1-pve root=/dev/mapper/pve-root ro quiet Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: systemd Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to impish on 2021-11-25 (0 days ago) dmi.bios.date: 12/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS MAX (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.90:bd12/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUSMAX(MS-7B79):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952191/+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 1952107] Re: Google Contacts API Deprecated
** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High -- 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/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952353] Re: dmesg: read kernel buffer failed: Operation not permitted
And yet /var/log/dmesg is wide open. How entertaining! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1952353 Title: dmesg: read kernel buffer failed: Operation not permitted Status in util-linux package in Ubuntu: Invalid Bug description: Run /bin/dmesg, get: dmesg: read kernel buffer failed: Operation not permitted sudo dmesg works, but I should not have to do that. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: util-linux 2.36.1-8ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Nov 25 11:13:58 2021 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: util-linux UpgradeStatus: Upgraded to impish on 2021-11-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1952353/+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 1945795] Re: krb5: Fail to build against OpenSSL 3.0
I've uploaded a package to https://launchpad.net/~schopin/+archive/ubuntu/test-ppa/+packages based on the above MR. autopkgtests against -proposed ran fine on amd64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1945795 Title: krb5: Fail to build against OpenSSL 3.0 Status in krb5 package in Ubuntu: New Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22098576/+files/buildlog_ubuntu- impish-amd64.krb5_1.18.3-6.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at https://www.openssl.org/docs/manmaster/man7/migration_guide.html For your tests, you can build against libssl-dev as found in the PPA schopin/openssl-3.0.0 Looking into the upstream master branch, I was able to find the following commits related to OpenSSL3: https://github.com/krb5/krb5/commit/00de1aad7b3647b91017c7009b0bc65cd0c8b2e0 https://github.com/krb5/krb5/commit/d6bf42279675100e3e4fe7c6e08eef74d49624cb https://github.com/krb5/krb5/commit/aa9b4a2a64046afd2fab7cb49c346295874a5fb6 Perhaps a simple cherry-pick of those would suffice? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1945795/+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 1952353] Re: dmesg: read kernel buffer failed: Operation not permitted
This has been intentionally changed a while ago, please see [1]. Thanks! [1] https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1952353 Title: dmesg: read kernel buffer failed: Operation not permitted Status in util-linux package in Ubuntu: Invalid Bug description: Run /bin/dmesg, get: dmesg: read kernel buffer failed: Operation not permitted sudo dmesg works, but I should not have to do that. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: util-linux 2.36.1-8ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Nov 25 11:13:58 2021 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: util-linux UpgradeStatus: Upgraded to impish on 2021-11-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1952353/+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 1952242] Re: [jammy] missing rules for samba profile
Related: https://gitlab.com/apparmor/apparmor/-/issues/203 ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #203 https://gitlab.com/apparmor/apparmor/-/issues/203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1952242 Title: [jammy] missing rules for samba profile Status in apparmor package in Ubuntu: New Bug description: ubuntu jammy apparmor-profiles 3.0.3-0ubuntu3 samba 2:4.13.5+dfsg-2ubuntu3 smbd: Nov 25 14:59:56 jammy-samba-apparmor systemd[1]: Starting Samba SMB Daemon... Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586080] audit: type=1400 audit(1637852396.969:77): apparmor="ALLOWED" operation="capable" profile="smbd" pid=1094 comm="smbd" capability=12 capname="net_admin" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.586241] audit: type=1400 audit(1637852396.969:78): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592258] audit: type=1400 audit(1637852396.977:79): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/sys/kernel/osrelease" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592460] audit: type=1400 audit(1637852396.977:80): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/1/environ" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592532] audit: type=1400 audit(1637852396.977:81): apparmor="ALLOWED" operation="ptrace" profile="smbd" pid=1094 comm="smbd" requested_mask="read" denied_mask="read" peer="unconfined" Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.592683] audit: type=1400 audit(1637852396.977:82): apparmor="ALLOWED" operation="open" profile="smbd" name="/proc/cmdline" pid=1094 comm="smbd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 25 14:59:56 jammy-samba-apparmor kernel: [ 227.600378] audit: type=1400 audit(1637852396.985:83): apparmor="ALLOWED" operation="sendmsg" profile="smbd" name="/run/systemd/notify" pid=1094 comm="smbd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 nmbd: Nov 25 14:59:26 jammy-samba-apparmor systemd[1]: Starting Samba NMB Daemon... Nov 25 14:59:26 jammy-samba-apparmor kernel: [ 196.718721] audit: type=1400 audit(1637852366.105:76): apparmor="ALLOWED" operation="capable" profile="nmbd" pid=1067 comm="nmbd" capability=1 2 capname="net_admin" The systemd notify one for smbd was first fixed for nmbd in https://gitlab.com/apparmor/apparmor/-/merge_requests/236 for nmbd, but smbd was missed. net_admin might be https://github.com/systemd/systemd/pull/10085, I didn't check if jammy's systemd has that patch (it should, since it's old) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1952242/+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 1950511] Re: FTBFS due to meson disallowing + for bools
This is already included in v249.5 stable, that is to be uploaded soon. (https://git.launchpad.net/~slyon/ubuntu/+source/systemd/log/?h=ubuntu- jammy-249) -- 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/1950511 Title: FTBFS due to meson disallowing + for bools Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: In Progress Bug description: FTBFS with new meson: ../meson.build:46:3: ERROR: Object <[BooleanHolder] holds [bool]: False> of type bool does not support the `+` operator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950511/+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 1952457] [NEW] choosing Ubuntu on xorg fails to launch X, launches Wayland
Public bug reported: have to reboot if choosing Ubuntu on xorg results in loading of Ubuntu (wayland) - reboot allows xorg to be used. Logging out/in does not load X even though it was chosen ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 08:13:12 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.28, 5.13.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-10-24 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) Lsusb: Bus 001 Device 004: ID 1058:1230 Western Digital Technologies, Inc. My Book (WDBFJK) Bus 001 Device 003: ID 0bda:58dc Realtek Semiconductor Corp. HP 1.0MP High Definition Webcam Bus 001 Device 002: ID 04b8:1137 Seiko Epson Corp. XP-4100 Series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=a7759f50-03ba-4e51-bb83-fd8b08f86a95 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug has-workaround jammy 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/1952457 Title: choosing Ubuntu on xorg fails to launch X, launches Wayland Status in xorg package in Ubuntu: New Bug description: have to reboot if choosing Ubuntu on xorg results in loading of Ubuntu (wayland) - reboot allows xorg to be used. Logging out/in does not load X even though it was chosen ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 26 08:13:12 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.28, 5.13.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2021-10-24 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) Lsusb: Bus 001 Device 004: ID 1058:1230 Western Digital Technologies, Inc. My Book (WDBFJK) Bus 001 Device 003: ID 0bda:58dc Realtek Semiconductor Corp. HP 1.0MP High Definition Webcam Bus 001 Device 002: ID 04b8:1137 Seiko Epson Corp. XP-4100 Series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=a7759f50-03ba-4e51-bb83-fd8b08f86a95 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek Gm
[Touch-packages] [Bug 1951943] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.14 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Committed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1951943] Re: Engine crashes when loading the configuration more than once
Hello Dimitri, or anyone else affected, Accepted openssl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal ** Changed in: openssl (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Committed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1951943] Re: Engine crashes when loading the configuration more than once
Hello Dimitri, or anyone else affected, Accepted openssl into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1j-1ubuntu3.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Focal: In Progress Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Committed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1951943] Re: Engine crashes when loading the configuration more than once
Hello Dimitri, or anyone else affected, Accepted openssl into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1l-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Focal: In Progress Status in openssl source package in Hirsute: In Progress Status in openssl source package in Impish: Fix Committed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent
** Merge proposal linked:
https://code.launchpad.net/~utkarsh/ubuntu/+source/openssh/+git/openssh/+merge/412456
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1952421
Title:
Issue on sshd finds correct private key for a certificate when using
ssh-agent
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
New
Status in openssh source package in Hirsute:
New
Status in openssh source package in Impish:
New
Bug description:
Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254
upstream:
Please take a look at line 1936 in main() function in sshd.c.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_keys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
the sshkey_equal_public() is trying to compare a cert's pub with a private
key, and it never find a match which makes sshd cannot use this certificate
even though its private key is in ssh-agent.
I believe it should be comparing a cert's public key with a public key in
sensitive_data as follow.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_pubkeys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936
Due to this HostCertificate and HostKeyAgent not working together in
sshd and this affects every version of openssh back till Focal, at
least.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1952430] Re: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while pro
all commands implemented under admin privilege (sudo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1952430 Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system Status in software-properties package in Ubuntu: New Bug description: while installing mysql-server-core-8.0 or any other packages. at first it was fine i do install apache2 but when i tried to install mysql then i faced this error error terminal log /lib: /sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Read-only file system dpkg: error processing package libc-bin (--configure): installed libc-bin package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.9.5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 26 14:14:20 2021 ErrorMessage: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system InstallationDate: Installed on 2021-11-24 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1952430/+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 1952430] [NEW] package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while p
Public bug reported: while installing mysql-server-core-8.0 or any other packages. at first it was fine i do install apache2 but when i tried to install mysql then i faced this error error terminal log /lib: /sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Read-only file system dpkg: error processing package libc-bin (--configure): installed libc-bin package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.9.5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 26 14:14:20 2021 ErrorMessage: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system InstallationDate: Installed on 2021-11-24 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1952430 Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system Status in software-properties package in Ubuntu: New Bug description: while installing mysql-server-core-8.0 or any other packages. at first it was fine i do install apache2 but when i tried to install mysql then i faced this error error terminal log /lib: /sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Read-only file system dpkg: error processing package libc-bin (--configure): installed libc-bin package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.9.5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 26 14:14:20 2021 ErrorMessage: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system InstallationDate: Installed on 2021-11-24 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1952430/+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 1952429] [NEW] package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while p
Public bug reported: while installing mysql-server-core-8.0 or any other packages. at first it was fine i do install apache2 but when i tried to install mysql then i faced this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.9.5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 26 14:14:20 2021 ErrorMessage: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system InstallationDate: Installed on 2021-11-24 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1952429 Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system Status in software-properties package in Ubuntu: New Bug description: while installing mysql-server-core-8.0 or any other packages. at first it was fine i do install apache2 but when i tried to install mysql then i faced this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.9.5 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 26 14:14:20 2021 ErrorMessage: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system InstallationDate: Installed on 2021-11-24 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.98.9.5 failed to install/upgrade: unable to create '/etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf.dpkg-new' (while processing './etc/dbus-1/system.d/com.ubuntu.SoftwareProperties.conf'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1952429/+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 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent
** Also affects: openssh (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1952421
Title:
Issue on sshd finds correct private key for a certificate when using
ssh-agent
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
New
Status in openssh source package in Hirsute:
New
Status in openssh source package in Impish:
New
Bug description:
Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254
upstream:
Please take a look at line 1936 in main() function in sshd.c.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_keys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
the sshkey_equal_public() is trying to compare a cert's pub with a private
key, and it never find a match which makes sshd cannot use this certificate
even though its private key is in ssh-agent.
I believe it should be comparing a cert's public key with a public key in
sensitive_data as follow.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_pubkeys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936
Due to this HostCertificate and HostKeyAgent not working together in
sshd and this affects every version of openssh back till Focal, at
least.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1952421] [NEW] Issue on sshd finds correct private key for a certificate when using ssh-agent
Public bug reported:
Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream:
Please take a look at line 1936 in main() function in sshd.c.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_keys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
the sshkey_equal_public() is trying to compare a cert's pub with a private key,
and it never find a match which makes sshd cannot use this certificate even
though its private key is in ssh-agent.
I believe it should be comparing a cert's public key with a public key in
sensitive_data as follow.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_pubkeys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936
Due to this HostCertificate and HostKeyAgent not working together in
sshd and this affects every version of openssh back till Focal, at
least.
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1952421
Title:
Issue on sshd finds correct private key for a certificate when using
ssh-agent
Status in openssh package in Ubuntu:
New
Bug description:
Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254
upstream:
Please take a look at line 1936 in main() function in sshd.c.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_keys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
the sshkey_equal_public() is trying to compare a cert's pub with a private
key, and it never find a match which makes sshd cannot use this certificate
even though its private key is in ssh-agent.
I believe it should be comparing a cert's public key with a public key in
sensitive_data as follow.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_pubkeys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936
Due to this HostCertificate and HostKeyAgent not working together in
sshd and this affects every version of openssh back till Focal, at
least.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
@Cijay Sure, if you're interested in anything particular, just let me know. There's full bug report output attached to the original bug report ticket for my old setup. Hope those two help: dmesg | grep -e usb3 -e usb\ 3-1 > dmesg.txt pacmd list-sinks output > pacmd.txt ** Attachment added: "Output of dmesg and pacmd" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+attachment/5543528/+files/dmesg_pacmd.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- Mailing list: https://launchpad.net/~touch-
[Touch-packages] [Bug 1952083] Re: Add support for Beige Goby
** Tags added: oem-priority originate-from-1947372 somerville ** Tags added: originate-from-1948411 -- 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/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1952083] Re: Add support for Beige Goby
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority Status: New => Fix Committed -- 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/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1952083] Re: Add support for Beige Goby
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- 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/1952083 Title: Add support for Beige Goby Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952083/+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
