[Touch-packages] [Bug 1995247] Autopkgtest regression report (apt/2.5.3ubuntu0.1)
All autopkgtests for the newly accepted apt (2.5.3ubuntu0.1) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: sbuild/0.83.1ubuntu1 (ppc64el, arm64, s390x, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1995247 Title: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: In Progress Status in apt source package in Kinetic: Fix Committed Status in apt source package in Lunar: Fix Committed Bug description: [Impact] When keys are embedded into deb822 sources files as Signed-By, apt writes them to a temporary file, but the code to delete them accidentally had an if (0) in front of the deletion, so they don't get deleted and accumulate with each `apt update` run. [Test plan] Including a test case for this in our comprehensive integration test suite which runs as autopkgtest, so passing autopkgtest = good. [Where problems could occur] Files could end up being removed too soon if the code is otherwise wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+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 1965219] Re: gnome lock screen does not permit reentering password
Same behavior with an Entroware laptop on 5.15.0-52-generic (both touchpad and internal keyboard, function keys work) Hard to tell who's the culprit among the kernel, libusb, udev and gdm One weird thing in the context of resuming : The Xorg.log generated by gdm shows: (II) UnloadModule: "libinput" message [...] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) [...] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7) [...] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8) (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9) (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10) Typically: [79.317] (II) config/udev: Adding input device Chicony USB2.0 Camera: Chicony (/dev/input/event9) [79.317] (**) Chicony USB2.0 Camera: Chicony : Applying InputClass "libinput keyboard catchall" [79.317] (II) Using input driver 'libinput' for 'Chicony USB2.0 Camera: Chicony ' [79.317] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 43 paused 0 [79.317] (**) Chicony USB2.0 Camera: Chicony : always reports core events [79.317] (**) Option "Device" "/dev/input/event9" [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : is tagged by udev as: Keyboard [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : device is a keyboard [79.319] (II) event9 - Chicony USB2.0 Camera: Chicony : device removed [79.319] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input17/event9" [79.319] (II) XINPUT: Adding extended input device "Chicony USB2.0 Camera: Chicony " (type: KEYBOARD, id 12) [79.319] (**) Option "xkb_model" "pc105" [79.319] (**) Option "xkb_layout" "fr" [79.319] (**) Option "xkb_variant" "azerty" [79.320] (II) event9 - Chicony USB2.0 Camera: Chicony : is tagged by udev as: Keyboard [79.320] (II) event9 - Chicony USB2.0 Camera: Chicony : device is a keyboard (a webcam tagged keyboard?) I don't know if it's related, but if it is it could be a problem with udev rules during resume? -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 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-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
[Touch-packages] [Bug 1993478] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu7.1)
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.1) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: dropbear/2022.82-4 (armhf) gvfs/1.50.2-2 (amd64, arm64) sbuild/0.83.1ubuntu1 (s390x, amd64, arm64, ppc64el) piuparts/1.1.5 (s390x, amd64, arm64, ppc64el) xen-tools/4.9.1-1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#openssh [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Fix Committed Bug description: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere
[Touch-packages] [Bug 1995294] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu7.1)
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.1) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: dropbear/2022.82-4 (armhf) gvfs/1.50.2-2 (amd64, arm64) sbuild/0.83.1ubuntu1 (s390x, amd64, arm64, ppc64el) piuparts/1.1.5 (s390x, amd64, arm64, ppc64el) xen-tools/4.9.1-1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#openssh [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1995294 Title: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Fix Committed Bug description: [Impact] If a user a has an existing drop-in config for ssh.socket in /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh- server.postint determines it should *not* perform migration to socket- activated ssh, they will receive an error from dpkg: Errors were encountered while processing: openssh-server Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. E:Sub-process /usr/bin/dpkg returned an error code (1) Setting up openssh-server (1:9.0p1-1ubuntu7) ... rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server [Test Plan] * On a Jammy machine, install openssh-server if necessary. Edit /etc/ssh/sshd_config to contain the following: $ cat /etc/ssh/sshd_config [... defaults everywhere else ...] #Port 22 #AddressFamily any ListenAddress 0.0.0.0 ListenAddress :: [... defaults everywhere else ...] * Create a trivial drop-in override for ssh.socket: $ systemctl edit ssh.socket $ cat /etc/systemd/system/ssh.socket.d/override.conf [Unit] Description=Testing * Now perform an upgrade to Kinetic, and observe the dpkg error. [Where problems could occur] The solution should be to use rmdir's --ignore-fail-on-empty flag. If the flag was mis-spelled, that would produce a new error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995294/+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 1979032] Re: cpu_freq returns current value in GHz but min/max (fixed in 5.9.1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: s-tui (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-psutil in Ubuntu. https://bugs.launchpad.net/bugs/1979032 Title: cpu_freq returns current value in GHz but min/max (fixed in 5.9.1) Status in python-psutil package in Ubuntu: Confirmed Status in s-tui package in Ubuntu: Confirmed Bug description: Can python-psutil be updated to 5.9.1? It fixes incorrect cpu_freq which affects s-tui. https://github.com/giampaolo/psutil/issues/2049 https://github.com/amanusk/s-tui/issues/186#issuecomment-1100639705 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-psutil/+bug/1979032/+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 1995247] Re: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources
Hello Julian, or anyone else affected, Accepted apt into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.5.3ubuntu0.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: apt (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1995247 Title: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: In Progress Status in apt source package in Kinetic: Fix Committed Status in apt source package in Lunar: Fix Committed Bug description: [Impact] When keys are embedded into deb822 sources files as Signed-By, apt writes them to a temporary file, but the code to delete them accidentally had an if (0) in front of the deletion, so they don't get deleted and accumulate with each `apt update` run. [Test plan] Including a test case for this in our comprehensive integration test suite which runs as autopkgtest, so passing autopkgtest = good. [Where problems could occur] Files could end up being removed too soon if the code is otherwise wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
Hello msaxl, or anyone else affected, Accepted openssh into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu7.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: openssh (Ubuntu Kinetic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Fix Committed Bug description: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run
[Touch-packages] [Bug 1995294] Re: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty
Hello Nick, or anyone else affected, Accepted openssh into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu7.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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: openssh (Ubuntu Kinetic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1995294 Title: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty Status in openssh package in Ubuntu: Triaged Status in openssh source package in Kinetic: Fix Committed Bug description: [Impact] If a user a has an existing drop-in config for ssh.socket in /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh- server.postint determines it should *not* perform migration to socket- activated ssh, they will receive an error from dpkg: Errors were encountered while processing: openssh-server Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. E:Sub-process /usr/bin/dpkg returned an error code (1) Setting up openssh-server (1:9.0p1-1ubuntu7) ... rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server [Test Plan] * On a Jammy machine, install openssh-server if necessary. Edit /etc/ssh/sshd_config to contain the following: $ cat /etc/ssh/sshd_config [... defaults everywhere else ...] #Port 22 #AddressFamily any ListenAddress 0.0.0.0 ListenAddress :: [... defaults everywhere else ...] * Create a trivial drop-in override for ssh.socket: $ systemctl edit ssh.socket $ cat /etc/systemd/system/ssh.socket.d/override.conf [Unit] Description=Testing * Now perform an upgrade to Kinetic, and observe the dpkg error. [Where problems could occur] The solution should be to use rmdir's --ignore-fail-on-empty flag. If the flag was mis-spelled, that would produce a new error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995294/+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 1995507] Re: List number of crashes in motd on servers
Personally, I'd like to see this implemented so that we get crash reports from more systems so I've tagged it foundations-triage-discuss in the hopes it'll move to foundations-todo. ** Tags added: foundations-triage-discuss -- 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/1995507 Title: List number of crashes in motd on servers Status in apport package in Ubuntu: New Bug description: To make users more aware of existing crashes that should/could be reported, please mention the number of crashes in the motd (if there are any). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995507/+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 1995507] Re: List number of crashes in motd on servers
I think there should also be an informational message about how to report the crash(es) as is done with messages in the motd. Example: 1 device has a firmware upgrade available. Run `fwupdmgr get-upgrades` for more information. 0 updates can be applied immediately. New release '22.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it. So "Run 'apport-cli /var/crash/$package.crash'". Ideally running 'apport-cli' would prompt you about the pending crash reports in /var/crash instead of you having to pass the specific crash file to 'apport-cli'. -- 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/1995507 Title: List number of crashes in motd on servers Status in apport package in Ubuntu: New Bug description: To make users more aware of existing crashes that should/could be reported, please mention the number of crashes in the motd (if there are any). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995507/+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 1995507] [NEW] List number of crashes in motd on servers
Public bug reported: To make users more aware of existing crashes that should/could be reported, please mention the number of crashes in the motd (if there are any). ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1995507 Title: List number of crashes in motd on servers Status in apport package in Ubuntu: New Bug description: To make users more aware of existing crashes that should/could be reported, please mention the number of crashes in the motd (if there are any). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1995507/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Invalid ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: Confirmed => Invalid ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: ubuntu-settings (Ubuntu Kinetic) Assignee: Dave Jones (waveform) => (unassigned) -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Invalid Status in pulseaudio source package in Jammy: Confirmed Status in ubuntu-settings source package in Jammy: Invalid Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Invalid Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
Thanks for the reproducer, Maximilian. I added this to the server team backlog so someone can work on this one soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1995260 Title: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Focal: Triaged Bug description: We upgraded our openstack containers which host dnsmasq services from bionic to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN. This is already fixed upstream with the following commit [1]. The Ubuntu dnsmasq 2.80 package should get a backport with a release for the focal packages which includes this bug fix. [1] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
** Changed in: dnsmasq (Ubuntu Focal) Status: New => Triaged ** Tags added: bitesize server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1995260 Title: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Focal: Triaged Bug description: We upgraded our openstack containers which host dnsmasq services from bionic to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN. This is already fixed upstream with the following commit [1]. The Ubuntu dnsmasq 2.80 package should get a backport with a release for the focal packages which includes this bug fix. [1] https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+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 1982583] Re: Fix for zlib CRC32 optimization for s390x
Folded into the LP #1990379 uploads to Jammy, Kinetic and Lunar. ** Also affects: zlib (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zlib (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1982583 Title: Fix for zlib CRC32 optimization for s390x Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Jammy: New Status in zlib source package in Kinetic: New Bug description: SRU Justification: -- [ Impact ] * There were two issues identified in the current zlib CRC32 optimization for s390x implementation: * 1) s390_crc32_vx() signature mismatch which causes a warning * 2) '-DS390_CRC32_VX' was not added to SFLAGS which results in vectorization being enabled only in the static library. * The fixes are quite small and affect each only one line: * 1) by using unsigned longs instead of uint32_t in s390_crc32_vx declaration * 2) by add line 'SFLAGS="$SFLAGS -DS390_CRC32_VX"' [ Test Plan ] * An affected Ubuntu release ([20.04], 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that checks for s390_crc32_vx() signature mismatches. * The bug reporter has a set of s390x-specific tests that will be executed. * Test will be done by IBM. [ Where problems could occur ] * The fixes are each limited to one line, hence there are not many issues to expect, other than: * Typos (e.g. in the flags), mixing of CFLAGS and SFLAGS, * in case the changed data type in s390_crc32_vx is causing issues inside of s390_crc32_vx or in other parts of the code. * Structural and syntactical issues can be identified with a test build that was done for all affected Ubuntu releases and for all major archs: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379+lp1982583 [ Other Info ] * This bug (LP#1982583) is solved in combination with LP#1990379, so that only one package update is needed. However, LP#1990379 also affects Focal, but this bug only Jammy and Kinetic. * To fix LP#1990379 also for focal the debdiff mentioned there is needed, too. __ 'zlib CRC32 optimization for s390x works only in a static library' I've discovered two issues in lp1932010-ibm-z-add-vectorized- crc32-implementation.patch: 1) s390_crc32_vx() signature mismatch, resulting in a warning. 2) -DS390_CRC32_VX is not added to SFLAGS, resulting in vectorization being enabled only in the static library. I've attached the updated patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982583/+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 1711428] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily-upgrade.service execution
See https://github.com/canonical/cloud-init/pull/1034 and https://github.com/canonical/cloud-init/pull/1153 ** Changed in: cloud-init Status: Incomplete => Fix Released -- 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/1711428 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily- upgrade.service execution Status in cloud-init: Fix Released Status in apt package in Ubuntu: Expired Bug description: This is the same problem as https://bugs.launchpad.net/cloud- init/+bug/1693361, but with a different APT invoking service. In this case it is apt-daily-upgrade.service. So, I guess add apt-daily-upgrade.service to the Before line in /lib/systemd/system/cloud-final.service along side apt-daily.service. Or wait for an APT fix. Or retry APT commands when executing "packages:" Reporting this to save someone else trouble, but I think we'll be rolling back to Trusty at this point. Hopefully the B LTS will have an alternative to systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1711428/+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 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
Uploaded to Lunar, Kinetic, Jammy and Focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Status in zlib source package in Focal: Triaged Status in zlib source package in Jammy: Triaged Status in zlib source package in Kinetic: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. * This bug (LP#1990379) is solved in combination with LP#1982583, so that only one package update is needed. However, this bug affects Kinetic, jammy and Focal, but LP#1982583 only Jammy and Kinetic. * The debdiffs for Kinetic and Jammy should be taken from LP#1982583, and the remaining debdiff for Focal from here. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+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 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
** Tags removed: foundations-triage-discuss -- 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/1992979 Title: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Status in systemd package in Ubuntu: Incomplete Bug description: Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU, single CPU, 1GB memory, rebooted, can NO longer login. Stuck in systems boot phase. Attached is an image of the hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
Still a problem on jammy, and removing switch-on-connect does fix things there. The result of that change is that plugging in a new (never seen before) USB device does *not* automatically switch to it, but once the device has been selected as the output, it will subsequently be automatically selected when plugged in (or at least that's my experience on my PC). And it also clears up the "always selects headphones output" issue on the Pi. I'll target this to jammy given we're still getting duplicate reports about it (LP: #1995459 is the latest) ** Also affects: pulseaudio (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Confirmed Status in pulseaudio source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in pulseaudio source package in Kinetic: Won't Fix Status in ubuntu-settings source package in Kinetic: Confirmed Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1995459] Re: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 This sounds like a duplicate of LP: #1877194 -- a workaround is available in that report (see comment 2) ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- 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/1995459 Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995459/+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 1995459] [NEW] [vc4-hdmi - vc4-hdmi-0, playback] Playback problem
Public bug reported: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image wayland-session -- 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/1995459 Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: System sound output setting always defaults to headphones instead of hdmi at startup and login and must be reset every time. No headphones are connected; only hdmi from pi 4 to TV and from TV to sound system via hdmi-arc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1017.19-raspi 5.15.60 Uname: Linux 5.15.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bruzr 10351 F pulseaudio /dev/snd/controlC0: bruzr 10351 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 2 04:54:41 2022 ImageMediaBuild: 20220809 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:vc4hdmi0 failed Symptom_AlsaPlaybackTestStderr: S a m p l e f o r m a t n o t a v a i l a b l e f o r p l a y b a c k : I n v a l i d a r g u m e n t Symptom_Card: vc4-hdmi - vc4-hdmi-1 Symptom_Type: None of the above Title: [vc4-hdmi - vc4-hdmi-0, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1995459/+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
