[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic
** Changed in: openssh (Ubuntu) Importance: Medium => High -- 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/1991199 Title: sshd port migration is missing two config lines from jammy to kinetic Status in openssh package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Bug description: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]: /etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of section. Ignoring. $ cat /etc/systemd/system/ssh.socket.d/override.conf ListenStream= # Analysis The migration script must be missing the `[Socket]` line and the next one. sshd works after I added those two lines manually. Either the migration script never worked or systemd changed the syntax in the meantime. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 Package: systemd 251.4-1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 Tags: kinetic Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd05/19/2017:br4.6:svnASUSTeKCOMPUTERINC.:pnK30BF_M32BF_A_F_K31BF_6:pvrSystemVersion:rvn
[Touch-packages] [Bug 1991283] Re: "sshd -i" breaks due to socket activation
** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => In Progress ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- 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/1991283 Title: "sshd -i" breaks due to socket activation Status in openssh package in Ubuntu: In Progress Bug description: On Jammy and earlier, simply running "sshd -i" worked. Now, it fails silently, and running it with "-d" gives me: Missing privilege separation directory: /run/sshd This directory is normally created with "RuntimeDirectory=sshd" as defined in /lib/systemd/system/ssh.service. In Jammy, this directory got created by the ssh service starting at boot, so "sshd -i" worked. Now, with socket activation, it no longer does that, so "sshd -i" fails unless someone has actually connected on TCP port 22 (which they often won't have, since that's the point of "sshd -i"). systemd will then remove /run/sshd when the ssh service is stopped. I think maybe this won't interfere with an existing "sshd -i", but it's not really clean. Further, the privilege separation directory doesn't appear to be configurable - at least I couldn't find any mention in sshd_config(5). The workaround is to "mkdir -p /run/sshd && sshd -i" instead. Given that "sshd -i"'s use of /run/sshd isn't really related to the systemd service, maybe we should move the creation of that directory into tmpfiles.d instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991283/+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 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic
I see on review that your patch does fix any broken override files, by virtue of replaying the same upgrade code if upgrading from 1ubuntu6. There are some corner cases where that might not be desirable, but as these are all pre-release versions I think it's ok to ignore these in favor of landing the fix more quickly. ** Changed in: openssh (Ubuntu) Status: Triaged => In Progress -- 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/1991199 Title: sshd port migration is missing two config lines from jammy to kinetic Status in openssh package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Bug description: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]: /etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of section. Ignoring. $ cat /etc/systemd/system/ssh.socket.d/override.conf ListenStream= # Analysis The migration script must be missing the `[Socket]` line and the next one. sshd works after I added those two lines manually. Either the migration script never worked or systemd changed the syntax in the meantime. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 Package: systemd 251.4-1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 Tags: kinetic Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 dmi.board.vendor: ASUSTeK COM
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
This bug was fixed in the package apt - 2.5.3 --- apt (2.5.3) unstable; urgency=medium [ Povilas Kanapickas ] * doc: Explain that apt-get download ensures package authenticity [ David Kalnischkies ] * Keep color disabled if APT::Color was set to false * Don't reuse filename for in-tree builds of apt * Respect users pkg order on `apt install` for resolving [ Hideki Yamane ] * Fix typo in Japanese program translation [ lancethepants ] * porting (musl): - apt-pkg/contrib/fileutl.h Explicitly include sys/stat.h [ Khem Raj ] * porting (clang15): - typecast time_t and suseconds_t from std::chrono - interactive-helper: Undefine _FORTIFY_SOURCE [ Julian Andres Klode ] * edsp: Add support for phased updates (test in LP#1990586) * Check state of dependency, not depender in dependency keep back (LP: #1990684) * full-upgrade: Mark phased upgrades for keep before anything else (LP: #1990586) -- Julian Andres Klode Wed, 28 Sep 2022 17:16:41 +0200 ** Changed in: apt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990586 Title: 22.04: python3* mismatched phasing breaks dist-upgrades Status in apt package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Plan - autopkgtests run the integration test suite. We have added a simplified version of the EDSP file attached here with additional fields for the phasing info (and support to the EDSP reader) to automatically check this as part of the test suite. The changes made were to essentially only include installed and phased python3.10, python3-defaults upgrades. And then we run the solver on that and check the exact actions it takes, which is an autoremove of systemd-hwe-hwdb which is fine. Before the change, it was removing half the system. Original test case: This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Where problems could occur -- This fix touches the dist-upgrade code and the enablement for the test case also touches the EDSP writer and reader, so problems can occur in the EDSP debugging bits and during dist-upgrades, related to phasing upgrades. Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateu
[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed
This bug was fixed in the package apt - 2.5.3 --- apt (2.5.3) unstable; urgency=medium [ Povilas Kanapickas ] * doc: Explain that apt-get download ensures package authenticity [ David Kalnischkies ] * Keep color disabled if APT::Color was set to false * Don't reuse filename for in-tree builds of apt * Respect users pkg order on `apt install` for resolving [ Hideki Yamane ] * Fix typo in Japanese program translation [ lancethepants ] * porting (musl): - apt-pkg/contrib/fileutl.h Explicitly include sys/stat.h [ Khem Raj ] * porting (clang15): - typecast time_t and suseconds_t from std::chrono - interactive-helper: Undefine _FORTIFY_SOURCE [ Julian Andres Klode ] * edsp: Add support for phased updates (test in LP#1990586) * Check state of dependency, not depender in dependency keep back (LP: #1990684) * full-upgrade: Mark phased upgrades for keep before anything else (LP: #1990586) -- Julian Andres Klode Wed, 28 Sep 2022 17:16:41 +0200 ** Changed in: apt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1990684 Title: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed Status in apt package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: [Impact] Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade anything anymore, for example, see the original bug report below. [Test plan] We cannot reproduce the exact failure here, but we have included a minimal test case that triggers the same error in the integration test test-phased-updates-upgrade. The test suite is exhaustive and covers more than a human reasonably can, especially since we also cannot publish broken updates again to get people to test the fix. [Where problems could occur] This is a one word fix in the solver. When deciding whether a depends could be kept back, we accidentally looked at the package declaring the dependency instead of the package we depend upon. Of course this might unearth other fancy solver bugs. There is one limitation in that this only applies to "Protected" packages (not in the Protected field sense, but if you "Protect" the change in the solver), which is *mostly* triggered only if you have held packages or phased updates, so workarounds should always be easy. [Original bug report] # apt clean # apt update Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed E: Broken packages # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu10 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz"; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7) Package: grub-efi-arm64-signed Depends: grub-efi-arm64 (= 2.06-2ubuntu7) # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz"; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10) Package: grub-efi-arm64-signed Depends: grub-efi-arm64 (= 2.06-2ubuntu10) [[Workaround]] echo "APT::Get::Never-Include-Phased-Updates: 1;" > /etc/apt/apt.conf.d/99phased-updates Pr
[Touch-packages] [Bug 1991427] [NEW] ssh doesn't offer identity files in the right order
Public bug reported:
"man ssh_config" claims that the "IdentityFile"s will be tried in
sequence:
IdentityFile
Specifies a file from which the user's DSA, ECDSA, authenticator-hosted
ECDSA, Ed25519, authenticator-hosted Ed25519 or RSA au‐
thentication identity is read. The default is ~/.ssh/id_rsa,
~/.ssh/id_ecdsa, ~/.ssh/id_ecdsa_sk, ~/.ssh/id_ed25519,
~/.ssh/id_ed25519_sk and ~/.ssh/id_dsa. Additionally, any identities
represented by the authentication agent will be used for
authentication unless IdentitiesOnly is set. If no certificates have
been explicitly specified by CertificateFile, ssh(1) will
try to load certificate information from the filename obtained by
appending -cert.pub to the path of a specified IdentityFile.
Arguments to IdentityFile may use the tilde syntax to refer to a user's
home directory or the tokens described in the TOKENS sec‐
tion.
It is possible to have multiple identity files specified in
configuration files; all these identities will be tried in sequence.
Multiple IdentityFile directives will add to the list of identities
tried (this behaviour differs from that of other configura‐
tion directives).
IdentityFile may be used in conjunction with IdentitiesOnly to select
which identities in an agent are offered during authentica‐
tion. IdentityFile may also be used in conjunction with
CertificateFile in order to provide any certificate also needed for au‐
thentication with the identity.
Yet it doesn't try them in the order specified ("id_ed25519-postfix"
comes before "id_ed25519" in my "~/.ssh/config"):
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_ed25519-postfix type 3
debug1: identity file /home/user/.ssh/id_ed25519-postfix-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519 type 3
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
...
debug1: Will attempt key: /home/user/.ssh/id_ed25519 ED25519 SHA256:
explicit agent
debug1: Will attempt key: /home/user/.ssh/id_ed25519-postfix ED25519
SHA256: explicit agent
This causes the wrong key to be used for log in. This is especially
problematic when using Git over SSH, which causes the server to report
repository doesn't exist as the username are the same and the key
dictates the account being logged in, and instead of getting a
permission denied the server would give out a more confusing message,
misleading the direction the user goes to debug.
Ubuntu 22.04.1 with openssh-client 1:8.9p1-3
** 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/1991427
Title:
ssh doesn't offer identity files in the right order
Status in openssh package in Ubuntu:
New
Bug description:
"man ssh_config" claims that the "IdentityFile"s will be tried in
sequence:
IdentityFile
Specifies a file from which the user's DSA, ECDSA,
authenticator-hosted ECDSA, Ed25519, authenticator-hosted Ed25519 or RSA au‐
thentication identity is read. The default is ~/.ssh/id_rsa,
~/.ssh/id_ecdsa, ~/.ssh/id_ecdsa_sk, ~/.ssh/id_ed25519,
~/.ssh/id_ed25519_sk and ~/.ssh/id_dsa. Additionally, any identities
represented by the authentication agent will be used for
authentication unless IdentitiesOnly is set. If no certificates have
been explicitly specified by CertificateFile, ssh(1) will
try to load certificate information from the filename obtained by
appending -cert.pub to the path of a specified IdentityFile.
Arguments to IdentityFile may use the tilde syntax to refer to a
user's home directory or the tokens described in the TOKENS sec‐
tion.
It is possible to have multiple identity files specified in
configuration files; all these identities will be tried in sequence.
Multiple IdentityFile directives will add to the list of identities
tried (this behaviour differs from that of other configura‐
tion directives).
IdentityFile may be used in conjunction with IdentitiesOnly to select
which identities in an agent are offered during authentica‐
tion. IdentityFile may also be used in conjunction with
CertificateFile in order to provide any certificate also needed for au‐
thentication with the identity.
Yet it doesn't try them in the order specified ("id_ed25519-postfix"
comes before "id_ed25519" in my "~/.ssh/config"):
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_ed25519-postfix type 3
debug1: identity file /home/user/.ssh/id_ed25519-postfix-cert type -1
debug1: identity file /home/user/.ssh/id_ed25519 type 3
debug1: identity file /home/user/.ssh/id_ed25519-c
[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic
Thanks for the patch, Nick. We should also make sure that for users that had 1ubuntu6 unpacked, we fix up any broken override file as well. I have some other changes for openssh in progress and will intend to pick up this fix as part of my next upload. ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- 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/1991199 Title: sshd port migration is missing two config lines from jammy to kinetic Status in openssh package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]: /etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of section. Ignoring. $ cat /etc/systemd/system/ssh.socket.d/override.conf ListenStream= # Analysis The migration script must be missing the `[Socket]` line and the next one. sshd works after I added those two lines manually. Either the migration script never worked or systemd changed the syntax in the meantime. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 Package: systemd 251.4-1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 Tags: kinetic Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chass
[Touch-packages] [Bug 1971901] Re: dlltool uses non-unique temp filenames
** Tags removed: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1971901 Title: dlltool uses non-unique temp filenames Status in binutils: Fix Released Status in Wine: Won't Fix Status in binutils package in Ubuntu: Confirmed Status in binutils-mingw-w64 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 22.04 LTS Release:22.04 binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1 /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.delay.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Assembler messages: Error: can't open winmm_dll_t.s for reading: No such file or directory /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited with status 1 /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: winmm_dll_t.o: No such file or directory winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1 make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1 make: *** Waiting for unfinished jobs tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/winmm/libwinmm.cross.a --export \ ../wine-6.0.4/dlls/winmm/winmm.spec Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for it's temp file - these are not unique when building libwinmm.delay.a and libwinmm.cross.a in parallel. (This can of course affect any dll wine is building import libs for, winmm is just the one I happaned to get caught on). This is regression newly introduced in binutils 2.38 vs older versions which used getpid() as the basis of their temp name. We just encountered it as part of updating our CI for a winelib application from focal to jammy, but it seems to have been discovered by others already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885 There is an upstream fix on master (2.39) which is already backported to the binutils-2_38 branch: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just be a matter of cherry-picking. Hopefully the fact it's a regression from impish->jammy and that upstream already backported it to 2.38 might make this a candidate for jammy-updates? To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1971901/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
** Bug watch added: Linux Kernel Bug Tracker #216194 https://bugzilla.kernel.org/show_bug.cgi?id=216194 -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Created attachment 301907 attachment-12523-0.html Almost certainly your laptop doesn't have the _DSD entries needed to properly get sound working. Check dmesg for either of these messages: dmesg | grep -i "Platform not supported -EINVAL" or dmesg | grep -i "Error: ACPI _DSD Properties are missing for HID" For reference, see: https://www.spinics.net/lists/alsa-devel/msg146157.html https://bugzilla.kernel.org/show_bug.cgi?id=216194 I have the same problem with the Lenovo Legion 2022 Gen 7 (16IAX7). I filed a support ticket with Lenovo a few weeks back, but when support followed back they wanted to text during work hours, and I was too busy to deal with that then and too busy to deal with it since. I think I may actually have some time today. If you have either message in your dmesg, I'd suggest filing a support ticket. If enough people complain about these issues, it may compel them to add the proper _DSD entries into a BIOS update. There's no reason that Lenovo can't include this information in a BIOS update. It does seem that going forward that the intention of Cirrus Logic is for the vendors to include this information in the BIOS. For vendors where this is not the case, likely what's happening is that these values are hard coded in the vendor provided drivers or firmware. It doesn't require them to touch Linux at all. It should be relatively simple for them to add this information as there's already an incomplete entry in the ACPI table as it is. In the kernel bug linked above, I attached a hacky patch that gets sound working on the 16IAX7... But it's a hack where I guessed and hard-coded the values and these could physically damage your speakers if the settings are too inappropriate for your model of laptop (including the 16IAX7). This is very much a USE AT YOUR OWN RISK scenario, and I sincerely recommend against using my patches to avoid any possibility of damage to your laptop. Furthermore, sound doesn't work after resume anyway. Although it could be argued that if people start trying to use hacks like these to enable sound under Linux for their laptop, vendors such as Lenovo may need to issue BIOS updates to address this to avoid costly laptop repairs. On 9/30/22 05:11, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > jochemp...@gmail.com changed: > > What|Removed |Added > > CC||jochemp...@gmail.com > > --- Comment #696 fromjochemp...@gmail.com --- > I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my > alsa-info hopefully it's of some use: > http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c > -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.
[Touch-packages] [Bug 1958019]
I seem to have the same issue on a lenovo Legion S7 16ARHA7, here is my alsa-info hopefully it's of some use: http://alsa-project.org/db/?f=59acbf18b993b0a49edaaee0027d4b57fcf2055c -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
This bug was fixed in the package p11-kit - 0.24.1-1ubuntu2 --- p11-kit (0.24.1-1ubuntu2) kinetic; urgency=medium * debian/patches/lp-1991067-pkcs11-gnu-Enable-testing-with-p11-kit- pkcs11x.h.patch: Fix gnutls FTBFS. Closes LP: #1991067. -- Adrien Nader Thu, 29 Sep 2022 10:55:32 + ** Changed in: p11-kit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: Fix Released Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+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 1991143] Re: Systemd reboot halt Lenovo ThinkPad x230 running jammy
Well, it's really weird but I tried to reproduce the problem (what I see happening for at least 2 months) and for some unknown reason I couldn't. It's rebooting as expected using any of those methods. I will try to investigate and understand what could be the change that fixed it but it's not worth it to keep this ticket open while I do it. Thanks anyway! -- 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/1991143 Title: Systemd reboot halt Lenovo ThinkPad x230 running jammy Status in systemd package in Ubuntu: Incomplete Bug description: I've installed Ubuntu Desktop jammy on a Lenovo Thinkpad x230 laptop and upgraded all packages to latest version. When I try to reboot machine using command line reboot, shutdown -r now or using Restart option on desktop it just halts the laptop instead of reboot it. I've downloaded klibc-utils package, which contains a reboot binary, and when I run it, laptop reboots just as expected. I've collected strace output from both systemd and binary reboot calls (until SSH was dropped) and pasted at https://gist.github.com/rbgarga/b6a35e448a9c30502eaea09611191c73 Just let me know if you need any other information about my running system or hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991143/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
I was able to reproduce it on an Lubuntu kinetic-desktop-amd64.iso (from 20220927.4) by running: ``` $ PATH=/usr/sbin:/usr/bin:/sbin:/bin xdg-open https://ubuntu.com /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://ubuntu.com' ``` -- 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/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Status in xdg-utils package in Ubuntu: Invalid Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1973470/+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 1097467] Re: bash does not fulfill --rcfile option properly
** Changed in: bash (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1097467 Title: bash does not fulfill --rcfile option properly Status in bash package in Ubuntu: Confirmed Bug description: I am starting a bash shell using $ bash --noprofile --rcfile my-custom-bash-rc-file Due to the --rcflag, the newly started bash should *not* execute commands from /etc/bash.bashrc. That is at least how I interpret `man bash`: --rcfile file Execute commands from file instead of the system wide initialization file /etc/bash.bashrc and the standard personal initial‐ ization file ~/.bashrc if the shell is interactive (see INVOCATION below). However, it seems that the commands in /etc/bash.bashrc are in fact executed. To see/reproduce/diagnose this, on Ubuntu I believe one can just invoke bash like this (as the regular user): $ touch testrc $ env -i bash --noprofile --rcfile testrc The expected result would be that nothing special is printed on the terminal. However, there is an error message, which is printed from /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the invoked shell, which in turn triggers the error. The error message is: > To run a command as administrator (user "root"), use "sudo ". > See "man sudo_root" for details. Another way to see this -- without the "env -i" -- is to add a command to /etc/bash.bashrc, such as echo HELLO THERE To trigger the bug(?), one can then just do $ touch testrc $ bash --noprofile --rcfile testrc The expected result would be that nothing special is shown in the terminal. However, it turns out that the string HELLO THERE is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+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 1990689] Re: Cannot connect to Google account after upgrading to 22.04 LTS
Problem identified today : the folder ~/.local/share/webkitgtk is owned by root, with no permissions granted to other users. I changed the permissions to RW for other users, and I am now able to log in my google accounts ! Chris -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990689 Title: Cannot connect to Google account after upgrading to 22.04 LTS Status in gnome-online-accounts package in Ubuntu: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS, my Google accounts were disconnected. In the "Parameters/Online accounts" window, a double-click on each Google account opens a window indicating "authentication data expired. Please login to use this account". A click on the "Login" button opens a blank window, the only thing I can do is closing the window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 23 21:00:36 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2021-12-29 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2022-09-11 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message
Good morning Nick, Yes; as the PIs normally boot headlessly or with hdmi, it's not easy to gather the logs. What I will do is hookup a serial line to I can catch the logs from another systems miniterm and attach them to the bugreport. I will also add the recipe to reproduce this. Important, prior tot 22.04 I had the issue of drivers being stripped from the initramfs but in 22.04 whole binaries are apperently not locatable anymore. Strings thing is, when I loop them up by unarchiving the initramfs, they are definately there? Could be some PATH problem? Other question from my side to assist you in solving / fixing this; is there some design/document that explains how it works and if is different (flash-kernel?) on PIs? Thanks in advance. Kind regards, Pascal van Dam On 9/30/22 18:28, Nick Rosbrook wrote: > Can you please provide some specific examples of the errors you are > seeing, as well as some instructions to try and reproduce your setup? > > ** Changed in: initramfs-tools (Ubuntu) > Status: New => Incomplete > -- ** Attachment added: "g501.png" https://bugs.launchpad.net/bugs/1991324/+attachment/5620322/+files/g501.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991324 Title: Initramfs-tools: iSCSI boot resulting in modprobe not found error message Status in initramfs-tools package in Ubuntu: Incomplete Bug description: My RPi4's are having their rootvg on iSCSI and boot from them. The kernel modules etc are in the initramfs. However since 22.04 the initramfs is not generated corrected and while booting from it it results in error messages stating various binaries/scripts are not locatable. E.g. modprobe, systemd-udev, mdadm etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+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 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)
Hello Reuben, I've started working on getting this fix into Ubuntu. In the meantime, if you would like this fix in 22.04 you can get it from a ppa I made here: https://launchpad.net/~lvoytek/+archive/ubuntu/dnsmasq-fix-denied- dns-retries To install run the following commands: sudo add-apt-repository ppa:lvoytek/dnsmasq-fix-denied-dns-retries sudo apt update thanks! ** Changed in: dnsmasq (Ubuntu Kinetic) Status: Confirmed => In Progress -- 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/1981794 Title: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream) Status in dnsmasq package in Ubuntu: In Progress Status in dnsmasq source package in Jammy: Confirmed Status in dnsmasq source package in Kinetic: In Progress Bug description: Duplicate or retried DNS queries will return REFUSED for one of the queries causing intermittent failures in clients. This probably breaks lots of things, but for me is causing 22.04's internet connection sharing to be unstable. It's particularly bad for my Xbox which seems to like sending duplicate queries. Here's an example capture: 22:37:25.308212 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? title.auth.xboxlive.com. (41) 22:37:25.332711 IP 10.42.0.16.54248 > 10.42.0.1.53: 22442+ A? title.auth.xboxlive.com. (41) 22:37:25.332740 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 Refused 0/0/0 (41) 22:37:25.353003 IP 10.42.0.1.53 > 10.42.0.16.54248: 22442 2/0/0 CNAME title.auth.xboxlive.com.akadns.net., A 40.64.90.82 (105) This has been fixed in upstream as of Sept 2021 in the unreleased 2.87 version. It's apparently a regression in version 2.86 (also released in Sept 2021). Ubuntu 22.04 and later all use the broken 2.86 version. Upstream fix: https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be1df48da1e2bd3d3feaa138c2 Upstream bug thread: https://www.mail-archive.com/search?l=dnsmasq-discuss%40lists.thekelleys.org.uk&q=subject:%22%5C%5BDnsmasq%5C-discuss%5C%5D+REFUSED+after+dropped+packets%22&o=oldest&f=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1981794/+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 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message
Can you please provide some specific examples of the errors you are seeing, as well as some instructions to try and reproduce your setup? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991324 Title: Initramfs-tools: iSCSI boot resulting in modprobe not found error message Status in initramfs-tools package in Ubuntu: Incomplete Bug description: My RPi4's are having their rootvg on iSCSI and boot from them. The kernel modules etc are in the initramfs. However since 22.04 the initramfs is not generated corrected and while booting from it it results in error messages stating various binaries/scripts are not locatable. E.g. modprobe, systemd-udev, mdadm etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991324/+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 1990729] Re: gdb crashes when run from VSCode
Lowell - Thank you for testing and confirming that the gdb SRU[1] fixes this! [1] https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474 ** Changed in: gdb (Ubuntu) Status: New => Fix Committed ** Changed in: gdb (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1990729 Title: gdb crashes when run from VSCode Status in gdb package in Ubuntu: Fix Committed Bug description: I had no pre-existing breakpoints in VSCode, then added a breakpoint, and used F5 to run the debugger to the one breakpoint. It crashed before it got there. This is a C++ executable compiled for debugging using CMAKE. I can successfully debug the program using the TUI mode of gdb, so I think the problem likes in the vscode interface to gdb. /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.0.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21 Uname: Linux 5.14.0-1051-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 11:10:11 2022 InstallationDate: Installed on 2022-02-15 (221 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdb UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+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 1989803] Re: Adjust apport for the new Ubuntu debuginfod service
https://github.com/canonical/apport/pull/6 got merged to main. ** Changed in: apport Status: Triaged => Fix Committed -- 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/1989803 Title: Adjust apport for the new Ubuntu debuginfod service Status in Apport: Fix Committed Status in apport package in Ubuntu: In Progress Bug description: With the new Ubuntu debuginfod service (https://debuginfod.ubuntu.com), and with the prospect of having the system automatically fetch debuginfo from the internet without user intervention, it is necessary to adjust apport to cope with this scenario. I had a conversation with bdmurray and he was concerned that having a debuginfod-enabled GDB generate the corefiles that are eventually submitted to Ubuntu can be a problem. My proposed solution is to disable GDB's debuginfod support when collecting the corefile. This should keep things as is and not disturb the retrace service. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1989803/+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 1991200] Re: apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno'
** Changed in: apport Status: Triaged => Fix Committed -- 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/1991200 Title: apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno' Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Bug description: apport-collect crashed. # lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 # apt-cache policy apport apport: Installed: 2.23.0-0ubuntu2 Candidate: 2.23.0-0ubuntu2 Version table: *** 2.23.0-0ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status # Instructions 1. Run apport-collect NUMBER as root 2. Get to the point it asks before sending 3. Choose to view the report 4. Watch the crash # Expected behavior Apport-collect should stay alive and not crash with a stacktrace. # Actual behavior # apport-collect 1991199 Please open this authorization page: (REDACTED) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Package openssh not installed and no hook available, ignoring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** It seems you have modified the contents of "/etc/systemd/logind.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n *** It seems you have modified the contents of "/etc/systemd/sleep.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (597.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v Traceback (most recent call last): File "/usr/bin/apport-cli", line 442, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 858, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 758, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 258, in ui_present_report_details self.ui_update_view() File "/usr/bin/apport-cli", line 187, in ui_update_view subprocess.run( File "/usr/lib/python3.10/subprocess.py", line 501, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.10/subprocess.py", line 835, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "/usr/lib/python3.10/subprocess.py", line 1606, in _get_handles p2cread = stdin.fileno() AttributeError: 'bytes' object has no attribute 'fileno' --- ProblemType: Bug ApportLog: ERROR: apport (pid 42855) Thu Sep 29 00:30:05 2022: executable was modified after program start, ignoring ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:0:148:22558:2022-09-29 02:33:04.712637295 -0400:2022-09-29 02:33:04.708637298 -0400:/var/crash/_usr_bin_apport-cli.0.crash DistroRelease: Ubuntu 22.10 Package: apport 2.23.0-0ubuntu2 PackageArchitecture: all Tags: kinetic third-party-packages Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1991200/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Our goal should be to merge the entire patch series into kinetic, worst
case, kinetic will not be installable for some users. This means we will
have decent results from people trying that in the next 4 weeks (by Oct
27 the release has been out 1 week).
In the meantime, next week we should push out the security update again.
Then we can take dannf's patches and the first patch here for that SRU
to unblock the other OEM thing which certainly is less controversial.
And on like Oct 27 if we don't have serious regressions do a final SRU
with all the patches.
I'll see what I can do to get those into kinetic so that we get that bit
moving but I'll be travelling or meeting people most of next week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “
[Touch-packages] [Bug 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain
I am a bit confused by the bug report. I think ssh-add is correctly adding the DSA key to the agent, and the fact that running ssh-add again requests the password again is normal and expected. Looks Trusty behaves the same: ubuntu@paride-t:~$ eval $(ssh-agent -s) Agent pid 2406 ubuntu@paride-t:~$ ssh-add Enter passphrase for /home/ubuntu/.ssh/id_rsa: Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) ubuntu@paride-t:~$ ssh-add Enter passphrase for /home/ubuntu/.ssh/id_rsa: Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) So in my view this part of the bug is Invalid. @Rolf maybe you didn't realize as normally when ssh pubkey authentication just works there's no point in re-running ssh-agent? I don't think keychain comes into play in this, as it is just a handy tool to manage the environment variables pointing to the ssh-agent socket. The password prompts are from ssh-add. Then there is the fact that DSA keys have been deprecated from authentication, which is the root of the issue in my opinion. This is in my opinion a Wontfix, as heightening the security baseline requires deprecating older standards. I'm moving this back to Incomplete. ** Changed in: openssh (Ubuntu) Status: Triaged => Incomplete -- 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/1764044 Title: ssh-add asks about passphrases for keys already unlocked in the keychain Status in openssh package in Ubuntu: Incomplete Bug description: In the below example, on the second invocation of ssh-add I should not be prompted to enter the passphrase again after I successfully entered it on the first instance. This used to work fine in trusty i386 setup. $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Starting ssh-agent... Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) $ keychain && ssh-add * keychain 2.8.2 ~ http://www.funtoo.org * Found existing ssh-agent: 25744 Enter passphrase for /home/rolf/.ssh/id_rsa: Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa) Enter passphrase for /home/rolf/.ssh/id_dsa: Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa) gnome-keyring is running: $ ps -ax|grep key 2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components ssh 2078 ?Ssl0:01 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk 6987 ?S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh 17832 pts/2S+ 0:00 grep --color=auto key ssh-agent is running: $ ps aux | grep ssh-agent leggewie 1928 0.0 0.0 15548 340 ?Ss 02:38 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 /usr/lib/gnome-session/run-systemd-session unity-session.target leggewie 6987 0.0 0.0 11304 1484 ?S02:50 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh leggewie 9952 0.0 0.0 11304 320 ?Ss 04:11 0:00 ssh-agent bash leggewie 17850 0.0 0.0 14492 1160 pts/2S+ 06:06 0:00 grep --color=auto ssh-agent $ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992 SSH_AGENT_PID=9952 SSH_AGENT_LAUNCHER=gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I don't have such "there is allways that machine (or bad firmware) that nobody
heard of that will fail" case from my hand but it's frustrated if it becomes a
blocker for fixing the bug for new devices from market.
However, I understand how users feel helpless if a SRU introduces a regression
especially the bootloader.
I think it's worth to mention that, here are many users reported their
certain real cases (as opposed to "there is allways that machine (or bad
firmware) that nobody heard of that will fail") which causes there
system not able to boot.
As we all known, Fedora and Arch linux are using higher compression rate
(for initramfs) to avoid this issue.
I could try the upstream grub as soon as I can and to see if I can
prepare such scheme as what the mailing thread mentioned but I afraid
it'll definitely take times.
Anyway, if we can have some solutions for existing impacted user, then
it'll very helpful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7
[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu
On my machine, I didn't need to modify my firewall to get around the issue; just use a different mechanism to create a hotspot. The app "Wifi Hotspot" (available on Ubuntu Software) worked just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1972790] Re: Can't connect to hotspot created on ubuntu
which firewall did you disable to workaround the issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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
