[Touch-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
I'm using VirtualBox to test upcoming Ubuntu versions using the exact same config and packages that will later be used on several physical machines. So it's pretty important to me to install the third-party packages in VMs as well. But yes, I can live with the workaround for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
Dropped to Medium because I don't think there's any useful reason to tick the third party software option in virtual machines. You're not missing out on anything that a virtual machine could otherwise do. ** Changed in: gnome-shell (Ubuntu) Importance: High => Medium ** Changed in: gstreamer-vaapi (Ubuntu) Importance: High => Medium ** Changed in: libx11 (Ubuntu) Importance: High => Medium ** Changed in: libxcb (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1991491] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert
This bug report shows that you were doing a release upgrade from 20.04 to 22.04 on a system which has a separate /boot partition, 461MiB in size with 81MiB free space; and the system ran out of room while trying to write out the initramfs for the new kernel. 461MiB is unfortunately on the small size now for /boot partitions given the size of recent kernels / initramfses. Were you using update-manager (the recommended interface, on desktop systems) to do the upgrade? It includes checks to ensure /boot is large enough before committing to the upgrade, so we would want to know if those checks were inadequate here. ** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Changed in: ubuntu-release-upgrader (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/1991491 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: I undated from 20.04.5 to 22.04.1 and this is what the update ended with. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 2 19:06:19 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-03 (1946 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1991491/+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 1991566] Re: Package creates a socket file for all addresses of all families, even when bind to a single address
*** This bug is a duplicate of bug 1991592 *** https://bugs.launchpad.net/bugs/1991592 ** This bug has been marked a duplicate of bug 1991592 openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config -- 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/1991566 Title: Package creates a socket file for all addresses of all families, even when bind to a single address Status in openssh package in Ubuntu: Incomplete Bug description: I am configuring OpenSSH to listen only on ipv4 and only on one interface and one address, with nginx listening on 22 on the other interface, and families. In order to make this happen, I had to "break" the socket file installed by the package at: /etc/systemd/system/sockets.target.wants/ssh.socket To read as follows: [Unit] Description=OpenBSD Secure Shell server socket Before=ssh.service Conflicts=ssh.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run #[Socket] #ListenStream=22 #Accept=yes #[Install] #WantedBy=sockets.target (Commented out the lines that installed the socket) Then a daemon-reload, and restart of ngxinx, and all components of the solution are working as required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket] ProcVersionSignature: Uname: Linux 5.15.53-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 16:36:37 2022 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+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 1991477] Re: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
The error in your log is: Processing triggers for linux-image-5.15.0-48-generic (5.15.0-48.54) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic cpio: write error: No space left on device E: mkinitramfs failure cpio 2 update-initramfs: failed for /boot/initrd.img-5.15.0-48-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 This is not a bug in initramfs-tools, per se; initramfs-tools can't make your root partition larger than it is. And you do not have a separate /boot partition, so this is not a bug of an installer setting up /boot to be an inappropriate size. The only thing that can be done in this circumstance is for you to free up some space on your root partition and try to resume the upgrade with 'apt -f install'. Were you running apt dist-upgrade manually to go from focal to jammy, or were you using do-release-upgrade, the recommended tool? The release upgrader includes some checks to ensure sufficient free space before committing to the upgrade, so we would want to know if those are inadequate. ** Package changed: initramfs-tools (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Changed in: ubuntu-release-upgrader (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/1991477 Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: Trying to upgrade to the latest image. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 2 01:45 seq crw-rw 1 root audio 116, 33 Oct 2 01:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Sun Oct 2 01:51:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=db153994-91fe-426f-bd88-f751e07f97f2 ro console=tty1 console=ttyS0 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1991477/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
Looks like a bug in libx11 or libxcb because I don't think it's meant to be possible for XOpenDisplay() to hang. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+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 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
I think the problem is gnome-shell waiting for this command (which never finishes): /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l /usr/bin/gnome-shell because it's waiting for an X server (which does exist as Xwayland): #0 0x7f76ea710ec4 in __GI___poll (fds=0x7ffed6d30280, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f76e9c78e23 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f76e9c7c522 in xcb_connect_to_fd () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f76e9c7cedc in xcb_connect_to_display_with_auth_info () from /lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7f76e9e57eea in _XConnectXCB () from /lib/x86_64-linux-gnu/libX11.so.6 #5 0x7f76e9e47d17 in XOpenDisplay () from /lib/x86_64-linux-gnu/libX11.so.6 #6 0x7f76ea37c537 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so #7 0x7f76ea353d28 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so #8 0x7f76ea3181f7 in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so #9 0x7f76eaae85c5 in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #10 0x7f76eaaef84d in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #11 0x7f76eaaf08f4 in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #12 0x7f76eaaf19b8 in _gst_plugin_loader_client_run () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 #13 0x55c6eaeb61dc in ?? () #14 0x7f76ea623510 in __libc_start_call_main (main=main@entry=0x55c6eaeb6120, argc=argc@entry=3, argv=argv@entry=0x7ffed6d30c98) at ../sysdeps/nptl/libc_start_call_main.h:58 #15 0x7f76ea6235c9 in __libc_start_main_impl (main=0x55c6eaeb6120, argc=3, argv=0x7ffed6d30c98, init=, fini=, rtld_fini=, stack_end=0x7ffed6d30c88) at ../csu/libc-start.c:381 #16 0x55c6eaeb6235 in _start () ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gstreamer1.0 (Ubuntu) ** Also affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Changed in: libx11 (Ubuntu) Status: New => Confirmed ** Changed in: libx11 (Ubuntu) Importance: Undecided => High ** Also affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Changed in: libxcb (Ubuntu) Status: New => Confirmed ** Changed in: libxcb (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBo
[Touch-packages] [Bug 1899103] Re: libpam-cap causes PAM applications to crash
Had not heard about this specifically before. Some bug fixes to pam_cap.so found by static analysis: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=954a5ce4fdf195e062909f2c921d8f915d2905b9 https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=552db8f4116df3fad4e4ebf90a9a05a77b9486fd Perhaps they address this problem? The more recent of these two appeared in libcap-2.50. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1899103 Title: libpam-cap causes PAM applications to crash Status in libcap2 package in Ubuntu: Confirmed Bug description: Install ocserv and setup for PAM authentication. On second connection, ocserv crashes due to a double free in PAM. Repro steps: 1. Create Dockerfile that installs ocserv + libpam-cap ``` FROM ubuntu:20.04 RUN apt update && apt install -y ocserv libpam-cap && apt autoremove && apt clean COPY server-cert.pem /etc/ssl/ocserv_test.cert COPY server-key.pem /etc/ssl/ocserv_test.key COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem COPY ocserv.conf /etc/ocserv/ocserv.conf RUN useradd test RUN echo "test\ntest" | passwd test ENV MALLOC_CHECK_=3 CMD ocserv -f -d 1 ``` 2. Build container: ``` sudo docker build -t ocserv:20.04 . ``` 3. Launch container: ``` docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun --cap-add net_admin ocserv:20.04 ``` 4. From another console, connect / disconnect: ``` while true; do echo test | openconnect https://localhost -u test --passwd-on-stdin --servercert pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 && pkill openconnect && sleep 2;done ``` 5. ocserv crashes: free(): invalid pointer ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed ocserv[8]: main: main.c:1179: error in command from sec-mod ocserv[8]: main: termination request received; waiting for children to die For more details see: https://gitlab.com/openconnect/ocserv/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+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 1991436] Re: "invalid argument" error from logger command when passing messages via STDIN
I cannot reproduce this on jammy. $ echo "some message" | logger -p auth.info --id="$$" $ echo $? 0 $ (using auth.info instead of local0.info because I have the former logged to a log file and the latter not). ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1991436 Title: "invalid argument" error from logger command when passing messages via STDIN Status in util-linux package in Ubuntu: Incomplete Bug description: When invoking the `logger` command on Ubuntu Jammy (bsdutils 2.37.2) with explicit PID and passing messages via STDIN ``` echo "some message" | logger -p local0.info --id="$$" ``` the command produces the following error instead of sending the message to syslog: > logger: send message failed: Invalid argument The error does not appear when the message is passed as an argument: ``` logger -p local0.info --id="$$" "some message" # this works! ``` When using process substitution the error only appears for the first log message: ``` exec > >(logger -p local0.info --id="$$") echo "first message" # throws error, message not logged echo "second message" # no error, message logged correctly ``` The issue does not exist in older versions (e.g. Ubuntu Xenial, bsdutils 2.27.1). Workaround: Omit `--id` and include the PID in a tag. ``` echo "some message" | logger -p local0.info -t "foo[$$]" ``` Expected Behavior - All messages passed via STDIN should be sent to syslog without throwing an error. OS Release -- Description: Ubuntu 22.04 LTS Release: 22.04 Package Version --- bsdutils: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1991436/+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 error message about not finding executables
Also, as this is an rpi4, is this running the armhf port or the arm64 port? (32 or 64 bit) -- 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 error message about not finding executables 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 1971901] Re: dlltool uses non-unique temp filenames
> Changed in binutils-mingw-w64 (Ubuntu): > status: Triaged → Fix Released not fixed in Kinetic yet either; it would be if rebuilt with the binutils-source there now, but https://launchpad.net/ubuntu/+source/binutils-mingw-w64/9build1 built on 2022-04-26 is before Mattias brought in PR2885 on https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 Unless you marked binutils-mingw-w64 as Fix Released in based on something I didn't find... -- 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: Fix Released Status in binutils-mingw-w64 package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Committed Status in binutils-mingw-w64 source package in Jammy: Triaged 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 1991324] Re: Initramfs-tools: iSCSI boot resulting in modprobe not found error message
> Loading, please wait... > /scripts/init-top/udev: line 24: /lib/systemd/systemd-udevd: not found > Begin: Loading essential drivers ... /init: line 150: modprobe: not found > /init: line 150: modprobe: not found So basically, none of the binaries are in the initramfs, or else they're in the initramfs but not on the PATH. How was this initramfs generated? Please attach to this bug report. ** Summary changed: - Initramfs-tools: iSCSI boot resulting in modprobe not found error message + Initramfs-tools: iSCSI boot resulting in error message about not finding executables -- 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 error message about not finding executables 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 1991283] Re: "sshd -i" breaks due to socket activation
** Changed in: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1991283 Title: "sshd -i" breaks due to socket activation Status in openssh package in Ubuntu: Fix Committed 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 1990783] Re: distorted mouse pointer under Wayland in Kinetic
** Tags added: kinetic ** Tags added: wayland wayland-session ** Tags added: radeon ** Summary changed: - distorted mouse pointer under Wayland in Kinetic + [radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10 ** No longer affects: wayland (Ubuntu) ** Bug watch added: KDE Bug Tracking System #456306 https://bugs.kde.org/show_bug.cgi?id=456306 ** Also affects: kdebase-workspace via https://bugs.kde.org/show_bug.cgi?id=456306 Importance: Unknown Status: Unknown ** Tags added: cursor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1990783 Title: [radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10 Status in KDE Base Workspace: Unknown Status in kwin package in Ubuntu: New Bug description: After upgrading to Kubuntu 22.10 Kinetic dev. I found mouse pointer distorted. Please, look at attached screenshot. Under X session mouse pointer looks as it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1990783/+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 1971901] Re: dlltool uses non-unique temp filenames
** Changed in: binutils-mingw-w64 (Ubuntu) Status: Confirmed => Triaged ** Changed in: binutils-mingw-w64 (Ubuntu) Importance: Undecided => Low ** Changed in: binutils (Ubuntu) Status: Confirmed => Fix Released ** Changed in: binutils-mingw-w64 (Ubuntu) Status: Triaged => Fix Released ** Also affects: binutils (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: binutils-mingw-w64 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: binutils (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: binutils-mingw-w64 (Ubuntu Jammy) Status: New => Triaged ** Changed in: binutils-mingw-w64 (Ubuntu Jammy) Importance: Undecided => Low -- 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: Fix Released Status in binutils-mingw-w64 package in Ubuntu: Fix Released Status in binutils source package in Jammy: Fix Committed Status in binutils-mingw-w64 source package in Jammy: Triaged 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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
** Tags added: foundations-todo -- 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 1871392] Re: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'
And the bug report shows this crash happened with python3-apt 1.9.10, which was a prerelease version of python3-apt before Ubuntu 20.04 LTS came out. So I'm surprised another user has just marked this bug as affecting them, causing the report to bubble up to the top. We would need some concrete evidence that this failure happens with released versions of the software to take further action here. ** Changed in: python-apt (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1871392 Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' Status in python-apt package in Ubuntu: Incomplete Bug description: System locked up ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Aptdaemon: Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 09:16:14 2020 ExecutablePath: /usr/bin/update-manager InstallationDate: Installed on 2020-03-01 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map'] PythonDetails: N/A SourcePackage: update-manager Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' UpgradeStatus: Upgraded to focal on 2020-03-25 (12 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871392/+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 1871392] Re: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'
The stacktrace points to: File "/usr/lib/python3/dist-packages/apt/package.py", line 541, in _records if not self.package._pcache._records.lookup(self._cand.file_list[0]): AttributeError: 'NoneType' object has no attribute 'lookup' So, reassigning. ** Package changed: update-manager (Ubuntu) => python-apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1871392 Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' Status in python-apt package in Ubuntu: Incomplete Bug description: System locked up ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Aptdaemon: Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 09:16:14 2020 ExecutablePath: /usr/bin/update-manager InstallationDate: Installed on 2020-03-01 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map'] PythonDetails: N/A SourcePackage: update-manager Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' UpgradeStatus: Upgraded to focal on 2020-03-25 (12 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871392/+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
** Changed in: grub2-signed (Ubuntu)
Status: Confirmed => Triaged
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Won't Fix
--
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:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
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 “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my cas
[Touch-packages] [Bug 1871392] [NEW] update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup'
You have been subscribed to a public bug: System locked up ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Aptdaemon: Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 09:16:14 2020 ExecutablePath: /usr/bin/update-manager InstallationDate: Installed on 2020-03-01 (36 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map'] PythonDetails: N/A SourcePackage: update-manager Title: update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' UpgradeStatus: Upgraded to focal on 2020-03-25 (12 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Affects: python-apt (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-crash focal -- update-manager crashed with AttributeError in _records(): 'NoneType' object has no attribute 'lookup' https://bugs.launchpad.net/bugs/1871392 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic
** Changed in: openssh (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 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: Fix Committed 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:pvrS
[Touch-packages] [Bug 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config
** Changed in: openssh (Ubuntu) Status: Confirmed => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => High -- 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/1991592 Title: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config Status in openssh package in Ubuntu: Triaged Bug description: A criticism of the existing sshd socket activation implementation is that Port/ListenAddress options are migrated on a one-time basis at package upgrade time, and afterwards users get the surprising behavior that Port/ListenAddress settings added to sshd_config are ignored. A systemd generator could be used to change the ssh socket unit configuration on boot, and on each change of /etc/ssh/sshd_config. Sample implementation from Dimitri: ssh.socket: [Unit] Wants=sshd-config.path # # Note the below defaults are cleared and overriden by #/lib/systemd/system-generators/sshd-generator # based on the sshd config from the sshd -T output # ListenStream=[::]:22 ListenStream=0.0.0.0:22 diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path new file mode 100644 index 0..cfa9674a3 --- /dev/null +++ b/systemd/sshd-config.path @@ -0,0 +1,4 @@ +[Unit] +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run +[Path] +PathChanged=/etc/ssh/sshd_config diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service new file mode 100644 index 0..b009ea52c --- /dev/null +++ b/systemd/sshd-config.service @@ -0,0 +1,5 @@ +[Unit] +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in + +[Service] +ExecStart=/bin/systemctl daemon-reload diff --git a/systemd/sshd-generator b/systemd/sshd-generator new file mode 100755 index 0..72c6aac04 --- /dev/null +++ b/systemd/sshd-generator @@ -0,0 +1,10 @@ +#!/bin/sh +set -eu +mkdir -p /run/sshd +sshd -t +mkdir -p $1/ssh.socket.d +target="$1/ssh.socket.d/ssh-listen.conf" +echo '[Socket]' > $target +echo 'ListenStream=' >> $target +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target +rmdir --ignore-fail-on-non-empty /run/sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+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 1991592] Re: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New => Confirmed -- 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/1991592 Title: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config Status in openssh package in Ubuntu: Triaged Bug description: A criticism of the existing sshd socket activation implementation is that Port/ListenAddress options are migrated on a one-time basis at package upgrade time, and afterwards users get the surprising behavior that Port/ListenAddress settings added to sshd_config are ignored. A systemd generator could be used to change the ssh socket unit configuration on boot, and on each change of /etc/ssh/sshd_config. Sample implementation from Dimitri: ssh.socket: [Unit] Wants=sshd-config.path # # Note the below defaults are cleared and overriden by #/lib/systemd/system-generators/sshd-generator # based on the sshd config from the sshd -T output # ListenStream=[::]:22 ListenStream=0.0.0.0:22 diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path new file mode 100644 index 0..cfa9674a3 --- /dev/null +++ b/systemd/sshd-config.path @@ -0,0 +1,4 @@ +[Unit] +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run +[Path] +PathChanged=/etc/ssh/sshd_config diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service new file mode 100644 index 0..b009ea52c --- /dev/null +++ b/systemd/sshd-config.service @@ -0,0 +1,5 @@ +[Unit] +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in + +[Service] +ExecStart=/bin/systemctl daemon-reload diff --git a/systemd/sshd-generator b/systemd/sshd-generator new file mode 100755 index 0..72c6aac04 --- /dev/null +++ b/systemd/sshd-generator @@ -0,0 +1,10 @@ +#!/bin/sh +set -eu +mkdir -p /run/sshd +sshd -t +mkdir -p $1/ssh.socket.d +target="$1/ssh.socket.d/ssh-listen.conf" +echo '[Socket]' > $target +echo 'ListenStream=' >> $target +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target +rmdir --ignore-fail-on-non-empty /run/sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+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 1990863] Re: conversion from sshd service to socket is too bumpy
*** This bug is a duplicate of bug 1991592 *** https://bugs.launchpad.net/bugs/1991592 ** This bug has been marked a duplicate of bug 1991592 openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config -- 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/1990863 Title: conversion from sshd service to socket is too bumpy Status in openssh package in Ubuntu: New Bug description: During upgrade from Jammy to Kinetic, I get asked what to do because my sshd_config has been modified. I say to do a 3-way merge. It says 3-way merge fails. I shrug, figure I'll just restore my customizations with Ansible after the upgrade like I always do, and tell it to use the vendor version of the file. This removes my custom Port settings, so they are not migrated over to the ssh.socket settings like https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation- ubuntu-22-10-and-later/30189 says they would be. I subsequently run my Ansible which restores the customizations and enables the ssh service, but now ssh.service and ssh.socket are enabled at the same time, sshd isn't listening on my specified ports, and everything is a mess. I've never used socket-based activation before and have no idea how to configure it so now I have to go reading man pages, Googling all over the place, and generally struggle to figure out what the heck is going wrong. I don't know what the right answer is here, but I really feel like some effort needs to be put into figuring out a smoother transition for people who are upgrading to Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 11:41:58 2022 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: openssh UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+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 1991592] [NEW] openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config
Public bug reported: A criticism of the existing sshd socket activation implementation is that Port/ListenAddress options are migrated on a one-time basis at package upgrade time, and afterwards users get the surprising behavior that Port/ListenAddress settings added to sshd_config are ignored. A systemd generator could be used to change the ssh socket unit configuration on boot, and on each change of /etc/ssh/sshd_config. Sample implementation from Dimitri: ssh.socket: [Unit] Wants=sshd-config.path # # Note the below defaults are cleared and overriden by #/lib/systemd/system-generators/sshd-generator # based on the sshd config from the sshd -T output # ListenStream=[::]:22 ListenStream=0.0.0.0:22 diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path new file mode 100644 index 0..cfa9674a3 --- /dev/null +++ b/systemd/sshd-config.path @@ -0,0 +1,4 @@ +[Unit] +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run +[Path] +PathChanged=/etc/ssh/sshd_config diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service new file mode 100644 index 0..b009ea52c --- /dev/null +++ b/systemd/sshd-config.service @@ -0,0 +1,5 @@ +[Unit] +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in + +[Service] +ExecStart=/bin/systemctl daemon-reload diff --git a/systemd/sshd-generator b/systemd/sshd-generator new file mode 100755 index 0..72c6aac04 --- /dev/null +++ b/systemd/sshd-generator @@ -0,0 +1,10 @@ +#!/bin/sh +set -eu +mkdir -p /run/sshd +sshd -t +mkdir -p $1/ssh.socket.d +target="$1/ssh.socket.d/ssh-listen.conf" +echo '[Socket]' > $target +echo 'ListenStream=' >> $target +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target +rmdir --ignore-fail-on-non-empty /run/sshd ** Affects: openssh (Ubuntu) Importance: High Status: Triaged -- 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/1991592 Title: openssh-server should ship a systemd generator to generate ssh socket port configuration from sshd_config Status in openssh package in Ubuntu: Triaged Bug description: A criticism of the existing sshd socket activation implementation is that Port/ListenAddress options are migrated on a one-time basis at package upgrade time, and afterwards users get the surprising behavior that Port/ListenAddress settings added to sshd_config are ignored. A systemd generator could be used to change the ssh socket unit configuration on boot, and on each change of /etc/ssh/sshd_config. Sample implementation from Dimitri: ssh.socket: [Unit] Wants=sshd-config.path # # Note the below defaults are cleared and overriden by #/lib/systemd/system-generators/sshd-generator # based on the sshd config from the sshd -T output # ListenStream=[::]:22 ListenStream=0.0.0.0:22 diff --git a/systemd/sshd-config.path b/systemd/sshd-config.path new file mode 100644 index 0..cfa9674a3 --- /dev/null +++ b/systemd/sshd-config.path @@ -0,0 +1,4 @@ +[Unit] +ConditionPathExists=!/etc/ssh/sshd_not_to_be_run +[Path] +PathChanged=/etc/ssh/sshd_config diff --git a/systemd/sshd-config.service b/systemd/sshd-config.service new file mode 100644 index 0..b009ea52c --- /dev/null +++ b/systemd/sshd-config.service @@ -0,0 +1,5 @@ +[Unit] +Description=Regenerate ssh.socket.d/ssh-listen.conf drop-in + +[Service] +ExecStart=/bin/systemctl daemon-reload diff --git a/systemd/sshd-generator b/systemd/sshd-generator new file mode 100755 index 0..72c6aac04 --- /dev/null +++ b/systemd/sshd-generator @@ -0,0 +1,10 @@ +#!/bin/sh +set -eu +mkdir -p /run/sshd +sshd -t +mkdir -p $1/ssh.socket.d +target="$1/ssh.socket.d/ssh-listen.conf" +echo '[Socket]' > $target +echo 'ListenStream=' >> $target +sshd -T | sed -n 's/^listenaddress /ListenStream=/p' >> $target +rmdir --ignore-fail-on-non-empty /run/sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991592/+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 1989309] Re: [FFe] new apparmor features for 3.0.7
I updated the description and PPAs to reflect what we are hoping to land: patches on top of 3.0.7 instead of a new 3.1.1 release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989309 Title: [FFe] new apparmor features for 3.0.7 Status in apparmor package in Ubuntu: Incomplete Bug description: We propose two new features for 3.0.7 Apparmor: 1. parser support for user namespace mediation. Since the last kernel update with commit https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=30bce26855c9171f8dee74d93308fd506730c914 Ubuntu 22.10 mediates user namespaces which allows for confined applications to have unprivileged user namespace creation, instead of disabling it completely. If we want applications to have this ability, then we need to add support on the parser, which is a feature we are introducing. Bug 1990064 is an example caused by this. 2. userspace support for posix message queue mediation Kernel also has POSIX message queue mediation with commit https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master- next&id=44f28e2ccee2000c7da971876dd003d38a8232d8 which indicates that if admins want to allow legitimate use of POSIX message queues, then they will need the support of userspace tools. We are also adding a fix for Bug 1990692 which will make the AppArmor profiles for samba to be up to date with upstream. TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[1] for AppArmor and the extensive QA Regression Tests[2] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~georgiag/+archive/ubuntu/apparmor-kinetic-ffe, build logs can be found on Launchpad at: https://launchpad.net/~georgiag/+archive/ubuntu/test2/+build/24518253 for amd64 DEBDIFF The debdiff can be found in the PPA: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5620824/+files/apparmor-3.0.7-1ubuntu2-apt-upgrade.log INSTALL / UPGRADE LOG The apt upgrade log is attached in [1] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+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 1989309] Re: [FFe] new apparmor features for 3.0.7
** Attachment added: "apparmor-3.0.7-1ubuntu2-apt-upgrade.log" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5620824/+files/apparmor-3.0.7-1ubuntu2-apt-upgrade.log ** Description changed: - AppArmor 3.1.1 is the latest upstream version of the apparmor userspace - tooling. + We propose two new features for 3.0.7 Apparmor: - This includes a large number of bug fixes since the 3.0.7 release which - is currently in kinetic, as well as various cleanups and optimisations - to the different tools to improve performance and maintainability. + 1. parser support for user namespace mediation. - The full ChangeLog can be seen at [1]. Upstream does not provide a - ChangeLog file, however I have generated one based on the git commit - history of apparmor from the 3.0.7 tag to 3.1.1 as: + Since the last kernel update with commit https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=30bce26855c9171f8dee74d93308fd506730c914 + Ubuntu 22.10 mediates user namespaces which allows for confined applications to have unprivileged user namespace creation, instead of disabling it completely. + If we want applications to have this ability, then we need to add support on the parser, which is a feature we are introducing. Bug 1990064 is an example caused by this. - $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git- - log.log + 2. userspace support for posix message queue mediation - This can be seen in the attached file - https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- - log.log + Kernel also has POSIX message queue mediation with commit + https://git.launchpad.net/~ubuntu- + kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master- + next&id=44f28e2ccee2000c7da971876dd003d38a8232d8 which indicates that if + admins want to allow legitimate use of POSIX message queues, then they + will need the support of userspace tools. + + We are also adding a fix for Bug 1990692 which will make the AppArmor + profiles for samba to be up to date with upstream. TESTING This has been extensively tested by the security team - this includes - following the documented Ubuntu merges test plan[2] for AppArmor and the - extensive QA Regression Tests[3] for AppArmor as well. This ensures that + following the documented Ubuntu merges test plan[1] for AppArmor and the + extensive QA Regression Tests[2] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS - This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on + This is currently uploaded to https://launchpad.net/~georgiag/+archive/ubuntu/apparmor-kinetic-ffe, build logs can be found on Launchpad at: - https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc + https://launchpad.net/~georgiag/+archive/ubuntu/test2/+build/24518253 for amd64 DEBDIFF - The debdiff can be found in the PPA: - https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz - + The debdiff can be found in the PPA: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5620824/+files/apparmor-3.0.7-1ubuntu2-apt-upgrade.log INSTALL / UPGRADE LOG The apt upgrade log is attached in - https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- - upgrade.log - [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 - [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor - [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py + [1] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor + [2] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989309 Title: [FFe] new apparmor features for 3.0.7 Status in apparmor package in Ubuntu: Incomplete Bug description: We propose two new features for 3.0.7 Apparmor: 1. parser support for user namespace mediation. Since the last kernel update with commit https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=30bce26855c9171f8dee74d93308fd506730c914 Ubuntu 22.10 mediates user namespaces which allows for confined applications to have unprivileged user namespace creation, instead of disabling it completely. If we want applications to have this abi
[Touch-packages] [Bug 1989309] Re: [FFe] new apparmor features for 3.0.7
** Summary changed: - [FFe] apparmor 3.1.1 upstream release + [FFe] new apparmor features for 3.0.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989309 Title: [FFe] new apparmor features for 3.0.7 Status in apparmor package in Ubuntu: Incomplete Bug description: AppArmor 3.1.1 is the latest upstream version of the apparmor userspace tooling. This includes a large number of bug fixes since the 3.0.7 release which is currently in kinetic, as well as various cleanups and optimisations to the different tools to improve performance and maintainability. The full ChangeLog can be seen at [1]. Upstream does not provide a ChangeLog file, however I have generated one based on the git commit history of apparmor from the 3.0.7 tag to 3.1.1 as: $ git log v3.0.7...v3.1.1 -- > ~/Downloads/apparmor-3.0.7-to-3.1.1-git-log.log This can be seen in the attached file https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617640/+files/apparmor-3.0.7-to-3.1.1-git- log.log TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309, build logs can be found on Launchpad at: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+build/24491969 for amd64 etc DEBDIFF The debdiff can be found in the PPA: https://launchpad.net/~alexmurray/+archive/ubuntu/lp1989309/+files/apparmor_3.0.7-1ubuntu1_3.1.1-0ubuntu1.diff.gz INSTALL / UPGRADE LOG The apt upgrade log is attached in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+attachment/5617638/+files/apparmor-3.1.1-0ubuntu1-apt- upgrade.log [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.1 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989309/+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 1704416] Re: CAP_AUDIT_READ is not supported on Xenial
This was fixed upstream in libcap-2.25 : https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=9c3d89fbb9d819ade80b544f8a35f7b90c07cd14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1704416 Title: CAP_AUDIT_READ is not supported on Xenial Status in libcap2 package in Ubuntu: New Bug description: I'm encountering the same issue as #1451601 describes. The fix, a more recent libcap2 2.25, has made it into the Yakkety distribution but not Xenial. Summary of the problem: One cannot raise or lower CAP_AUDIT_READ, which is equal to decimal value 37. As compiled, libcap2 2.24 supports up to CAP_BLOCK_SUSPEND (36). lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy libcap2 libcap2: Installed: 1:2.24-12 Candidate: 1:2.24-12 Version table: *** 1:2.24-12 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status setcap cap_audit_read=eip /bin/ls fatal error: Invalid argument usage: setcap [-q] [-v] (-r|-|) [ ... (-r|-|) ] Note must be a regular (non-symlink) file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1704416/+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 1955804] Re: make and make test fail
Is this still a problem with libcap-2.66 ? https://git.kernel.org/pub/scm/libs/libcap/libcap.git/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1955804 Title: make and make test fail Status in libcap2 package in Ubuntu: New Bug description: Hello, make and make test fail like the printscreen following : CGO_LDFLAGS_ALLOW="-Wl,-wrap,.+" CGO_CFLAGS="-I/home/ubuntu/programs/libcap-2.32/libcap/include" CGO_LDFLAGS="-L/home/ubuntu/programs/libcap-2.32/libcap" GOPATH="/home/ubuntu/programs/libcap-2.32/go" go install libcap/psx go install: version is required when current directory is not in a module Try 'go install libcap/psx@latest' to install the latest version make[1]: *** [Makefile:37 : pkg/linux_amd64/libcap/psx.a] Erreur 1 make[1] : on quitte le répertoire « /home/ubuntu/programs/libcap-2.32/go » make: *** [Makefile:13 : all] Erreur 2 root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# go install libcap/psx@latest go install: libcap/psx@latest: malformed module path "libcap/psx": missing dot in first path element root@ubuntu-ThinkPad-X250:/home/ubuntu/programs/libcap-2.32# thank you in advance to help myself fully install your program, Regards. Dorian ROSSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1955804/+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 1700814] Re: Default capability of cap_setfcap+i should be set on setcap
FWIW This used to be the default inside the libcap build tree, but the problems with the container defaults (eventually fixed with https://github.com/moby/moby/security/advisories/GHSA-2mm7-x5h6-5pvq ) changed my position on this: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=2b5f5635be6131d7e89b4c6244b29f32ebd163c1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1700814 Title: Default capability of cap_setfcap+i should be set on setcap Status in libcap2 package in Ubuntu: New Bug description: If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them to be able to use setcap without sudo. setcap is not provided with any default file capabilities however, so either the user has to sudo, or I have to grant the setfcap capability to setcap with setcap. In my mind, it would be reasonable to grant setfcap+i to setcap by default on installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+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 1991566] Re: Package creates a socket file for all addresses of all families, even when bind to a single address
I ran this from a container image running under LXC, so perhaps that's the confusion of jammy vs kinetic. Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.53-1-pve x86_64) (From motd) While yes, this "solution" I did will in fact get wiped on upgrade, it was done as a troubleshooting step, to figure out if this was, in fact, the usse. However, listening on all interfaces, as a default, may be fine, however, this is managed via the sshd config. Otherwise, we are left with 2 places to configure a service, that already has a very comprehensive configuration file, all of it's own (/etc/ssh/sshd_config). If the sshd config is modified, it should trigger re-creation of the pertinent socket, or all configuration of sshd should be within it's unit file, and not in another configuration file. A more sane default would be "Listen only on the interfaces the service has requested", not "Listen on all interfaces, regardless of what the configuration file specifies" I would think? Or "Listen only on interfaces that have been requested". Prior to socket activation, openssh only listens on interfaces specified in it's config file, which does default to all families, all interfaces, unless it's specified. Then, it listens only where it is told to do so (As indicated in the attached sshd conf). -- 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/1991566 Title: Package creates a socket file for all addresses of all families, even when bind to a single address Status in openssh package in Ubuntu: Incomplete Bug description: I am configuring OpenSSH to listen only on ipv4 and only on one interface and one address, with nginx listening on 22 on the other interface, and families. In order to make this happen, I had to "break" the socket file installed by the package at: /etc/systemd/system/sockets.target.wants/ssh.socket To read as follows: [Unit] Description=OpenBSD Secure Shell server socket Before=ssh.service Conflicts=ssh.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run #[Socket] #ListenStream=22 #Accept=yes #[Install] #WantedBy=sockets.target (Commented out the lines that installed the socket) Then a daemon-reload, and restart of ngxinx, and all components of the solution are working as required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket] ProcVersionSignature: Uname: Linux 5.15.53-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 16:36:37 2022 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+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 1990783] Re: distorted mouse pointer under Wayland in Kinetic
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1990783/+attachment/5620782/+files/syslog ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1990783 Title: distorted mouse pointer under Wayland in Kinetic Status in kwin package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: After upgrading to Kubuntu 22.10 Kinetic dev. I found mouse pointer distorted. Please, look at attached screenshot. Under X session mouse pointer looks as it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1990783/+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 1991566] Re: Package creates a socket file for all addresses of all families, even when bind to a single address
Your bug report is against jammy, but socket activation is a default for ssh only in kinetic. Were you using ubuntu-bug from a different machine than the one affected? > In order to make this happen, I had to "break" the socket file installed by the package at: > /etc/systemd/system/sockets.target.wants/ssh.socket So first of all, this is a symlink to a file under /lib; your changes will be overwritten on package upgrade. Secondly, listening on all interfaces is a default for openssh, both before and after the move to socket-based activation. To configure the systemd socket unit to listen on a particular interface, you need only drop an override file in /etc/systemd/system/ssh.socket.d/ with the contents: [Socket] ListenStream= ListenStream=$address:22 ** 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/1991566 Title: Package creates a socket file for all addresses of all families, even when bind to a single address Status in openssh package in Ubuntu: Incomplete Bug description: I am configuring OpenSSH to listen only on ipv4 and only on one interface and one address, with nginx listening on 22 on the other interface, and families. In order to make this happen, I had to "break" the socket file installed by the package at: /etc/systemd/system/sockets.target.wants/ssh.socket To read as follows: [Unit] Description=OpenBSD Secure Shell server socket Before=ssh.service Conflicts=ssh.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run #[Socket] #ListenStream=22 #Accept=yes #[Install] #WantedBy=sockets.target (Commented out the lines that installed the socket) Then a daemon-reload, and restart of ngxinx, and all components of the solution are working as required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket] ProcVersionSignature: Uname: Linux 5.15.53-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 16:36:37 2022 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+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 1991566] [NEW] Package creates a socket file for all addresses of all families, even when bind to a single address
Public bug reported: I am configuring OpenSSH to listen only on ipv4 and only on one interface and one address, with nginx listening on 22 on the other interface, and families. In order to make this happen, I had to "break" the socket file installed by the package at: /etc/systemd/system/sockets.target.wants/ssh.socket To read as follows: [Unit] Description=OpenBSD Secure Shell server socket Before=ssh.service Conflicts=ssh.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run #[Socket] #ListenStream=22 #Accept=yes #[Install] #WantedBy=sockets.target (Commented out the lines that installed the socket) Then a daemon-reload, and restart of ngxinx, and all components of the solution are working as required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket] ProcVersionSignature: Uname: Linux 5.15.53-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 16:36:37 2022 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1991566 Title: Package creates a socket file for all addresses of all families, even when bind to a single address Status in openssh package in Ubuntu: New Bug description: I am configuring OpenSSH to listen only on ipv4 and only on one interface and one address, with nginx listening on 22 on the other interface, and families. In order to make this happen, I had to "break" the socket file installed by the package at: /etc/systemd/system/sockets.target.wants/ssh.socket To read as follows: [Unit] Description=OpenBSD Secure Shell server socket Before=ssh.service Conflicts=ssh.service ConditionPathExists=!/etc/ssh/sshd_not_to_be_run #[Socket] #ListenStream=22 #Accept=yes #[Install] #WantedBy=sockets.target (Commented out the lines that installed the socket) Then a daemon-reload, and restart of ngxinx, and all components of the solution are working as required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-server 1:8.9p1-3 [modified: lib/systemd/system/ssh.socket] ProcVersionSignature: Uname: Linux 5.15.53-1-pve x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 16:36:37 2022 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991566/+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 645404] Re: Support Private PPAs
see also bug 1991553 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Bionic: Won't Fix Status in software-properties source package in Cosmic: Won't Fix Status in software-properties source package in Disco: Won't Fix Status in software-properties source package in Eoan: Won't Fix Status in software-properties source package in Focal: Won't Fix Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 645404] Re: Support Private PPAs
The history is a bit confusing, but I think this was landed in software- properties 0.99.0, and so this bug should probably be closed. Am I right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Bionic: Won't Fix Status in software-properties source package in Cosmic: Won't Fix Status in software-properties source package in Disco: Won't Fix Status in software-properties source package in Eoan: Won't Fix Status in software-properties source package in Focal: Won't Fix Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1991427] Re: ssh doesn't offer identity files in the right order
Hello and thanks for this bug report. In my understanding, when ssh-
agent is in use, what matters is the order in which identities are added
to the agent. While I agree this is not clearly documented it's likely
that openssh is just working as expected.
The new agent restrictions feature of OpenSSH 8.9 may help in your
specific use case, see [1].
I'm marking this bug report as Incomplete for now. If you agree that we
don't have a bug in Ubuntu here please change the report status to
Invalid, otherwise comment back explaining why you do believe this is a
bug in Ubuntu and we'll look at this again. Thanks!
[1] https://www.openssh.com/agent-restrict.html
** 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/1991427
Title:
ssh doesn't offer identity files in the right order
Status in openssh package in Ubuntu:
Incomplete
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-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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991427/+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 1991553] [NEW] can't add a private PPA
Public bug reported: As per today's discussion in ~is : add-apt-repository has a bug when adding a private PPA. Quoting ~cjwatson : === It asks Launchpad for all your personal archive subscriptions _that have tokens_. But `Person:+archivesubscriptions` also shows subscriptions without tokens - the token is generated when you click on Viewt here for the first time. Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not `getArchiveSubscriptionURLs`) for the archive it's interested in. That generates tokens on-demand. Either it will get an HTTP 401, or it will get a URL which it can parse for the username and password. === Thanks ! ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1991553 Title: can't add a private PPA Status in software-properties package in Ubuntu: New Bug description: As per today's discussion in ~is : add-apt-repository has a bug when adding a private PPA. Quoting ~cjwatson : === It asks Launchpad for all your personal archive subscriptions _that have tokens_. But `Person:+archivesubscriptions` also shows subscriptions without tokens - the token is generated when you click on Viewt here for the first time. Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not `getArchiveSubscriptionURLs`) for the archive it's interested in. That generates tokens on-demand. Either it will get an HTTP 401, or it will get a URL which it can parse for the username and password. === Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+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] Fwd: [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.
Another screen print; I don't know if it is useful. Forwarded Message Subject:Re: [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound. Date: Mon, 3 Oct 2022 15:51:33 +0100 From: Joaquim Torres To: Bug 1991530 <1991...@bugs.launchpad.net> Hello, The problem remains. I'm trying to use the earphone output of my laptop. Best regards, Joaquim Torres On 03/10/22 15:22, Aaron Rainbolt wrote: > sudo apt install firmware-sof-signed ** Attachment added: "m921nhar3EQ4jweU.png" https://bugs.launchpad.net/bugs/1991530/+attachment/5620753/+files/m921nhar3EQ4jweU.png ** Attachment added: "rlik00YNECJYXwYl.png" https://bugs.launchpad.net/bugs/1991530/+attachment/5620754/+files/rlik00YNECJYXwYl.png ** Attachment added: "bZqsKXlsvwAr8d06.png" https://bugs.launchpad.net/bugs/1991530/+attachment/5620755/+files/bZqsKXlsvwAr8d06.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1991530 Title: After upgrading to Ubuntu 22.10-beta I lost the sound. Status in alsa-driver package in Ubuntu: New Bug description: In the list of devices for testing sound I get only "Dummy Output". With 22.04 everything was ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 14:27:59 2022 InstallationDate: Installed on 2019-07-01 (1190 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB002BPG dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB002BPG dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+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 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.
Hello, The problem remains. I'm trying to use the earphone output of my laptop. Best regards, Joaquim Torres On 03/10/22 15:22, Aaron Rainbolt wrote: > sudo apt install firmware-sof-signed ** Attachment added: "rlik00YNECJYXwYl.png" https://bugs.launchpad.net/bugs/1991530/+attachment/5620751/+files/rlik00YNECJYXwYl.png ** Attachment added: "bZqsKXlsvwAr8d06.png" https://bugs.launchpad.net/bugs/1991530/+attachment/5620752/+files/bZqsKXlsvwAr8d06.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1991530 Title: After upgrading to Ubuntu 22.10-beta I lost the sound. Status in alsa-driver package in Ubuntu: New Bug description: In the list of devices for testing sound I get only "Dummy Output". With 22.04 everything was ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 14:27:59 2022 InstallationDate: Installed on 2019-07-01 (1190 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB002BPG dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB002BPG dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+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 1991545] [NEW] Domain groups not accepted as 'AdminIdentities'
Public bug reported: Domain groups cannot be configured as 'AdminIdentities' under /etc/polkit-1/localauthority.conf.d EXAMPLE CONFIG # /etc/polkit-1/localauthority.conf.d/90-test.conf [Configuration] AdminIdentities=unix-group:sysapp With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the machine to allow domain users to log in. Sudo rules have been configured for the 'sysapp' group and work correctly. However, any action that creates a polkit/GUI prompt for authentication does not allow users in the 'sysapp' group to authenticate. Instead, it only accepts auth from the root user. If I change the config to use a local group, instead of a domain group, everything works as expected. Similarly if I specify a domain USER instead of a domain group, everything works as expected. The problem seems to only be with domain/LDAP groups. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 15:20:36 2022 InstallationDate: Installed on 2022-07-15 (80 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: policykit-1 UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago) ** Affects: policykit-1 (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 policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1991545 Title: Domain groups not accepted as 'AdminIdentities' Status in policykit-1 package in Ubuntu: New Bug description: Domain groups cannot be configured as 'AdminIdentities' under /etc/polkit-1/localauthority.conf.d EXAMPLE CONFIG # /etc/polkit-1/localauthority.conf.d/90-test.conf [Configuration] AdminIdentities=unix-group:sysapp With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the machine to allow domain users to log in. Sudo rules have been configured for the 'sysapp' group and work correctly. However, any action that creates a polkit/GUI prompt for authentication does not allow users in the 'sysapp' group to authenticate. Instead, it only accepts auth from the root user. If I change the config to use a local group, instead of a domain group, everything works as expected. Similarly if I specify a domain USER instead of a domain group, everything works as expected. The problem seems to only be with domain/LDAP groups. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 3 15:20:36 2022 InstallationDate: Installed on 2022-07-15 (80 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: policykit-1 UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+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 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.
Can you try running "sudo apt install firmware-sof-signed" and see if that resolves the problem? -- 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/1991530 Title: After upgrading to Ubuntu 22.10-beta I lost the sound. Status in alsa-driver package in Ubuntu: New Bug description: In the list of devices for testing sound I get only "Dummy Output". With 22.04 everything was ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 14:27:59 2022 InstallationDate: Installed on 2019-07-01 (1190 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB002BPG dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB002BPG dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+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 1991530] [NEW] After upgrading to Ubuntu 22.10-beta I lost the sound.
Public bug reported: In the list of devices for testing sound I get only "Dummy Output". With 22.04 everything was ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 14:27:59 2022 InstallationDate: Installed on 2019-07-01 (1190 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB002BPG dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB002BPG dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1991530 Title: After upgrading to Ubuntu 22.10-beta I lost the sound. Status in alsa-driver package in Ubuntu: New Bug description: In the list of devices for testing sound I get only "Dummy Output". With 22.04 everything was ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 14:27:59 2022 InstallationDate: Installed on 2019-07-01 (1190 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB002BPG dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB002BPG dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+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
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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: Invalid 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 1991525] [NEW] vim.gtk3 won't run after 22.04 upgrade: “libpng12.so.0: cannot open shared object file”
Public bug reported:
After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
longer runs:
$ vim.gtk3
vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open
shared object file: No such file or directory
(vim.basic still runs fine).
These are the vim packages we have installed, and their versions:
vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
Previously I did have a PPA of Vim installed from
http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
purged, and as you can see all the vim packages now installed are
official Ubuntu jammy versions.
libpng12 isn't in Ubuntu any more, so I think the problem is that vim is
trying to use it, not that it's missing.
Attached is strace output of the failure.
** Affects: vim (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "strace of the failure"
https://bugs.launchpad.net/bugs/1991525/+attachment/5620716/+files/vim.gtk3.strace
** Description changed:
After upgrading a system running Ubuntu 20.04 to 22.04, vim.gtk3 no
longer runs:
- $ vim.gtk3
- vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open
shared object file: No such file or directory
+ $ vim.gtk3
+ vim.gtk3: error while loading shared libraries: libpng12.so.0: cannot open
shared object file: No such file or directory
(vim.basic still runs fine).
These are the vim packages we have installed, and their versions:
- vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
- vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
- vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
- vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
- vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
- vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim-gtk3:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim-gui-common:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim-runtime:all/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
+ vim-tiny:amd64/jammy-security 2:8.2.3995-1ubuntu2.1 uptodate
Previously I did have a PPA of Vim installed from
- http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been purged, and
- as you can see all the vim packages now installed are official Ubuntu jammy
- versions.
+ http://ppa.launchpad.net/jonathonf/vim/ubuntu — but that has been
+ purged, and as you can see all the vim packages now installed are
+ official Ubuntu jammy versions.
- libpng12 isn't in Ubuntu any more, so I think the problem is that vim is
trying
- to use it, not that it's missing.
+ libpng12 isn't in Ubuntu any more, so I think the problem is that vim is
+ trying to use it, not that it's missing.
- Here's some strace output leading up to the failure:
-
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libwayland-client.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=64776, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libXext.so.6", O_RDONLY|O_CLOEXEC)
= 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=81640, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libthai.so.0", O_RDONLY|O_CLOEXEC)
= 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=41152, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=21448, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpixman-1.so.0",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
- newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=694448, ...},
AT_EMPTY_PATH) = 0
- close(3)= 0
- openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfreetype.so.6",
O_RDONLY|O_CLOEXEC) = 3
- read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0
[Touch-packages] [Bug 1991524] [NEW] regression: broadwell-rt286 sound card audio output is extremely low
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center alsa-base: Installed: 1.0.25+dfsg-0ubuntu7 Candidate: 1.0.25+dfsg-0ubuntu7 Version table: *** 1.0.25+dfsg-0ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen In Ubuntu 22.04 and prior versions, audio output via my laptop speakers worked just fine. It was clear and played at a reasonable max volume. I expected the same for 22.10. 4) What happened instead Audio output for my laptop (an HP Spectre x360 Convertible 13--802D) is extremely low, to the point where I thought sound wasn't playing at all. It was only when I played an extremely loud YouTube video with volume at max with the speaker held up to my ear that I realized it was playing. The same issue is happening with my laptop's headphone jack, but not when I plug in a USB speaker or play sound via HDMI. I know that Ubuntu is switching to pipewire and wireplumber for audio in the 22.10 release. Pipewire has given me trouble on other distributions that already use it for this particular device, so that may be part of the problem. I've tried increasing all volume sliders in alsamixer as well, with no improvement. Please let me know if there's any other information you need. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 07:18:54 2022 InstallationDate: Installed on 2022-10-03 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.release: 15.81 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 802D dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.63 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 58.99 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.51:bd06/20/2018:br15.81:efr58.99:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.63:cvnHewlett-Packard:ct10:cvrChassisVersion:skuL0Q56UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13 dmi.product.sku: L0Q56UA#ABA dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center alsa-base: - Installed: 1.0.25+dfsg-0ubuntu7 - Candidate: 1.0.25+dfsg-0ubuntu7 - Version table: - *** 1.0.25+dfsg-0ubuntu7 500 - 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 1.0.25+dfsg-0ubuntu7 + Candidate: 1.0.25+dfsg-0ubuntu7 + Version table: + *** 1.0.25+dfsg-0ubuntu7 500 + 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages + 100 /var/lib/dpkg/status 3) What you expected to happen In Ubuntu 22.04 and prior versions, audio output via my laptop speakers worked just fine. It was clear and played at a reasonable max volume. I expected the same for 22.10. 4) What happened instead Audio output for my laptop (an HP Spectre x360 Convertible 13--802D) is extremely low, to the point where I thought sound wasn't playing at all. It was only when I played an extremely loud YouTube video with volume at max with the speaker held up to my ear that I realized it was playing. The same issue is happening with my laptop's headphone jack, but not when I plug in a USB speaker or play sound via HDMI. I know that Ubuntu is switching to pipewire and wireplumber for audio in the 22.10 release. Pipewire has given me trouble on other distributions tha
[Touch-packages] [Bug 1990448] Re: Show Ubuntu Pro settings
** Merge proposal linked: https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+merge/430260 ** Changed in: software-properties (Ubuntu Kinetic) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: Incomplete Status in software-properties source package in Kinetic: Fix Committed Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1990448] Re: Show Ubuntu Pro settings
@Dan, the design is available on https://app.zeplin.io/project/6319abf25548b04abcee1b5f/dashboard The Kinetic target is correct, even if the service isn't available on non LTS serie we need the code to be merged in the current serie before being backported by SRU rules The corresponding PR is https://code.launchpad.net/~robert- ancell/software-properties/+git/software-properties/+merge/430260 ** Changed in: software-properties (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: software-properties (Ubuntu Kinetic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1990448 Title: Show Ubuntu Pro settings Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: Incomplete Status in software-properties source package in Kinetic: Fix Committed Bug description: Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of just Livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+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 1896540] Re: Incorrectly specified Touchpad size for Lenovo T490
I have the same problem on Ubuntu 20.04.5 -- 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/1896540 Title: Incorrectly specified Touchpad size for Lenovo T490 Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Expired Bug description: The vertical sensitivity of the touchpad on my laptop Lenovo T490 seemed significantly higher than the horizontal sensitivity. After doing some research I found out that the touchpad size is incorrectly listed by the kernel. Touchpad size listed by the kernel: 77x107mm The real size of the touchpad: 68x100mm Description: Ubuntu 20.04.1 LTS Release: 20.04 Systemd version: 245.4-4ubuntu3.2 Output from the touchpad-edge-detector: miroslav@miroslav-ThinkPad-T490:~$ sudo touchpad-edge-detector 68x100 /dev/input/event5 Touchpad SynPS/2 Synaptics TouchPad on /dev/input/event5 Move one finger around the touchpad to detect the actual edges Kernel says: x [1266..5678], y [1162..4694] Touchpad sends: x [1266..5678], y [1161..4694] -^C Touchpad size as listed by the kernel: 77x107mm User-specified touchpad size: 68x100mm Calculated ranges: 4412/3533 Suggested udev rule: # evdev:name:SynPS/2 Synaptics TouchPad:dmi:bvnLENOVO:bvrN2IET75W(1.53):bd08/21/2019:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:* EVDEV_ABS_00=1266:5678:65 EVDEV_ABS_01=1161:4694:35 EVDEV_ABS_35=1266:5678:65 EVDEV_ABS_36=1161:4694:35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1896540/+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 1991507] Re: Monitor does not turn on
Thanks for the bug report. This is probably bug 1968040 so please try the workaround mentioned there. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991507 Title: Monitor does not turn on Status in mutter package in Ubuntu: Incomplete Bug description: The main screen does not turn on after the monitors are turned off due to energy saving (there is no video signal). The secondary screen turns on correctly. It doesn't happen every time ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 09:17:24 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299] InstallationDate: Installed on 2022-09-26 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP Z4D06EA#ABE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2019 dmi.bios.release: 2.27 dmi.bios.vendor: HP dmi.bios.version: P01 Ver. 02.27 dmi.board.name: 8299 dmi.board.vendor: HP dmi.board.version: KBC Version 06.21 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.33 dmi.modalias: dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: Z4D06EA#ABE dmi.product.sku: Z4D06EA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1991507/+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 1990586] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released 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-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zipp rygel whoop
[Touch-packages] [Bug 1990586] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
This bug was fixed in the package apt - 2.4.8 --- apt (2.4.8) jammy; urgency=medium * edsp: Add support for phased updates (test in LP#1990586) * Check state of dependency, not dependee 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:37:51 +0200 ** Changed in: apt (Ubuntu Jammy) Status: Fix Committed => 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 Released 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-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney python3-jwt python3-keyring python3-launchpadlib python3-lazr.restfulclient python3-lazr.uri python3-lockfile python3-louis python3-monotonic python3-more-itertools python3-oauthlib python3-olefile python3-pexpect python3-pkg-resources python3-problem-report python3-ptyprocess python3-pyparsing python3-requests python3-rfc3339 python3-secretstorage python3-six python3-tz python3-urllib3 python3-wadllib python3-xkit python3-zi
[Touch-packages] [Bug 1990684] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released 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 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53 Uname: Linux 5.15.0-1020-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 23 13:12:07 2022 Ec2AMI: ami-092d30890417a55e5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ca-central-1d Ec2InstanceType: t4g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: grub
[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.4.8 --- apt (2.4.8) jammy; urgency=medium * edsp: Add support for phased updates (test in LP#1990586) * Check state of dependency, not dependee 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:37:51 +0200 ** Changed in: apt (Ubuntu Jammy) Status: Fix Committed => 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 Released 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 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-efi-arm64-signed 1.180+2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-1020.24-aws 5.15.53 Uname: Linux 5.15.0-1020-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 23 13:12:07 2022 Ec2AMI: ami-092d30890417a55e5 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ca-central-1d Ec2InstanceType: t4g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) Sour
[Touch-packages] [Bug 1991507] [NEW] Monitor does not turn on
Public bug reported: The main screen does not turn on after the monitors are turned off due to energy saving (there is no video signal). The secondary screen turns on correctly. It doesn't happen every time ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 09:17:24 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299] InstallationDate: Installed on 2022-09-26 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP Z4D06EA#ABE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2019 dmi.bios.release: 2.27 dmi.bios.vendor: HP dmi.bios.version: P01 Ver. 02.27 dmi.board.name: 8299 dmi.board.vendor: HP dmi.board.version: KBC Version 06.21 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.33 dmi.modalias: dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: Z4D06EA#ABE dmi.product.sku: Z4D06EA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991507 Title: Monitor does not turn on Status in xorg package in Ubuntu: New Bug description: The main screen does not turn on after the monitors are turned off due to energy saving (there is no video signal). The secondary screen turns on correctly. It doesn't happen every time ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 3 09:17:24 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299] InstallationDate: Installed on 2022-09-26 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP Z4D06EA#ABE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (pro
