[Touch-packages] [Bug 2105846] [NEW] riscv64 autopkgtest failure due to a timeout during upstream-runtime-tests-isolation test
Public bug reported: The autopkgtest for keyutils failed because the test upstream-runtime- tests-isolation timed out. https://autopkgtest.ubuntu.com/results/autopkgtest- plucky/plucky/riscv64/k/keyutils/20250321_130957_b8ac0@/log.gz ** Affects: keyutils (Ubuntu) Importance: Undecided Status: New ** Summary changed: - riscv64 autopkgtest failure due to a timeout during the upstream-runtime-tests-isolation test + riscv64 autopkgtest failure due to a timeout during upstream-runtime-tests-isolation test -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/2105846 Title: riscv64 autopkgtest failure due to a timeout during upstream-runtime- tests-isolation test Status in keyutils package in Ubuntu: New Bug description: The autopkgtest for keyutils failed because the test upstream-runtime- tests-isolation timed out. https://autopkgtest.ubuntu.com/results/autopkgtest- plucky/plucky/riscv64/k/keyutils/20250321_130957_b8ac0@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/2105846/+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 2098424] Re: p11-kit 0.25.5-2ubuntu2 makes gnutls fail to build from source in plucky
** Changed in: gnutls28 (Ubuntu) Milestone: ubuntu-25.04 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2098424 Title: p11-kit 0.25.5-2ubuntu2 makes gnutls fail to build from source in plucky Status in gnutls28 package in Ubuntu: Invalid Status in p11-kit package in Ubuntu: Fix Released Bug description: When building gnutls for[1] I have encountered the following build error: protection -fdebug-prefix-map=/<>=/usr/src/gnutls28-3.8.9-2ubuntu2 -Wall -c ../../lib/srp.c -fPIC -DPIC -o .libs/srp.o In file included from ../../lib/pkcs11x.h:24, from ../../lib/pkcs11_write.c:28: /usr/include/p11-kit-1/p11-kit/pkcs11x.h:321:5: error: unknown type name 'CK_BBOOL' 321 | CK_BBOOLbPrepend; | ^~~~ make[6]: *** [Makefile:3582: pkcs11_write.lo] Error 1 [1] https://code.launchpad.net/~adrien/ubuntu/+source/gnutls28/+git/gnutls28/+merge/469926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/2098424/+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 2103526] Re: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports
For posterity: I discussed this FFe with Skia and approved it in a side channel, before sponsoring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2103526 Title: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports Status in whoopsie package in Ubuntu: Fix Released Bug description: [Context] Apt solver 3 is coming to plucky. Julian, apt's maintainer, would like to collect apt solver issues in the Ubuntu Error Tracker. Everything is already mostly wired, but `whoopsie` currently doesn't allow the `AptSolverDump` field in the produced crashes. [Changes] This is mostly a one-line change to add `AptSolverDump` to the right allow-list. Since I'm slowly taking over this mostly unmaintained package, I'm also improving some other small things that would be good to be evaluated in the FFe: * Add some additional logging for more discoverable behavior. * Fix some lintian errors. * Raise debhelper-compat to 13. The exhaustive list of changes can be found on this MP: https://code.launchpad.net/~hyask/whoopsie/+git/whoopsie/+merge/482986 [Test plan] Here is a PPA: https://launchpad.net/~hyask/+archive/ubuntu/whoopsie- aptsolverdump/+packages I've already installed the package from the PPA, and verified the following: * systemd .service and .path files are correctly installed at the right place. * whoopsie service correctly triggers when something appears in `/var/crash`. * The new log lines correctly appear in the journal of the whoopsie service: ``` mars 18 17:44:49 kiffex systemd[1]: Started whoopsie.service - Service uploading crash reports to the Ubuntu Error Tracker. mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Using lock path: /var/lock/whoopsie/lock mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Looking for .upload files in /var/crash mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_share_apport_apport.0.crash) mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_libexec_fwupd_fwupd.0.crash) mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Crash already uploaded, skipping mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Found .crash corresponding to .upload (/var/crash/_usr_bin_seg-fault.1000.crash) mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Parsing /var/crash/_usr_bin_seg-fault.1000.crash. mars 18 17:44:49 kiffex whoopsie[1209860]: [17:44:49] Uploading /var/crash/_usr_bin_seg-fault.1000.crash. mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Sent; server replied with: No error mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Response code: 200 mars 18 17:44:50 kiffex whoopsie[1209860]: [17:44:50] Reported OOPS ID 4e2150de-0418-11f0-999a-fa163e171f02 mars 18 17:44:50 kiffex systemd[1]: whoopsie.service: Deactivated successfully. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526/+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 2078555] Re: Upgrading from 22.04 to 24.04.01 breaks dnsmasq
This bug was fixed in the package systemd - 249.11-0ubuntu3.15 --- systemd (249.11-0ubuntu3.15) jammy; urgency=medium * d/systemd.prerm: call d-s-h update-state for resolved on upgrades (LP: #2078555) systemd (249.11-0ubuntu3.14) jammy; urgency=medium [ Ioanna Alifieraki ] * network: skip to reassign master ifindex if already set (LP: #2003250) [ Nick Rosbrook ] * network: do not bring down a bonding port interface when it is already joined (This is a follow-up commit required for LP: 2003250) * networkd-test: skip test_resolved_domain_restricted_dns (LP: #2009859) systemd (249.11-0ubuntu3.13) jammy; urgency=medium [ Lukas Märdian ] * Fixing GRE6 and VTI6 on newer kernels (LP: #2037667) [ Nick Rosbrook ] * debian/tests/tests-in-lxd: update workaround patch (LP: #2055200) [ Chengen Du ] * udev: Handle PTP device symlink properly on udev action 'change' (LP: #209) -- Nick Rosbrook Thu, 20 Feb 2025 08:24:02 -0500 ** Changed in: systemd (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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2078555 Title: Upgrading from 22.04 to 24.04.01 breaks dnsmasq Status in Ubuntu: Triaged Status in dnsmasq package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in dnsmasq source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Invalid Status in The Noble Numbat: New Status in dnsmasq source package in Noble: Invalid Status in systemd source package in Noble: Won't Fix Status in ubuntu-release-upgrader source package in Noble: Fix Released Bug description: [Impact] During upgrades, systemd-resolved will be started and enabled, even if it was not previously. This is due to (a) the package split that made systemd-resolved its own package (during kinetic cycle, hence between jammy and noble), and (b) an ubuntu-release-upgrader quirk that (re)starts systemd-resolved out of stub mode during the upgrade to avoid DNS resolution failures during the upgrade. [Test Plan] The complete test plan requires the fixed version of systemd *and* ubuntu-release-upgrader. On a Jammy machine, install systemd from jammy-proposed: $ cat > /etc/apt/sources.list.d/proposed.list << EOF deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main universe EOF $ cat
[Touch-packages] [Bug 2105455] Re: python3-venv : Depends: python3 (= 3.12.3-0ubuntu1) but 3.12.3-0ubuntu2 is to be installed
I'd say it's a mirror issue.
> And it's the same with your mirror.
What do you mean exactly? My mirror (br.archive.ubuntu.com) showed
0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2105455
Title:
python3-venv : Depends: python3 (= 3.12.3-0ubuntu1) but
3.12.3-0ubuntu2 is to be installed
Status in python3-defaults package in Ubuntu:
Incomplete
Bug description:
ommand: /usr/bin/apt-get install -y python3-venv
Output:
Reading package lists...
Building dependency tree...
Reading state information...
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:
python3-venv : Depends: python3 (= 3.12.3-0ubuntu1) but 3.12.3-0ubuntu2 is
to be installed
Couldn't be fixed by normal update/upgrade or mirror change.
I've patched my system for now with:
sudo apt install --allow-downgrades
python3{,-full,-doc,-examples,-minimal}=3.12.3-0ubuntu1
libpython3-stdlib=3.12.3-0ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2105455/+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 2092363] Re: Missing (but referenced) SOF firmware in pc-kernel – No Audio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firmware-sof (Ubuntu) Status: New => Confirmed -- 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/2092363 Title: Missing (but referenced) SOF firmware in pc-kernel – No Audio Status in canonical-kernel-snaps: Confirmed Status in pc-kernel-snap: Invalid Status in apt package in Ubuntu: Invalid Status in boot-managed-by-snapd package in Ubuntu: Invalid Status in firmware-sof package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I am encountering an issue with the pc-kernel snap on my HP EliteBook 840 G11 laptop running Ubuntu 24.04.1 LTS with the new TPM+FDE feature. Despite testing multiple kernel channels, the system fails to detect any audio devices. However, when booting into a live session of Ubuntu 24.04.1 LTS, audio functions as expected. This suggests the issue may be related to the pc-kernel snap. Right now I'm on channel 24/stable (version: 6.8.0-50.51), but I have tried 24-hwe/stable and 24.10/stable as well. For reference, I have first tried to seek help in the support section over at Ubuntu Discourse, and I was encouraged to file a bug report here against the linux package on Discourse: https://discourse.ubuntu.com/t/no-audio-device-detected-on-hp-elitebook-840-14-g11-running-ubuntu-24-04/51498/7 Details: OS: Ubuntu 24.04.1 LTS Setup: TPM-backed Full Disk Encryption (FDE) using pc-kernel snap Kernel Channels Tried: 24-hwe/stable, 24/stable, 24.10/stable Issue: aplay -l reports "no sound card found"; only "Dummy output" is listed in Audio settings. Observation: Audio works correctly in a live session of Ubuntu 24.04.1 LTS. Listing audio devices: $ aplay -l aplay: device_list:277: no soundcards found... Relevant lspci Output: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Meteor Lake-P HD Audio Controller [8086:7e28] (rev 20) Subsystem: Hewlett-Packard Company Meteor Lake-P HD Audio Controller [103c:8c26] Kernel driver in use: sof-audio-pci-intel-mtl Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl Additional Notes: Could the issue be related to missing kernel drivers or modules, such as firmware-sof-signed? Reference: https://packages.ubuntu.com/noble/firmware-sof-signed Please let me know if additional details, logs, or steps are required. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-50-generic (not installed) ProcVersionSignature: Ubuntu 6.8.0-50.51-generic 6.8.12 Uname: Linux 6.8.0-50-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:kihen 3216 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 22 20:09:17 2024 MachineType: HP HP EliteBook 840 14 inch G11 Notebook PC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb 1 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-50-generic N/A linux-backports-modules-6.8.0-50-generic N/A linux-firmwareN/A SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 06/20/2024 dmi.bios.release: 2.6 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.02.06 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.43.50 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.67 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.02.06:bd06/20/2024:br2.6:efr2.67:svnHP:pnHPEliteBook84014inchG11NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.43.50:cvnHP:ct10:cvr:sku8M4W7AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 14 inch G11 Notebook PC dmi.product.sku: 8M4W7AV dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2092363/+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 2081692] Re: apparmor profile too restrictive : kernel logs spammed with ~/.cache/mesa_shader_cache_db accesses
Fixed in plucky, thanks! ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- 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/2081692 Title: apparmor profile too restrictive : kernel logs spammed with ~/.cache/mesa_shader_cache_db accesses Status in apparmor package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: Hi, I am running Plasma on X11, and Xorg is running in AppArmor complain mode: # aa-status [...] 1 processes are in complain mode. /usr/lib/xorg/Xorg (5903) Xorg The kernel logs are spammed with the following AppArmor messages: # dmesg | grep mesa_shader_cache_db [ 30.513476] audit: type=1400 audit(1727008543.347:433): apparmor="ALLOWED" operation="mknod" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [ 30.513562] audit: type=1400 audit(1727008543.347:434): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="rc" denied_mask="rc" fsuid=1000 ouid=1000 [ 30.513584] audit: type=1400 audit(1727008543.347:435): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [ 30.513592] audit: type=1400 audit(1727008543.347:436): apparmor="ALLOWED" operation="mknod" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.idx" pid=5903 comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 I think that the Xorg AppArmor profile should be updated to allow those accesses. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xserver-xorg-core 2:21.1.13-2ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Sep 23 09:36:08 2024 DistUpgraded: Fresh install DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev d7) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8b6e] MachineType: HP HP EliteBook 865 16 inch G10 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=/dev/mapper/MonVolume-Racine ro vsyscall=none security=apparmor preempt=full split_lock_detect=warn quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2024 dmi.bios.release: 5.11 dmi.bios.vendor: HP dmi.bios.version: V82 Ver. 01.05.11 dmi.board.name: 8B6E dmi.board.vendor: HP dmi.board.version: KBC Version 60.2E.60 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 96.46 dmi.modalias: dmi:bvnHP:bvrV82Ver.01.05.11:bd06/18/2024:br5.11:efr96.46:svnHP:pnHPEliteBook86516inchG10NotebookPC:pvrSBKPF:rvnHP:rn8B6E:rvrKBCVersion60.2E.60:cvnHP:ct10:cvr:sku70A94AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 865 16 inch G10 Notebook PC dmi.product.sku: 70A94AV dmi.product.version: SBKPF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu12 version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2081692/+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 2092438] Re: System fails to restart after install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2092438 Title: System fails to restart after install Status in gnome-session: New Status in subiquity: Fix Released Status in systemd: Fix Released Status in ubuntu-desktop-provision: New Status in gnome-session package in Ubuntu: Confirmed Status in subiquity package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: Testing Ubuntu Plucky Desktop daily ISO dated 24-12-24 Upon completion of the installation the system fails to restart - instead it re-enters the desktop. If the system is then restarted by selecting "restart" (in the upper right-hand corner)then all works as normal - a message appears to remove the media and the system reboots. ProblemType: Bug DistroRelease: Ubuntu 25.04 Package: subiquity (295 of snap /snap/ubuntu-desktop-bootstrap/295 of version 0+git.1db71a4e2) ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.31.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.502 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Tue Dec 24 08:42:41 2024 DesktopInstallerRev: 295 LiveMediaBuild: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241224) MachineType: Dell Inc. OptiPlex 7090 UFF ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash SnapUpdated: False SnapVersion: 295 of snap /snap/ubuntu-desktop-bootstrap/295 of version 0+git.1db71a4e2 SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2024 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.0 dmi.board.name: 0X6NW1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 35 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.0:bd11/14/2024:br1.32:svnDellInc.:pnOptiPlex7090UFF:pvr:rvnDellInc.:rn0X6NW1:rvrA00:cvnDellInc.:ct35:cvr:sku0A2E: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7090 UFF dmi.product.sku: 0A2E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/2092438/+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 2028282] Re: [SRU] SSH pubkey authetication fails when GSSAPI enabled
I tested openssh (1:8.9p1-3ubuntu0.12) from jammy-proposed, according to "Test Plan 2". Looking good! [ Test Plan 2 ] ###Set up a Jammy LXD container & install openssh-server from proposed: root@jjsru:~# apt list *openssh-server* Listing... Done openssh-server/jammy-proposed,now 1:8.9p1-3ubuntu0.12 amd64 [installed] root@jjsru:~# adduser test Adding user `test' ... Adding new group `test' (1001) ... Adding new user `test' (1001) with group `test' ... Creating home directory `/home/test' ... Copying files from `/etc/skel' ... New password: [test] Retype new password: [test] passwd: password updated successfully Changing the user information for test Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] ### Adopt SSH config & restart service root@jjsru:~# vim /etc/ssh/sshd_config.d/60-cloudimg-settings.conf root@jjsru:~# grep -R PasswordAuthentication /etc/ssh/ /etc/ssh/ssh_config:# PasswordAuthentication yes /etc/ssh/sshd_config.d/60-cloudimg-settings.conf:PasswordAuthentication yes /etc/ssh/sshd_config:#PasswordAuthentication yes /etc/ssh/sshd_config:# PasswordAuthentication. Depending on your PAM configuration, /etc/ssh/sshd_config:# PAM authentication, then enable this but set PasswordAuthentication root@jjsru:~# systemctl restart ssh.service root@jjsru:~# ip a show eth0 41: eth0@if42: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:49:68:fb brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.238.94.15/24 metric 100 brd 10.238.94.255 scope global dynamic eth0 valid_lft 3390sec preferred_lft 3390sec inet6 fd42:7213:f20e:bd74:216:3eff:fe49:68fb/64 scope global mngtmpaddr noprefixroute valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe49:68fb/64 scope link valid_lft forever preferred_lft forever ### From the host (password login OK): $ ssh test@10.238.94.15 The authenticity of host '10.238.94.15 (10.238.94.15)' can't be established. ED25519 key fingerprint is SHA256:nC8MUedwKPMY/uH6RjxGExIHo06T1w+9o7yblelI/XQ. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '10.238.94.15' (ED25519) to the list of known hosts. test@10.238.94.15's password: [test] The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. test@jjsru:~$ ssh-import-id-lp slyon 2025-04-01 13:24:57,218 INFO Authorized key ['4096', 'SHA256:sciOAYEEOgZuev6e/fxLpojXxsiZsJPzn1Jk8LaYvVg', 'lukas.maerd...@canonical.com', '(RSA)'] 2025-04-01 13:24:57,219 INFO [1] SSH keys [Authorized] ### From the host (pubkey login OK): $ ssh -i ~/.ssh/canonical_id_rsa test@10.238.94.15 Enter passphrase for key '/home/lukas/.ssh/canonical_id_rsa': Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 6.8.0-55-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/pro System information as of Tue Apr 1 13:25:54 UTC 2025 System load: 0.64 Usage of /:72.0% of 294.23GB Memory usage: 0% Swap usage:0% Temperature: 56.0 C Processes: 31 Users logged in: 0 IPv4 address for eth0: 10.238.94.15 IPv6 address for eth0: fd42:7213:f20e:bd74:216:3eff:fe49:68fb Expanded Security Maintenance for Applications is not enabled. 19 updates can be applied immediately. To see these additional updates run: apt list --upgradable Enable ESM Apps to receive additional future security updates. See https://ubuntu.com/esm or run: sudo pro status New release '24.04.2 LTS' available. Run 'do-release-upgrade' to upgrade to it. Last login: Tue Apr 1 13:24:24 2025 from 10.238.94.1 test@jjsru:~$ => All working as expected! -- 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/2028282 Title: [SRU] SSH pubkey authetication fails when GSSAPI enabled Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Noble: Fix Released Status in openssh source package in Oracular: Fix Released Status in openssh source package in Plucky: Fix Released Status in openssh package in Debian: Fix Released Bug description: [ Impact ] * Login with publickey fails when openssh server is configured to use GSSAPI authentication, too. Error: "sign_and_send_pubkey: internal error: initial hostkey not recorded" * To trigger it, one needs to (a) perform a successful GSSAPI key exchange, (b) attem
[Touch-packages] [Bug 2105894] Re: package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglap
*** This bug is a duplicate of bug 2104900 *** https://bugs.launchpad.net/bugs/2104900 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2104900/comments/5 ** This bug has been marked a duplicate of bug 2104900 Conflict installing package libgl1-mesa-dri version 25.0.2-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2105894 Title: package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) Status in mesa package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 25.04 Package: libgl1-mesa-dri 25.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0 Uname: Linux 6.14.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.32.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Mon Mar 31 15:29:30 2025 DistUpgraded: Fresh install DistroCodename: plucky DistroVariant: ubuntu ErrorMessage: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2033] InstallationDate: Installed on 2024-10-17 (166 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: Positivo Informatica SA H14CU01 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=f5d51f96-5656-44b1-8df3-fee715807591 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 Python3Details: /usr/bin/python3.13, Python 3.13.2, python3-minimal, 3.13.2-2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.18ubuntu2 apt 2.9.35 SourcePackage: mesa Title: package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.02.U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H14CU01 dmi.board.vendor: Positivo Informatica SA dmi.board.version: POSITIVO dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Informatica SA dmi.chassis.version: POSITIVO dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.02.U:bd02/20/2014:br4.6:efr1.13:svnPositivoInformaticaSA:pnH14CU01:pvr2.02.U_POS:rvnPositivoInformaticaSA:rnH14CU01:rvrPOSITIVO:cvnPositivoInformaticaSA:ct10:cvrPOSITIVO:sku3011095: dmi.product.family: To be filled by O.E.M. dmi.product.name: H14CU01 dmi.product.sku: 3011095 dmi.product.version: 2.02.U_POS dmi.sys.vendor: Positivo Informatica SA version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu13 version.libdrm2: libdrm2 2.4.123-1 version.libgl1-mesa-dri: libgl1-mesa-dri 25.0.2-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.16-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2105894/+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 2089757] Re: software-properties-gtk crashed with Exception in detect_drivers(): Exit code: None
** Changed in: software-properties (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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2089757
Title:
software-properties-gtk crashed with Exception in detect_drivers():
Exit code: None
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
Closing the software-properties-gtk window while it's detecting
drivers crashes with:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1414, in detect_drivers
raise Exception(f"Exit code: {self.search_process.exitcode}")
Exception: Exit code: None
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: software-properties-gtk 0.105
Uname: Linux 6.12.1-x64v3-xanmod1 x86_64
ApportVersion: 2.30.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 27 18:40:47 2024
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2024-11-27 (0 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241126)
InterpreterPath: /usr/bin/python3.12
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal,
3.12.6-0ubuntu1
PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
PythonDetails: N/A
SourcePackage: software-properties
Title: software-properties-gtk crashed with Exception in detect_drivers():
Exit code: None
Traceback:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1469, in detect_drivers
raise Exception(f"Exit code: {self.search_process.exitcode}")
Exception: Exit code: None
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2089757/+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 2089757] Re: software-properties-gtk crashed with Exception in detect_drivers(): Exit code: None
This bug was fixed in the package software-properties - 0.110
---
software-properties (0.110) plucky; urgency=medium
* gtk: Make driver search process non-daemonic (LP: #2089757)
-- Alessandro Astone Tue, 01 Apr
2025 16:08:29 +0200
** Changed in: software-properties (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2089757
Title:
software-properties-gtk crashed with Exception in detect_drivers():
Exit code: None
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
Closing the software-properties-gtk window while it's detecting
drivers crashes with:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1414, in detect_drivers
raise Exception(f"Exit code: {self.search_process.exitcode}")
Exception: Exit code: None
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: software-properties-gtk 0.105
Uname: Linux 6.12.1-x64v3-xanmod1 x86_64
ApportVersion: 2.30.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 27 18:40:47 2024
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2024-11-27 (0 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20241126)
InterpreterPath: /usr/bin/python3.12
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
ProcEnviron:
LANG=zh_CN.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
Python3Details: /usr/bin/python3.12, Python 3.12.7, python3-minimal,
3.12.6-0ubuntu1
PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
PythonDetails: N/A
SourcePackage: software-properties
Title: software-properties-gtk crashed with Exception in detect_drivers():
Exit code: None
Traceback:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1469, in detect_drivers
raise Exception(f"Exit code: {self.search_process.exitcode}")
Exception: Exit code: None
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2089757/+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 2099990] Re: lsusb fails due to apparmor
Both paths involved should be in the latest lsusb profile - can you double check the AppArmor package version you have installed and also include the contents of your /etc/apparmor.d/lsusb? -- 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/200 Title: lsusb fails due to apparmor Status in apparmor package in Ubuntu: Fix Released Bug description: With apparmor 4.1.0~beta5-0ubuntu5 on a RISC-V Microchip Icicle Kit I see that the kernel discovers USB: [ +0.008662] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.007425] usb 1-1: Product: Ultra [ +0.003688] usb 1-1: Manufacturer: SanDisk [ +0.004245] usb 1-1: SerialNumber: 010187b422912d2f128c699458cec5c82b7af2ece2713972b09d1de68f741b2afecb66a842d0ff9957008a558107452c91e7 [ +0.011662] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.012149] scsi host0: usb-storage 1-1:1.0 [ +0.011826] usbcore: registered new interface driver usb-storage [ +0.035775] usbcore: registered new interface driver uas But lsusb shows not device. Looking as journalctl shows that apparmor is blocking: Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:207): apparmor="DENIED" operation="capable" class="cap" profile="lsusb" pid=1510 comm="lsusb" capability=12 capname="net_admin" Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.039:208): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:209): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.043:210): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-0:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu kernel: audit: type=1400 audit(1740487618.047:211): apparmor="DENIED" operation="open" class="file" profile="lsusb" name="/sys/devices/platform/soc/20201000.usb/musb-hdrc.2.auto/usb1/1-1/1-1:1.0/uevent" pid=1510 comm="lsusb" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 12:46:58 ubuntu sudo[1508]: pam_unix(sudo:session): session closed for user root /etc/apparmor.d/usr.bin.lsusb does not exist. sudo apparmor_status shows that lsusb is in enforce mode. Only after putting /usb/bin/lsusb into complain mode the command starts to work. Best regards Heinrich --- ProblemType: Bug ApportVersion: 2.31.0+git20250220-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250225 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) DistroRelease: Ubuntu 25.04 Package: apparmor 4.1.0~beta5-0ubuntu5 PackageArchitecture: riscv64 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.14.0-4-generic root=UUID=d7adaa9d-66b4-4ce4-a45f-3651ae4bbb85 ro efi=debug earlycon=sbi sysctl.kernel.watchdog_thresh=60 ProcVersionSignature: Ubuntu 6.14.0-4.4.1~1-generic 6.14.0-rc3 Syslog: 2025-02-25T12:34:08.711312+00:00 ubuntu dbus-daemon[909]: [system] AppArmor D-Bus mediation is enabled Tags: cloud-image plucky Uname: Linux 6.14.0-4-generic riscv64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True mtime.conffile..etc.apparmor.d.lsusb: 2025-02-25T12:57:31.410467 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/200/+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 2103945] Re: Qt 6.8.3 in Ubuntu 25.04
This bug was fixed in the package qt6-translations - 6.8.3-0ubuntu1 --- qt6-translations (6.8.3-0ubuntu1) plucky; urgency=medium * New upstream release (LP: #2103945). -- Simon Quigley Thu, 27 Mar 2025 22:28:05 -0500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2103945 Title: Qt 6.8.3 in Ubuntu 25.04 Status in calibre package in Ubuntu: In Progress Status in copyq package in Ubuntu: In Progress Status in digikam package in Ubuntu: In Progress Status in dolphin package in Ubuntu: In Progress Status in dtk6log package in Ubuntu: In Progress Status in elisa-player package in Ubuntu: In Progress Status in fcitx-qt5 package in Ubuntu: In Progress Status in fcitx5-qt package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gammaray package in Ubuntu: In Progress Status in gst-plugins-good1.0 package in Ubuntu: In Progress Status in gwenview package in Ubuntu: In Progress Status in haruna package in Ubuntu: In Progress Status in itinerary package in Ubuntu: In Progress Status in kaidan package in Ubuntu: In Progress Status in kasts package in Ubuntu: In Progress Status in kate package in Ubuntu: In Progress Status in kde-cli-tools package in Ubuntu: In Progress Status in kde-spectacle package in Ubuntu: In Progress Status in kdeconnect package in Ubuntu: In Progress Status in kf6-kcmutils package in Ubuntu: In Progress Status in kf6-kcolorscheme package in Ubuntu: In Progress Status in kf6-kconfigwidgets package in Ubuntu: In Progress Status in kf6-kdbusaddons package in Ubuntu: In Progress Status in kf6-kglobalaccel package in Ubuntu: In Progress Status in kf6-kiconthemes package in Ubuntu: In Progress Status in kf6-kio package in Ubuntu: In Progress Status in kf6-kirigami package in Ubuntu: In Progress Status in kf6-kjobwidgets package in Ubuntu: In Progress Status in kf6-kwindowsystem package in Ubuntu: In Progress Status in kf6-kxmlgui package in Ubuntu: In Progress Status in kf6-qqc2-desktop-style package in Ubuntu: In Progress Status in kglobalacceld package in Ubuntu: In Progress Status in kinfocenter package in Ubuntu: In Progress Status in kirigami-addons package in Ubuntu: In Progress Status in koko package in Ubuntu: In Progress Status in konqueror package in Ubuntu: In Progress Status in kontactinterface package in Ubuntu: In Progress Status in kosmindoormap package in Ubuntu: In Progress Status in kquickimageeditor package in Ubuntu: In Progress Status in krfb package in Ubuntu: In Progress Status in kruler package in Ubuntu: In Progress Status in kscreen package in Ubuntu: In Progress Status in kscreenlocker package in Ubuntu: In Progress Status in kwayland package in Ubuntu: In Progress Status in kwin package in Ubuntu: In Progress Status in layer-shell-qt package in Ubuntu: In Progress Status in libfm-qt package in Ubuntu: In Progress Status in libkscreen package in Ubuntu: In Progress Status in libqtxdg package in Ubuntu: In Progress Status in lxqt-qtplugin package in Ubuntu: In Progress Status in nheko package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: In Progress Status in okular package in Ubuntu: In Progress Status in oxygen package in Ubuntu: In Progress Status in photoqt package in Ubuntu: In Progress Status in plasma-desktop package in Ubuntu: In Progress Status in plasma-integration package in Ubuntu: In Progress Status in plasma-mobile package in Ubuntu: In Progress Status in plasma-workspace package in Ubuntu: In Progress Status in plasma5support package in Ubuntu: In Progress Status in powerdevil package in Ubuntu: In Progress Status in pyqt6 package in Ubuntu: In Progress Status in pyside6 package in Ubuntu: In Progress Status in qcoro package in Ubuntu: In Progress Status in qgnomeplatform package in Ubuntu: In Progress Status in qt6-3d package in Ubuntu: In Progress Status in qt6-5compat package in Ubuntu: In Progress Status in qt6-base package in Ubuntu: In Progress Status in qt6-charts package in Ubuntu: In Progress Status in qt6-connectivity package in Ubuntu: In Progress Status in qt6-datavis3d package in Ubuntu: In Progress Status in qt6-declarative package in Ubuntu: In Progress Status in qt6-graphs package in Ubuntu: In Progress Status in qt6-grpc package in Ubuntu: In Progress Status in qt6-httpserver package in Ubuntu: In Progress Status in qt6-imageformats package in Ubuntu: In Progress Status in qt6-languageserver package in Ubuntu: Fix Released Status in qt6-location package in Ubuntu: In Progress Status in qt6-lottie package in Ubuntu: In Progress Status in qt6-multimedia package in Ubuntu: In Progress Status in qt6-networkauth package in Ubuntu: In Progress Status in qt6-positioning pack
[Touch-packages] [Bug 2103945] Re: Qt 6.8.3 in Ubuntu 25.04
This bug was fixed in the package qt6-languageserver - 6.8.3-0ubuntu1 --- qt6-languageserver (6.8.3-0ubuntu1) plucky; urgency=medium * New upstream release (LP: #2103945). -- Simon Quigley Thu, 27 Mar 2025 22:19:58 -0500 ** Changed in: qt6-languageserver (Ubuntu) Status: In Progress => Fix Released ** Changed in: qt6-translations (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2103945 Title: Qt 6.8.3 in Ubuntu 25.04 Status in calibre package in Ubuntu: In Progress Status in copyq package in Ubuntu: In Progress Status in digikam package in Ubuntu: In Progress Status in dolphin package in Ubuntu: In Progress Status in dtk6log package in Ubuntu: In Progress Status in elisa-player package in Ubuntu: In Progress Status in fcitx-qt5 package in Ubuntu: In Progress Status in fcitx5-qt package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gammaray package in Ubuntu: In Progress Status in gst-plugins-good1.0 package in Ubuntu: In Progress Status in gwenview package in Ubuntu: In Progress Status in haruna package in Ubuntu: In Progress Status in itinerary package in Ubuntu: In Progress Status in kaidan package in Ubuntu: In Progress Status in kasts package in Ubuntu: In Progress Status in kate package in Ubuntu: In Progress Status in kde-cli-tools package in Ubuntu: In Progress Status in kde-spectacle package in Ubuntu: In Progress Status in kdeconnect package in Ubuntu: In Progress Status in kf6-kcmutils package in Ubuntu: In Progress Status in kf6-kcolorscheme package in Ubuntu: In Progress Status in kf6-kconfigwidgets package in Ubuntu: In Progress Status in kf6-kdbusaddons package in Ubuntu: In Progress Status in kf6-kglobalaccel package in Ubuntu: In Progress Status in kf6-kiconthemes package in Ubuntu: In Progress Status in kf6-kio package in Ubuntu: In Progress Status in kf6-kirigami package in Ubuntu: In Progress Status in kf6-kjobwidgets package in Ubuntu: In Progress Status in kf6-kwindowsystem package in Ubuntu: In Progress Status in kf6-kxmlgui package in Ubuntu: In Progress Status in kf6-qqc2-desktop-style package in Ubuntu: In Progress Status in kglobalacceld package in Ubuntu: In Progress Status in kinfocenter package in Ubuntu: In Progress Status in kirigami-addons package in Ubuntu: In Progress Status in koko package in Ubuntu: In Progress Status in konqueror package in Ubuntu: In Progress Status in kontactinterface package in Ubuntu: In Progress Status in kosmindoormap package in Ubuntu: In Progress Status in kquickimageeditor package in Ubuntu: In Progress Status in krfb package in Ubuntu: In Progress Status in kruler package in Ubuntu: In Progress Status in kscreen package in Ubuntu: In Progress Status in kscreenlocker package in Ubuntu: In Progress Status in kwayland package in Ubuntu: In Progress Status in kwin package in Ubuntu: In Progress Status in layer-shell-qt package in Ubuntu: In Progress Status in libfm-qt package in Ubuntu: In Progress Status in libkscreen package in Ubuntu: In Progress Status in libqtxdg package in Ubuntu: In Progress Status in lxqt-qtplugin package in Ubuntu: In Progress Status in nheko package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: In Progress Status in okular package in Ubuntu: In Progress Status in oxygen package in Ubuntu: In Progress Status in photoqt package in Ubuntu: In Progress Status in plasma-desktop package in Ubuntu: In Progress Status in plasma-integration package in Ubuntu: In Progress Status in plasma-mobile package in Ubuntu: In Progress Status in plasma-workspace package in Ubuntu: In Progress Status in plasma5support package in Ubuntu: In Progress Status in powerdevil package in Ubuntu: In Progress Status in pyqt6 package in Ubuntu: In Progress Status in pyside6 package in Ubuntu: In Progress Status in qcoro package in Ubuntu: In Progress Status in qgnomeplatform package in Ubuntu: In Progress Status in qt6-3d package in Ubuntu: In Progress Status in qt6-5compat package in Ubuntu: In Progress Status in qt6-base package in Ubuntu: In Progress Status in qt6-charts package in Ubuntu: In Progress Status in qt6-connectivity package in Ubuntu: In Progress Status in qt6-datavis3d package in Ubuntu: In Progress Status in qt6-declarative package in Ubuntu: In Progress Status in qt6-graphs package in Ubuntu: In Progress Status in qt6-grpc package in Ubuntu: In Progress Status in qt6-httpserver package in Ubuntu: In Progress Status in qt6-imageformats package in Ubuntu: In Progress Status in qt6-languageserver package in Ubuntu: Fix Released Status in qt6-location package in Ubuntu: In Progress Status in qt6-lottie pack
[Touch-packages] [Bug 2105484] Re: Invalid "fan-map" in iproute2 JSON output
This bug was fixed in the package iproute2 - 6.14.0-1ubuntu1
---
iproute2 (6.14.0-1ubuntu1) plucky; urgency=low
* Merge from Debian unstable. Remaining changes:
- Ubuntu Fan Support
* FAN: Bump IFLA_VXLAN_FAN_MAP to match the kernel. (LP: #2105484)
-- Ubuntu Merge-o-Matic Tue, 25 Mar 2025 15:20:15
+
** Changed in: iproute2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2105484
Title:
Invalid "fan-map" in iproute2 JSON output
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in netplan.io package in Ubuntu:
Invalid
Bug description:
The netplan.io autopkgtests started failing a while ago on Plucky VMs.
The armhf based containers are unaffected, pointing towards a kernel
issue.
Local reproducer: autopkgtest -U -B netplan.io --test-name=tunnels -s
-- qemu /data/autopkgtest-plucky-amd64.img
=> see the following failure:
==
ERROR: test_tunnel_vxlan (__main__.TestNetworkd.test_tunnel_vxlan)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.oVutZW/tree/tests/integration/tunnels.py", line 281,
in test_tunnel_vxlan
json = self.iface_json('vx0')
File "/tmp/autopkgtest.oVutZW/tree/tests/integration/base.py", line 315, in
iface_json
json_dict = json.loads(out)
File "/usr/lib/python3.13/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
~~~^^^
File "/usr/lib/python3.13/json/decoder.py", line 345, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
~~~^^^
File "/usr/lib/python3.13/json/decoder.py", line 361, in raw_decode
obj, end = self.scan_once(s, idx)
~~
json.decoder.JSONDecodeError: Expecting ',' delimiter: line 1 column 379
(char 378)
Digging deeper I found the offending JSON string to be this:
'[{"ifindex":165,"ifname":"vx0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1450,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"ce:b7:0a:11:3e:75","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":0,"allmulti":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"vxlan","info_data":{"id":1337,"group":"224.0.0.5"fan-map
,"local":"10.10.10.42","link":"eth42","port_range":{"low":4000,"high":4200},"port":4567,"ttl":64,"df":"unset","ageing":100,"external":false,"learning":false,"proxy":false,"rsc":true,"l2miss":true,"l3miss":true,"udp_csum":true,"udp_zero_csum6_tx":true,"udp_zero_csum6_rx":true,"remcsum_tx":true,"remcsum_rx":true,"localbypass":true}},"num_tx_queues":1,"num_rx_queues":1,"gso_max_size":65536,"gso_max_segs":65535,"tso_max_size":524280,"tso_max_segs":65535,"gro_max_size":65536,"gso_ipv4_max_size":65536,"gro_ipv4_max_size":65536,"addr_info":[{"family":"inet6","local":"fe80::ccb7:aff:fe11:3e75","prefixlen":64,"
scope":"link","protocol":"kernel_ll","valid_life_time":4294967295,"preferred_life_time":4294967295}]}]'
There seems to be an unrelated "fan-map" word in-between.
That Netplan autopkgtest does this to trigger the issue:
"""
network:
renderer: networkd
version: 2
tunnels:
vx0:
mode: vxlan
id: 1337
link: eth0
local: 10.10.10.42
remote: 224.0.0.5 # multicast group
ttl: 64
aging: 100
port: 4567
port-range: [4000, 4200]
mac-learning: false
short-circuit: true
notifications: [l2-miss, l3-miss]
checksums: [udp, zero-udp6-tx, zero-udp6-rx, remote-tx, remote-rx] #
sd-networkd only
ethernets:
eth0:
addresses: [10.10.10.42/24]
"""
$ netplan apply
$ ip -j -d a show dev vx0
If we pipe that previous output to "json_pp" we get:
$ ip -j -d a show dev vx0 | json_pp
, or } expected while parsing object/hash, at character offset 378 (before
"fan-map ,"local":"10...") at /usr/bin/json_pp line 59.
If we try to parse it in Python (as the Netplan tests do):
>>> input
'[{"ifindex":165,"ifname":"vx0","flags":["BROADCAST","MULTICAST","UP","LOWER_UP"],"mtu":1450,"qdisc":"noqueue","operstate":"UNKNOWN","group":"default","txqlen":1000,"link_type":"ether","address":"ce:b7:0a:11:3e:75","broadcast":"ff:ff:ff:ff:ff:ff","promiscuity":0,"allmulti":0,"min_mtu":68,"max_mtu":65535,"linkinfo":{"info_kind":"vxlan","info_data":{"id":1337,"group":"224.0.0.5"fan-map
,"local":"10.10.10.42","link":"eth42","port_range":{"low":4000,"high":4200},"port":4567,"ttl":64,"df":"unset","ageing":100,"external":false,"learning":false,"proxy":false,"rsc":true,"l2miss":true,"l3miss":true,
[Touch-packages] [Bug 1869655] Re: Boot splash starts too late to be useful
The new plan for 25.10: 1. https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/290, for cleanliness and to get https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/323 included. 2. Ubuntu to use plymouth.use-simpledrm by default. ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #290 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/290 -- 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/1869655 Title: Boot splash starts too late to be useful Status in Plymouth: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Triaged Bug description: The boot splash and animations start too late to be useful. Modern systems spend all their boot time (a couple of seconds) decompressing the kernel. During that time the user only sees the static BIOS logo (ACPI BGRT). Then when Plymouth can finally start animating, the startup process is already finished and there's virtually no time left to show any useful animations. This could be fixed in: grub: By adding a splash under the BIOS logo to show some progress _before_ a Linux kernel is even started and/or plymouth: By preferencing legacy framebuffer devices (like EFI) over DRM, if we find those are available a few seconds sooner. That would also fix bug 1868240 completely, and bug 1836858 mostly as the flicker moves to when the login screen starts. To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+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 2052137] Re: bonded link goes down on reconfigure
This may be fixed as a result of bug 2003250 being fixed. -- 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/2052137 Title: bonded link goes down on reconfigure Status in systemd: Fix Released Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Jammy: Invalid Status in systemd source package in Jammy: Confirmed Bug description: systemd-networkd brings down member interfaces of a bond when they get reconfigured Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link down This has a result that a server has complete downtime for a few seconds, this has also been reported upstream https://github.com/systemd/systemd/issues/31165. A pull request has been opened to fix this https://github.com/systemd/systemd/pull/31172 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2052137/+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 2103945] Re: Qt 6.8.3 in Ubuntu 25.04
** Changed in: calibre (Ubuntu) Status: In Progress => Fix Committed ** Changed in: copyq (Ubuntu) Status: In Progress => Fix Committed ** Changed in: digikam (Ubuntu) Status: In Progress => Fix Committed ** Changed in: dolphin (Ubuntu) Status: In Progress => Fix Committed ** Changed in: dtk6log (Ubuntu) Status: In Progress => Fix Committed ** Changed in: elisa-player (Ubuntu) Status: In Progress => Fix Committed ** Changed in: fcitx-qt5 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: fcitx5-qt (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gambas3 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gammaray (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gwenview (Ubuntu) Status: In Progress => Fix Committed ** Changed in: haruna (Ubuntu) Status: In Progress => Fix Committed ** Changed in: itinerary (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kaidan (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kasts (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kate (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kde-cli-tools (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kde-spectacle (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kdeconnect (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kcmutils (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kcolorscheme (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kconfigwidgets (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kdbusaddons (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kglobalaccel (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kiconthemes (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kio (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kirigami (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kjobwidgets (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kwindowsystem (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-kxmlgui (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kf6-qqc2-desktop-style (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kglobalacceld (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kinfocenter (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kirigami-addons (Ubuntu) Status: In Progress => Fix Committed ** Changed in: koko (Ubuntu) Status: In Progress => Fix Committed ** Changed in: konqueror (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kontactinterface (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kosmindoormap (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kquickimageeditor (Ubuntu) Status: In Progress => Fix Committed ** Changed in: krfb (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kruler (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kscreen (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kscreenlocker (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kwayland (Ubuntu) Status: In Progress => Fix Committed ** Changed in: kwin (Ubuntu) Status: In Progress => Fix Committed ** Changed in: layer-shell-qt (Ubuntu) Status: In Progress => Fix Committed ** Changed in: libfm-qt (Ubuntu) Status: In Progress => Fix Committed ** Changed in: libkscreen (Ubuntu) Status: In Progress => Fix Committed ** Changed in: libqtxdg (Ubuntu) Status: In Progress => Fix Committed ** Changed in: lxqt-qtplugin (Ubuntu) Status: In Progress => Fix Committed ** Changed in: nheko (Ubuntu) Status: In Progress => Fix Committed ** Changed in: nvidia-cuda-toolkit (Ubuntu) Status: In Progress => Fix Committed ** Changed in: okular (Ubuntu) Status: In Progress => Fix Committed ** Changed in: oxygen (Ubuntu) Status: In Progress => Fix Committed ** Changed in: photoqt (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plasma-desktop (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plasma-integration (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plasma-mobile (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plasma-workspace (Ubuntu) Status: In Progress => Fix Committed ** Changed in: plasma5support (Ubuntu) Status: In Progress => Fix Committed ** Changed in: powerdevil (Ubuntu) Status: In Progress => Fix Co
[Touch-packages] [Bug 2028282] Re: [SRU] SSH pubkey authetication fails when GSSAPI enabled
re comment #24 piuparts is regressed in -release (since Jammy+):
https://autopkgtest.ubuntu.com/packages/piuparts – I triggered
migration-reference/0 tests on Jammy to confirm this.
--
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/2028282
Title:
[SRU] SSH pubkey authetication fails when GSSAPI enabled
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Jammy:
Fix Committed
Status in openssh source package in Noble:
Fix Released
Status in openssh source package in Oracular:
Fix Released
Status in openssh source package in Plucky:
Fix Released
Status in openssh package in Debian:
Fix Released
Bug description:
[ Impact ]
* Login with publickey fails when openssh server is configured to use
GSSAPI authentication, too. Error: "sign_and_send_pubkey: internal
error: initial hostkey not recorded"
* To trigger it, one needs to (a) perform a successful GSSAPI key
exchange, (b) attempt public key authentication.
* In addition, the client and the server must both have the hostbound
authentication protocol extension enabled for the problem to manifest
itself (On by default).
* This is not a very common combination, but it can happen if one has
Kerberos credentials for the correct realm but the wrong user, and a
private key for the right user.
* This SRU fixes this by adding an additional
"ssh->kex->initial_hostkey != NULL" check in
sshconnect2.c:sign_and_send_pubkey(), as suggested by upstream in
https://bugzilla.mindrot.org/show_bug.cgi?id=3406 (comment 2).
[ Test Plan ]
The reproducer was codified in autopkgtests, thanks to Colin Watson!
* Make sure to have the latest debian/tests/ssh-gssapi test case
(included as of 1:9.9p1-2, and shipped as part of this SRU),
especially the delta described in
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2028282/+attachment/5845545/+files/dep8-verifier.diff
* Execute the "ssh-gssapi" dep8 test:
$ autopkgtest -U openssh --apt-pocket=proposed=src:openssh
--test-name=ssh-gssapi -- lxd autopkgtest/ubuntu/oracular/amd64
* Confirm the log contains 3 login attempts, with the final one using the
"publickey" authentication method ("Accepted publickey for testuser..."):
"""
## Checking ssh logs to confirm publickey auth was used
Dec 14 22:44:16 sshd-gssapi.example.fake sshd-session[2213]: Accepted
publickey for testuser2020-2 from 127.0.0.1 port 43364 ssh2: ED25519
SHA256:7vF3468XCZOawompwDThLsGsnPoUaP5Ki/3KaQLq/2M
## PASS test_gssapi_keyex_pubkey_fallback
"""
[ Test Plan 2 ]
* In addition to the codified test for this specific issue, we want
to confirm normal password and publickey login are still working as
expected.
* Enable "PasswordAuthentication yes" in /etc/ssh/sshd_config &
restart ssh.service
* Login using password, confirm success
* Copy public key over to system-under-test
* Enable "PubkeyAuthentication yes" in /etc/ssh/sshd_config & restart
* Login using private key, confirm success
[ Where problems could occur ]
* This SRU tweaks the authentication logic of OpenSSH, therefore it's
a high-impact change. If something goes wrong, it could lock people
out of their remote machines.
* The change has been deployed to Debian testing and Ubuntu Plucky
since October 2024, without major issues raised.
* I've added "[ Test Plan 2 ]" to confirm normal publickey & password
login is still working as expected
[ Other Info ]
* Fixed as of 1:9.9p1-2 (e.g. in Plucky)
* Rejected upstream, due to being a bug in the Debian delta:
https://bugzilla.mindrot.org/show_bug.cgi?id=3406
* Fixed in Debian by Colin Watson:
https://salsa.debian.org/ssh-team/openssh/-/commit/7d291bb
=== original bug report ===
Since the upgrade from Ubuntu 20.04 to 22.04 the SSH login via a SSH pubkey
to our servers fails, while password and kerberos are still working.
$ssh user@server
sign_and_send_pubkey: internal error: initial hostkey not recorded
This seem related to the bugreport at openssh:
https://bugzilla.mindrot.org/show_bug.cgi?id=3406
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openssh-server 1:8.9p1-3ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Jul 20 17:25:01 2023
InstallationDate: Installed on 2020-08-24 (1060 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
SourcePackage: openssh
UpgradeStatus: Upgraded to jammy on 2023-07-20 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
[Touch-packages] [Bug 2101817] Re: gnome-shell crashed with SIGSEGV in drisw_init_screen() from driCreateNewScreen3() from dri2_create_screen() from dri2_initialize_device() from dri2_initialize()
** Changed in: mesa (Ubuntu) Importance: Undecided => Critical ** Changed in: mesa (Ubuntu) Milestone: None => ubuntu-25.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2101817 Title: gnome-shell crashed with SIGSEGV in drisw_init_screen() from driCreateNewScreen3() from dri2_create_screen() from dri2_initialize_device() from dri2_initialize() Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 48~beta-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/29b4464c85e6349b307fd74e2fd50e3e047fbe64 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2101817/+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 2105894] [NEW] package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libgl
Public bug reported: bug ProblemType: Package DistroRelease: Ubuntu 25.04 Package: libgl1-mesa-dri 25.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0 Uname: Linux 6.14.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.32.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Mon Mar 31 15:29:30 2025 DistUpgraded: Fresh install DistroCodename: plucky DistroVariant: ubuntu ErrorMessage: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2033] InstallationDate: Installed on 2024-10-17 (166 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: Positivo Informatica SA H14CU01 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=f5d51f96-5656-44b1-8df3-fee715807591 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 Python3Details: /usr/bin/python3.13, Python 3.13.2, python3-minimal, 3.13.2-2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.18ubuntu2 apt 2.9.35 SourcePackage: mesa Title: package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.02.U dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H14CU01 dmi.board.vendor: Positivo Informatica SA dmi.board.version: POSITIVO dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Informatica SA dmi.chassis.version: POSITIVO dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.02.U:bd02/20/2014:br4.6:efr1.13:svnPositivoInformaticaSA:pnH14CU01:pvr2.02.U_POS:rvnPositivoInformaticaSA:rnH14CU01:rvrPOSITIVO:cvnPositivoInformaticaSA:ct10:cvrPOSITIVO:sku3011095: dmi.product.family: To be filled by O.E.M. dmi.product.name: H14CU01 dmi.product.sku: 3011095 dmi.product.version: 2.02.U_POS dmi.sys.vendor: Positivo Informatica SA version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu13 version.libdrm2: libdrm2 2.4.123-1 version.libgl1-mesa-dri: libgl1-mesa-dri 25.0.2-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.16-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package plucky ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2105894 Title: package libgl1-mesa-dri 25.0.2-1ubuntu2 failed to install/upgrade: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) Status in mesa package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 25.04 Package: libgl1-mesa-dri 25.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 6.14.0-13.13-generic 6.14.0 Uname: Linux 6.14.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.32.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Mon Mar 31 15:29:30 2025 DistUpgraded: Fresh install DistroCodename: plucky DistroVariant: ubuntu ErrorMessage: tentando sobrescrever '/usr/lib/x86_64-linux-gnu/libglapi.so.0', que também está no pacote libglapi-mesa:amd64 (24.3.4-3ubuntu1) GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2033] InstallationDate: Installed on 2024-10-17 (166 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: Positivo Informatica SA H14CU01 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=f5d51f96-5656-44b1-8df3-fee715807591 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 Python3Details: /usr/bin/python3.13, Python 3.13.2, python3-minimal, 3.13.2-2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.18ubuntu2 apt 2.9.35 SourcePackage: mesa Title:
[Touch-packages] [Bug 2105892] [NEW] i386: seed inclusion: rpds-py
Public bug reported: I came here following https://wiki.ubuntu.com/i386#How_to_expand_i386_port_scope Assuming this is the right thing to do, I would like to ask that src:rpds-py also builds on i386. The reason is that currently jq is an FTBFS[1] in oracular and plucky because: jq -> Build-Depends: python3-jsonschema -> Build-Depends/Depends: python3-rpds-py and bin:python3-rpds-py is not availeble for i386. jq has been copied-over from noble for oracular and plucky, so jq@i386 exists in the archive for these ubuntu releases, and even runs, but can't be rebuild. The list of reverse-depends of jq is quite large, many packages that currently build on i386 require it, so dropping jq@i386 at this point would be a lot of work. Maybe something for the QQ+ releases of ubuntu, but not plucky. 1. https://bugs.launchpad.net/ubuntu/+source/jq/+bug/2104170 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2105892 Title: i386: seed inclusion: rpds-py Status in ubuntu-meta package in Ubuntu: New Bug description: I came here following https://wiki.ubuntu.com/i386#How_to_expand_i386_port_scope Assuming this is the right thing to do, I would like to ask that src:rpds-py also builds on i386. The reason is that currently jq is an FTBFS[1] in oracular and plucky because: jq -> Build-Depends: python3-jsonschema -> Build-Depends/Depends: python3-rpds-py and bin:python3-rpds-py is not availeble for i386. jq has been copied-over from noble for oracular and plucky, so jq@i386 exists in the archive for these ubuntu releases, and even runs, but can't be rebuild. The list of reverse-depends of jq is quite large, many packages that currently build on i386 require it, so dropping jq@i386 at this point would be a lot of work. Maybe something for the QQ+ releases of ubuntu, but not plucky. 1. https://bugs.launchpad.net/ubuntu/+source/jq/+bug/2104170 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2105892/+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
