[Touch-packages] [Bug 1969182] [NEW] package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Have this problem and kernel panic when boot on 5.15.0-25. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grid 2148 F pulseaudio /dev/snd/pcmC0D0p: grid 2148 F...m pulseaudio CasperMD5CheckResult: fail Date: Fri Apr 15 08:32:07 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-04-04 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20RA002SRT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vg_core-sys ro quite splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET33W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RA002SRT dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14: dmi.product.family: ThinkPad E14 dmi.product.name: 20RA002SRT dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14 dmi.product.version: ThinkPad E14 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1969182 Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Have this problem and kernel panic when boot on 5.15.0-25. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: grid 2148 F pulseaudio /dev/snd/pcmC0D0p: grid 2148 F...m pulseaudio CasperMD5CheckResult: fail Date: Fri Apr 15 08:32:07 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-04-04 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20RA002SRT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/vg_core-sys ro quite splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.15.0-25-generic 5.15.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET33W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RA002SRT dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR16ET33W(1.19):bd09/15/2021:br1.19:efr1.13:svnLENOVO:pn20RA002SRT:pvrThinkPadE14:rvnLENOVO:rn20RA002SRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:
[Touch-packages] [Bug 1837937] Re: CRASH
I will mark it Fixed. ** Changed in: linux (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Touch-packages] [Bug 1837937] Re: CRASH
I'm not sure this was fixed upstream yet. Though I'm sure it has. I moved on to Jammy :P -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Touch-packages] [Bug 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
I don't really know what's going on with the agent, I just assumed it crashes. I found out that the agent stops working only when the repository is cloned, when connected to the server by key, it works well. The problem concerns only the arm platform, because I don’t see this on x86_64. -- 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
I've uploaded a fix to the jammy unapproved queue, but it's a rather large patch and I think it should be reviewed by another member of the release team. ** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Fix Committed Bug description: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 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: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1969115] Re: Update glib to 2.72.1
** Changed in: glib2.0 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1969115 Title: Update glib to 2.72.1 Status in glib2.0 package in Ubuntu: In Progress Bug description: Impact -- glib has a new bugfix release as part of their GNOME 42 series https://gitlab.gnome.org/GNOME/glib/-/blob/glib-2-72/NEWS Test Case - Ensure that the autopkgtests complete successfully. The autopkgtests run installed tests. Where Problems Could Occur -- This is believed to be part of the GNOME micro-release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1969115/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-image (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Changed in: openssl (Ubuntu) Importance: High => Critical ** Changed in: openssl (Ubuntu) Status: Confirmed => In Progress ** Changed in: openssl (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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: In Progress Bug description: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 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: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
It worked! I must have flashed the wrong image, Thank you so much for taking the time! And Thanks to everyone that worked on this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
** Changed in: openssh (Ubuntu) Status: New => 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
Also: you mention that "ssh agent crashes". What do you see exactly to be able to tell it's a crash and not some other authentication or key handling issue? -- 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
Hello testpi and thanks for this bug report. Can you reproduce this issue from a fresh install on the Raspberry, and attempting a simple ssh login instead of a git clone? Something on these lines: - ssh-keygen cp ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys killall ssh-agent || true eval $(ssh-agent) ssh-add ssh localhost - I'll try to reproduce this issue myself but I don't have access to a Rpi4 at the moment, but I should have soon. As we're waiting for more information here I'm marking this report as Incomplete for now. -- 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/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Tags added: fr-2255 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Confirmed Bug description: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 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: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1959475] Re: "machinectl shell" connections immediately terminated
Please consider backporting for Focal (20.04) at least. The backport is trivial and applies cleanly as-is except for patch offsets. Might be wise to test some other combinations though. For example hosts without this commit, running nspawn containers with it. -- 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/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Confirmed Bug description: The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
Hi! Could you run the follwoing command on your server certificate? openssl x509 -in $SERVER_CRT -text | grep -i algorithm With the new OpenSSL version, older certificates with SHA1 digests are now invalid by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8
** Tags added: rls-jj-incoming ** Changed in: openssl (Ubuntu) Importance: Undecided => High ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: Confirmed Bug description: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 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: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997/+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 1959475] Re: "machinectl shell" connections immediately terminated
Just tested, and can confirm backporting e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 to focal's systemd fixes the segfaults when using machinectl shell on a Jammy host trying to start a shell in a Focal nspawn container. -- 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/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Confirmed Bug description: The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1959475] Re: "machinectl shell" connections immediately terminated
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Confirmed Bug description: The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
@noahod I've just tried this with the current https://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/jammy-preinstalled-server-arm64+raspi.img.xz image (downloaded today) and with just your growpart config (I didn't try the resize_rootfs key), the card booted without resizing the rootfs: ubuntu@ubuntu:~$ df -h / Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 3.3G 2.2G 964M 70% / ubuntu@ubuntu:~$ sudo fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc34fdafd Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 * 2048 526335 524288 256M c W95 FAT32 (LBA) /dev/mmcblk0p2 526336 7656787 7130452 3.4G 83 Linux Could you have a go with just the growpart config? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
This bug was fixed in the package six - 1.16.0-3ubuntu1 --- six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 ** Changed in: six (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 six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Released Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
Any chance this will get fixed in focal? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Confirmed Status in evolution-data-server source package in Focal: Confirmed Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy
This bug was fixed in the package pyyaml - 5.4.1-1ubuntu1 --- pyyaml (5.4.1-1ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:09:36 +0100 ** Changed in: pyyaml (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 six in Ubuntu. https://bugs.launchpad.net/bugs/1958720 Title: python3-yaml and python3-six are not co-installable with python-is- python2 in jammy Status in pyyaml package in Ubuntu: Fix Released Status in six package in Ubuntu: Fix Committed Bug description: The packages python3-yaml and python-is-python2 are not co-installable in jammy and I believe they should be. This currently prevents me from upgrading one of my machines from focal to jammy. Further analysis with the help of Stefano Rivera revealed that what- is-python no longer produces a python-is-python2 package and the changelog hints at that being intentional. Jammy still has a python2 package, though. python3-yaml in jammy breaks on python (<2.7.18). The python-is- python2 package in focal is version 2.7.17-4 and in impish it is 2.7.18-9 and thus will be forcefully removed when going to jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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 1969115] [NEW] Update glib to 2.72.1
Public bug reported: Impact -- glib has a new bugfix release as part of their GNOME 42 series https://gitlab.gnome.org/GNOME/glib/-/blob/glib-2-72/NEWS Test Case - Ensure that the autopkgtests complete successfully. The autopkgtests run installed tests. Where Problems Could Occur -- This is believed to be part of the GNOME micro-release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1969115 Title: Update glib to 2.72.1 Status in glib2.0 package in Ubuntu: New Bug description: Impact -- glib has a new bugfix release as part of their GNOME 42 series https://gitlab.gnome.org/GNOME/glib/-/blob/glib-2-72/NEWS Test Case - Ensure that the autopkgtests complete successfully. The autopkgtests run installed tests. Where Problems Could Occur -- This is believed to be part of the GNOME micro-release exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1969115/+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 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
** Changed in: webkit2gtk (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: In Progress Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+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 1968922] Re: libnss3 is affected by CVE-2022-22747
Thanks, I've added it to our tracker now. ** Information type changed from Private Security to Public Security ** Changed in: nss (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1968922 Title: libnss3 is affected by CVE-2022-22747 Status in nss package in Ubuntu: Confirmed Bug description: libnss3 2:3.49.1-1ubuntu1.6 is affected by CVE-2022-22747. The entry for this CVE in the Ubuntu CVE tracker does not list this source package. This CVE was fixed in Debian 11 on January 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1968922/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
we use gnome not kde ii gnome-desktop3-data42.0-1ubuntu1 all Common files for GNOME desktop apps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1968996] Re: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound
Note, issue was resolved by updating kernel to Linux zlegion 5.17.3-051703-generic #202204131853 SMP PREEMPT Wed Apr 13 18:57:08 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux using "mainline" tool -- 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/1968996 Title: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Not much to say, just noticed that there is a crackling sound when playing youtube videos. I first thought it was the Q5 AMP it self, but I connected it to a different device and it works just fine. I tried other audio devices on the laptop and none seemed to have the same problem. Not sure what's the cause but everything I tried so far hasn't fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Apr 14 09:08:43 2022 InstallationDate: Installed on 2021-10-21 (174 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AMP successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2020 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrEUCN28WW:bd10/20/2020:br1.28:efr1.28:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968996/+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 1968997] [NEW] openssl has catastrophic issues when locale set to TR_UTF8
Public bug reported: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM) fips yes n/a NIST-certified core packages fips-updates yes n/a NIST-certified core packages with priority security updates livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: il...@fastmail.fm Subscription: il...@fastmail.fm If Ubuntu 22 ships with current configuration, entire TR will suffer considering you can't find http:// downloads anymore. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssl 3.0.2-0ubuntu1 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: unknown Date: Thu Apr 14 10:21:09 2022 InstallationDate: Installed on 2021-12-29 (105 days ago) InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: openssl UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1968997 Title: openssl has catastrophic issues when locale set to TR_UTF8 Status in openssl package in Ubuntu: New Bug description: I noticed this when I checked "ua status". It alerted me that I should check my openssl configuration. "ua status Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy Cannot verify certificate of server Please check your openssl configuration." I also figured wget doesn't work with https:// URLs at all. On web I found: https://github.com/openssl/openssl/issues/18039 So I changed locale to C_UTF-8 #locale LANG=tr_TR.UTF-8 LANGUAGE= LC_CTYPE="tr_TR.UTF-8" LC_NUMERIC=tr_TR.UTF-8 LC_TIME=tr_TR.UTF-8 LC_COLLATE="tr_TR.UTF-8" LC_MONETARY=tr_TR.UTF-8 LC_MESSAGES="tr_TR.UTF-8" LC_PAPER=tr_TR.UTF-8 LC_NAME=tr_TR.UTF-8 LC_ADDRESS=tr_TR.UTF-8 LC_TELEPHONE=tr_TR.UTF-8 LC_MEASUREMENT=tr_TR.UTF-8 LC_IDENTIFICATION=tr_TR.UTF-8 LC_ALL= casaba@ship-macbook:/backups$ sudo locale-gen c ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8 ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8 ca_ES ca_FR ce_RU crh_UA cv_RU ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 Generating locales (this might take a while)... C.UTF-8... done Generation complete. casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8 casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8 Now the result is (after logout/login) ua status SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis yes n/a Security compliance and audit tools esm-infra
[Touch-packages] [Bug 1968996] [NEW] [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound
Public bug reported: Not much to say, just noticed that there is a crackling sound when playing youtube videos. I first thought it was the Q5 AMP it self, but I connected it to a different device and it works just fine. I tried other audio devices on the laptop and none seemed to have the same problem. Not sure what's the cause but everything I tried so far hasn't fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Apr 14 09:08:43 2022 InstallationDate: Installed on 2021-10-21 (174 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AMP successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2020 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrEUCN28WW:bd10/20/2020:br1.28:efr1.28:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1968996 Title: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Not much to say, just noticed that there is a crackling sound when playing youtube videos. I first thought it was the Q5 AMP it self, but I connected it to a different device and it works just fine. I tried other audio devices on the laptop and none seemed to have the same problem. Not sure what's the cause but everything I tried so far hasn't fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Thu Apr 14 09:08:43 2022 InstallationDate: Installed on 2021-10-21 (174 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AMP successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - SMSL Q5 AMP, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2020 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrEUCN28WW:bd10/20/2020:br1.28:efr1.28:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968996/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
** Tags added: originate-from-1968990
--
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/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Fix Committed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Status in systemd source package in Impish:
Fix Released
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1967038] Re: Add mic mute key for HP Elite x360 series
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1967038 Title: Add mic mute key for HP Elite x360 series Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: Upstream commit: https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e [Impact] * User can't use mic mute key if they buy Elite x360 G9 series. [Test Plan] * Test mic mute key on Elite x360 G9 series. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1967038/+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
