[Touch-packages] [Bug 2060615] Re: [noble] two versions of perl-modules are published, breaking debootstrap
Aside from curl this can be reproduced most quickly with sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n http://archive.ubuntu.com/ubuntu Errors were encountered while processing: perl libdpkg-perl libperl5.38t64:amd64 dpkg-dev build-essential These are all ultimately due to dpkg: dependency problems prevent configuration of perl: perl depends on perl-modules-5.38 (>= 5.38.2-3.2build2); however: Version of perl-modules-5.38 on system is 5.38.2-3. dpkg: error processing package perl (--configure): dependency problems - leaving unconfigured ** Tags added: debootstrap noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2060615 Title: [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap Status in perl package in Ubuntu: New Status in perl source package in Noble: New Bug description: For the last two weeks, building noble VM images for our CI has been broken. Most of it was uninstallability due to the xz reset, but for the last three days, `pbuilder --create` has failed [2] because it gets perl and perl-modules-5.38 in two different versions: 2024-04-08 08:47:08 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb [1822564/1822564] -> "/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1] 2024-04-08 08:47:09 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb [3110080/3110080] -> "/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1] and then trying to configure the packages blows up. The root cause is that perl-modules has *two* versions published: # curl -s http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep -A5 'Package: perl-modules-' Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3.2build2 Multi-Arch: foreign Priority: optional Build-Essential: yes -- Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3 Multi-Arch: foreign Priority: optional Build-Essential: yes While apt is clever enough to pick the right one, debootstrap isn't. Can you please remove the old perl-modules-5.38 5.38.2-3 from noble? Thanks! [1] https://github.com/cockpit-project/bots/issues/6147 [2] https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2060615/+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 2060615] Re: [noble] two versions of perl-modules are published, breaking debootstrap
I wonder where that comes from -- https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that 5.38.2-3 was deleted, but only from noble-updates. In noble proper it is merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3 doesn't show it being published anyway, and it's not in https://ubuntu- archive-team.ubuntu.com/nbs.html either. ** Summary changed: - [noble] two versions of perl-modules are published, breaking debootstrap + [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2060615 Title: [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap Status in perl package in Ubuntu: New Status in perl source package in Noble: New Bug description: For the last two weeks, building noble VM images for our CI has been broken. Most of it was uninstallability due to the xz reset, but for the last three days, `pbuilder --create` has failed [2] because it gets perl and perl-modules-5.38 in two different versions: 2024-04-08 08:47:08 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb [1822564/1822564] -> "/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1] 2024-04-08 08:47:09 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb [3110080/3110080] -> "/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1] and then trying to configure the packages blows up. The root cause is that perl-modules has *two* versions published: # curl -s http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep -A5 'Package: perl-modules-' Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3.2build2 Multi-Arch: foreign Priority: optional Build-Essential: yes -- Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3 Multi-Arch: foreign Priority: optional Build-Essential: yes While apt is clever enough to pick the right one, debootstrap isn't. Can you please remove the old perl-modules-5.38 5.38.2-3 from noble? Thanks! [1] https://github.com/cockpit-project/bots/issues/6147 [2] https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2060615/+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 2060615] [NEW] [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap
Public bug reported: For the last two weeks, building noble VM images for our CI has been broken. Most of it was uninstallability due to the xz reset, but for the last three days, `pbuilder --create` has failed [2] because it gets perl and perl-modules-5.38 in two different versions: 2024-04-08 08:47:08 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb [1822564/1822564] -> "/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1] 2024-04-08 08:47:09 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb [3110080/3110080] -> "/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1] and then trying to configure the packages blows up. The root cause is that perl-modules has *two* versions published: # curl -s http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep -A5 'Package: perl-modules-' Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3.2build2 Multi-Arch: foreign Priority: optional Build-Essential: yes -- Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3 Multi-Arch: foreign Priority: optional Build-Essential: yes While apt is clever enough to pick the right one, debootstrap isn't. Can you please remove the old perl-modules-5.38 5.38.2-3 from noble? Thanks! [1] https://github.com/cockpit-project/bots/issues/6147 [2] https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Affects: perl (Ubuntu Noble) Importance: Undecided Status: New ** Tags: debootstrap noble ** Also affects: perl (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2060615 Title: [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap Status in perl package in Ubuntu: New Status in perl source package in Noble: New Bug description: For the last two weeks, building noble VM images for our CI has been broken. Most of it was uninstallability due to the xz reset, but for the last three days, `pbuilder --create` has failed [2] because it gets perl and perl-modules-5.38 in two different versions: 2024-04-08 08:47:08 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-base_5.38.2-3.2build2_amd64.deb [1822564/1822564] -> "/var/cache/pbuilder/aptcache//perl-base_5.38.2-3.2build2_amd64.deb" [1] 2024-04-08 08:47:09 URL:http://archive.ubuntu.com/ubuntu/pool/main/p/perl/perl-modules-5.38_5.38.2-3_all.deb [3110080/3110080] -> "/var/cache/pbuilder/aptcache//perl-modules-5.38_5.38.2-3_all.deb" [1] and then trying to configure the packages blows up. The root cause is that perl-modules has *two* versions published: # curl -s http://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.xz|xzgrep -A5 'Package: perl-modules-' Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3.2build2 Multi-Arch: foreign Priority: optional Build-Essential: yes -- Package: perl-modules-5.38 Architecture: all Version: 5.38.2-3 Multi-Arch: foreign Priority: optional Build-Essential: yes While apt is clever enough to pick the right one, debootstrap isn't. Can you please remove the old perl-modules-5.38 5.38.2-3 from noble? Thanks! [1] https://github.com/cockpit-project/bots/issues/6147 [2] https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-ubuntu-stable-02cafde3-20240407-074108/log.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2060615/+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 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
Also bug 2060555. -- 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/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: New Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+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 2060555] Re: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones
See also bug 205 having trouble with the same chip. ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- 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/2060555 Title: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones Status in bluez package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2060555/+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 2060555] Re: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones
Please reboot, try to connect them again, and after it fails run: journalctl -b0 > journal.txt and attach the resulting text file here. Please also specify how long ago and in which Ubuntu release it was working. ** Summary changed: - I cant connect my bluetooth keyboard, mouse and jbl headpones + [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/2060555 Title: [RTL8822CE] I cant connect my bluetooth keyboard, mouse and jbl headpones Status in bluez package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2060555/+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 2052669] Re: update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/in
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2052669
Title:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic E:
/usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-
initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
Status in initramfs-tools package in Ubuntu:
Expired
Bug description:
My bare metal server would not restart. After some research, I found
out that I get the following error:
"Kernel Panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)"
I started up in a Rescue, and followed the steps in
https://askubuntu.com/a/41939/36315, to "update-initramfs -u -k
{version}".
Then I got the below message:
update-initramfs: Generating /boot/initrd.img-5.15.0-92-generic
E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15.0-92-generic with 1.
I found a workaround for it: https://askubuntu.com/a/916283/36315
"sudo chmod -x /usr/share/initramfs-tools/hooks/fixrtc"
I did that for every file in usr/share/initramfs-tools/hooks/*
After that I did
update-initramfs -u -k all
update-grub
I rebooted from Rescue, and then I got the following error:
"Kernel Panic - not syncing: No working init found. Try passing
init= option to kernel."
AFter this, I reinstalled Ubuntu 22.04 on my bare metal server, but
even after reinstall, I get the "No working init found" error message.
I have no idea now how to fix this.
Any help is greatly appreciated!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2052669/+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 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-gnome-meta package in Ubuntu: Confirmed Bug description: Package vanilla-gnome-desktop 0.97 depends on pulseaudio which conflicts with pipewire-alsa and pipewire-audio which in turn are required for upgrading gnome to version 43. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2011404/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
To complete the list of products: In addition to games, this change is also useful for users of Elasticsearch and/or Opensearch and Apache Lucene/Solr on large clusters. Elasticsearch also suggests raising the value, although not so high: https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html Opensearch: https://opensearch.org/docs/latest/install-and-configure/install-opensearch/index/#important-settings Apache Solr: https://solr.apache.org/guide/solr/latest/deployment-guide/taking-solr-to-production.html If you e.g. start Elasticsearch without a large enough vm.max_map_count, it will print a log message to raise it and exit. My personal opinion: Actually the game issues described here should better be fixed in Steam's launcher when starting such a game (or in Wine). The downstream software should better ask the user to raise the value upon starting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Released Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+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 2060581] [NEW] stop shipping debian-installer package hook
Public bug reported: I don't remember when we stopped producing installer images with debian- installer but it should be long enough ago that people won't be reporting bugs about it on Noble. So let's drop that from the apport package. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming ** Changed in: apport (Ubuntu) Milestone: None => ubuntu-24.04 ** Tags added: rls-nn-incoming -- 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/2060581 Title: stop shipping debian-installer package hook Status in apport package in Ubuntu: New Bug description: I don't remember when we stopped producing installer images with debian-installer but it should be long enough ago that people won't be reporting bugs about it on Noble. So let's drop that from the apport package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060581/+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
Mantic verification In all architectures, except i386, the new test passed. Here is a log from the amd64 run[1]: 4333s autopkgtest [16:47:27]: test ssh-gssapi: [--- 4333s ## Setting up test environment 4333s ## Creating Kerberos realm EXAMPLE.FAKE 4333s Initializing database '/var/lib/krb5kdc/principal' for realm 'EXAMPLE.FAKE', 4333s master key name 'K/m...@example.fake' 4333s ## Creating principals 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Principal "testuser1...@example.fake" created. 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Principal "host/sshd-gssapi.example.f...@example.fake" created. 4333s ## Extracting service principal host/sshd-gssapi.example.fake 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 4333s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 4333s ## Adjusting /etc/krb5.conf 4333s ## TESTS 4333s 4333s ## TEST test_gssapi_login 4333s ## Configuring sshd for gssapi-with-mic authentication 4333s ## Restarting ssh 4333s ## Obtaining TGT 4333s Password for testuser1...@example.fake: 4333s Ticket cache: FILE:/tmp/krb5cc_0 4333s Default principal: testuser1...@example.fake 4333s 4333s Valid starting ExpiresService principal 4333s 04/05/24 16:47:27 04/06/24 02:47:27 krbtgt/example.f...@example.fake 4333s renew until 04/06/24 16:47:27 4333s 4333s ## ssh'ing into localhost using gssapi-with-mic auth 4333s Warning: Permanently added 'sshd-gssapi.example.fake' (ED25519) to the list of known hosts. 4334s Fri Apr 5 16:47:27 UTC 2024 4334s 4334s ## checking that we got a service ticket for ssh (host/) 4334s 04/05/24 16:47:27 04/06/24 02:47:27 host/sshd-gssapi.example.fake@ 4334s Ticket server: host/sshd-gssapi.example.f...@example.fake 4334s 4334s ## Checking ssh logs to confirm gssapi-with-mic auth was used 4334s Apr 05 16:47:27 sshd-gssapi.example.fake sshd[1688]: Accepted gssapi-with-mic for testuser1620 from 127.0.0.1 port 44922 ssh2: testuser1...@example.fake 4334s ## PASS test_gssapi_login 4334s 4334s ## TEST test_gssapi_keyex_login 4334s ## Configuring sshd for gssapi-keyex authentication 4334s ## Restarting ssh 4334s ## Obtaining TGT 4334s Password for testuser1...@example.fake: 4334s Ticket cache: FILE:/tmp/krb5cc_0 4334s Default principal: testuser1...@example.fake 4334s 4334s Valid starting ExpiresService principal 4334s 04/05/24 16:47:28 04/06/24 02:47:28 krbtgt/example.f...@example.fake 4334s renew until 04/06/24 16:47:28 4334s 4334s ## ssh'ing into localhost using gssapi-keyex auth 4334s Fri Apr 5 16:47:28 UTC 2024 4334s 4334s ## checking that we got a service ticket for ssh (host/) 4334s 04/05/24 16:47:28 04/06/24 02:47:28 host/sshd-gssapi.example.fake@ 4334s Ticket server: host/sshd-gssapi.example.f...@example.fake 4334s 4334s ## Checking ssh logs to confirm gssapi-keyex auth was used 4334s Apr 05 16:47:28 sshd-gssapi.example.fake sshd[1758]: Accepted gssapi-keyex for testuser1620 from 127.0.0.1 port 44930 ssh2: testuser1...@example.fake 4334s ## PASS test_gssapi_keyex_login 4334s 4334s ## ALL TESTS PASSED 4334s ## Cleaning up 4334s autopkgtest [16:47:28]: test ssh-gssapi: ---] 4335s ssh-gssapi PASS 4335s autopkgtest [16:47:29]: test ssh-gssapi: - - - - - - - - - - results - - - - - - - - - - 4335s autopkgtest [16:47:29]: summary 4335s regress PASS 4335s systemd-socket-activation PASS 4335s ssh-gssapi PASS Mantic verification succeeded. 1. https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/o/openssh/20240405_164750_3a52b@/log.gz ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- 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: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Mantic: Fix Committed Status in openssh source package in Noble: Fix Released Bug description: [ Impact ] The gssapi-keyex authentication mechanism has been inadvertently broken in openssh. It comes from a distro patch[1], and while the patch still applied, it was no longer correct. Without the fix, sshd will fail to start if gssapi-keyex is listed in the AuthenticationMethods of the server, and if not, sshd will still start, but gssapi-keyex will not be available. [ Test Plan ] This update, besides fixing the
[Touch-packages] [Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Jammy verification In all architectures (except i386, which is a known failure everywhere) the new ssh-gssapi test passed. Here is the run on amd64[1]: 3438s autopkgtest [16:33:21]: test ssh-gssapi: [--- 3438s ## Setting up test environment 3438s ## Creating Kerberos realm EXAMPLE.FAKE 3438s Loading random data 3438s Initializing database '/var/lib/krb5kdc/principal' for realm 'EXAMPLE.FAKE', 3438s master key name 'K/m...@example.fake' 3438s ## Creating principals 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Principal "testuser1...@example.fake" created. 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Principal "host/sshd-gssapi.example.f...@example.fake" created. 3438s ## Extracting service principal host/sshd-gssapi.example.fake 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 3438s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 3438s ## Adjusting /etc/krb5.conf 3438s ## TESTS 3438s 3438s ## TEST test_gssapi_login 3438s ## Configuring sshd for gssapi-with-mic authentication 3438s ## Restarting ssh 3438s ## Obtaining TGT 3438s Password for testuser1...@example.fake: 3438s Ticket cache: FILE:/tmp/krb5cc_0 3438s Default principal: testuser1...@example.fake 3438s 3438s Valid starting ExpiresService principal 3438s 04/05/24 16:33:20 04/06/24 02:33:20 krbtgt/example.f...@example.fake 3438s renew until 04/06/24 16:33:20 3438s 3438s ## ssh'ing into localhost using gssapi-with-mic auth 3438s Warning: Permanently added 'sshd-gssapi.example.fake' (ED25519) to the list of known hosts. 3439s Fri Apr 5 16:33:21 UTC 2024 3439s 3439s ## checking that we got a service ticket for ssh (host/) 3439s 04/05/24 16:33:21 04/06/24 02:33:20 host/sshd-gssapi.example.fake@ 3439s Ticket server: host/sshd-gssapi.example.f...@example.fake 3439s 3439s ## Checking ssh logs to confirm gssapi-with-mic auth was used 3439s Apr 05 16:33:21 sshd-gssapi.example.fake sshd[1518]: Accepted gssapi-with-mic for testuser1457 from 127.0.0.1 port 50668 ssh2: testuser1...@example.fake 3439s ## PASS test_gssapi_login 3439s 3439s ## TEST test_gssapi_keyex_login 3439s ## Configuring sshd for gssapi-keyex authentication 3439s ## Restarting ssh 3439s ## Obtaining TGT 3439s Password for testuser1...@example.fake: 3439s Ticket cache: FILE:/tmp/krb5cc_0 3439s Default principal: testuser1...@example.fake 3439s 3439s Valid starting ExpiresService principal 3439s 04/05/24 16:33:21 04/06/24 02:33:21 krbtgt/example.f...@example.fake 3439s renew until 04/06/24 16:33:21 3439s 3439s ## ssh'ing into localhost using gssapi-keyex auth 3439s Fri Apr 5 16:33:21 UTC 2024 3439s 3439s ## checking that we got a service ticket for ssh (host/) 3439s 04/05/24 16:33:21 04/06/24 02:33:21 host/sshd-gssapi.example.fake@ 3439s Ticket server: host/sshd-gssapi.example.f...@example.fake 3439s 3439s ## Checking ssh logs to confirm gssapi-keyex auth was used 3439s Apr 05 16:33:21 sshd-gssapi.example.fake sshd[1558]: Accepted gssapi-keyex for testuser1457 from 127.0.0.1 port 50670 ssh2: testuser1...@example.fake 3439s ## PASS test_gssapi_keyex_login 3439s 3439s ## ALL TESTS PASSED 3439s ## Cleaning up 3439s autopkgtest [16:33:22]: test ssh-gssapi: ---] 3439s autopkgtest [16:33:22]: test ssh-gssapi: - - - - - - - - - - results - - - - - - - - - - 3439s ssh-gssapi PASS 3440s autopkgtest [16:33:23]: summary 3440s regress PASS 3440s ssh-gssapi PASS Jammy verification succeeded. 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/o/openssh/20240405_163345_c46fa@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released Status in openssh source package in Jammy: Fix Committed Status in openssh source package in Mantic: Fix Committed Status in openssh source package in Noble: Fix Released Bug description: [ Impact ] The gssapi-keyex authentication mechanism has been inadvertently broken in openssh. It comes from a distro patch[1], and while the patch still applied, it was no longer correct. Without the fix, sshd will fail to start if gssapi-keyex is listed in the AuthenticationMethods of the server, and if not, sshd will still start, but gssapi-keyex will not be available. [ Test Plan ] This
[Touch-packages] [Bug 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
** Changed in: c2esp (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: Fix Committed Status in cups package in Ubuntu: Fix Released Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2059281] Re: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd
** Changed in: c2esp (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059281 Title: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd Status in c2esp package in Ubuntu: Invalid Status in cups package in Ubuntu: Fix Released Bug description: libcupsfilters 2.0.0-0ubuntu6 results in autopkgtest regressions in c2esp, cpdb-backend-cups, cpdb-libs, cups-browsed, libppd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059281/+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 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg
After kernel + x.org updates this week, firefox is now displaying properly using xserver-xorg on the Athlon 200GE. -- 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/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE using built-in graphics. (Radeon™ Vega 3 Graphics) Firefox and Chromium browsers had their windows corrupted to the point where they were unreadable. I think this is an xorg bug, because when I installed Wayland and logged in with a Wayland session, the browsers displayed correctly. Same behaviour with an Athlon 220GE. KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs Wayland that was the critical difference. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Tags: jammy wayland-session ubuntu Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/04/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6210 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Tags: jammy ubuntu Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True
[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Installing 'gawk' package fixed the issue for both noble and mantic- proposed. Thank you! -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Fix Committed Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm2' Selected version '24.1~git2402280600.41722c~oibaf~n' (Updated Open
[Touch-packages] [Bug 2037022] Re: logrotate systemd timer should run hourly rather than daily
I am hitting this issue as well - I've been able to work around it by running a script post startup which uses sed to replace the `Daily` lines in the logrotate.timer file with hourly, and reload the systemd daemon config. #!/bin/bash sed -i "/Description=Daily rotation of log files/c\Description=Hourly rotation of log files" /lib/systemd/system/logrotate.timer sed -i "/OnCalendar=daily/c\OnCalendar=hourly" /lib/systemd/system/logrotate.timer systemctl daemon-reload; systemctl stop logrotate.timer; systemctl start logrotate.timer This is a crude workaround, but I assume the actual fix should be to modify the same items in the distro logrotate.timer file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/2037022 Title: logrotate systemd timer should run hourly rather than daily Status in logrotate package in Ubuntu: Confirmed Bug description: Logrotate supports "hourly rotation, however the Ubuntu logrotate systemd Timer runs "daily" - so "hourly" logrotate jobs are still only run daily. Updating /etc/systemd/system/timers.target.wants/logrotate.timer: ... [Timer] OnCalendar=hourly ... should allow "logrotate hourly" to work as expected. See related comment at https://github.com/logrotate/logrotate/issues/249#issuecomment-485829363 "The tricky part is that one needs to change the default cron hook (or systemd timer) to make hourly actually work as expected." Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: logrotate 3.21.0-1 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Sep 21 22:11:04 2023 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: logrotate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/2037022/+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 2060331] Re: add-apt-repository --list not returning any deb822 repositories
Thanks for the bug report. This was overlooked when adding deb822 support. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Tags added: foundations-todo -- 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/2060331 Title: add-apt-repository --list not returning any deb822 repositories Status in software-properties package in Ubuntu: Confirmed Bug description: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+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 2055200] Re: tests-in-lxd is broken with latest autopkgtest version
** Changed in: systemd (Ubuntu Mantic) Status: Won't Fix => Triaged ** Changed in: systemd (Ubuntu Mantic) Importance: Undecided => Low -- 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/2055200 Title: tests-in-lxd is broken with latest autopkgtest version Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Mantic: Triaged Bug description: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+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 2059796] Re: Other Software > Remove button doesn't work
I had killed the authentication agent and forgot to bring it back, so my
last comment conclusion is wrong.
The incorrect behavior does seem to be tied to deb822; for .source files
the exception being suppressed is
--->
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1158, in on_remove_clicked
self.backend.RemoveSource(str(source_entry))
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
^^^
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 634, in
call_blocking
reply_message = self.send_message_with_reply_and_block(
^^^
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.ValueError:
Traceback (most recent call last):
File "/lib/python3/dist-packages/dbus/service.py", line 712, in _message_cb
retval = candidate_method(self, *args, **keywords)
^
File
"/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py",
line 285, in RemoveSource
self.remove_source(_to_unicode(source))
File "/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py",
line 779, in remove_source
self.remove_source(source, True)
File "/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py",
line 781, in remove_source
self.remove_source(source, False)
File "/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py",
line 802, in remove_source
self.sourceslist.list.append(SourceEntry("", file=source.file))
^
File "/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/2059796
Title:
Other Software > Remove button doesn't work
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Test Case
-
- Add a PPA
- Open the Software & Updates tab
- Switch to the Other Software tab
- Select the PPA line and click Remove
- After Authentication, nothing happens.
No error is emitted to the command line. The repo line still shows.
The repo is still in /etc/apt/sources.list.d/
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.44
ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
Uname: Linux 6.8.0-20-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 12:06:07 2024
InstallationDate: Installed on 2022-04-06 (723 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
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: Upgraded to noble on 2023-12-09 (111 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059796/+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 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
Yes, a no-change rebuild fixes the issue. Please see attached debdiff for the fix. I have provided a PPA with the build and tests: PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower arm64 autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz arm64 autopkgtests artifacts: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz ** Patch added: "upower_1.90.2-8build3_1.90.2-8build4.debdiff" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+attachment/5762206/+files/upower_1.90.2-8build3_1.90.2-8build4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+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 2059796] Re: Other Software > Remove button doesn't work
After racking my brains thinking this had to do with deb822, I found that a Dbus exception was being suppressed by only logging one particular exception. Disabling the catch with ---> def on_remove_clicked(self, widget): """Remove the selected source""" model = self.treeview_sources.get_model() (path, column) = self.treeview_sources.get_cursor() iter = model.get_iter(path) if iter: source_entry = model.get_value(iter, LIST_ENTRY_OBJ) #try: self.backend.RemoveSource(str(source_entry)) #except dbus.DBusException as e: #maybe_log_authentication_canceled_error(e) <--- reveals the issue: ---> Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1159, in on_remove_clicked self.backend.RemoveSource(str(source_entry)) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, ^^^ File "/usr/lib/python3/dist-packages/dbus/connection.py", line 634, in call_blocking reply_message = self.send_message_with_reply_and_block( ^^^ dbus.exceptions.DBusException: com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy: com.ubuntu.softwareproperties.applychanges <--- -- 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/2059796 Title: Other Software > Remove button doesn't work Status in software-properties package in Ubuntu: Triaged Bug description: Test Case - - Add a PPA - Open the Software & Updates tab - Switch to the Other Software tab - Select the PPA line and click Remove - After Authentication, nothing happens. No error is emitted to the command line. The repo line still shows. The repo is still in /etc/apt/sources.list.d/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-gtk 0.99.44 ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1 Uname: Linux 6.8.0-20-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 12:06:07 2024 InstallationDate: Installed on 2022-04-06 (723 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) 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: Upgraded to noble on 2023-12-09 (111 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2059796/+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 2057836] Re: gst-python1.0 fails to build: test failures
** Changed in: gst-python1.0 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: Fix Released Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Fix Released Status in gst-python1.0 package in Debian: Fix Released Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
This bug was fixed in the package bash - 5.2.21-2ubuntu4 --- bash (5.2.21-2ubuntu4) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 08:41:03 + ** Changed in: bash (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 Status in bash package in Ubuntu: Fix Released Status in faketime package in Ubuntu: New Status in sssd package in Ubuntu: New Bug description: faketime 0.9.10-2.1ubuntu1 is stuck in -proposed with build failures on armhf. On armhf, the testsuite confusingly fails with a stack smash error. But this error happens in bash, which isn't even meant to be the process under test. Minimal reproducer: # LD_PRELOAD=./src/libfaketime.so.1 bash -c 'exit 0' *** stack smashing detected ***: terminated Aborted (core dumped) # Confusingly, ltrace shows different results for the newly-built binary than from one built without 64-bit time_t. # LD_PRELOAD=./src/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->getrandom(0x1f3bf08, 1, 0x9683b0, 0) = 0xc8202 bash->getrandom(0xc8203, 0xf7fad53c, 1023, 0xf7eef801) = 0xc8202 *** stack smashing detected ***: terminated --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ # LD_PRELOAD=/usr/lib/arm-linux-gnueabihf/faketime/libfaketime.so.1 ltrace --library '*faketime*' bash -c 'exit 0' bash->gettimeofday(0x8b07a0, 0) = 0 bash->getpid() = 819717 bash->gettimeofday(0xffb88714, 0)= 0 bash->getpid() = 819717 bash->gettimeofday(0xffb8871c, 0)= 0 bash->getpid() = 819717 +++ exited (status 0) +++ # Unsetting -DFAKE_RANDOM in debian/rules does not fix the problem however. So simply loading the LD_PRELOAD library without executing it seems to be enough to break bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+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 2060535] Re: apparmor's is_container_with_internal_policy() does not recognize incus
This is already available in noble. An SRU for jammy and focal (and
ideally bionic) would be nice.
** Changed in: apparmor (Ubuntu Bionic)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Focal)
Status: New => Triaged
** Changed in: apparmor (Ubuntu Jammy)
Status: New => Triaged
--
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/2060535
Title:
apparmor's is_container_with_internal_policy() does not recognize
incus
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Bionic:
Triaged
Status in apparmor source package in Focal:
Triaged
Status in apparmor source package in Jammy:
Triaged
Status in apparmor source package in Noble:
Fix Released
Bug description:
apparmor is not loading for Ubuntu containers under incus. This is due
to `/lib/apparmor/rc.apparmor.functions` (18.04 uses
`/lib/apparmor/functions`):
is_container_with_internal_policy() {
# this function is sometimes called independently of
# is_apparmor_loaded(), so also define this here.
local ns_stacked_path="${SFS_MOUNTPOINT}/.ns_stacked"
local ns_name_path="${SFS_MOUNTPOINT}/.ns_name"
local ns_stacked
local ns_name
if ! [ -f "$ns_stacked_path" ] || ! [ -f "$ns_name_path" ]; then
return 1
fi
read -r ns_stacked < "$ns_stacked_path"
if [ "$ns_stacked" != "yes" ]; then
return 1
fi
# LXD and LXC set up AppArmor namespaces starting with "lxd-" and
# "lxc-", respectively. Return non-zero for all other namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi
return 0
}
This can be fixed by adjusting it to have:
# LXD, LXC and incus set up AppArmor namespaces starting with "lxd-",
# "lxc-", and "incus-" respectively. Return non-zero for all other
namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ] && \
[ "${ns_name#incus-*}" = "$ns_name" ] ; then
return 1
fi
References:
* https://github.com/lxc/incus/issues/740
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2060535/+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 2060535] Re: apparmor's is_container_with_internal_policy() does not recognize incus
https://gitlab.com/apparmor/apparmor/-/commit/659a187687fc8802045c113da0d12bc4b836d591
was committed upstream for this. It would be nice if this was SRU'd.
** Changed in: apparmor (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2060535
Title:
apparmor's is_container_with_internal_policy() does not recognize
incus
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Bionic:
Triaged
Status in apparmor source package in Focal:
Triaged
Status in apparmor source package in Jammy:
Triaged
Status in apparmor source package in Noble:
Fix Released
Bug description:
apparmor is not loading for Ubuntu containers under incus. This is due
to `/lib/apparmor/rc.apparmor.functions` (18.04 uses
`/lib/apparmor/functions`):
is_container_with_internal_policy() {
# this function is sometimes called independently of
# is_apparmor_loaded(), so also define this here.
local ns_stacked_path="${SFS_MOUNTPOINT}/.ns_stacked"
local ns_name_path="${SFS_MOUNTPOINT}/.ns_name"
local ns_stacked
local ns_name
if ! [ -f "$ns_stacked_path" ] || ! [ -f "$ns_name_path" ]; then
return 1
fi
read -r ns_stacked < "$ns_stacked_path"
if [ "$ns_stacked" != "yes" ]; then
return 1
fi
# LXD and LXC set up AppArmor namespaces starting with "lxd-" and
# "lxc-", respectively. Return non-zero for all other namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi
return 0
}
This can be fixed by adjusting it to have:
# LXD, LXC and incus set up AppArmor namespaces starting with "lxd-",
# "lxc-", and "incus-" respectively. Return non-zero for all other
namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ] && \
[ "${ns_name#incus-*}" = "$ns_name" ] ; then
return 1
fi
References:
* https://github.com/lxc/incus/issues/740
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2060535/+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 2058976] Re: Configuration files for networkd are created when NetworkManager is the default renderer
Alfonso, do you have any debug-logs for sytemd-networkd and udev to see
what happens when the interface enters the "failed" state?
--
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/2058976
Title:
Configuration files for networkd are created when NetworkManager is
the default renderer
Status in Netplan:
New
Status in systemd package in Ubuntu:
New
Bug description:
This is happening in a UC image created with a gadget that disables
console-conf:
$ ubuntu-image snap --snap=network-manager=22 --snap pc_22.snap
The snaps are:
$ snap list
Name Version RevTracking Publisher Notes
core22 202403211344 latest/edge canonical✓ base
network-manager 1.36.6-987622/stablecanonical✓ -
pc 22-0.3 x1 --
gadget
pc-kernel5.15.0-102.112.1+1 1731 22/beta canonical✓
kernel
snapd2.62+git2017.g1afc063e 21490 latest/edge canonical✓ snapd
On first boot, the content in /etc/netplan is:
ubuntu@ubuntu:~$ cat /etc/netplan/00-default-nm-renderer.yaml
network:
renderer: NetworkManager
ubuntu@ubuntu:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
ens3:
dhcp4: true
match:
macaddress: '52:54:00:12:34:56'
set-name: ens3
version: 2
But we have a configuration file for systemd-networkd that should not be
there:
ubuntu@ubuntu:~$ cat /run/systemd/network/10-netplan-ens3.link
[Match]
PermanentMACAddress=52:54:00:12:34:56
[Link]
Name=ens3
WakeOnLan=off
ubuntu@ubuntu:~$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutableconfigured
While having to:
ubuntu@ubuntu:~$ sudo cat
/run/NetworkManager/system-connections/netplan-ens3.nmconnection
[connection]
id=netplan-ens3
type=ethernet
interface-name=ens3
[ethernet]
wake-on-lan=0
[ipv4]
method=auto
[ipv6]
method=ignore
ubuntu@ubuntu:~$ nmcli c
NAME UUID TYPE DEVICE
netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3
ubuntu@ubuntu:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ens3ethernet connected netplan-ens3
lo loopback unmanaged --
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2058976/+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 2060555] [NEW] I cant connect my bluetooth keyboard, mouse and jbl headpones
Public bug reported: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2060555 Title: I cant connect my bluetooth keyboard, mouse and jbl headpones Status in bluez package in Ubuntu: New Bug description: The keyboard and mouse are dell brand and they were able to connect to my system and now they cannot. My headdpone are JBL ear pods and they were able to be detected but never connected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 09:42:46 2024 InstallationDate: Installed on 2024-03-31 (7 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP ProBook x360 435 G7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic root=UUID=35bab0c0-13e7-40a8-9606-02a74c223e18 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2023 dmi.bios.release: 13.0 dmi.bios.vendor: HP dmi.bios.version: S80 Ver. 01.13.00 dmi.board.name: 8735 dmi.board.vendor: HP dmi.board.version: KBC Version 09.2D.00 dmi.chassis.asset.tag: 5CG0340N3Z dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.45 dmi.modalias: dmi:bvnHP:bvrS80Ver.01.13.00:bd03/24/2023:br13.0:efr9.45:svnHP:pnHPProBookx360435G7:pvr:rvnHP:rn8735:rvrKBCVersion09.2D.00:cvnHP:ct31:cvr:sku17G39UT#ABA: dmi.product.family: 103C_5336AN HP ProBook x360 dmi.product.name: HP ProBook x360 435 G7 dmi.product.sku: 17G39UT#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 1C:BF:C0:C6:9F:CA ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:173926 acl:0 sco:0 events:4200 errors:0 TX bytes:58386 acl:0 sco:0 commands:1483 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2060555/+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 2060548] Re: [FFe] Update and seed wsl-pro-service in the WSL images
** Summary changed: - Update and seed wsl-pro-service in the WSL images + [FFe] Update and seed wsl-pro-service in the WSL images ** Description changed: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. + + It also fixes a vulnerability by depending on latest Go and latest + x/net/http. -- 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/2060548 Title: [FFe] Update and seed wsl-pro-service in the WSL images Status in ubuntu-meta package in Ubuntu: New Status in wsl-pro-service package in Ubuntu: New Bug description: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. It also fixes a vulnerability by depending on latest Go and latest x/net/http. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+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 2057836] Re: gst-python1.0 fails to build: test failures
This bug was fixed in the package pygobject - 3.48.2-1 --- pygobject (3.48.2-1) unstable; urgency=medium * New upstream release - Fix gst-python1.0 build (Closes: #1065547) (LP: #2057836) -- Jeremy Bícha Sat, 06 Apr 2024 06:49:50 -0400 ** Changed in: pygobject (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2057836 Title: gst-python1.0 fails to build: test failures Status in pygobject: Fix Released Status in gst-python1.0 package in Ubuntu: Triaged Status in pygobject package in Ubuntu: Fix Released Status in gst-python1.0 package in Debian: Confirmed Bug description: gst-python1.0 fails to build because of test failures. https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1 https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1 I have reported the issue to the upstream developers https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353 To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2056555] Re: Python can't write to /proc files
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/2056555
Title:
Python can't write to /proc files
Status in dash package in Ubuntu:
Confirmed
Bug description:
Occurs since an update around March 2 Ubuntu 24.04.
Bitbake is broken due to file permission problem.
Traceback (most recent call last):
File "/home/hains/openpli-oe-core/bitbake/bin/bitbake-worker", line 268, in
child
bb.utils.disable_network(uid, gid)
File "/home/hains/openpli-oe-core/bitbake/lib/bb/utils.py", line 1653, in
disable_network
with open("/proc/self/uid_map", "w") as f:
PermissionError: [Errno 1] Operation not permitted
Test code
with open("/proc/self/uid_map", "w") as f:
f.write("%s %s 1" % (1000, 1000))
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: dash 0.5.12-6ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 8 14:34:08 2024
InstallationDate: Installed on 2023-03-24 (350 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: dash
UpgradeStatus: Upgraded to noble on 2024-01-10 (58 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2056555/+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 2060548] [NEW] Update and seed wsl-pro-service in the WSL images
Public bug reported: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: wsl-pro-service (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2060548 Title: Update and seed wsl-pro-service in the WSL images Status in ubuntu-meta package in Ubuntu: New Status in wsl-pro-service package in Ubuntu: New Bug description: This is a new package for this release. It’s only functional with a Windows agent which is not publically released and under beta for now. As the end of the beta will be after the 24.04 release, we want to get as close as possible to the current code level, knowing that current code will still certainly grow feature-wise once with the Beta user feedback. However, having it seeded (the MIR is approved and security issues fixed but the certificate one, which has been discussed as minor for now) with the current code level will be great to diminish the diff when the SRU that will be needed then. The impact is on existing non beta users (and beta users are using a ppa with the ppa containing the current code level). Current diff is large as the development is very active and won’t really provide anything more. Note that it contains also a packaging change to fix bug #2057651. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
I opened a new bug report for the awk issue affecting ppa-purge please redirect any new issues with the fix to here: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2060544 ** Merge proposal unlinked: https://code.launchpad.net/~ghadi-rahme/ubuntu/+source/ppa-purge/+git/ppa-purge/+merge/463813 -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Fix Committed Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1'
[Touch-packages] [Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
-
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
-
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that change
is already present in the upstream code, and we are just updating it in
the new gssapi-keyex code (introduced by the distro[1] patch, already
present). Therefore, mistakes here should manifest themselves just in
the gssapi-keyex code, which wasn't working anyway. Effectively, though,
we are enabling a new authentication mechanism in sshd, one that was not
supposed to have been removed, but was broken by mistake.
-
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
+
+
+ 1.
https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/patches/gssapi.patch
+
[ Original 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
===
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
- This update adds a new autopkgtest to the package, which tests both
- gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
- and gssapi-keyex, which, before this update, does not work.
+ This update, besides fixing the patch, also adds a new autopkgtest to
+ the package, which tests both gssapi-with-mic ("normal" gssapi, which is
+ not affected by this bug), and gssapi-keyex, which, before this update,
+ did not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that change
is already present in the upstream code, and we are
[Touch-packages] [Bug 2060535] [NEW] apparmor's is_container_with_internal_policy() does not recognize incus
Public bug reported:
apparmor is not loading for Ubuntu containers under incus. This is due
to `/lib/apparmor/rc.apparmor.functions` (18.04 uses
`/lib/apparmor/functions`):
is_container_with_internal_policy() {
# this function is sometimes called independently of
# is_apparmor_loaded(), so also define this here.
local ns_stacked_path="${SFS_MOUNTPOINT}/.ns_stacked"
local ns_name_path="${SFS_MOUNTPOINT}/.ns_name"
local ns_stacked
local ns_name
if ! [ -f "$ns_stacked_path" ] || ! [ -f "$ns_name_path" ]; then
return 1
fi
read -r ns_stacked < "$ns_stacked_path"
if [ "$ns_stacked" != "yes" ]; then
return 1
fi
# LXD and LXC set up AppArmor namespaces starting with "lxd-" and
# "lxc-", respectively. Return non-zero for all other namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi
return 0
}
This can be fixed by adjusting it to have:
# LXD, LXC and incus set up AppArmor namespaces starting with "lxd-",
# "lxc-", and "incus-" respectively. Return non-zero for all other namespace
# identifiers.
read -r ns_name < "$ns_name_path"
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ] && \
[ "${ns_name#incus-*}" = "$ns_name" ] ; then
return 1
fi
References:
* https://github.com/lxc/incus/issues/740
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
apparmor is not loading for Ubuntu containers under incus. This is due
to `/lib/apparmor/rc.apparmor.functions` (18.04 uses
`/lib/apparmor/functions`):
+ is_container_with_internal_policy() {
+ # this function is sometimes called independently of
+ # is_apparmor_loaded(), so also define this here.
+ local ns_stacked_path="${SFS_MOUNTPOINT}/.ns_stacked"
+ local ns_name_path="${SFS_MOUNTPOINT}/.ns_name"
+ local ns_stacked
+ local ns_name
- is_container_with_internal_policy() {
- # this function is sometimes called independently of
- # is_apparmor_loaded(), so also define this here.
- local ns_stacked_path="${SFS_MOUNTPOINT}/.ns_stacked"
- local ns_name_path="${SFS_MOUNTPOINT}/.ns_name"
- local ns_stacked
- local ns_name
+ if ! [ -f "$ns_stacked_path" ] || ! [ -f "$ns_name_path" ]; then
+ return 1
+ fi
- if ! [ -f "$ns_stacked_path" ] || ! [ -f "$ns_name_path" ]; then
- return 1
- fi
+ read -r ns_stacked < "$ns_stacked_path"
+ if [ "$ns_stacked" != "yes" ]; then
+ return 1
+ fi
- read -r ns_stacked < "$ns_stacked_path"
- if [ "$ns_stacked" != "yes" ]; then
- return 1
- fi
+ # LXD and LXC set up AppArmor namespaces starting with "lxd-" and
+ # "lxc-", respectively. Return non-zero for all other namespace
+ # identifiers.
+ read -r ns_name < "$ns_name_path"
+ if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
+[ "${ns_name#lxc-*}" = "$ns_name" ]; then
+ return 1
+ fi
- # LXD and LXC set up AppArmor namespaces starting with "lxd-" and
- # "lxc-", respectively. Return non-zero for all other namespace
- # identifiers.
- read -r ns_name < "$ns_name_path"
- if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
- [ "${ns_name#lxc-*}" = "$ns_name" ]; then
- return 1
- fi
-
- return 0
+ return 0
}
- ```
This can be fixed by adjusting it to have:
- ```
- # LXD, LXC and incus set up AppArmor namespaces starting with "lxd-",
- # "lxc-", and "incus-" respectively. Return non-zero for all other
namespace
- # identifiers.
- read -r ns_name < "$ns_name_path"
- if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
- [ "${ns_name#lxc-*}" = "$ns_name" ] && \
- [ "${ns_name#incus-*}" = "$ns_name" ] ; then
- return 1
- fi
- return 0
+ # LXD, LXC and incus set up AppArmor namespaces starting with "lxd-",
+ # "lxc-", and "incus-" respectively. Return non-zero for all other
namespace
+ # identifiers.
+ read -r ns_name < "$ns_name_path"
+
[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Changed in: ppa-purge (Ubuntu Mantic) Status: In Progress => Fix Released ** Changed in: ppa-purge (Ubuntu Mantic) Status: Fix Released => Fix Committed ** Changed in: ppa-purge (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Fix Committed Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1' Selected version
[Touch-packages] [Bug 2058003] Re: Keine Freigabe
Nein die DAtei ist nicht im Papierkorb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058003 Title: Keine Freigabe Status in tzdata package in Ubuntu: Incomplete Bug description: Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf die Partition nicht um den Anteil gelöscht. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058003/+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 2059976] Re: unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed
I could easily add an examine option to show what the initramfs consists
of, e.g.
$ init-cpio --examine /boot/initrd.img
0: uncompressed cpio
123: uncompressed cpio
456: uncompressed cpio
7890: zstd compressd cpio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2059976
Title:
unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution
proposed
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to
parse headers of each entry in uncompressed archives.
> time unmkinitramfs 23.04/{initrd,unpack}
real0m3.625s
user0m1.595s
sys 0m3.467s
> time unmkinitramfs 23.10/{initrd,unpack}
real0m15.982s
user0m20.174s
sys 0m6.995s
> for dir in 23.04/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.04/unpack/early 5
23.04/unpack/early2 6
> for dir in 23.10/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.10/unpack/early 5
23.10/unpack/early2 6
23.10/unpack/early3 2874
Here https://github.com/slowpeek/unmkinitramfs-turbo I've made it a lot
faster with two changes:
- bash instead of sh for bash's "read -N"
- xxd dump of initrd instead of raw binary data
I wonder, if the developers are interested in accepting my improvements into
the code base?
> time unmkinitramfs-classic-turbo 23.10/{initrd,unpack}
real0m2.209s
user0m2.161s
sys 0m1.341s
> time unmkinitramfs-turbo 23.10/{initrd,unpack}
early .. +
early2 .. +
early3 .. +
main .. +
real0m1.973s
user0m2.094s
sys 0m1.244s
All tools in the repo, even the classic one, feature -s/--scan option. With
it, the tools only dump offset + size for embedded archives, nothing is
unpacked. It can be used to measure parsing speed.
In the repo there are three tools:
- unmkinitramfs-classic: the original tool
- unmkinitramfs-classic-turbo: the improved tool with minimal changes
- unmkinitramfs-turbo: the improved tool with many changes to my tastes,
extra dependency on "file" and some additional features (-ss option,
decompression with 7za)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059976/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Merge proposal linked: https://code.launchpad.net/~ghadi-rahme/ubuntu/+source/ppa-purge/+git/ppa-purge/+merge/463813 -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: In Progress Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: In Progress Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: In Progress Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm2' Selected version
[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Tags removed: verification-failed verification-failed-mantic ** Tags added: verification-needed verification-needed-mantic -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: In Progress Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: In Progress Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: In Progress Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm2' Selected version
[Touch-packages] [Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
Also see bug #2036358
--
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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online" does no longer work with latest noble image
Status in Netplan:
New
Status in Ubuntu on IBM z Systems:
New
Status in systemd package in Ubuntu:
New
Bug description:
Especially on s390x (but not limited to s390x) it's often the case that a
system has network devices that are not necessarily connected during boot-up
and one gets such a 2 min timeout:
"Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"
In the past I could avoid that by setting "optional: true" post-install (no
perfect, but worked),
but this does no longer seem to work using the latest noble ISO image (Apr
5th).
Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
this for me:
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enP1p0s0:
optional: true
dhcp4: true
enP1p0s0d1:
optional: true
dhcp4: true
enP2p0s0:
optional: true
dhcp4: true
enP2p0s0d1:
optional: true
dhcp4: true
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.11.12.15/24
gateway4: 10.11.12.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.11.12.1
... can be set fine (also --dry-run does not moan, except about
dhcp4).
This worked in the past on noble, but also on older Ubuntu releases
like jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2059976] Re: unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution proposed
> I have implemented the listing of uncompressed cpio archives (roughly
120 lines of code). Now I have to add the decompression support
Finding offsets of the embedded archives is the only time consuming part
of the whole script. Mby it is better to create a separate tool, say
"scaninitramfs", to only list offsets and size of embedded archives,
just like my tools' "-s" option does, and use it in the original script?
Scan output can be of interest beyond unmkinitramfs. For example, if you
need to know the compression used in some initrd. With a scan tool you
can quickly get the offset of the compressed cpio and "dd .. | file .."
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2059976
Title:
unmkinitramfs is very slow on initrd from ubuntu 23.10+, solution
proposed
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Since 23.10 the initrd consists of 4 embedded cpio:
- amd microcode
- intel microcode
- firmware + kernel modules
- rest (compressed)
Previously it was:
- amd microcode
- intel microcode
- rest (compressed)
There is no archive size header for cpio, so unmkinitramfs has to
parse headers of each entry in uncompressed archives.
> time unmkinitramfs 23.04/{initrd,unpack}
real0m3.625s
user0m1.595s
sys 0m3.467s
> time unmkinitramfs 23.10/{initrd,unpack}
real0m15.982s
user0m20.174s
sys 0m6.995s
> for dir in 23.04/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.04/unpack/early 5
23.04/unpack/early2 6
> for dir in 23.10/unpack/early*; do printf '%-20s %s\n' "$dir" "$(find
"$dir" | wc -l)"; done
23.10/unpack/early 5
23.10/unpack/early2 6
23.10/unpack/early3 2874
Here https://github.com/slowpeek/unmkinitramfs-turbo I've made it a lot
faster with two changes:
- bash instead of sh for bash's "read -N"
- xxd dump of initrd instead of raw binary data
I wonder, if the developers are interested in accepting my improvements into
the code base?
> time unmkinitramfs-classic-turbo 23.10/{initrd,unpack}
real0m2.209s
user0m2.161s
sys 0m1.341s
> time unmkinitramfs-turbo 23.10/{initrd,unpack}
early .. +
early2 .. +
early3 .. +
main .. +
real0m1.973s
user0m2.094s
sys 0m1.244s
All tools in the repo, even the classic one, feature -s/--scan option. With
it, the tools only dump offset + size for embedded archives, nothing is
unpacked. It can be used to measure parsing speed.
In the repo there are three tools:
- unmkinitramfs-classic: the original tool
- unmkinitramfs-classic-turbo: the improved tool with minimal changes
- unmkinitramfs-turbo: the improved tool with many changes to my tastes,
extra dependency on "file" and some additional features (-ss option,
decompression with 7za)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2059976/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
Hello Norbert, thank you for your testing and results. This issue is caused by the fact that Ubuntu server and Ubuntu desktop use different types of awk. Ubuntu server uses gawk (GNU awk) by default while Ubuntu desktop ships with mawk which has less features than gawk and does not have support for the -i argument hence the error "awk: not an option: -i". If your workflow depends on ppa-purge I recommend installing gawk (apt install gawk) and this will fix the issue temporarily while I get a permanent fix for ppa-purge. side note: I am not sure why there is a difference in the default awk installed/used between Ubuntu desktop and server maybe it is an oversight and should be labeled as a bug? or maybe there is another reason that someone could clarify? To my knowledge gawk is the default version of awk on most linux distros and has all the features of mawk. I will add gawk as a dependency to ppa-purge but I still believe that someone should look into why different versions of awk are shipped between server and desktop since this means shell scripts are not compatible between server and desktop by default. ** Changed in: ppa-purge (Ubuntu Mantic) Status: Fix Committed => In Progress ** Changed in: ppa-purge (Ubuntu Noble) Status: Fix Released => In Progress ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-failed verification-failed-mantic -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: In Progress Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: In Progress Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: In Progress Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version
[Touch-packages] [Bug 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS
Hi Seth, I do not think that we are using the wrong authorized key or keyfiles here, I have double checked. Also, if we were using the wrong keys, we would see the same issue in Ubuntu 18.04 and 20.04 (FIPS and non-FIPS), however, this is not so. We are only seeing this issue with Ubuntu 22.04 FIPS. Thanks -- 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/2059367 Title: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS Status in openssh package in Ubuntu: New Bug description: On a FIPS Enabled Ubuntu 22.04 kernel, we are seeing an issue with self-ssh. We created a key with the following steps: touch /home/core/.ssh/known_hosts ssh-keygen -q -t rsa -f /home/core/.ssh/id_rsa -N '' > /dev/null cp /home/core/.ssh/id_rsa.pub /home/core/.ssh/authorized_keys chmod 0600 /home/core/.ssh/id_rsa chmod 0600 /home/core/.ssh/authorized_keys When we try to do a self ssh with the key, the following happens: ssh -i .ssh/id_rsa onprem_shell@10.14.169.25 Connection closed by 10.14.169.25 port 22 FIPS status: cat /proc/sys/crypto/fips_enabled 1 PFB, the ssh dump: ssh -v user@10.14.169.25 OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: FIPS mode initialized debug1: Connecting to 10.14.169.25 [10.14.169.25] port 22. debug1: Connection established. debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa_sk type -1 debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: identity file /root/.ssh/id_ed25519_sk type -1 debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /root/.ssh/id_xmss type -1 debug1: identity file /root/.ssh/id_xmss-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 debug1: compat_banner: match: OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 pat OpenSSH* compat 0x0400 debug1: Authenticating to 10.14.169.25:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: ecdh-sha2-nistp256 debug1: kex: host key algorithm: ssh-rsa debug1: kex: server->client cipher: aes128-cbc MAC: hmac-sha1 compression: none debug1: kex: client->server cipher: aes128-cbc MAC: hmac-sha1 compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY Connection closed by 10.14.169.25 port 22 hostname -i 10.14.169.25 Please note that SSH onto other hosts (both FIPS and non-FIPS) works. The only workaround that we have found has been removing the ssh-rsa entry from “HostKeyAlgorithms” in “etc/ssh/sshd_config” and restarting the SSH service. This issue has neither been encountered in the Ubuntu 18.04 FIPS nor Ubuntu 20.04 FIPS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059367/+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 2059367] Re: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS
Hi João, we are installing FIPS packages by using the Pro token. PFB, the detailed debug logs of the SSH connection ssh -vv onprem_shell@10.14.169.25 OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 10.14.169.25 is address debug1: FIPS mode initialized debug1: Connecting to 10.14.169.25 [10.14.169.25] port 22. debug1: Connection established. debug1: identity file /home/core/.ssh/id_rsa type -1 debug1: identity file /home/core/.ssh/id_rsa-cert type -1 debug1: identity file /home/core/.ssh/id_ecdsa type -1 debug1: identity file /home/core/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/core/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/core/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/core/.ssh/id_ed25519 type -1 debug1: identity file /home/core/.ssh/id_ed25519-cert type -1 debug1: identity file /home/core/.ssh/id_ed25519_sk type -1 debug1: identity file /home/core/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/core/.ssh/id_xmss type -1 debug1: identity file /home/core/.ssh/id_xmss-cert type -1 debug1: identity file /home/core/.ssh/id_dsa type -1 debug1: identity file /home/core/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 debug1: compat_banner: match: OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 10.14.169.25:22 as 'onprem_shell' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,ext-info-c,kex-strict-c-...@openssh.com debug2: host key algorithms: ssh-rsa,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug2: ciphers ctos: aes128-cbc,aes256-cbc,aes128-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: ciphers stoc: aes128-cbc,aes256-cbc,aes128-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: MACs ctos: hmac-sha1 debug2: MACs stoc: hmac-sha1 debug2: compression ctos: none,z...@openssh.com,zlib debug2: compression stoc: none,z...@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,kex-strict-s-...@openssh.com debug2: host key algorithms: ssh-rsa,ecdsa-sha2-nistp256 debug2: ciphers ctos: aes128-cbc,aes256-cbc,aes128-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: ciphers stoc: aes128-cbc,aes256-cbc,aes128-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: MACs ctos: hmac-sha1 debug2: MACs stoc: hmac-sha1 debug2: compression ctos: none,z...@openssh.com debug2: compression stoc: none,z...@openssh.com debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: ecdh-sha2-nistp256 debug1: kex: host key algorithm: ssh-rsa debug1: kex: server->client cipher: aes128-cbc MAC: hmac-sha1 compression: none debug1: kex: client->server cipher: aes128-cbc MAC: hmac-sha1 compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY Connection closed by 10.14.169.25 port 22 Thanks -- 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/2059367 Title: SSH-RSA not supported for Self-SSH in Ubuntu 22.04 FIPS Status in openssh package in Ubuntu: New Bug description: On a FIPS Enabled Ubuntu 22.04 kernel, we are seeing an issue with self-ssh. We created a key with the following steps: touch /home/core/.ssh/known_hosts ssh-keygen -q -t rsa -f /home/core/.ssh/id_rsa -N '' > /dev/null cp /home/core/.ssh/id_rsa.pub /home/core/.ssh/authorized_keys chmod 0600 /home/core/.ssh/id_rsa chmod 0600 /home/core/.ssh/authorized_keys When we try to do a self ssh with the key, the following happens: ssh -i .ssh/id_rsa onprem_shell@10.14.169.25 Connection closed by 10.14.169.25 port 22 FIPS status: cat /proc/sys/crypto/fips_enabled 1 PFB, the ssh dump: ssh -v user@10.14.169.25 OpenSSH_8.9p1 Ubuntu-3ubuntu0.6+Fips1, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: FIPS mode initialized debug1: Connecting to 10.14.169.25 [10.14.169.25] port 22. debug1: Connection established. debug1:
[Touch-packages] [Bug 2060433] [NEW] Lack of GUI handled poorly
Public bug reported: As the graphical session failed to start, I tried to invoke apport- collect from terminal (with multi-user.target -ish level of services having already started), but it redirected me to the "default" browser, which happens to be firefox for GUI and lynx for terminal in my case. I couldn't progress after the password prompt as lynx apparently doesn't support http Referer feature. Here, apport should present its own login prompt or allow fetching the access token from system keyring for more robustness. ** Affects: apport Importance: Undecided Status: New ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: needs-design ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags added: needs-design -- 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/2060433 Title: Lack of GUI handled poorly Status in Apport: New Status in apport package in Ubuntu: New Bug description: As the graphical session failed to start, I tried to invoke apport- collect from terminal (with multi-user.target -ish level of services having already started), but it redirected me to the "default" browser, which happens to be firefox for GUI and lynx for terminal in my case. I couldn't progress after the password prompt as lynx apparently doesn't support http Referer feature. Here, apport should present its own login prompt or allow fetching the access token from system keyring for more robustness. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2060433/+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 2060431] [NEW] error message during gdebi-core installation
Public bug reported:
When installing gdebi I encounter the following message:
Setting up gdebi-core (0.9.5.7+nmu7) ...
/usr/share/gdebi/GDebi/GDebiCli.py:159: SyntaxWarning: invalid escape sequence
'\S'
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdebi-core 0.9.5.7+nmu7
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 8 08:40:37 2024
InstallationDate: Installed on 2024-04-08 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gdebi (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 gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/2060431
Title:
error message during gdebi-core installation
Status in gdebi package in Ubuntu:
New
Bug description:
When installing gdebi I encounter the following message:
Setting up gdebi-core (0.9.5.7+nmu7) ...
/usr/share/gdebi/GDebi/GDebiCli.py:159: SyntaxWarning: invalid escape
sequence '\S'
c = findall("[[(](\S+)/\S+[])]", msg)[0].lower()
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdebi-core 0.9.5.7+nmu7
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 8 08:40:37 2024
InstallationDate: Installed on 2024-04-08 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/2060431/+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 2000001] Re: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!
I could not determine exactly which part was having the problems, seems to me the dhcp client package or API to network-managers. To this ubuntu develop/changes much on parts the network management handling ubuntu go other ways than other Debian/Linux OS. If Company's disable IPV6 on local LAN for easy Firewall-Security-Handling, they will run into problems. I know IPv6 should be implemented but on small Areas it makes less sense. Users have still Problems on "easy" managing IPv6. They wont use small Routers to route local devices to the Internernet Provider's IPv6-DHCP Servers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!! Status in dhcp package in Ubuntu: New Status in dhcpcd package in Ubuntu: New Status in dhcpcd5 package in Ubuntu: New Status in isc-dhcp package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Status in wicd package in Ubuntu: New Bug description: Updated: 19.12.2022 # Hi Support at startup of analysis: Wifi5/6 dropped randomly if ipv6 is enabled/disabled on gnome-network-manager-gui no Error on Logs! No red Kernel Messages. My Lab: At my Lab i disabled all ipv6 on my Subnet LAN Openwrt-Routers, and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. First Handling: After i manual enable/disable WIFI by switch is works again fast. Analysis: After some search on Net i disabled ipv6 in sysctl.conf ! GTK-Apps Affected: seen on network-manager/network-manager-gnome/wicd Managers Hardware Change/Test: I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW mini-pci-cards same problem! Now testing again.. Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: http_proxy: http://127.0.0.1:8118/ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2022-06-30T19:17:37.737049 nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0b1 wifi connected/org/freedesktop/NetworkManager/Devices/3 AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b /org/freedesktop/NetworkManager/ActiveConnection/3 enp2s0ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled no_proxy: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp/+bug/201/+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
openssh-server_8.9p1-3ubuntu0.7_amd64.deb does fix the gssapi-keyex
problem for us on jammy
Syslog output is as expected
===
2024-04-08T08:09:53.608275+02:00 somehost sshd[169530]: Authorized to root,
krb5 principal xxx/r...@our.do.main (krb5_kuserok)
2024-04-08T08:09:53.619114+02:00 somehost sshd[169530]: Accepted gssapi-keyex
for root from 1.2.3.4 port 60232 ssh2: xxx/r...@our.do.main
===
--
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:
Fix Released
Status in openssh source package in Jammy:
Fix Committed
Status in openssh source package in Mantic:
Fix Committed
Status in openssh source package in Noble:
Fix Released
Bug description:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently
broken in openssh. It comes from a distro patch[1], and while the
patch still applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that
change is already present in the upstream code, and we are just
updating it in the new gssapi-keyex code (introduced by the distro[1]
patch, already present). Therefore, mistakes here should manifest
themselves just in the gssapi-keyex code, which wasn't working anyway.
Effectively, though, we are enabling a new authentication mechanism in
sshd, one that was not supposed to have been removed, but was broken
by mistake.
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
[ Original 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 2060291] Re: [Intel N95] Horizonral line artifact/ghosting when scaling windows to a certain width
** Summary changed:
- Horizonral line artifact/ghosting when scaling windows to a certain width
+ [Intel N95] Horizonral line artifact/ghosting when scaling windows to a
certain width
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Package changed: nautilus (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2060291
Title:
[Intel N95] Horizonral line artifact/ghosting when scaling windows to
a certain width
Status in linux package in Ubuntu:
New
Status in mesa package in Ubuntu:
New
Bug description:
When scaling some windows in some programs down horizontal lines
appear that seem to be part of the texture memory somewhere else on
the screen.
This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.
It did however occur when I opened the dialog in firefox to attach the
screen capture.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64
(20210915)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet
K-2024 Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060291/+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
