[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
It was nice to have LXD around and ready for many test/dev workloads, and I feel it was worth it back then. But we already replaced it with lxd-installer in minimal environments and it was fine there too. I never heard someone complaining that LXD takes a bit there, but every second of boot time seems to be valued highly. Now that we had to reduce this to the lxd-installer everywhere (Due to LP #2051346) it is really worth to be re-revaluated. Thank you for driving this Phil! IMHO now that your first LXD command will take a bit longer already (due to fetching LXD snap), the exact amount of that "a bit longer" (as being more by also fetching snapd and base) seems almost irrelevant as long as it is in the same ballpark. On one hand those dev/test environments that use it most, can easily be made to tolerate the bit of extra time - they usually start with a barrage of other "install this" anyway that has the same "wait for network and install" characteristic. On the other hand reducing size and the initialization effort of it will save transfer and startup time for everyone - the guessed 3-5 seconds mentioned/assumed above would be totally worth it IMHO. --- Furthermore as Simon showed (thanks), by snapd being a baseless snap we'd not even gain something by having that around already for the latter fetch of lxd by lxd-installer. --- I further appreciate John's comment that we should back up some of our current assumptions (how much will this slow down lxc interactions, how much will the boot speed gain) with some actual data. But if that data will not totally upset what we expect, then I very much agree with Steve in comment #1 and would not optimize for it at the cost of all others and thereby I'd be fine to not preseed the other bits there. --- P.S. I wanted to mention that our perception might also be biased. I believe (no data) that the closer to Ubuntu development itself you are, the more likely you use LXD heavily in testing. But that same ratio likely does not apply to any user of Ubuntu images in the world. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package apparmor - 4.0.0~alpha4-0ubuntu1 --- apparmor (4.0.0~alpha4-0ubuntu1) noble; urgency=medium [Georgia Garcia] * New upstream release. * Add unconfined profiles to support the use unprivileged user namespace (LP: #2052297, LP: #2046844) - d/p/u/add-keybase-unconfined-profile.patch - d/p/u/add-more-unconfined-profiles.patch * Fix regression tests failures on regex.sh, exec.sh and userns.sh - d/p/u/tests-fix-usr-merge-failures-on-exec-and-regex-tests.patch - d/p/u/tests-handle-unprivileged_userns-transition-in-usern.patch * Drop patches which have now been applied upstream - d/p/u/userns-unconfined-profiles.patch - d/p/u/tests-fix-userns-setns-opening-pipe-order.patch - d/p/u/tests-replace-individual-socket-permissions.patch - d/p/u/tests-fix-test-specifying-path-on-attach-disconnected.patch - d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch - d/p/u/oot-unconfined-profiles.patch * Refresh patches - d/p/d/etc-writable.patch - d/p/u/profiles-grant-access-to-systemd-resolved.patch - d/p/u/userns-runtime-disable.patch * d/apparmor.install - install new profiles - plasmashell - surfshark - unprivileged_userns - keybase - devhelp - epiphany - evolution - opam - renamed profiles - ch-checkns - ch-run - crun - flatpak - linux-sandbox - busybox - buildah - cam - ipa_verify - lc-compliance - libcamerify - qcam - podman - lxc-attach - lxc-create - lxc-destroy - lxc-execute - lxc-stop - lxc-unshare - lxc-usernsexec - mmdebstrap - vpnns - QtWebEngineProcess - systemd-coredump - rootlesskit - rpm - runc - virtiofsd - sbuild - sbuild-abort - sbuild-adduser - sbuild-apt - sbuild-checkpackages - sbuild-clean - sbuild-createchroot - sbuild-destroychroot - sbuild-distupgrade - sbuild-hold - sbuild-shell - sbuild-unhold - sbuild-update - sbuild-upgrade - slirp4netns - stress-ng - thunderbird - toybox - trinity - tup - userbindmount - uwsgi-core - vdens - chrome - msedge - brave - vivaldi-bin * d/apparmor.maintscript - add renamed profiles so they are removed on upgrade * d/libapache2-mod-apparmor.install - remove etc/apparmor.d/local/usr.sbin.apache2, no longer needed [John Johansen] * debian/rules: - don't run debian/put-all-profiles-in-complain-mode.sh on install [Alex Murray] * debian/apparmor.lintian-overrides: - suppress false-positive warning about needing a Depends: on adduser for the apparmor binary package -- Georgia Garcia Fri, 02 Feb 2024 16:12:21 -0300 ** Changed in: apparmor (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status
[Touch-packages] [Bug 2053235] Re: Upgrade libwayland to 1.22.0
** Summary changed: - Upgrade libwayland on ubuntu 22.04.3 LTS + Upgrade libwayland to 1.22.0 ** Also affects: wayland (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: wayland (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: wayland (Ubuntu Noble) Status: Invalid => Fix Released ** Changed in: wayland (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland to 1.22.0 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Jammy: New Status in wayland source package in Mantic: Fix Released Status in wayland source package in Noble: Fix Released Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 2052297] Re: Please add opt.keybase.keybase profile
This bug was fixed in the package apparmor - 4.0.0~alpha4-0ubuntu1
---
apparmor (4.0.0~alpha4-0ubuntu1) noble; urgency=medium
[Georgia Garcia]
* New upstream release.
* Add unconfined profiles to support the use unprivileged user namespace
(LP: #2052297, LP: #2046844)
- d/p/u/add-keybase-unconfined-profile.patch
- d/p/u/add-more-unconfined-profiles.patch
* Fix regression tests failures on regex.sh, exec.sh and userns.sh
- d/p/u/tests-fix-usr-merge-failures-on-exec-and-regex-tests.patch
- d/p/u/tests-handle-unprivileged_userns-transition-in-usern.patch
* Drop patches which have now been applied upstream
- d/p/u/userns-unconfined-profiles.patch
- d/p/u/tests-fix-userns-setns-opening-pipe-order.patch
- d/p/u/tests-replace-individual-socket-permissions.patch
- d/p/u/tests-fix-test-specifying-path-on-attach-disconnected.patch
- d/p/u/binutils-aa_status.c-quiet-verbose-outputs-when-json.patch
- d/p/u/oot-unconfined-profiles.patch
* Refresh patches
- d/p/d/etc-writable.patch
- d/p/u/profiles-grant-access-to-systemd-resolved.patch
- d/p/u/userns-runtime-disable.patch
* d/apparmor.install
- install new profiles
- plasmashell
- surfshark
- unprivileged_userns
- keybase
- devhelp
- epiphany
- evolution
- opam
- renamed profiles
- ch-checkns
- ch-run
- crun
- flatpak
- linux-sandbox
- busybox
- buildah
- cam
- ipa_verify
- lc-compliance
- libcamerify
- qcam
- podman
- lxc-attach
- lxc-create
- lxc-destroy
- lxc-execute
- lxc-stop
- lxc-unshare
- lxc-usernsexec
- mmdebstrap
- vpnns
- QtWebEngineProcess
- systemd-coredump
- rootlesskit
- rpm
- runc
- virtiofsd
- sbuild
- sbuild-abort
- sbuild-adduser
- sbuild-apt
- sbuild-checkpackages
- sbuild-clean
- sbuild-createchroot
- sbuild-destroychroot
- sbuild-distupgrade
- sbuild-hold
- sbuild-shell
- sbuild-unhold
- sbuild-update
- sbuild-upgrade
- slirp4netns
- stress-ng
- thunderbird
- toybox
- trinity
- tup
- userbindmount
- uwsgi-core
- vdens
- chrome
- msedge
- brave
- vivaldi-bin
* d/apparmor.maintscript
- add renamed profiles so they are removed on upgrade
* d/libapache2-mod-apparmor.install
- remove etc/apparmor.d/local/usr.sbin.apache2, no longer needed
[John Johansen]
* debian/rules:
- don't run debian/put-all-profiles-in-complain-mode.sh on install
[Alex Murray]
* debian/apparmor.lintian-overrides:
- suppress false-positive warning about needing a Depends: on adduser
for the apparmor binary package
-- Georgia Garcia Fri, 02 Feb 2024
16:12:21 -0300
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2052297
Title:
Please add opt.keybase.keybase profile
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
Like the other Chrome binaries, Keybase also needs a profile:
abi ,
/opt/keybase/Keybase flags=(unconfined) {
allow userns create,
}
Keybase is heavily used for security and boot engineering for cross-vendor
communication and broken without it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052297/+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 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
** Description changed: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily, upon starting my laptop, the audio often fails to work, displaying "Dummy Output." To resolve this, I find myself needing to restart the laptop two or three times before the audio becomes functional. Even when the audio is working, I've noticed a recurring issue where, after playing video or audio for approximately 2-3 minutes, the sound starts crackling and buzzing. The intensity of these distortions gradually increases, resembling the static interference on a radio station with a weak signal. This issue persists even when using 3.5mm headphones, requiring the use of a USB headset or Bluetooth headphones to enjoy distortion-free audio. Furthermore, I have observed that, regardless of the Ubuntu version (ranging from 22.04 to 22.04.3), I face difficulties changing the microphone output settings when an external audio peripheral, such as a USB headset, 3.5mm headphones, or Bluetooth headphones, is connected. The OS appears to exclusively utilize the microphone from the connected peripheral, making it impossible to switch to the laptop's built-in microphone. For your reference, here are the specifications of my laptop and the Ubuntu version I am currently using: Laptop: Dell Vostro 3400 CPU: 11th Gen Intel i5-1135G7 GPU: Intel TigerLake-LP GT2 Iris Xe Memory: 2490MiB / 19720MiB Resolution: 1920x1080 OS: Ubuntu 22.04.3 LTS x86_64 Kernel: 6.5.0-14-generic DE: GNOME 42.9 Shell: bash 5.1.16 Sound Card: Card: HDA Intel PCH, Chip: Cirrus Logic CS8409/CS42L42 - UPDATE 29-01-2024 After the latest Linux kernel update to - "6.5.0-15-generic." - - Following the update, I observed a significant reduction in crackling - sound (approximately 80%) after disabling C-states from the BIOS. - However, this improvement came at the cost of higher CPU temperatures, - with the fan constantly running. - - Conversely, with C-states enabled, the crackling sound occurs only when - the fan starts working. Additionally, I am still encountering the "Dummy - Output" audio issue consistently on a fresh start, necessitating a - reboot to resolve. - - I want to emphasize that I receive updates from the Tunisia Ubuntu - server. + UPDATE 12/02/2024 Noticed that every time my laptop fan starts spinning + the crackling sound appears, after fan stops the crackling sound + disappear. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: galxy-a10 1437 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: galxy-a10 1437 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:50:44 2024 InstallationDate: Installed on 2024-01-16 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: جانفي 29 17:49:49 galxya10-VR whoopsie-upload-all[712]: INFO:root:/var/crash/_usr_bin_pulseaudio.1000.crash already marked for upload, skipping Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2023 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd10/03/2023:br1.27:svnDellInc.:pnVostro3400:pvr:rvnDellInc.:rn0GGCMJ:rvrA02:cvnDellInc.:ct10:cvr:sku0A23: dmi.product.family: Vostro dmi.product.name: Vostro 3400 dmi.product.sku: 0A23 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-01-28T08:52:28.427855 -- 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/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Since the last three weeks' updates, I have encountered several challenges with the audio functionality on my system. Primarily,
[Touch-packages] [Bug 2053235] Re: Upgrade libwayland on ubuntu 22.04.3 LTS
** Also affects: wayland (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: wayland (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland on ubuntu 22.04.3 LTS Status in wayland package in Ubuntu: Invalid Status in wayland source package in Jammy: New Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 1995790] Autopkgtest regression report (apt/2.7.3ubuntu0.1)
All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.27.0-0ubuntu5 (amd64) apt/2.7.3ubuntu0.1 (armhf) auto-apt-proxy/14.1 (arm64) livecd-rootfs/23.10.57 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] The '?garbage' pattern doesn't work with install/remove commands which is confusing, and the fix for it is trivial. [Test plan] Successful autopkgtest. The comprehensive test suite run as an autopkgtest has been updated in test/integration/test-apt-get-autoremove to test for the correct behavior of '?garbage' with install and remove. [Where problems could occur] You can see we had to tweak the test suite in a bunch of places because it relies on exact debug output format and because we now call "markandsweep" there's additional mark flags in the debug output. It's unlikely that this is a problem for others. We have not seen regressions in noble in the past 2 weeks or noble- proposed since 2023-11-23 (it was stuck for other reasons there), hence other places the code change may affect have been thoroughly exercised in the builders and autopkgtest runners. [Original bug report] The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2051181] Autopkgtest regression report (apt/2.7.3ubuntu0.1)
All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have finished running. The following regressions have been reported in tests triggered by the package: apport/2.27.0-0ubuntu5 (amd64) apt/2.7.3ubuntu0.1 (armhf) auto-apt-proxy/14.1 (arm64) livecd-rootfs/23.10.57 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2051181 Title: apt cannot upgrade phased updates if the current security version is same as updates Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Committed Bug description: [Impact] A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team. [Test plan] An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test. [Where problems could occur] The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route). Otherwise the fix is fairly contained, it removes a single OtherVer++ increment which made it go one version below the current version, so we do not expect any problems; setting aside the usual regression potential from bugs in the compiler and so on. [Original bug report] When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on
[Touch-packages] [Bug 2053278] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ Freeze
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2053278
Title:
Freeze
Status in Ubuntu:
Incomplete
Bug description:
Everything freezes, several times per day. I am not sure if it's
NVIDIA related or not. I am willing to troubleshoot as long as I am
told very specifically what needs to be done.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 14:30:35 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-14 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240214)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.117-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.3-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
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:
[Touch-packages] [Bug 2053235] Re: Upgrade libwayland on ubuntu 22.04.3 LTS
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland on ubuntu 22.04.3 LTS Status in wayland package in Ubuntu: New Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 2045705] Re: FTBFS with default Java 21
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/apport/+git/apport/+merge/460642
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
Title:
FTBFS with default Java 21
Status in Apport:
Triaged
Status in apport package in Ubuntu:
Triaged
Bug description:
Dear Maintainers,
The package apport ftbfs with default Java 21.
The relevant part of the build log:
---
running build_java_subdir
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
Traceback (most recent call last):
File "/<>/setup.py", line 119, in
DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in
setup
setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in
setup
return distutils.core.setup(**attrs)
^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
185, in setup
return run_commands(dist)
^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
201, in run_commands
dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
969, in run_commands
self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line
131, in run
self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line
318, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in
run_command
super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
988, in run_command
cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target',
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned
non-zero exit status 2.
E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11"
returned exit code 13
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Build finished at 2023-12-04T07:37:06Z
---
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2051181] Autopkgtest regression report (apt/2.4.12)
All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished running. The following regressions have been reported in tests triggered by the package: livecd-rootfs/2.765.38 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2051181 Title: apt cannot upgrade phased updates if the current security version is same as updates Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Committed Bug description: [Impact] A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team. [Test plan] An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test. [Where problems could occur] The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route). Otherwise the fix is fairly contained, it removes a single OtherVer++ increment which made it go one version below the current version, so we do not expect any problems; setting aside the usual regression potential from bugs in the compiler and so on. [Original bug report] When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package linux-signatures-nvidia-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-objects-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package
[Touch-packages] [Bug 1995790] Autopkgtest regression report (apt/2.4.12)
All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished running. The following regressions have been reported in tests triggered by the package: livecd-rootfs/2.765.38 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] The '?garbage' pattern doesn't work with install/remove commands which is confusing, and the fix for it is trivial. [Test plan] Successful autopkgtest. The comprehensive test suite run as an autopkgtest has been updated in test/integration/test-apt-get-autoremove to test for the correct behavior of '?garbage' with install and remove. [Where problems could occur] You can see we had to tweak the test suite in a bunch of places because it relies on exact debug output format and because we now call "markandsweep" there's additional mark flags in the debug output. It's unlikely that this is a problem for others. We have not seen regressions in noble in the past 2 weeks or noble- proposed since 2023-11-23 (it was stuck for other reasons there), hence other places the code change may affect have been thoroughly exercised in the builders and autopkgtest runners. [Original bug report] The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995790/+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 2053289] [NEW] Internal microphone is not working in 24.04 (Fujitsu WU4/H1)
Public bug reported: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/2053289 Title: Internal microphone is not working in 24.04 (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: New Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+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 2053288] [NEW] systemd-networkd IPv6 default routes dropped under load, don't recover
Public bug reported: Ubuntu 22.04.3 LTS systemd 249.11-0ubuntu3.12 systemd issue tracker says this version is too old to report upstream and I should report to downstream bug tracker. IPv6 default routes are getting lost and not renewed. We're using IPv6 RA to find default routes for our servers and desktops. The RAs come from HP/Aruba routers and have a short lifetime of about 46s. Occasionally, we will see the default routes get dropped. Despite receiving RAs, the default routes don't get recreated. The most recent machine to be affected had a user running an excessively large job (load average 157). This is the state of the network when the machine is working: ```sh # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff altname enp4s0f0 3: eno2: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff permaddr 2c:ea:7f:56:9a:67 altname enp4s0f1 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff inet xxx.xxx.202.112/24 brd 129.215.202.255 scope global bond0 valid_lft forever preferred_lft forever inet6 :xxx:xxx:202:2eea:7fff:fe56:9a66/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 2591994sec preferred_lft 604794sec inet6 fe80::2eea:7fff:fe56:9a66/64 scope link valid_lft forever preferred_lft forever # ip -6 r ::1 dev lo proto kernel metric 256 pref medium :xxx:xxx:202::/64 dev bond0 proto ra metric 1024 expires 2591998sec pref medium fe80::/64 dev bond0 proto kernel metric 256 pref medium default proto ra metric 1024 expires 28sec pref medium nexthop via fe80::609:73ff:fe48:c000 dev bond0 weight 1 nexthop via fe80::609:73ff:fe48:6500 dev bond0 weight 1 ``` When the problem arises, the last three lines disappear. `tcpdump icmp6` shows RAs being received but networkd doesn't create the routes in the kernel. The machine keeps its IPv6 addresses, but without a default route it can't make any IPv6 connections or answer incoming IPv6 connections. Sorry, reproduction method is unclear. Here's a best guess: 1. Configure networkd using netplan: ```yaml --- network: bonds: bond0: addresses: - xxx.xxx.202.112/24 dhcp4: false interfaces: - eth0 - eth1 macaddress: 2C:EA:7F:56:9A:66 parameters: mii-monitor-interval: 1 mode: active-backup ethernets: eth0: dhcp4: false match: macaddress: 2C:EA:7F:56:9A:66 eth1: dhcp4: false match: macaddress: 2C:EA:7F:56:9A:67 renderer: networkd version: 2 ``` 2. Load the machine, or just wait. Possibly this is related to packets being dropped, but I would expect the system to recover once the load is removed. 3. Note the lack of IPv6 connectivity, inability to log in with ssh, etc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2053288 Title: systemd-networkd IPv6 default routes dropped under load, don't recover Status in systemd package in Ubuntu: New Bug description: Ubuntu 22.04.3 LTS systemd 249.11-0ubuntu3.12 systemd issue tracker says this version is too old to report upstream and I should report to downstream bug tracker. IPv6 default routes are getting lost and not renewed. We're using IPv6 RA to find default routes for our servers and desktops. The RAs come from HP/Aruba routers and have a short lifetime of about 46s. Occasionally, we will see the default routes get dropped. Despite receiving RAs, the default routes don't get recreated. The most recent machine to be affected had a user running an excessively large job (load average 157). This is the state of the network when the machine is working: ```sh # ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff altname enp4s0f0 3: eno2: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 2c:ea:7f:56:9a:66 brd ff:ff:ff:ff:ff:ff permaddr 2c:ea:7f:56:9a:67
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
Thank you for the detail sdeziel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051572] Re: Always preseed core and snapd snap in server seed
> "other cloud cases that have preseeded snaps" (thinking like ec2 or oracle that have snapped cloud agent This isn't something we need to worry about as there will be no change in this case. If any agent snaps are preseeded then so too will a core snap and snapd snap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2053165] Re: [noble] Version 2.7.5 causes software-properties to crash
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
** This bug has been marked a duplicate of bug 2053228
software-properties-gtk does not start
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2053165
Title:
[noble] Version 2.7.5 causes software-properties to crash
Status in python-apt package in Ubuntu:
Confirmed
Bug description:
Hi,
Only since recent 2.7.5 update along with 0.99.42 for software-properties.
Crash on start-up.
$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2053165/+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 2053228] Re: software-properties-gtk does not start
** Tags added: rls-nn-incoming
** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-24.04-beta
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Regardless of how the bluetooth device works, enabling unbonded devices in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be enabled by the security team. Perhaps GNOME or other desktops could become more aware of gaming controllers with these issues to make pairing easier, without needing to open a terminal. If there are feature requests for this, please link them in this bug for others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2051572] Re: Always preseed core and snapd snap in server seed
FYI, snapd is a "base-less" snap: $ lxc launch ubuntu-minimal-daily:22.04 c1 $ lxc shell c1 root@c1:~# snap list No snaps are installed yet. Try 'snap install hello-world'. root@c1:~# snap install snapd 2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart... snapd 2.61.1 from Canonical✓ installed root@c1:~# snap list Name Version RevTracking Publisher Notes snapd 2.61.1 20671 latest/stable canonical✓ snapd This is also visible by not having any `base:` while LXD currently uses core22: root@c1:~# snap info --verbose snapd | grep base: root@c1:~# snap info --verbose lxd | grep base: base:core22 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2040465] Re: New upstream microrelease 2.5.17
Hello Bryce, or anyone else affected, Accepted openldap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openldap/2.5.17+dfsg-0ubuntu0.22.04.1 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. ** Changed in: openldap (Ubuntu Jammy) Status: In Progress => 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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/2040465 Title: New upstream microrelease 2.5.17 Status in openldap package in Ubuntu: Invalid Status in openldap source package in Jammy: Fix Committed Bug description: [ Impact ] * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.17. This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/OpenLDAPUpdates. [ Major Changes ] * See the list of bugs fixed in this release here: https://lists.openldap.org/hyperkitty/list/openldap- annou...@openldap.org/thread/XRQE4CVQDLTG4EYPKVEU2L76DYGIFR2Q/ [ Test Plan ] * Upstream gitlab pipeline results: https://git.openldap.org/openldap/openldap/-/commit/99a124bb434052a71cf4ff115d0f949f6c6b7208/pipelines?ref=OPENLDAP_REL_ENG_2_5 * Upstream "call for testing": https://lists.openldap.org/hyperkitty/list/openldap- techni...@openldap.org/thread/4744NWC2HJP7L24WOUMZF4VCYGGUMRI7/ * As described in the MRE wiki page for OpenLDAP, the test plan is to build the package in a PPA and make sure that (1) all build-time tests pass and (2) all autopkgtest runs (from reverse dependencies) also pass. * Build log (amd64) confirming that the build-time testsuite has been performed and completed successfully: - https://launchpadlibrarian.net/679769800/buildlog_ubuntu-jammy-amd64.openldap_2.5.16+dfsg-0ubuntu0.22.04.1~ppa1_BUILDING.txt.gz [ Where problems could occur ] * Upstream tests are always executed during build-time. There are many reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage is good. Nevertheless, there is always a risk for something to break since we are dealing with a microrelease upgrade. Whenever a test failure is detected, we will be on top of it and make sure it doesn't affect existing users. [ Other Info ] * This is a reoccurring MRE. See below for links to previous OpenLDAP MREs. * CVEs fixed by this release: - None. Current versions in supported releases that got updates: openldap | 2.5.16+dfsg-0ubuntu0.22.04.2 | jammy-security | source Special cases: - None. Previous MREs for OpenLDAP: - https://pad.lv/1977627 - https://pad.lv/1983618 - https://pad.lv/2007625 - https://pad.lv/2027079 - https://pad.lv/2029170 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2040465/+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 2051572] Re: Always preseed core and snapd snap in server seed
I agree with vorlon in general. It is a bit odd to not be seeding snapd by default, since snaps are a recognized package format. preseeding snapd will bring in its base, but there's no guarantee that base will match any other snaps. Flip side is that somewhere back in history, it was decided that in a system without any other snaps preseeded, that having the snapd deb, which exists to bootstrap itself into a snapd snap, was the right choice. so let's narrow the cases we know of: * pre-installed systems with no other snaps pre-seeded That limits itself, right now, to cloud-images "downloads" (the qcow, ova, etc). Right now the cloud team sees a fairly long time in running `lxd` commands, as we specifically have a mandate to ensure `lxd` is operating well on our cloud-images. what we don't know right now * boot time differences with adding the snaps back in (from old reading it looks anywhere from 3-5s, which is a nice little gain) * the amount of time/slow down for `lxd` booting from `lxd-installer` in a "no snaps pre-seeded" setting * the _usage_ and _expectation_ about the speed here. We definitely support running lxd on cloud-images. and we know it is a use case. but we don't know if this is a "many users" or "a couple users," and we don't know their expectations regarding speed. We may be able to roll out with good documentation letting everyone know what the change is, what to expect, etc. The more info we can gather on our side for time cost the better. getting some data comparisons across the following would be good: * boot times w/ and w/o preseeded snaps * lxd launch time with no preseeded, snapd + it's core snap preseeded, and "other cloud cases that have preseeded snaps" (thinking like ec2 or oracle that have snapped cloud agents) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2053278] [NEW] Xorg freeze
Public bug reported:
Everything freezes, several times per day. I am not sure if it's NVIDIA
related or not. I am willing to troubleshoot as long as I am told very
specifically what needs to be done.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 14:30:35 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-14 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240214)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.117-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.3.3-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze noble ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2053278
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Everything freezes, several times per day. I am not sure if it's
NVIDIA related or not. I am willing to troubleshoot as long as I am
told very specifically what needs to be done.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.146.02 Sun Dec 3
14:06:14 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop:
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
> 15 seconds vs 30 seconds, on a thing that won't affect most cloud customers I'll see if I can find the data to back this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051572] Re: Always preseed core and snapd snap in server seed
If we don't preseed a core snap and snapd it feels like we're failing to prioritise the performance of snaps on server/cloud. But if we acknowledge that knowing that we are prioritising boot speed then that's fine and we can add it to the noble release notes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2051572] Re: Always preseed core and snapd snap in server seed
Good points I'll measure boot speed with and without core snap preseeded and add it here. time to initialize any snap was my goal but with lxd as an example as it is such a popular snap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)
We *should* get this via normal stable update processes relatively soon.
If for some reason it doesn't land in systemd-stable in time (unlikely
since the upstream PR is tagged for stable backport), then we will
backport it in Ubuntu directly.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Importance: High => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: 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/2049247
Title:
Broken IPv4 support on IPv6-preferring networks (v255)
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Bug description:
I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).
I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.
I'm still reporting the bug here anyways because this bug can, under
some conditions, result in the loss of IPv4 network connectivity in a
completely standard Ubuntu 24.04 installation just by updating to
systemd 255. I'm hoping that that's okay even though it's a bug caused
by upstream not by Ubuntu; just because it could have a bad impact if
this version ends up in 24.04 as it is.
---
In systemd version 255, a feature has been added to "support" the
IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
quotation marks because one functionality that this RFC marks as a
requirement is not implemented in systemd yet.
To summarize: Option 108 can be sent by a DHCPv4 client to signal to
the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
support and a working NAT64 gateway, I don't really need my own IPv4
address, I can handle it using 464XLAT and NAT64". The point of that
option is to be able to run a Dual Stack network, where only clients
that really need IPv4 (older Linux, Windows, etc.) will receive an
IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
Linux with systemd >=255, etc.) won't receive one from DHCP and
instead set up a 464XLAT for outgoing IPv4 connectivity.
This new code in systemd is enabled by default (the option
"IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
have code to set up a 464XLAT yet (which violates the RFC).
This means that systemd signals to the DHCPv4 server "Hey, I don't
need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
actually do that. Updating systemd on an Ubuntu 24.04 installation
(where systemd-networkd is used) will result in the loss of the DHCP-
assigned IPv4 address, breaking network connectivity for all IPv4-only
applications.
---
Information on how to reproduce this issue can be found in detail in
the github bug report linked above, but to summarize:
1. Have a Dual Stack network that announces a NAT64 through RAs or through
DNS (or, ideally, both)
2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
3. Connect an Ubuntu machine with systemd < 255.
4. Notice that IPv4 connectivity is working fine.
5. Update to systemd = 255.
6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.
---
The proper fix for this issue to make systemd conform to the RFC would
be to implement a 464XLAT. However that's not an easy task and most
certainly not something that would end up as a hotfix / patch release.
A good workaround for this bug would be, in my opinion, to change the
default value for the "IPv6OnlyMode" to "no" when compiling systemd.
That way, the RFC-violating code doesn't run by default, and if a user
does set up a 464XLAT on their machine in some other way (outside of
systemd) they can just change their config to include
"IPv6OnlyMode=yes" and it'll be working as intended.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.2-3ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Jan 13 07:05:42 2024
InstallationDate: Installed on 2024-01-12 (0 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64
(20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
> This is a significant difference and for a workload we intend to remain as a > core tested > and tracked workload. As such I propose we re-introduce core22 and snapd > snaps to our seed. I disagree that the image should be optimized by default to prioritize the one-time startup performance of an optional use case. 15 seconds vs 30 seconds, on a thing that won't affect most cloud customers, and happens at most once per image, AND should be weighed against the first-boot speed improvements in clouds resulting from having a smaller image? Also, statically seeding a particular base snap is bad form, as soon as lxd upgrades its base you lose your performance benefit and have to play catch-up in a stable release. If "time to initialize lxd" is your metric, I think you're measuring the wrong thing :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Changed in: steam (Ubuntu) Status: Confirmed => Fix Committed -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Confirmed Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Confirmed Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Confirmed Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: In Progress Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Particularly on the case of PS3 controller, I still think this is a regression that could be fixed. PS3 controllers do not use the standard Bluetooth connection procedure. Instead, they require a connection via USB, and keys are exchanged via there. There is the special `sixaxis` BlueZ plugin to support that protocol, and before that there was the `sixpair.c` utility found here: https://www.pabr.org/sixlinux/sixlinux.en.html Thus, it seems that there could be an exception for wire-paired devices, as it would still fix the issue raised by the CSV for us, PS3 controller users. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2049247] Re: Broken IPv4 support on IPv6-preferring networks (v255)
Given that systemd-v255 has just migrated from noble-proposed to noble
yesterday, this bug is now present in Ubuntu 24.04 as-is, without the
proposed repo enabled. Can this fix be backported before 22.04 releases
so people don't run into network issues with a newly-installed 22.04?
--
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/2049247
Title:
Broken IPv4 support on IPv6-preferring networks (v255)
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
New
Bug description:
I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).
I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.
I'm still reporting the bug here anyways because this bug can, under
some conditions, result in the loss of IPv4 network connectivity in a
completely standard Ubuntu 24.04 installation just by updating to
systemd 255. I'm hoping that that's okay even though it's a bug caused
by upstream not by Ubuntu; just because it could have a bad impact if
this version ends up in 24.04 as it is.
---
In systemd version 255, a feature has been added to "support" the
IPv6-only DHCP option 108 defined in RFC8925. I'm putting "support" in
quotation marks because one functionality that this RFC marks as a
requirement is not implemented in systemd yet.
To summarize: Option 108 can be sent by a DHCPv4 client to signal to
the DHCPv4 server: "Hey, if (and only if) your network has proper IPv6
support and a working NAT64 gateway, I don't really need my own IPv4
address, I can handle it using 464XLAT and NAT64". The point of that
option is to be able to run a Dual Stack network, where only clients
that really need IPv4 (older Linux, Windows, etc.) will receive an
IPv4 from DHCP, and clients that don't need IPv4 (Android, MacOS,
Linux with systemd >=255, etc.) won't receive one from DHCP and
instead set up a 464XLAT for outgoing IPv4 connectivity.
This new code in systemd is enabled by default (the option
"IPv6OnlyMode" defaults to "yes"). However, systemd does not actually
have code to set up a 464XLAT yet (which violates the RFC).
This means that systemd signals to the DHCPv4 server "Hey, I don't
need IPv4, I'll just use 464XLAT and NAT64" but then it doesn't
actually do that. Updating systemd on an Ubuntu 24.04 installation
(where systemd-networkd is used) will result in the loss of the DHCP-
assigned IPv4 address, breaking network connectivity for all IPv4-only
applications.
---
Information on how to reproduce this issue can be found in detail in
the github bug report linked above, but to summarize:
1. Have a Dual Stack network that announces a NAT64 through RAs or through
DNS (or, ideally, both)
2. Configure your DHCPv4 server to hand out option 108 ("v6-only-preferred")
3. Connect an Ubuntu machine with systemd < 255.
4. Notice that IPv4 connectivity is working fine.
5. Update to systemd = 255.
6. Notice that there's no IPv4 connectivity anymore and IPv4-only apps break.
---
The proper fix for this issue to make systemd conform to the RFC would
be to implement a 464XLAT. However that's not an easy task and most
certainly not something that would end up as a hotfix / patch release.
A good workaround for this bug would be, in my opinion, to change the
default value for the "IPv6OnlyMode" to "no" when compiling systemd.
That way, the RFC-violating code doesn't run by default, and if a user
does set up a 464XLAT on their machine in some other way (outside of
systemd) they can just change their config to include
"IPv6OnlyMode=yes" and it'll be working as intended.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd 255.2-3ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Jan 13 07:05:42 2024
InstallationDate: Installed on 2024-01-12 (0 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release amd64
(20231011)
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device,
Driver=usbhid, 12M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=b5e6aabf-881a-4589-85ae-688f41df0be7 ro
SourcePackage: systemd
UpgradeStatus: Upgraded to noble on 2024-01-12 (0 days ago)
dmi.bios.date:
[Touch-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 1995790] Please test proposed package
Hello Mekaniserad, 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.12 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/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] The '?garbage' pattern doesn't work with install/remove commands which is confusing, and the fix for it is trivial. [Test plan] Successful autopkgtest. The comprehensive test suite run as an autopkgtest has been updated in test/integration/test-apt-get-autoremove to test for the correct behavior of '?garbage' with install and remove. [Where problems could occur] You can see we had to tweak the test suite in a bunch of places because it relies on exact debug output format and because we now call "markandsweep" there's additional mark flags in the debug output. It's unlikely that this is a problem for others. We have not seen regressions in noble in the past 2 weeks or noble- proposed since 2023-11-23 (it was stuck for other reasons there), hence other places the code change may affect have been thoroughly exercised in the builders and autopkgtest runners. [Original bug report] The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 6 10:57:52 2022 SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-03-26 (224 days ago) To
[Touch-packages] [Bug 1995790] Re: regression: ?garbage does not work correctly in install commands
Hello Mekaniserad, or anyone else affected, Accepted apt into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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. ** Changed in: apt (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: apt (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: 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/1995790 Title: regression: ?garbage does not work correctly in install commands Status in apt package in Ubuntu: Fix Released Status in apt source package in Jammy: Fix Committed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Released Bug description: [Impact] The '?garbage' pattern doesn't work with install/remove commands which is confusing, and the fix for it is trivial. [Test plan] Successful autopkgtest. The comprehensive test suite run as an autopkgtest has been updated in test/integration/test-apt-get-autoremove to test for the correct behavior of '?garbage' with install and remove. [Where problems could occur] You can see we had to tweak the test suite in a bunch of places because it relies on exact debug output format and because we now call "markandsweep" there's additional mark flags in the debug output. It's unlikely that this is a problem for others. We have not seen regressions in noble in the past 2 weeks or noble- proposed since 2023-11-23 (it was stuck for other reasons there), hence other places the code change may affect have been thoroughly exercised in the builders and autopkgtest runners. [Original bug report] The awesome apt has a some wonderful tips on their EXAMPLES section (printed below). The choice of name to "garbage" might not have been the best but the function is extremely useful. $ man apt-patterns | sed '/EXAMPLES/,/^[^ ]/!d;/^[^ ]/d' apt remove ?garbage Remove all packages that are automatically installed and no longer needed - same as apt autoremove apt purge ?config-files Purge all packages that only have configuration files left apt list '~i !~M (~slibs|~sperl|~spython)' List all manually-installed packages in sections matching libs, perl, or python. Lets mark a package as automatically installed, and use the examples. $ sudo apt-mark auto shotwell shotwell set to automatically installed. $ sudo apt remove ?garbage Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libraw20 shotwell shotwell-common Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libraw20 shotwell shotwell-common 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 9.806 kB disk space will be freed. Do you want to continue? [Y/n] N Abort. Apt-patterns works as it should everywhere else, as far as I can see, it works wonders with ie `apt list '~g|~c'` and many other applications. I used `apt purge '~g|~c'` successfully in Ubuntu 20.04 for years, so I feel this is a regression. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.8 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs
[Touch-packages] [Bug 2051181] Re: apt cannot upgrade phased updates if the current security version is same as updates
Hello Andy, or anyone else affected, Accepted apt into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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. ** Tags added: verification-needed verification-needed-mantic ** Tags added: 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/2051181 Title: apt cannot upgrade phased updates if the current security version is same as updates Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Committed Bug description: [Impact] A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team. [Test plan] An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test. [Where problems could occur] The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route). Otherwise the fix is fairly contained, it removes a single OtherVer++ increment which made it go one version below the current version, so we do not expect any problems; setting aside the usual regression potential from bugs in the compiler and so on. [Original bug report] When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 <
[Touch-packages] [Bug 2051181] Please test proposed package
Hello Andy, 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.12 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/2051181 Title: apt cannot upgrade phased updates if the current security version is same as updates Status in apt package in Ubuntu: Fix Committed Status in apt source package in Jammy: Fix Committed Status in apt source package in Mantic: Fix Committed Status in apt source package in Noble: Fix Committed Bug description: [Impact] A package that has the same version in -security and -updates, with the latter having a Phased-Update-Percentage set is subject to phasing which is not expected by the security team. [Test plan] An automatic test case has been added to apt's comprehensive integration test suite that simulates the problem. Passing of the autopkgtests is a successful test. [Where problems could occur] The fix in question changes the behavior, some people may have relied on that, but also this should not have happened server side (normally security updates do not receive a value but the real one in this case went a different route). Otherwise the fix is fairly contained, it removes a single OtherVer++ increment which made it go one version below the current version, so we do not expect any problems; setting aside the usual regression potential from bugs in the compiler and so on. [Original bug report] When I finished installation with Jammy 22.04.3, I noticed that nvidia-driver-535 cannot be upgrade by either `apt upgrade` nor `apt dist-upgrade`. Below is the log of apt upgrade: ubuntu@ubuntu:~$ sudo apt -o Debug::pkgProblemResolver=1 upgrade --dry-run [2/1878] Reading package lists... Done Building dependency tree... Done Reading state information... Done Entering ResolveByKeep 10% Dependencies are not satisfied for nvidia-driver-535:amd64 < 535.129.03-0ubuntu0.22.04.1 | 535.154.05-0ubuntu0.22.04.1 @ii pumH NPb Ib > Package nvidia-driver-535:amd64 nvidia-driver-535:amd64 Depends on nvidia-dkms-535:amd64 < none | 535.154.05-0ubuntu0.22.04.1 @un umH > (<= 535.129.03-1) Keeping Package linux-modules-nvidia-535-oem-22.04c:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Keeping package linux-modules-nvidia-535-oem-22.04c:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-oem-22.04c:amd64 < 6.1.0-1027.27 | 6.1.0-1028.28+2 @ii umH Ib > Package linux-modules-nvidia-535-oem-22.04c:amd64 linux-modules-nvidia-535-oem-22.04c:amd64 Depends on linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU Ib > (= 6.1.0-1027.27) Keeping Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 due to Depends Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1028-oem:amd64 < none -> 6.1.0-1028.28+2 @un uN Ib > Keeping package linux-modules-nvidia-535-6.1.0-1028-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Keeping package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Dependencies are not satisfied for linux-modules-nvidia-535-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 | 6.1.0-1027.27+1 @ii umH Ib > Package linux-modules-nvidia-535-6.1.0-1027-oem:amd64 linux-modules-nvidia-535-6.1.0-1027-oem:amd64 Depends on linux-signatures-nvidia-6.1.0-1027-oem:amd64 < 6.1.0-1027.27 -> 6.1.0-1027.27+1 @ii umU > (= 6.1.0-1027.27) Keeping Package
[Touch-packages] [Bug 2053165] Re: [noble] Version 2.7.5 causes software-properties to crash
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2053165
Title:
[noble] Version 2.7.5 causes software-properties to crash
Status in python-apt package in Ubuntu:
Confirmed
Bug description:
Hi,
Only since recent 2.7.5 update along with 0.99.42 for software-properties.
Crash on start-up.
$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2053165/+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 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
** Summary changed: - Don't migrate glib yet + glib requires gobject-introspection >= 1.78.1-13 ** Changed in: glib2.0 (Ubuntu) Status: Invalid => Triaged ** Tags removed: block-proposd ** Tags added: update-excuse ** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Committed ** Description changed: - . + glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate + out of noble-proposed before or at the same as glib2.0. + + I'm filing this bug to explain why glib2.0 isn't migrating despite the + excuses page saying "Will attempt migration" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Committed Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+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 2052951] Re: ncurses/i386 autopkgtest failure
@juliank Testing was done by running autopkgtest locally against the source package only (-B, --no-built-binaries), I didn't rebuild the binaries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Verifying this should be fairly simple.
Look at the definition of Authmethod in auth.h and compare to how
method_gssapi is initialized compared to method_gsskeyex.
As for it being the only report it is only "AuthenticationMethods gssapi-keyex"
that is not working.
We have "AuthenticationMethods gssapi-keyex gssapi-with-mic" so on Jammy it
still works but we get complaints in the log, like this:
===
error: Disabled method "gssapi-keyex" in AuthenticationMethods list
"gssapi-keyex"
Authentication methods list "gssapi-keyex" contains disabled method, skipping
===
Regarding Noble, the patch for this in
openssh_9.6p1-3ubuntu1.debian.tar.xz is still having the same problem
with the initialization of method_gsskeyex.
===
@@ -333,6 +377,12 @@ input_gssapi_mic(int type, u_int32_t plen, struct ssh *ssh)
return 0;
}
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
+
Authmethod method_gssapi = {
"gssapi-with-mic",
NULL,
===
Note that there is still only three arguments in the init of
method_gsskeyex vs the required four.
--
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/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
Incomplete
Bug description:
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2052951] Re: ncurses/i386 autopkgtest failure
This failed to build due to missing update-maintainer, I'm adding this and uploading it but wondering how it was tested: dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address E: Failed to package source directory /home/jak/Projects/Ubuntu/Scratch/ncurses-6.4+20240113 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/2052951 Title: ncurses/i386 autopkgtest failure Status in ncurses package in Ubuntu: New Bug description: ncurses fails to pass its autopkgtests on i386: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/i386/n/ncurses/20240212_101858_8f6ad@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/2052951/+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 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Hello and thanks for this bug report. The analysis looks sensible to me,
but I'm not really familiar with gss. To better understand the situation
I have a couple of questions:
- Does this mean that gss is unusable in Jammy at the moment? AFAICT
this is the only bug report about it, so I would be surprised.
- Are you able to test openssh from newer Ubuntu releases, ideally
including Noble (the next LTS, currently in development)? The gss patch
has been updated since Jammy, the last time on:
Last-Updated: 2023-12-18
Thanks!
** Changed in: openssh (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146
Title:
openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
slightly wrong
Status in openssh package in Ubuntu:
Incomplete
Bug description:
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3
entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2053235] [NEW] Upgrade libwayland on ubuntu 22.04.3 LTS
Public bug reported: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland on ubuntu 22.04.3 LTS Status in wayland package in Ubuntu: New Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+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 2033646] Re: unattended-upgrade ignores apt-pinning to not-allowed origins
Confirmed by
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2033646
Title:
unattended-upgrade ignores apt-pinning to not-allowed origins
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
unattended-upgrade ignores apt-pinning to not-allowed origins
=
BUG:
unattended-upgrade notices an upgrade available in NOT-ALLOWED ORIGINS,
but then completely ignores those repositories
even if they contain apt-pinned versions
that are more favorable than versions from allowed origins.
The situation repeats every time there is an upgrade available in an
external PPA.
SOLUTION:
unattended-upgrade should not ignore NOT ALLOWED ORIGINS,
but check them for providing more favorable version
and in such case restrain from doing ANY upgrades for such packages.
Instructions for ubuntu lunar 23.04:
0. Upgrade all packages, uninstall Firefox:
$ sudo apt update
$ sudo apt upgrade
$ sudo snap remove firefox
$ sudo apt remove firefox
$ apt-cache policy firefox
firefox:
Installed: (none)
Candidate: 1:1snap1-0ubuntu3
Version table:
1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
1. Add mozilla-team Firefox PPA and apt-pin it with priority 1001:
$ echo 'deb
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar main' |
sudo tee /etc/apt/sources.list.d/firefox.list
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
9BDB3D89CE49EC21
$ echo -e 'Package: *\nPin: release o=LP-PPA-mozillateam\nPin-
Priority: 1001' | sudo tee /etc/apt/preferences.d/firefox
$ sudo apt update
$ apt-cache policy firefox
firefox:
Installed: (none)
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
117.0+build2-0ubuntu0.23.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
lunar/main arm64 Packages
2. Install Firefox (from mozilla-team Firefox PPA, as pinned):
$ sudo apt install firefox
$ apt-cache policy firefox
firefox:
Installed: 117.0+build2-0ubuntu0.23.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
*** 117.0+build2-0ubuntu0.23.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
lunar/main arm64 Packages
100 /var/lib/dpkg/status
3. SIMULATE AVAILABLE UPGRADE by downgrading Firefox from Mozilla-
Team's version for Ubuntu 23.04 to 22.04:
Download .deb. file from Mozilla-Team's PPA:
$ wget $(apt-get download --print-uris firefox | cut -d' ' -f1 |
tr -d "'" | sed -E 's/0ubuntu0\.[0-9]+\.[0-9]+\./0ubuntu0.22.04./')
Install it:
$ sudo dpkg -i firefox_*.22.04.*.deb
dpkg: warning: downgrading firefox from 117.0+build2-0ubuntu0.23.04.1~mt1
to 117.0+build2-0ubuntu0.22.04.1~mt1
(Reading database ... 295244 files and directories currently installed.)
Preparing to unpack firefox_117.0+build2-0ubuntu0.22.04.1~mt1_arm64.deb
...
Unpacking firefox (117.0+build2-0ubuntu0.22.04.1~mt1) over
(117.0+build2-0ubuntu0.23.04.1~mt1) ...
Setting up firefox (117.0+build2-0ubuntu0.22.04.1~mt1) ...
Please restart all running instances of firefox, or you will experience
problems.
Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-1) ...
$ apt-cache policy firefox
firefox:
Installed: 117.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 117.0+build2-0ubuntu0.23.04.1~mt1
Version table:
1:1snap1-0ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu lunar/main arm64 Packages
117.0+build2-0ubuntu0.23.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
lunar/main arm64 Packages
*** 117.0+build2-0ubuntu0.22.04.1~mt1 100
100 /var/lib/dpkg/status
4. Bug in unattended-upgrade:
Firefox is now at priority 100 ("now").
Firefox snap package is at priority 500.
Mozilla-Team PPA has priority 1001, BUT IS
[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] Re: software-properties-gtk does not start
Get the same errors on Mate Noble, (new perl packages and dependencies
previously upgraded; but might be of no concern here)
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2053228] [NEW] software-properties-gtk does not start
Public bug reported:
On a new install with the new format sources.list software-properties-gtk does
not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
New
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 2037604] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2 --- mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium * patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on Intel DG2. (LP: #2051068) mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium * Backport to 22.04. (LP: #2037604) * rules: Disable rusticl, FTBFS on jammy. -- Timo Aaltonen Wed, 24 Jan 2024 14:01:34 +0200 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: directx-headers (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
This bug was fixed in the package directx-headers - 1.610.2-2~ubuntu0.22.04.1 --- directx-headers (1.610.2-2~ubuntu0.22.04.1) jammy; urgency=medium * Backport to jammy. (LP: #2037604) -- Timo Aaltonen Fri, 27 Oct 2023 08:57:55 +0300 -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2051068] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2 --- mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium * patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on Intel DG2. (LP: #2051068) mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium * Backport to 22.04. (LP: #2037604) * rules: Disable rusticl, FTBFS on jammy. -- Timo Aaltonen Wed, 24 Jan 2024 14:01:34 +0200 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
Test builds are done here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1982336 ** Information type changed from Private to Public ** Changed in: ubuntu-z-systems Status: New => In Progress ** Changed in: gdb (Ubuntu) Status: New => In Progress -- 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/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: In Progress Status in gdb package in Ubuntu: In Progress Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+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 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
debdiff ** Patch added: "debdiff_gdb_noble_from_14.1-0ubuntu2_to_14.1-0ubuntu3.diff" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1982336/+attachment/5746408/+files/debdiff_gdb_noble_from_14.1-0ubuntu2_to_14.1-0ubuntu3.diff -- 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/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: In Progress Status in gdb package in Ubuntu: In Progress Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+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
