[Touch-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** No longer affects: linux (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Tags added: fixed-in-22.2.0 fixed-upstream ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released ** Tags added: rls-jj-incoming -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star
[Touch-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** Changed in: mesa Status: New => Fix Released -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed
Robie; thanks for the testing instructions link. verification-done-jammy; This bug is testable on AWS EC2 Graviton 1/2/3 (c6g,g5g,r6g,t4g) the cheapest of which is the t4g.nano ranging from 0.00280 0.00670 $USD/h depending on the region. So that's what I did. # echo -e "APT::Get::Always-Include-Phased-Updates: 1;" > /etc/apt/apt.conf.d/99phased-updates # apt clean && apt update && apt upgrade # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # echo "\"...The grub SRU has been rolled back...\" passed the test because only the old version was listed" # cat /dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu10 APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 Packages Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # echo "\"... to jammy-proposed...\" passed the test because both versions were listed" # shutdown -r now # apt show grub-efi-arm64 2>/dev/null | grep Version Version: 2.06-2ubuntu10 # echo "\"...fixed...\" passed the test because the new version is in use, apt worked, and reboot worked." ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- 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: In Progress Status in grub2-signed package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: [Impact] Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade anything anymore, for example, see the original bug report below. [Test plan] We cannot reproduce the exact failure here, but we have included a minimal test case that triggers the same error in the integration test test-phased-updates-upgrade. The test suite is exhaustive and covers more than a human reasonably can, especially since we also cannot publish broken updates again to get people to test the fix. [Where problems could occur] This is a one word fix in the solver. When deciding whether a depends could be kept back, we accidentally looked at the package declaring the dependency instead of the package we depend upon. Of course this might unearth other fancy solver bugs. There is one limitation in that this only applies to "Protected" packages (not in the Protected field sense, but if you "Protect" the change in the solver), which is *mostly* triggered only if you have held packages or phased updates, so workarounds should always be easy. [Original bug report] # apt clean # apt update Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed E: Broken packages # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu10 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg
[Touch-packages] [Bug 1991139] Re: prompted to remove systemd-hwe-hwdb but re-installed via updates
** Tags added: foundations-triage-discuss -- 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/1991139 Title: prompted to remove systemd-hwe-hwdb but re-installed via updates Status in apt package in Ubuntu: Confirmed Bug description: sudo apt upgrade gives me this : The following package was automatically installed and is no longer required: systemd-hwe-hwdb Use 'sudo apt autoremove' to remove it. The following packages have been kept back: libnss-systemd libpam-systemd libspeechd2 libsystemd0 libudev1 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng systemd systemd-oomd systemd-sysv systemd-timesyncd udev 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. sudo apt autoremove removes the no longer required systemd-hwe-hwdb but the software updater brings it back & this cycle goes on in loop. kindly check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1991139/+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 1991139] Re: prompted to remove systemd-hwe-hwdb but re-installed via updates
> this bug report should not be marked solved yet. duly noted. have made the changes. pardon me for the confusion. ** Summary changed: - prompted to remove systemd-hwe-hwdb but re-installed via updates [SOLVED] + prompted to remove systemd-hwe-hwdb but re-installed via updates -- 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/1991139 Title: prompted to remove systemd-hwe-hwdb but re-installed via updates Status in apt package in Ubuntu: Confirmed Bug description: sudo apt upgrade gives me this : The following package was automatically installed and is no longer required: systemd-hwe-hwdb Use 'sudo apt autoremove' to remove it. The following packages have been kept back: libnss-systemd libpam-systemd libspeechd2 libsystemd0 libudev1 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng systemd systemd-oomd systemd-sysv systemd-timesyncd udev 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. sudo apt autoremove removes the no longer required systemd-hwe-hwdb but the software updater brings it back & this cycle goes on in loop. kindly check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1991139/+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 1991139] Re: prompted to remove systemd-hwe-hwdb but re-installed via updates [SOLVED]
** Package changed: ubuntu => apt (Ubuntu) -- 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/1991139 Title: prompted to remove systemd-hwe-hwdb but re-installed via updates Status in apt package in Ubuntu: Confirmed Bug description: sudo apt upgrade gives me this : The following package was automatically installed and is no longer required: systemd-hwe-hwdb Use 'sudo apt autoremove' to remove it. The following packages have been kept back: libnss-systemd libpam-systemd libspeechd2 libsystemd0 libudev1 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng systemd systemd-oomd systemd-sysv systemd-timesyncd udev 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. sudo apt autoremove removes the no longer required systemd-hwe-hwdb but the software updater brings it back & this cycle goes on in loop. kindly check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1991139/+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 1991139] [NEW] prompted to remove systemd-hwe-hwdb but re-installed via updates [SOLVED]
You have been subscribed to a public bug: sudo apt upgrade gives me this : The following package was automatically installed and is no longer required: systemd-hwe-hwdb Use 'sudo apt autoremove' to remove it. The following packages have been kept back: libnss-systemd libpam-systemd libspeechd2 libsystemd0 libudev1 python3-speechd speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng systemd systemd-oomd systemd-sysv systemd-timesyncd udev 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. sudo apt autoremove removes the no longer required systemd-hwe-hwdb but the software updater brings it back & this cycle goes on in loop. kindly check. ** Affects: apt (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment jammy systemd-hwe-hwdb -- prompted to remove systemd-hwe-hwdb but re-installed via updates [SOLVED] https://bugs.launchpad.net/bugs/1991139 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 1991146] Re: ibus-daemon crashed with SIGABRT
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+attachment/5619840/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1991146 Title: ibus-daemon crashed with SIGABRT Status in ibus package in Ubuntu: New Bug description: Was logged on to user1 and did a Power off>Switch User to user2. Logged off user2 and signed in to user1. This crash was waiting. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Sep 28 14:22:49 2022 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2022-09-17 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: ibus-daemon --panel disable --xim ProcEnviron: LANG=en_US.UTF-8 Signal: 6 SourcePackage: ibus StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+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 1991148] Re: Error message upon startup, no bug apparent in UI user experience
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1990200, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991148/+attachment/5619851/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619853/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619857/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619858/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619859/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619860/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619861/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1990200 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1991148 Title: Error message upon startup, no bug apparent in UI user experience Status in gnome-online-accounts package in Ubuntu: New Bug description: 22.10 First start up after upgrading to 22.10 Beta. Unknown why error message was displayed. Hope this is helpful at all. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 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 Date: Wed Sep 28 20:38:33 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2021-12-04 (297 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-09-28 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I've managed to get my Lenovo Legion 7 16ACHg6 speakers working on kernel 5.18.x by setting the following kernel configuration CONFIG_SND_SOC_CS35L41_I2C=m CONFIG_SERIAL_MULTI_INSTANTIATE=m However, kernel 5.19.x seems to break it as with the same kernel config, the modules are loaded by do not work. Apart from the speaker, I'm having the same issue with the touchpad (works on 5.18, but not on 5.19). Any ideas why it would work on 5.18, but not on 5.19? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to Gergo K from comment #689) > The TAS2563 works without the firmware (tuning file). > Documentation: > https://www.ti.com/product/TAS2553 > > However there is an android driver with firmware loading support. > https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/ > Or a mainline RFC: > https://lkml.org/lkml/2020/6/9/800 > > > The bass speakers can be enabled with: > i2cset 3 0x4c 0x2 0 > i2cset 3 0x4d 0x2 0 > > they are listening on 0x48 too, so in one turn: > i2cset 3 0x48 0x2 0 > > I don't know how safe it is to use it this way. > > They have to be enabled after suspend, and if you plug in-out the headphone > (only if auto mute is enabled). OK, that works! But what can I do to make this register (3 0x38 0x02 0) set automatically? Does that have something to do with the power settings under /sys/bus/i2c/devices/i2c-3/device/power/*? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
Thank you very much @Jonathan. I can confirm removing the iwd.conf did the trick on my end. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 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 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990729] Re: gdb crashes when run from VSCode
Should I report this issue with Software and Updater not keeping the pre-released check after I try to change the Update menu to select all changes? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1990729 Title: gdb crashes when run from VSCode Status in gdb package in Ubuntu: New Bug description: I had no pre-existing breakpoints in VSCode, then added a breakpoint, and used F5 to run the debugger to the one breakpoint. It crashed before it got there. This is a C++ executable compiled for debugging using CMAKE. I can successfully debug the program using the TUI mode of gdb, so I think the problem likes in the vscode interface to gdb. /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] /build/gdb-wIRHdd/gdb-12.0.90/gdb/value.c:1731: internal-error: value_copy: Assertion `arg->contents != nullptr' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.0.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21 Uname: Linux 5.14.0-1051-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 11:10:11 2022 InstallationDate: Installed on 2022-02-15 (221 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdb UpgradeStatus: Upgraded to jammy on 2022-09-06 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1990729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
** Description changed:
[Impact]
When attempting to authenticate against a Windows Active Directory
server configured to require SASL channel binding over SSL/TLS ldap
connections (ldaps), authentication will fail stating invalid
credentials as the cause.
This is due to cyrus-sasl2 missing the sasl channel binding feature of
GSSAPI/GSS-SPNEGO.
Furthermore, for interoperability with Windows Active Directory Server,
it's necessary to be able to set the SASL SSF (security strength factor)
to 0 (zero) when it's used over an already encrypted connection like
ldaps.
To fix these issues, these items are added as patches from a set of
upstream commits.
[Test Plan]
To reproduce this issue, a machine running Windows with Active Directory
must be available over the network. As an example, for Windows Server
2019 Evaluation:
The ISO can be downloaded from
https://www.microsoft.com/en-us/evalcenter/download-windows-server-2019
Install Windows Server, Active Directory, and Certificate Services, then add
the following registry changes from
https://support.microsoft.com/en-us/topic/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
"ldapserverintegrity"=dword:0002
"LdapEnforceChannelBinding"=dword:0002
Also enable LDAP logging for Active Directory:
Reg Add
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics /v
"16 LDAP Interface Events" /t REG_DWORD /d 2
With the Windows machine available, set up an Ubuntu system on a network
that can reach the Windows server. This works best and with less
configuration needed if the Windows server is acting as DNS and DHCP
server for that network.
Install packages with:
$ sudo apt install ldap-utils libsasl2-modules-gssapi-mit krb5-user
When the Configuring Kerberos Authentication prompt shows up, use the realm
of the Windows Server. If prompted, use the windows server IP for the Kerberos
KDC and admin servers.
Save the Windows Server AD CA certificate file as
/usr/local/share/ca-certificates/ad-ca.crt then run
$ sudo update-ca-certificates
In /etc/ldap/ldap.conf set
BASE dc={REALM NAME} # split the domain components like dc=example,dc=com
URI ldaps://{WINDOWS SERVER MACHINE NAME}.{REALM NAME}
With Ubuntu set up, the actual test can be run:
$ kinit
Enter Password
$ ldapwhoami -Y GSSAPI -O maxssf=0 -o SASL_CBINDING=tls-endpoint
Prior to the fix, this would display the following:
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
With the fix, the authentication will display the user information.
The same happens with
$ ldapwhoami -Y GSS-SPNEGO -O maxssf=0 -o SASL_CBINDING=tls-endpoint
SASL/GSS-SPNEGO authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
[Where problems could occur]
Based on the patches added, any problems that show up would likely
occour either in the gssapi plugin or the SASL2 macros. The two files
changed are plugins/gssapi.c and m4/sasl2.m4, along with some tests.
There are various situations apart from this one in which GSS-API can be
used, and this change may affect the way some of these interactions over
the network are handled.
+ In parallel with this SRU, we tested, in jammy, cyrus-imapd server and
+ gssapi authentication over tls, with and without this updated sasl
+ package. Using as a client thunderbird, imtest (from cyrus-imapd-
+ clients), curl (it has imap support), mutt, evolution. All authenticated
+ without issues. Also postfix with gssapi authentication was tested, and
+ also worked.
+
[Other Info]
This issue was fixed in kinetic in version 2.1.28+dfsg-6ubuntu2
[Original Description]
> Are you uncertain if your issue is really a bug?
Effect is an authentication error. Root case is a "missing feature" (see
below) and requires updating dependencies, downporting.
> If you are certain this is a bug please include the source package the bug
is in.
It's in the interaction between three libraries: openldap, cyrus-sasl, krb5
> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Broken in 18.04 and also in 20.10 (I guess it's also broken in anything
inbetween)
> 2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1
ldap-utils: 2.4.53+dfsg-1ubuntu1.2
libgssapi-krb5-2: 1.17-10ubuntu0.1
> 3) What you expected to happen
#
[Touch-packages] [Bug 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
** Description changed:
[Impact]
- When attempting to bind to a SASL channel using GSSAPI or GSS-SPNEGO for
- Windows Active Directory, authentication will fail stating invalid
+ When attempting to authenticate against a Windows Active Directory
+ server configured to require SASL channel binding over SSL/TLS ldap
+ connections (ldaps), authentication will fail stating invalid
credentials as the cause.
- This is due to cyrus-sasl2 missing the feature of GSSAPI/GSS-SPNEGO
- channel binding and interoperability with Windows over TLS.
+ This is due to cyrus-sasl2 missing the sasl channel binding feature of
+ GSSAPI/GSS-SPNEGO.
- To fix the issue, these items are added as patches from a set of
+ Furthermore, for interoperability with Windows Active Directory Server,
+ it's necessary to be able to set the SASL SSF (security strength factor)
+ to 0 (zero) when it's used over an already encrypted connection like
+ ldaps.
+
+ To fix these issues, these items are added as patches from a set of
upstream commits.
[Test Plan]
To reproduce this issue, a machine running Windows with Active Directory
must be available over the network. As an example, for Windows Server
2019 Evaluation:
The ISO can be downloaded from
https://www.microsoft.com/en-us/evalcenter/download-windows-server-2019
Install Windows Server and Active Directory, then add the following registry
changes from
https://support.microsoft.com/en-us/topic/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
"ldapserverintegrity"=dword:0002
"LdapEnforceChannelBinding"=dword:0002
Also enable LDAP logging for Active Directory:
Reg Add
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics /v
"16 LDAP Interface Events" /t REG_DWORD /d 2
-
- With the Windows machine available, set up an Ubuntu system and do the
following:
+ With the Windows machine available, set up an Ubuntu system and do the
+ following:
Connect to the Windows machine's network
Reboot and check if an IP from Windows Server was provided
Install packages with:
$ sudo apt install ldap-utils libsasl2-modules-gssapi-mit krb5-user
When the Configuring Kerberos Authentication prompt shows up, use the realm
of the Windows Server
Save the Windows Server AD CA certificate file as
/usr/local/share/ca-certificates/ad-ca.crt then run
$ sudo update-ca-certificates
In /etc/ldap/ldap.conf set
BASE dc={REALM NAME}
URI ldaps://{WINDOWS SERVER MACHINE NAME}.{REALM NAME}
With Ubuntu set up, the actual test can be run:
$ kinit
Enter Password
$ ldapwhoami -Y GSSAPI -O maxssf=0 -o SASL_CBINDING=tls-endpoint
Prior to the fix, this would display the following:
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
- additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
+ additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
With the fix, the authentication will display the user information.
- The same happens with
+ The same happens with
$ ldapwhoami -Y GSS-SPNEGO -O maxssf=0 -o SASL_CBINDING=tls-endpoint
SASL/GSS-SPNEGO authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
- additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
+ additional info: 80090346: LdapErr: DSID-..., comment:
AcceptSecurityContext error, data 80090346, v4563
[Where problems could occur]
Based on the patches added, any problems that show up would likely
occour either in the gssapi plugin or the SASL2 macros. The two files
changed are plugins/gssapi.c and m4/sasl2.m4, along with some tests.
There are various situations apart from this one in which GSS-API can be
used, and this change may affect the way some of these interactions over
the network are handled.
[Other Info]
-
+
This issue was fixed in kinetic in version 2.1.28+dfsg-6ubuntu2
[Original Description]
> Are you uncertain if your issue is really a bug?
Effect is an authentication error. Root case is a "missing feature" (see
below) and requires updating dependencies, downporting.
> If you are certain this is a bug please include the source package the bug
is in.
It's in the interaction between three libraries: openldap, cyrus-sasl, krb5
> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Broken in 18.04 and also in 20.10 (I guess it's also broken in anything
inbetween)
> 2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1
[Touch-packages] [Bug 1991143] Re: Systemd reboot halt Lenovo ThinkPad x230 running jammy
I forgot to add mandatory system details: ❯ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 ii systemd-sysv 249.11-0ubuntu3.4 amd64system and service manager - SysV links -- 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: New 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 1991143] [NEW] Systemd reboot halt Lenovo ThinkPad x230 running jammy
Public bug reported: 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. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: halt reboot systemd -- 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: New 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 1991141] [NEW] "aa-disable" fails on autopkgtest.u.c (armhf)
Public bug reported: This bug affects django-auth-ldap and other packages that call "aa- disable" in a dep8 test. For some reason that I wasn't able to determine, the command fails when it's executed on autopkgtest.ubuntu.com, but only when run on armhf. The error looks like this: ERROR: /sbin/apparmor_parser: Unable to remove "/usr/sbin/slapd". Permission denied; attempted to load a profile while confined? Disabling /usr/sbin/slapd. https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/armhf/d/django-auth-ldap/20220927_015039_0a1ae@/log.gz I wasn't able to reproduce the problem. I believe it's something specific to how autopkgtest.u.c launches the armhf containers. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: django-auth-ldap (Ubuntu) Importance: Undecided Status: New ** Affects: volatildap (Ubuntu) Importance: Undecided Status: New ** Also affects: volatildap (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1991141 Title: "aa-disable" fails on autopkgtest.u.c (armhf) Status in apparmor package in Ubuntu: New Status in django-auth-ldap package in Ubuntu: New Status in volatildap package in Ubuntu: New Bug description: This bug affects django-auth-ldap and other packages that call "aa- disable" in a dep8 test. For some reason that I wasn't able to determine, the command fails when it's executed on autopkgtest.ubuntu.com, but only when run on armhf. The error looks like this: ERROR: /sbin/apparmor_parser: Unable to remove "/usr/sbin/slapd". Permission denied; attempted to load a profile while confined? Disabling /usr/sbin/slapd. https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/armhf/d/django-auth-ldap/20220927_015039_0a1ae@/log.gz I wasn't able to reproduce the problem. I believe it's something specific to how autopkgtest.u.c launches the armhf containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1991141/+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] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
In terms of risk, touching apt is always going to be high risk because users need apt to revert or upgrade away from any regression. QA is therefore essential. Normally I'd like this to "bake" in the development release first, but given the nature of the bug, that's probably not going to give us any practical benefit over testing this in jammy- proposed. In terms of the details of testing, I can't think of anything that we could do better over relying on the test suite, and I'm happy to see that these bugfixes come with corresponding tests. Since Kinetic is in beta freeze but this bugfix is urgent, I think it makes sense to accept this into jammy-proposed immediately to maximise testing opportunity. ** Tags removed: foundtations-todo ** Tags added: foundations-todo ** Changed in: apt (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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: In Progress Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Plan - autopkgtests run the integration test suite. We have added a simplified version of the EDSP file attached here with additional fields for the phasing info (and support to the EDSP reader) to automatically check this as part of the test suite. The changes made were to essentially only include installed and phased python3.10, python3-defaults upgrades. And then we run the solver on that and check the exact actions it takes, which is an autoremove of systemd-hwe-hwdb which is fine. Before the change, it was removing half the system. Original test case: This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Where problems could occur -- This fix touches the dist-upgrade code and the enablement for the test case also touches the EDSP writer and reader, so problems can occur in the EDSP debugging bits and during dist-upgrades, related to phasing upgrades. Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp python-apt-common python3-blinker python3-certifi python3-cffi-backend python3-chardet python3-click python3-colorama python3-cryptography python3-dateutil python3-debconf python3-debian python3-defer python3-distro-info python3-fasteners python3-future python3-httplib2 python3-idna python3-importlib-metadata python3-jeepney
[Touch-packages] [Bug 1990586] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted apt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.4.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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: In Progress Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system Test Plan - autopkgtests run the integration test suite. We have added a simplified version of the EDSP file attached here with additional fields for the phasing info (and support to the EDSP reader) to automatically check this as part of the test suite. The changes made were to essentially only include installed and phased python3.10, python3-defaults upgrades. And then we run the solver on that and check the exact actions it takes, which is an autoremove of systemd-hwe-hwdb which is fine. Before the change, it was removing half the system. Original test case: This test case won't work as well if phasing is set to 0% or 100% Create /etc/apt/apt.conf.d/phasing and set its contents to APT::Machine-ID 2c030cfce3b4487f9810f12a3ac6e87c; Then run sudo apt update sudo apt dist-upgrade Where problems could occur -- This fix touches the dist-upgrade code and the enablement for the test case also touches the EDSP writer and reader, so problems can occur in the EDSP debugging bits and during dist-upgrades, related to phasing upgrades. Workaround In Advance - Don't run sudo apt dist-upgrade. Just run sudo apt upgrade Or use Update Manager or the Ubuntu Store to apply updates Workaround Afterwards - Fortunately, apt phasing is ignored for new package installs. So to get your Ubuntu Desktop back, just run sudo apt install ubuntu-desktop Other Info -- These 3 updates were published today: python3-stdlib-extensions python3-defaults python3.10 Suggested Fix - Fully phase those 3 source packages to 100% Apt Output -- The following packages were automatically installed and are no longer required: apg apport-symptoms aptdaemon-data avahi-utils cups-pk-helper distro-info gdb gedit-common genisoimage gir1.2-dbusmenu-glib-0.4 gir1.2-dee-1.0 gir1.2-goa-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gtksource-4 gir1.2-gudev-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-rb-3.0 gir1.2-secret-1 gir1.2-snapd-1 gir1.2-totem-1.0 gir1.2-totemplparser-1.0 gir1.2-udisks-2.0 gir1.2-unity-7.0 gir1.2-vte-2.91 gir1.2-wnck-3.0 gnome-control-center-faces gnome-software-common gnome-terminal-data hplip-data ibus-data ibus-gtk4 libbabeltrace1 libboost-regex1.74.0 libc6-dbg libcolord-gtk1 libdebuginfod-common libdebuginfod1 libdmapsharing-3.0-2 libglu1-mesa libgpod-common libgpod4 libgsound0 libgssdp-1.2-0 libgupnp-1.2-1 libgupnp-av-1.0-3 libgupnp-dlna-2.0-4 libhpmud0 libimagequant0 libipt2 liblirc-client0 libmalcontent-0-0 libnetplan0 libraqm0 librsync2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libsane-hpaio libsgutils2-2 libsource-highlight-common libsource-highlight4v5 libwhoopsie-preferences0 libwnck-3-0 libwnck-3-common libxatracker2 libxres1 libxss1 libxvmc1 mobile-broadband-provider-info network-manager-gnome patch printer-driver-hpcups printer-driver-postscript-hp
[Touch-packages] [Bug 1990684] Please test proposed package
Hello elatllat, or anyone else affected, Accepted apt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.4.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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: In Progress Status in grub2-signed package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: [Impact] Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade anything anymore, for example, see the original bug report below. [Test plan] We cannot reproduce the exact failure here, but we have included a minimal test case that triggers the same error in the integration test test-phased-updates-upgrade. The test suite is exhaustive and covers more than a human reasonably can, especially since we also cannot publish broken updates again to get people to test the fix. [Where problems could occur] This is a one word fix in the solver. When deciding whether a depends could be kept back, we accidentally looked at the package declaring the dependency instead of the package we depend upon. Of course this might unearth other fancy solver bugs. There is one limitation in that this only applies to "Protected" packages (not in the Protected field sense, but if you "Protect" the change in the solver), which is *mostly* triggered only if you have held packages or phased updates, so workarounds should always be easy. [Original bug report] # apt clean # apt update Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed E: Broken packages # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu10 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7) Package: grub-efi-arm64-signed Depends: grub-efi-arm64 (= 2.06-2ubuntu7) # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10) Package: grub-efi-arm64-signed Depends:
[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed
In terms of risk, touching apt is always going to be high risk because users need apt to revert or upgrade away from any regression. QA is therefore essential. Normally I'd like this to "bake" in the development release first, but given the nature of the bug, that's probably not going to give us any practical benefit over testing this in jammy- proposed. In terms of the details of testing, I can't think of anything that we could do better over relying on the test suite, and I'm happy to see that these bugfixes come with corresponding tests. Since Kinetic is in beta freeze but this bugfix is urgent, I think it makes sense to accept this into jammy-proposed immediately to maximise testing opportunity. ** Changed in: apt (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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: In Progress Status in grub2-signed package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Bug description: [Impact] Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade anything anymore, for example, see the original bug report below. [Test plan] We cannot reproduce the exact failure here, but we have included a minimal test case that triggers the same error in the integration test test-phased-updates-upgrade. The test suite is exhaustive and covers more than a human reasonably can, especially since we also cannot publish broken updates again to get people to test the fix. [Where problems could occur] This is a one word fix in the solver. When deciding whether a depends could be kept back, we accidentally looked at the package declaring the dependency instead of the package we depend upon. Of course this might unearth other fancy solver bugs. There is one limitation in that this only applies to "Protected" packages (not in the Protected field sense, but if you "Protect" the change in the solver), which is *mostly* triggered only if you have held packages or phased updates, so workarounds should always be easy. [Original bug report] # apt clean # apt update Hit:1 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy InRelease Hit:2 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease Hit:3 http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed E: Broken packages # apt show -a grub-efi-arm64 2>/dev/null | grep -P "Version:|APT-Sources:" Version: 2.06-2ubuntu10 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages Version: 2.06-2ubuntu7 APT-Sources: http://ca-central-1.ec2.ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy/main/binary-arm64/Packages.gz; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu7) Package: grub-efi-arm64-signed Depends: grub-efi-arm64 (= 2.06-2ubuntu7) # curl -s "http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/main/binary-arm64/Packages.gz; | zgrep -B 13 "Depends: grub-efi-arm64" | grep -P "Package:|Depends:" Package: grub-efi-arm64-dbg Depends: grub-efi-arm64-bin (= 2.06-2ubuntu10) Package: grub-efi-arm64-signed Depends: grub-efi-arm64 (= 2.06-2ubuntu10) [[Workaround]] echo "APT::Get::Never-Include-Phased-Updates: 1;" > /etc/apt/apt.conf.d/99phased-updates 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:
[Touch-packages] [Bug 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
The attachment "lp-1991067-fix-gnutls-ftbfs.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: In Progress Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981042] Re: /etc/localtime symlink not correctly handled when using /etc/writable
** Tags removed: foundations-todo -- 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/1981042 Title: /etc/localtime symlink not correctly handled when using /etc/writable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink to /etc/writable/localtime (which in itself if a symlink). Systemd doesn't handle this correctly when doing firstboot or using inotify to watch for changes to localtime. [Test Plan] This is somewhat hard to test, the following situations need to be reproduced: - On firstboot the timezone link will not be read correctly, it will with this change. - Starting a timer unit and then changing timezone will cause it not to occur at the correct time. [Where problems could occur] This could potentially break other users of localtime, however the change is similar to existing changes which have been in Ubuntu's version of systemd for some time. The change detects the /etc/writable case and if not should have the same existing behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Tags removed: foundations-todo -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. [Test Plan] This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. * Make sure nfs-common is installed: $ apt install nfs-common -y * Check the NFS server exports using showmount: $ showmount -e $NFS_SERVER_IP Export list for $NFS_SERVER_IP: /data * * Add the appropriate entries to /etc/fstab. In this example, we will make /home2 a bind mount to /data/home: # /etc/fstab $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0 /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 * Check systemctl status home2.mount. On an affected system, we should see a permission denied error: $ systemctl status home2.mount x home2.mount - /home2 Loaded: loaded (/etc/fstab; generated) Active: failed (Result: resources) Where: /home2 What: /data/home Docs: man:fstab(5) man:systemd-fstab-generator(8) systemd[1]: home2.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied systemd[1]: home2.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home2. * On a patched system, we expect /home2 to be mounted successfully. [Where problems could occur] The patch makes it so that systemd will not fail bind mounts immediately if creating the directory fails. Thus, any regressions would be seen during bind mounts with systemd. N.B. that this patch restores previous behavior in systemd. [Original Description] I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to:
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
** Tags removed: foundations-todo
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Invalid
Status in systemd source package in Jammy:
Fix Released
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1982462] Re: Some modprobe loading services requested by the pstore service fail
** Tags removed: foundations-todo -- 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/1982462 Title: Some modprobe loading services requested by the pstore service fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] It has been detected that some modprobe services fail on UC22 after the jammy upgrade 249.11-0ubuntu3.4: $ systemctl --system --no-ask-password --no-pager list-units --state=failed Failed units: UNIT LOAD ACTIVE SUBDESCRIPTION ● modprobe@chromeos_pstore.service loaded failed failed Load Kernel Module chromeos_pstore ● modprobe@efi_pstore.service loaded failed failed Load Kernel Module efi_pstore ● modprobe@mtdpstore.service loaded failed failed Load Kernel Module mtdpstore ● modprobe@pstore_blk.service loaded failed failed Load Kernel Module pstore_blk ● modprobe@pstore_zone.service loaded failed failed Load Kernel Module pstore_zone ● modprobe@ramoops.service loaded failed failed Load Kernel Module ramoops This happens because of some changes to systemd-pstore.service that now has: After=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service Wants=modprobe@efi_pstore.service modprobe@mtdpstore.service modprobe@chromeos_pstore.service modprobe@ramoops.service modprobe@pstore_zone.service modprobe@pstore_blk.service This causes too many tries of the modprobe services, that fail in the end with Jul 20 09:02:39 ubuntu systemd[1]: modprobe@chromeos_pstore.service: Start request repeated too quickly. Although we have seen this only on UC22, it potentially can affect classic systems as well, as systemd-pstore.service is re-tried there a few times too. See https://github.com/snapcore/core-base/issues/72 for more details. A fix for this is available upstream: https://github.com/systemd/systemd/commit/9625350e5381a68c1179ae4581e7586c206663e1 [Test Plan] Start the device and check that there is no modprobe-pstore related failed service. This is racy, so a few tries will be needed to make sure things are fine. [Where problems could occur] The modprobe services are usually dependencies from other services, so it should be fine if the retry behavior is controlled by those other services. Risk should be small. If something goes wrong we might see a lot of restarts for these services. [Other Info] Testing should happen on UC22 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982462/+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 1989969] Re: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el
** Tags removed: foundations-todo -- 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/1989969 Title: autopkgtest TEST-36-NUMAPOLICY failure on ppc64el Status in systemd package in Ubuntu: Fix Released Bug description: In Kinetic, TEST-36-NUMAPOLICY from upstream-2 fails very frequently on ppc64el. See for example: https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/ppc64el/s/systemd/20220908_195425_da51e@/log.gz, and the full kinetic ppc64el history: https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el. It has passed on very few occasions. I have tried to debug this locally but have gotten very little useful information (i.e. not enough to open an upstream bug). For now it is probably best to denylist this test on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989969/+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 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed
** Description changed: + [Impact] + Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade + anything anymore + + [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: grub2-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] Phased updates with interdependencies can become uninstallable, breaking the upgrade command (and presumably dist-upgrade), so it cannot upgrade - anything anymore + 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
[Touch-packages] [Bug 1989596] Re: Completing Copying of Logs stage takes a very long time
I believe this was a side effect of bug 1990278, because it changed the way lb_chroot_resolv configured /etc/resolv.conf in the chroot, since systemd-resolved was not installed yet. Since the latest daily image built with systemd 251.4-1ubuntu6, the issue is no longer present. ** Tags removed: foundations-todo ** Changed in: ubiquity (Ubuntu Kinetic) Assignee: Nick Rosbrook (enr0n) => (unassigned) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: ubiquity (Ubuntu Kinetic) Status: Triaged => 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/1989596 Title: Completing Copying of Logs stage takes a very long time Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in systemd source package in Kinetic: Fix Released Status in ubiquity source package in Kinetic: Invalid Bug description: Standard virtualbox install of Ubuntu Budgie daily ISO 14th Sept. No extra options chosen. Install from live session or just from the normal Try screen takes the same amount of time It is taking several minutes to complete the Copying of Logs stage. This is clearly a regression of 22.04 where this stage takes a second or two. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ubiquity 22.10.6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.474 CurrentDesktop: Budgie:GNOME Date: Wed Sep 14 16:55:44 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220914) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1989596/+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] Re: 22.04: python3* mismatched phasing breaks dist-upgrades
** Description changed: Impact -- Users who manually run sudo apt dist-upgrade without paying attention can remove essential parts of their system - Test Case + 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 whoopsie-preferences x11-apps x11-session-utils xbitmaps xbrlapi xcvt xfonts-scalable xinit xinput xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: apport apport-gtk aptdaemon apturl apturl-common command-not-found deja-dup duplicity gedit gnome-control-center gnome-online-accounts gnome-software gnome-software-plugin-snap gnome-terminal hplip ibus ibus-table language-selector-common language-selector-gnome nautilus-extension-gnome-terminal nautilus-share netplan.io networkd-dispatcher orca python3-apport python3-apt
[Touch-packages] [Bug 1990684] Re: grub-efi-arm64-signed : Depends: grub-efi-arm64 (= 2.06-2ubuntu7) but 2.06-2ubuntu10 is to be installed
** Tags added: foundations-todo ** Also affects: apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Jammy) Status: New => Triaged ** No longer affects: grub2-signed (Ubuntu Jammy) ** Changed in: apt (Ubuntu Jammy) Assignee: (unassigned) => Julian Andres Klode (juliank) -- 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: In Progress Status in grub2-signed package in Ubuntu: Fix Released Status in apt source package in Jammy: Triaged 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: grub2-signed UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy
Two ideas, one of which I've already mentioned above: 1) You could migrate the address and port settings from sshd_config to listen.conf _before_ installing the new sshd_config, so that they will be preserved even if the config gets replaced with the vendor version because of a merge conflict like it was in my case. 2) You could have the preinst script detect if the service is currently enabled and going to be switched to the socket, and if so, pop up an interactive warning explaining the change and telling the user where to look for more info, like many other packages do, e.g., the Docker restart warning. If you'd like you can only display the warning if there are address or port settings specified in the user's old sshd_config. Finally, as I said in my original report, "I don't know what the right answer is here." What I "expect [you] to do" when someone points out an issue like this is to put some thought into how to make it better rather than seeming to imply that the person who reported the issue is being petulant. Putting it another way: neither of the ideas above is rocket science, and I'm not sure why I should have to be the one to think of them, rather than the people who are, you know, being paid to do that. -- 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 1990961] Re: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Given your comment and dmesg log full of "PCIe error", this look like a hardware failure. I mark this bug as invalid. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1990961 Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Not entirely sure what happened but I believe it was due to my computer switching off as it was booting. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 23 10:39:58 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-09-06 (21 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
I'm attaching a debdiff that should fix the issue. I built and published the result in the ppa at https://launchpad.net/~adrien-n/+archive/ubuntu/lp-1991067 and rebuild gnutls successfully. ** Patch added: "lp-1991067-fix-gnutls-ftbfs.debdiff" https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+attachment/5619806/+files/lp-1991067-fix-gnutls-ftbfs.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: In Progress Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy
On Wed, Sep 28, 2022 at 01:19:35PM -, Jonathan Kamens wrote: > 1) Nobody reads the release notes. That's where we document edge case issues that can't be handled automatically. Maybe we can handle this automatically, which is why I invited Steve to take a look. But if it turns out that we can't, then how else do you propose that we document this? > 2) I am not "overwriting configuration files with 'known good' ones," I > am making specific changes to the config files with ansible plays. Either way, it's necessary for you to 1) discover that you need to update your customisation, and then 2) update your customisation yourself. I don't see any automated way for the upgrade to Kinetic to automatically update your Ansible playbooks for you. You seem to be proposing that we should change Ubuntu in some way to accommodate your case, but it's not obvious to me what we can do, or what you expect us to do. Robie -- 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 1990863] Re: conversion from sshd service to socket is too bumpy
1) Nobody reads the release notes.
2) I am not "overwriting configuration files with 'known good' ones," I
am making specific changes to the config files with ansible plays.
Specifically, before fixing my playbook for Kinetic, it looked like
this:
- name: enable root ssh public key authentication
lineinfile:
dest: /etc/ssh/sshd_config
line: PermitRootLogin without-password
register: rootsshyeskey
- name: disable root ssh non-key authentication
replace:
dest: /etc/ssh/sshd_config
regexp: ^\s*PermitRootLogin(?!.*without-password).*\n?
register: rootsshnopassword
- name: add default sshd port
lineinfile:
dest: /etc/ssh/sshd_config
line: 'Port 22'
when: extra_ssh_port is defined
- name: add additional sshd port
lineinfile:
dest: /etc/ssh/sshd_config
line: 'Port {{extra_ssh_port}}'
when: extra_ssh_port is defined
register: sshdport
--
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 1990863] Re: conversion from sshd service to socket is too bumpy
Thank you for taking the time to report this bug and helping to make Ubuntu better. Feedback on this is appreciated as we do want to make the transition as smooth as possible. I would warn though that just overwriting configuration files with "known good" ones following a release upgrade, as you're doing with Ansible, is not advisable in the general case, and cannot be a supportable path in packaging. Because a release upgrade means major version bumps by definition, and configuration file syntaxes change. The assumption of "known good" therefore cannot be made in release upgrades. Therefore, I'm not sure the upgrade path can really be improved here. You can't assume that you can overwrite configuration with what you had in a previous release without looking into the details of how your previous change may no longer apply correctly. What we can do is improve documentation on this, but the documentation has yet to be written because Kinetic hasn't been released yet. The documentation is expected to appear in the release notes at https://discourse.ubuntu.com/t/kinetic-kudu-release-notes/27976, which is the usual place for us to note upgrade path edge cases. I wonder if there's some conflict here between the conffile (or ucf?) prompt and the upgrade path handling, so I subscribed Steve to take a look. -- 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 1621801] Re: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd
Marking as Won't Fix as this was reported for a series that's now unsupported (Xenial) ** Changed in: p11-kit (Ubuntu) Status: New => Won't Fix -- 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/1621801 Title: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) Status in p11-kit package in Ubuntu: Won't Fix Bug description: Crashes every time the machine is restarted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Sep 7 14:53:00 2016 DuplicateSignature: package:p11-kit-modules:i386:0.23.2-5~ubuntu16.04.1 Setting up libfontembed1:amd64 (1.8.3-2ubuntu3.1) ... dpkg: error processing package p11-kit-modules:amd64 (--configure): package p11-kit-modules:amd64 0.23.2-5~ubuntu16.04.1 cannot be configured because p11-kit-modules:i386 is at a different version (0.23.2-3) ErrorMessage: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) InstallationDate: Installed on 2016-04-12 (149 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: p11-kit Title: package p11-kit-modules:i386 0.23.2-5~ubuntu16.04.1 failed to install/upgrade: package p11-kit-modules:i386 0.23.2-3 cannot be configured because p11-kit-modules:amd64 is at a different version (0.23.2-5~ubuntu16.04.1) UpgradeStatus: Upgraded to xenial on 2016-08-14 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1621801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
The attachment "debdiffs.tgz" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. --- External link: https://warthogs.atlassian.net/browse/PEI-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991067] Re: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
** Changed in: p11-kit (Ubuntu) Status: New => Triaged ** Changed in: p11-kit (Ubuntu) Importance: Undecided => High ** Changed in: p11-kit (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: In Progress Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
** Description changed: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. + + --- + External link: https://warthogs.atlassian.net/browse/PEI-28 ** Tags added: pei-28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff:
[Touch-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)
[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY. [335842.604] (WW) glamor: Expect reduced performance. [335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed) followed by [335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in glUnmapBuffer(buffer is not mapped) It looks like a failed allocation is not detected, and an illegal unmap follows. >From a distant it looks like an application is exhausting the Xserver memory, en the Xserver is not robust enough to report these problems to the application program and stay unaffected. When it is followed by a segmentation error later it sure looks like memory corruption, due to not detecting the failure return from glMapBuffer. -- 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/1989964 Title: Segmentation fault crocus_dri.so (X server dies) Status in mesa package in Ubuntu: New Bug description: The desktop session is running for 0 or more days. Suddenly the X server dies, and login screen reappears. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 16 14:45:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/sun--vg-root ro SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.release: 2.59 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.59 dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard 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 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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/mesa/+bug/1989964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
debdiffs for F, J and K ** Attachment added: "debdiffs.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+attachment/5619739/+files/debdiffs.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
** Description changed: + SRU Justification: + -- + + [ Impact ] + + * The zlib function inflate() does not update strm.adler +in case DFLTCC is used. + + * This issue was exposed by Java Certification Kit (JCK) running on z15 +hardware and newer and impacts all JDK versions (8,11,17, etc.) +that use the system default settings. + + * The JCK failure impacts the ability to certify Java SDKs on this +platform/Linux-distribution combination. + + * On top the incorrect alder32 result may cause functional issues with +Java applications that depend on the result. + + [ Test Plan ] + + * An affected Ubuntu release (20.04, 22.04 and 22.10) installed +on a z15/LinuxONE III or newer system is needed. + + * Then it's possible to test the updated package with the help +of a small test program (in C) that makes use of the zlib1g library +or run the Java Certification Kit. + + * Test will be done by IBM. + + [ Where problems could occur ] + + * The patch is a one-line change: +https://launchpadlibrarian.net/626003193/410-lp1990379.patch +and there are not many issues to expect. + + * There could be a potential problem with the adler field +in the strm struct. +For example in case the struct is not as assumed or contains +and unexpected value, which would then ripple through +the other fields, too. + + * Structural changes could be identified with a test build that was done +for all affected Ubuntu releases and for all major architectures: +https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 + + [ Other Info ] + + * The patch itself is the same for all zlib version in +20.04, 22.04 and 22.10 - no further adjustments were needed. + __ + == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. ** Changed in: zlib (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: In Progress Bug description: SRU Justification: -- [ Impact ] * The zlib function inflate() does not update strm.adler in case DFLTCC is used. * This issue was exposed by Java Certification Kit (JCK) running on z15 hardware and newer and impacts all JDK versions (8,11,17, etc.) that use the system default settings. * The JCK failure impacts the ability to certify Java SDKs on this platform/Linux-distribution combination. * On top the incorrect alder32 result may cause functional issues with Java applications that depend on the result. [ Test Plan ] * An affected Ubuntu release (20.04, 22.04 and 22.10) installed on a z15/LinuxONE III or newer system is needed. * Then it's possible to test the updated package with the help of a small test program (in C) that makes use of the zlib1g library or run the Java Certification Kit. * Test will be done by IBM. [ Where problems could occur ] * The patch is a one-line change: https://launchpadlibrarian.net/626003193/410-lp1990379.patch and there are not many issues to expect. * There could be a potential problem with the adler field in the strm struct. For example in case the struct is not as assumed or contains and unexpected value, which would then ripple through the other fields, too. * Structural changes could be identified with a test build that was done for all affected Ubuntu releases and for all major architectures: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 [ Other Info ] * The patch itself is the same for all zlib version in 20.04, 22.04 and 22.10 - no further adjustments were needed. __ == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff:
[Touch-packages] [Bug 1034050] Re: Lame generate invalid filenames
This patch is included in lame 3.100 and therefore in Ubuntu >= 18.04. Therefore I am closing this bug as "Fix Released". ** Changed in: lame (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1034050 Title: Lame generate invalid filenames Status in lame package in Ubuntu: Fix Released Bug description: When lame generate a .mp3 file it replaces the ".wav" in the extension to ".mp3" but generates an invalid filename when the original file has a colon in it, because under Windows the colon is the drive letter separator. The colon character should be handled differently under Windows and Unix OSes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1034050/+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 1071611] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure
Thank you for taking the time to report this bug and helping to make Ubuntu better. The reported Ubuntu version is end of life and the current Ubuntu release seem to be unaffected. Therefore I am closing this bug as Won't Fix. In case you experience this issue with a recent Ubuntu version, don't hesitate to file another bug report. ** Changed in: lame (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 lame in Ubuntu. https://bugs.launchpad.net/bugs/1071611 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure Status in lame package in Ubuntu: Won't Fix Bug description: Ubuntu 12.10 Fresh installation ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 26 09:50:08 2012 ErrorMessage: no package named `libmp3lame0' is installed, cannot configure InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1071611/+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 1071611] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lame (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1071611 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure Status in lame package in Ubuntu: Won't Fix Bug description: Ubuntu 12.10 Fresh installation ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 26 09:50:08 2012 ErrorMessage: no package named `libmp3lame0' is installed, cannot configure InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1071611/+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 1078083] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować
*** This bug is a duplicate of bug 1071611 *** https://bugs.launchpad.net/bugs/1071611 ** This bug has been marked a duplicate of bug 1071611 package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1078083 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować Status in lame package in Ubuntu: New Bug description: Error ocured after I tried: sudo apt-get install ubuntu-restricted- extras ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 21:23:57 2012 ErrorMessage: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować InstallationDate: Installed on 2012-10-30 (13 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1078083/+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 1649604] Re: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Thank you for taking the time to report this bug and helping to make Ubuntu better. Have you tried to reinstall the library? sudo apt-get install --reinstall libmp3lame0 ** Changed in: lame (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1649604 Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lame package in Ubuntu: Incomplete Bug description: audio package error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmp3lame0:amd64 3.99.5+repack1-9build1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Tue Dec 13 20:14:44 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libmp3lame0:amd64:3.99.5+repack1-9build1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package libmp3lame0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-12-03 (10 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: lame Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1649604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991067] [NEW] p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls
Public bug reported: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . ** Affects: p11-kit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/1991067 Title: p11-kit 0.24.1-1ubuntu1 induces FTBFS in gnutls Status in p11-kit package in Ubuntu: New Bug description: Patches added in 0.24.1-1ubuntu1 prevent gnutls from building. Upstream has indicated that an additional change should have been included as mentioned at https://github.com/p11-glue/p11-kit/issues/419#issuecomment-1259353294 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1991067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1990379] Re: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
Ok, that's a (minimal) patch that can be handled nicely, thanks Ilya! Test packages are now being build in the following PPA for focal/20.04, jammy/22.04 and kinetic/22.10: https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379 https://launchpad.net/~fheimes/+archive/ubuntu/lp1990379/+packages It would be great if someone (for example 'rahil'?!) could test (probably) at least the focal package upfront, to ensure that the situation is really solved, and with that, give us confidence for the SRU process. (Please notice that this would be on top of the official verification request that will come up later during the SRU process). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1990379 Title: [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: == Comment: #0 - Ilya Leoshkevich - 2022-09-21 05:02:24 == inflate() does not update strm.adler if DFLTCC is used. Found with a JDK test. zlib-ng PR: https://github.com/zlib-ng/zlib-ng/pull/1349 Updated zlib PR: https://github.com/madler/zlib/pull/410 zlib tag: https://github.com/iii-i/zlib/releases/tag/dfltcc-20220920 zlib diff: https://github.com/madler/zlib/compare/e6aed68ff815be74855ec6a19d6ae35065a4adb4..171d0ff3c9ed40da0ac14085ab16b766b1162069#diff-325baa03829572a9f26b4bb8b3cada1ddc637854529d6a6cb111b8c3ca785620 Ubuntu 20.04 and later need to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1990379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
