[Touch-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
re: tegra, I have no idea, mesa surely doesn't use any of this llvm: looking at focal, it seems libllvmNN is in main, the rest is in universe -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort
I tweaked the version numbers slightly (ubuntu1 -> ubuntu0.1) and uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Bionic: In Progress Status in libunwind source package in Focal: In Progress Bug description: [Impact] On architectures other than i386 and amd64, the C++ exception support in libunwind appears to be broken, always failing and calling std::terminate() which leads to the program aborting. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xf7c2daac in __GI_abort () at abort.c:79 #2 0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #3 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #4 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #5 0xf7e1f5e0 in __cxa_rethrow () from /lib/aarch64-linux-gnu/libstdc++.so.6 #6 0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #7 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #8 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #9 0xf7e1f574 in __cxa_throw () from /lib/aarch64-linux-gnu/libstdc++.so.6 #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9 #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9 Compiling libunwind with --enable-cxx-exceptions enabled leads to _Unwind_RaiseException being called during __cxa_throw(), which fails to find a handler, and the generic std::terminate() is called instead, aborting the program. On i386 and amd64 this doesn't seem to be the case, and the libunwind handlers seem to be present. To fix, we only enable the configure option --enable-cxx-exceptions on i386 and amd64 only, in debian/rules. This lets other architectures fall back to the symbols provided by libgcc_s, which implementation works correctly. [Testcase] Ali Sadi has provided a reproducer program. Start an arm64 instance, for example, a c6g.medium instance on AWS, with either Bionic or Focal. $ wget https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz $ sudo apt install -y build-essential libunwind-dev $ tar xvf libunwind.tar.gz && cd test $ make all There are two executable, main and main_unwind. main is not linked to libunwind, and main_unwind is linked to libunwind. $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) If you install the test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test $ make clean $ sudo apt install -y libunwind-dev $ make all $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main The exception is caught as expected the program does not abort. [Where problems could occur] For architectures other than i386 and amd64, we are changing from libunwind provided exception handlers for __cxa_throw(), and using those provided by libgcc_s instead. There are a few reverse dependencies for libunwind-dev and libunwind8, which need to be considered: $ apt rdepends libunwind-dev libunwind-dev Reverse Depends: Depends: libunwind-setjmp0-dev (= 1.2.1-9build1) Depends: libefl-all-dev t$ apt rdepends libunwind-dev8 libunwind8 Reverse Depends: Depends: libunwind-dev (= 1.2.1-9build1) Depends: xvfb Depends: xnest Depends: xdmx Depends: xwayland Depends: xserver-xorg-core Depends: xserver-xephyr Depends: linux-tools-5.4.0-* Depends: linux-raspi-tools-* Depends: linux-raspi2-tools-5.4.0-* Depends: linux-raspi2-5.4-tools-5.4.0-* Depends: linux-oracle-5.15-tools-5.15.0-* Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-* Depends: linux-hwe-5.8-tools-5.8.0-* Depends: linux-hwe-5.15-tools-5.15.0-* Depends: linux-gke-tools-5.4.0-* Depends: linux-gke-5.15-tools-5.15.0-* Depends: linux-gcp-tools-5.4.0-* Depends: linux-gcp-5.15-tools-5.15.0-* Depends: linux-azure-tools-5.4.0-* Depends: linux-azure-5.15-tools-5.15.0-* Depends: linux-aws-tools-5.4.0-* Depends: linux-aws-5.8-tools-5.8.0-* Depends: linux-aws-5.15-tools-5.15.0-* Depends: xvfb Depends: xnest Depends: xdmx Depends: trafficserver Depends: tilix Depends:
[Touch-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
llvm-toolchain-15 will presumably need to be promoted to main in jammy- proposed/-updates, yes? I'm not familiar with the process of backporting NEW packages into main; presumably because it's in main in lunar that'll be ok, but I'd like to check with the MIR team that my assumption is correct. -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1724623] Re: Update ubuntu cloud info
The attachment "apport_cloud.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
Right, but as far as the archive is concerned, libdrm-tegra0 itself is unused :) What code *does* use libdrm-tegra0, and how sure are we that it doesn't use those symbols (even accidentally)? -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: In Progress Status in llvm-toolchain-15 source package in Jammy: In Progress Status in mesa source package in Jammy: In Progress Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: In Progress Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1999698] Re: Dodgy looking patch applied to our build.
Please see https://salsa.debian.org/freedesktop- team/accountsservice/-/commit/19eaa3f1 ** Changed in: accountsservice (Ubuntu) Status: New => Fix Committed ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: Fix Committed Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+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 1998787] Re: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable.
Sponsored, thanks Dave! ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Dan Bungert (dbungert) ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Wishlist ** Changed in: unattended-upgrades (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1998787 Title: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable. Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Please merge unattended-upgrades 2.9.1+nmu2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1998787/+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 1724623] Re: Update ubuntu cloud info
Attached is a possible patch to remedy some of the issues (and a few other bugs i've seen in the backlog with errors re: EC2 and other clouds). the gist: 1. change how we check if something is a cloud-image, generally 2. use /etc/cloud/build.info as a check if something is a Canonical cloud image 2a. if it's rolled by someone else, hard to guarantee things 3. use /run/cloud-init/instance-data.json as a local store of info 3a. this will run on most supported clouds, and provide more info I've tried to make some graceful warning prints and error catches, along the lines of "if it's not there, just move on." ** Patch added: "apport_cloud.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+attachment/5635644/+files/apport_cloud.patch -- 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/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1981385] Re: initrd lacks modules to mount boot image from http boot
** Tags removed: foundations-todo
--
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/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the
initrd; presumably some modules are missing. Dimitri added some
modules that are clearly going to be necessary (kernel/drivers/nvdimm)
in 0.140ubuntu14 and I added kernel/drivers/dax too in local
experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a
machine via http boot and the installer just works as normal (the
speed and, uh, quality, of the implementation of HTTP in a given
machine's firmware may mean this isn't always the best option but it
would be nice if it worked in case someone's machine actually does
this well).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1999698] [NEW] Dodgy looking patch applied to our build.
Public bug reported: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: New Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+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 1981385] Re: initrd lacks modules to mount boot image from http boot
This bug was fixed in the package initramfs-tools - 0.140ubuntu13.1
---
initramfs-tools (0.140ubuntu13.1) jammy; urgency=medium
* Backport pmem support from kinetic by adding the nvdimm, dax, and nfit
modules (LP: #1981385)
-- Dan Bungert Thu, 27 Oct 2022
11:44:07 -0600
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385
Title:
initrd lacks modules to mount boot image from http boot
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Jammy:
Fix Released
Bug description:
[ Impact ]
* If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can
access the boot image as /dev/pmem0. But this is not accessible in
the initrd; presumably some modules are missing.
* This is desirable because then you can just feed an installer ISO to
a machine via http boot and the installer just works as normal
* Add support for physical pmem devices, and simulation thereof with
the memmap kernel command line parameter
* The initrd is larger
[ Test Plan ]
* unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are not present
* install the updated initramfs-tools packages from proposed
* again unpack an initrd on a Jammy system with the generic kernel
metapackage with unmkinitramfs
* observe that the directories kernel/drivers/{nvdimm,dax,acpi/nfit}
are present now
* reboot to confirm that the system still boots
* modify /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT to contain a
memmap entry - memmap=1G!4G seems to work on many systems over 4G of
RAM, or do `dmesg | grep BIOS-e820` to observe the memory regions
and select a usable one.
* update-grub and reboot again
* a /dev/pmem device should now be present on the system
[ Where problems could occur ]
* The growth of the files in /boot will accelerate issues for users
who have a dedicated boot partition that is not large enough
[ Other Info ]
* Details on the memmap kernel command line parameter:
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
* PMEM simulation with memmap:
https://docs.pmem.io/persistent-memory/getting-started-guide/creating-development-environments/linux-environments/linux-memmap
[ Original Bug Description ]
If you use UEFI http boot to boot an image (rather than an EFI
executable) and get all the way to a normal userspace, you can access
the boot image as /dev/pmem0. But this is not accessible in the
initrd; presumably some modules are missing. Dimitri added some
modules that are clearly going to be necessary (kernel/drivers/nvdimm)
in 0.140ubuntu14 and I added kernel/drivers/dax too in local
experiments but this appears not to be enough to get it to appear.
This is desirable because then you can just feed an installer ISO to a
machine via http boot and the installer just works as normal (the
speed and, uh, quality, of the implementation of HTTP in a given
machine's firmware may mean this isn't always the best option but it
would be nice if it worked in case someone's machine actually does
this well).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981385/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello Togo28, or anyone else affected, Accepted evince into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/42.3-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: evince (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: New Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1997036] Re: python-apt: FTBFS with Python 3.11 as a supported version
This bug was fixed in the package python-apt - 2.5.0 --- python-apt (2.5.0) unstable; urgency=medium [ Jelmer Vernooij ] * Fix attribute name in indexfile.py. * Expose MetaIndex.type. [ Michael Vogt ] * debian: remove `python3-*-dbg` packages (Closes: #994348) * apt: fix mypy in apt.progress.text.AcquireProgress [ Julian Andres Klode ] * AcquireFile: Handle large files (LP: #1998265) * apt/progress/base.py: Return False in default cdrom change * Code style fixes * Mirror list updates * d/t/control: Depend on binutils for ar * Untrack all GC tracked objects before freeing them (LP: #1997036) [ Steve Langasek ] * Drop references to archive.canonical.com (LP: #1959343) -- Julian Andres Klode Wed, 30 Nov 2022 17:35:59 +0100 ** Changed in: python-apt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1997036 Title: python-apt: FTBFS with Python 3.11 as a supported version Status in python-apt package in Ubuntu: Fix Released Bug description: python-apt FTBFS with Python 3.11 as a supported version: https://launchpad.net/ubuntu/+source/python-apt/2.3.0ubuntu3 I've copied what I hope is the relevant part of the log below. I: pybuild base:240: env PYTHONPATH=/<>/.pybuild/cpython3_3.11_dbg_apt/build python3.11-dbg tests/test_all.py [tests] Running on 3.11.0+ (main, Nov 4 2022, 09:23:33) [GCC 12.2.0] Using pybuild supplied build dir s...gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction gc:0: ResourceWarning: Object of type apt_pkg.Package is not untracked before destruction ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1997036/+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 1998265] Re: OverFlow error when using cnf-extractor
This bug was fixed in the package python-apt - 2.5.0 --- python-apt (2.5.0) unstable; urgency=medium [ Jelmer Vernooij ] * Fix attribute name in indexfile.py. * Expose MetaIndex.type. [ Michael Vogt ] * debian: remove `python3-*-dbg` packages (Closes: #994348) * apt: fix mypy in apt.progress.text.AcquireProgress [ Julian Andres Klode ] * AcquireFile: Handle large files (LP: #1998265) * apt/progress/base.py: Return False in default cdrom change * Code style fixes * Mirror list updates * d/t/control: Depend on binutils for ar * Untrack all GC tracked objects before freeing them (LP: #1997036) [ Steve Langasek ] * Drop references to archive.canonical.com (LP: #1959343) -- Julian Andres Klode Wed, 30 Nov 2022 17:35:59 +0100 ** Changed in: python-apt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Focal: Fix Committed Status in python-apt source package in Jammy: Fix Committed Status in python-apt source package in Kinetic: Fix Committed Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. For kinetic, the package was copied in from lunar without changes. This upload is actually built in kinetic and hence there is additional regression potential from toolchain changes. [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1999258] Re: Please merge dbus 1.14.4-1 from Debian unstable.
Attaching patch against Debian unstable. For ease of review, relevant commits and tags have been pushed to the following repository: https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus Specifically: * logical/1.14.0-2ubuntu3 represents our split-out delta on top of old/debian (1.14.0-2) * logical/1.14.4-1ubuntu1 represents our rebased delta on top of new/debian (1.14.4-1) * merge/1.14.4-1ubuntu1 just adds changelog and maintainer changes on top of logical/1.14.4-1ubuntu1 Hence, the following command may produce output useful to the purposes of review: git range-diff old/debian..logical/1.14.0-2ubuntu3 new/debian..logical/1.14.4-1ubuntu1 Test packages are building in ppa:waveform/dbus (https://launchpad.net/~waveform/+archive/ubuntu/dbus) ** Patch added: "1-1999258.debdiff" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+attachment/5635632/+files/1-1999258.debdiff ** Tags added: fr-3127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1999258 Title: Please merge dbus 1.14.4-1 from Debian unstable. Status in dbus package in Ubuntu: New Bug description: Please merge dbus 1.14.4-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1999258/+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 1239756] Re: apport-bug linux hangs forever at "collecting problem information"
same issue as in https://bugs.launchpad.net/launchpad/+bug/1996471 -- 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/1239756 Title: apport-bug linux hangs forever at "collecting problem information" Status in apport package in Ubuntu: Confirmed Bug description: also apport-cli ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportLog: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 12:13:38 2013 InstallationDate: Installed on 2013-09-17 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1239756] Re: apport-bug linux hangs forever at "collecting problem information"
same for me. Bug report is https://bugs.launchpad.net/ubuntu/+source/gdm3/+filebug/2954d34c-7bd9-11ed-8040-40a8f03099c8? ** Changed in: apport (Ubuntu) Status: Incomplete => Confirmed -- 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/1239756 Title: apport-bug linux hangs forever at "collecting problem information" Status in apport package in Ubuntu: Confirmed Bug description: also apport-cli ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportLog: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 12:13:38 2013 InstallationDate: Installed on 2013-09-17 (26 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1999625] Re: man page for copy_file_range() not up to date with mainstream
** Package changed: coreutils (Ubuntu) => ubuntu-docs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1999625 Title: man page for copy_file_range() not up to date with mainstream Status in ubuntu-docs package in Ubuntu: New Bug description: The man page for copy_file_range() system call is not up to date with the corresponding mainline kernel release. For example, the contents of the following commit is not there when I run man 2 copy_file_range: https://git.kernel.org/pub/scm/docs/man-pages/man- pages.git/commit/?id=d7ba612d0ab10af2ed4e367306784212cc3f3595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1999625/+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 1724623] Re: Update ubuntu cloud info
Can you provide some example /etc/cloud/build.info and /run/cloud- init/cloud.cfg files and expected output for them? Then I could write that code. -- 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/1724623 Title: Update ubuntu cloud info Status in apport package in Ubuntu: New Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+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 1993409] Re: Merge libmnl from Debian unstable for l-series
No new upload to debian yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libmnl in Ubuntu. https://bugs.launchpad.net/bugs/1993409 Title: Merge libmnl from Debian unstable for l-series Status in libmnl package in Ubuntu: Incomplete Bug description: Scheduled-For: ubuntu-22.12 Upstream: tbd Debian: 1.0.4-3 Ubuntu: 1.0.4-3ubuntu1 ### Old Ubuntu Delta ### libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium * Static build does not work for libmnl (-lmnl) (LP: #1971523) -- Michal Maloszewski Thu, 21 Jul 2022 14:02:16 +0200 libmnl (1.0.4-3build2) jammy; urgency=high * No change rebuild for ppc64el baseline bump. -- Julian Andres Klode Thu, 24 Mar 2022 13:13:28 +0100 libmnl (1.0.4-3build1) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:16:42 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1993409/+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 1999625] Re: man page for copy_file_range() not up to date with mainstream
** Package changed: ubuntu => coreutils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1999625 Title: man page for copy_file_range() not up to date with mainstream Status in coreutils package in Ubuntu: New Bug description: The man page for copy_file_range() system call is not up to date with the corresponding mainline kernel release. For example, the contents of the following commit is not there when I run man 2 copy_file_range: https://git.kernel.org/pub/scm/docs/man-pages/man- pages.git/commit/?id=d7ba612d0ab10af2ed4e367306784212cc3f3595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1999625/+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 1999625] [NEW] man page for copy_file_range() not up to date with mainstream
You have been subscribed to a public bug: The man page for copy_file_range() system call is not up to date with the corresponding mainline kernel release. For example, the contents of the following commit is not there when I run man 2 copy_file_range: https://git.kernel.org/pub/scm/docs/man-pages/man- pages.git/commit/?id=d7ba612d0ab10af2ed4e367306784212cc3f3595 ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment manpage -- man page for copy_file_range() not up to date with mainstream https://bugs.launchpad.net/bugs/1999625 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998970] Re: Remove pypy from lunar
python-ipaddress was removed by Steve Langasek. ** Changed in: python-ipaddress (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1998970 Title: Remove pypy from lunar Status in pypy package in Ubuntu: New Status in python-ipaddress package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in rawkit package in Ubuntu: Fix Released Bug description: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) Resolved Reverse-Build-Depends: * python-cheroot >= 9.0.0+ds1-2 Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypy/+bug/1998970/+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 1998970] Re: Remove pypy from lunar
rawkit was removed by Steve Langasek. ** Changed in: rawkit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1998970 Title: Remove pypy from lunar Status in pypy package in Ubuntu: New Status in python-ipaddress package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in rawkit package in Ubuntu: Fix Released Bug description: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) Resolved Reverse-Build-Depends: * python-cheroot >= 9.0.0+ds1-2 Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypy/+bug/1998970/+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 1998970] Re: Remove pypy from lunar
python-setuptools was removed by Steve Langasek. ** Changed in: python-setuptools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1998970 Title: Remove pypy from lunar Status in pypy package in Ubuntu: New Status in python-ipaddress package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in rawkit package in Ubuntu: Fix Released Bug description: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) Resolved Reverse-Build-Depends: * python-cheroot >= 9.0.0+ds1-2 Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypy/+bug/1998970/+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 1998970] Re: Remove pypy from lunar
Synced python-cheroot 9.0.0+ds1-2 from Debian unstable which removes the dependency on pypy-lib. ** Description changed: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) - * python-cheroot(for pypy-lib) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) + Resolved Reverse-Build-Depends: + * python-cheroot >= 9.0.0+ds1-2 + Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1998970 Title: Remove pypy from lunar Status in pypy package in Ubuntu: New Status in python-ipaddress package in Ubuntu: Fix Released Status in python-setuptools package in Ubuntu: Fix Released Status in rawkit package in Ubuntu: Fix Released Bug description: pypy is an alternative implementation of Python2 and was very recently removed from Debian. (There is now a pypy3 source package instead.) We need to remove pypy from Ubuntu Lunar because its autopkgtest failure is blocking the migration of several packages. However, someone will need to work through these reverse dependencies: $ reverse-depends -b -r lunar src:pypy Reverse-Build-Depends * pypy (for pypy) * python-ipaddress (for pypy) * python-setuptools (for pypy) * rawkit(for pypy) Resolved Reverse-Build-Depends: * python-cheroot >= 9.0.0+ds1-2 Resolved Reverse-Testsuite-Triggers: * python-virtualenv >= 20.16.3+ds-4.1 * dh-python >= 5.20221205 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pypy/+bug/1998970/+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 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
Have the same bug is in Ubuntu 20.04.5 and isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.4 It's very sad that bug is still haven't been fixed since 2015(!) year. For myself I solve it with rc.local: sleep 5 /usr/bin/systemctl restart isc-dhcp-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
** Description changed: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` - Based on grub_mm_dump, we can see the memory fragment (some parts seem - likely be used because of 4K resolution?) and doesn’t have available - contiguous memory for larger file as: - - ``` - grub_real_malloc(...) + Based on grub_mm_dump, we can see the memory region starvation in <1G + addresses: + + Type StartEnd # Pages Attributes + Available -00086FFF 0087 000F + BS_Data00087000-00087FFF 0001 000F + Available 00088000-0009EFFF 0017 000F + Reserved 0009F000-0009 0001 000F + Available 0010-00FF 0F00 000F + LoaderCode 0100-01021FFF 0022 000F + Available 01022000-238A7FFF 00022886 000F + BS_Data238A8000-23927FFF 0080 000F + Available 23928000-28860FFF 4F39 000F + BS_Data28861000-2AB09FFF 22A9 000F + LoaderCode 2AB0A000-2ACF8FFF 01EF 000F + BS_Data2ACF9000-2B2FAFFF 0602 000F + Available 2B2FB000-2B611FFF 0317 000F + BS_Data2B612000-2B630FFF 001F 000F + Available 2B631000-2B632FFF 0002 000F + BS_Data2B633000-2B63CFFF 000A 000F + Available 2B63D000-2B649FFF 000D 000F + BS_Data2B64A000-2B64EFFF 0005 000F + Available 2B64F000-2B666FFF 0018 000F + BS_Data2B667000-2D8D5FFF 226F 000F + LoaderCode 2D8D6000-2D8E9FFF 0014 000F + BS_Data2D8EA000-2D925FFF 003C 000F + LoaderCode 2D926000-2D932FFF 000D 000F + BS_Data2D933000-2D969FFF 0037 000F + BS_Code2D96A000-2D973FFF 000A 000F + BS_Data2D974000-2E377FFF 0A04 000F + Available 2E378000-2E37AFFF 0003 000F ... - if (cur->size >= n + extra) - ``` + Reserved 3C08B000-4192 58A5 000F + ACPI_NVS 4193-41B2 0200 000F + ACPI_Recl 41B3-41BFEFFF 00CF 000F + BS_Data41BFF000-41BF 0001 000F + Available 0001-0002AB7F 001AB800 000F + Reserved 000A-000F 0060 + Reserved 41C0-43FF 2400 + Reserved 4400-47FF 4000 000F + Reserved 4940-495F 0200 000F + Reserved 4C00-4FFF 4000 0009 + Reserved 5000-547F 4800 + MMIO C000-CFFF 0001
[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
could those having the issue also share output of $ echo $DESKTOP_SESSION ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: New Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
raof: if you mean removing the ioctl thing, they're apparently unused:
commit bec2a28e98f430f4a82b085b4d1c69a98988359f
Author: Thierry Reding
Date: Fri Jul 9 19:53:52 2021 +0200
tegra: Remove unused IOCTL implementations
The DRM_TEGRA_GEM_{GET,SET}_FLAGS and DRM_TEGRA_GEM_{GET,SET}_TILING
IOCTLs were badly designed and have since been obsoleted by framebuffer
modifiers. Remove these implementations to make it clear their usage is
discouraged.
--- a/tegra/tegra-symbols.txt
+++ b/tegra/tegra-symbols.txt
@@ -1,11 +1,7 @@
-drm_tegra_bo_get_flags
drm_tegra_bo_get_handle
-drm_tegra_bo_get_tiling
drm_tegra_bo_map
drm_tegra_bo_new
drm_tegra_bo_ref
-drm_tegra_bo_set_flags
-drm_tegra_bo_set_tiling
drm_tegra_bo_unmap
drm_tegra_bo_unref
drm_tegra_bo_wrap
I don't see other breakage, just additions
** Description changed:
[Impact
The graphics HWE stack from kinetic needs to be backported for 22.04.2
directx-headers
- build-dep of the new Mesa
libdrm
- build-dep of the new Mesa
llvm-15
- new package in jammy
- build-dep of the new Mesa
mesa
- new major release (22.2.x)
- new HW support, like AMD RDNA3, Intel DG2
spirv-headers
- needed by s-l-t-15
spirv-llvm-translator-14
- needed to bootstrap libclc from llvm
spirv-llvm-translator-15
- needed for the actual libclc-15 after initial bootstrap
Bootstrapping plan:
- s-l-t-14 built from NEW
- llvm-15 built with s-l-t-14
- s-l-t-15 built against llvm-15
- llvm-15 built again with s-l-t-15
-> mesa ready for building
[Test case]
Install the new mesa on various hw, see that everything still works like
before or better.
+ spirv-headers:
+ - test reverse-build-deps that they still build
+ Reverse-Build-Depends
+ * glslang
+ * intel-graphics-compiler
+ * spirv-llvm-translator-14
+ * spirv-llvm-translator-15
+ * spirv-tools
+ * vkbasalt
+ * vkd3d
+ * vulkan-validationlayers
+
[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll backport
the final stable release of 22.2.x in order to minimize the chance for those.
--
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/1991761
Title:
Backport packages for 22.04.2 HWE stack
Status in directx-headers package in Ubuntu:
Invalid
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-15 package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Invalid
Status in spirv-headers package in Ubuntu:
Invalid
Status in spirv-llvm-translator-14 package in Ubuntu:
Invalid
Status in spirv-llvm-translator-15 package in Ubuntu:
Invalid
Status in directx-headers source package in Jammy:
Fix Committed
Status in libdrm source package in Jammy:
In Progress
Status in llvm-toolchain-15 source package in Jammy:
In Progress
Status in mesa source package in Jammy:
In Progress
Status in spirv-headers source package in Jammy:
Fix Committed
Status in spirv-llvm-translator-14 source package in Jammy:
In Progress
Status in spirv-llvm-translator-15 source package in Jammy:
In Progress
Bug description:
[Impact
The graphics HWE stack from kinetic needs to be backported for 22.04.2
directx-headers
- build-dep of the new Mesa
libdrm
- build-dep of the new Mesa
llvm-15
- new package in jammy
- build-dep of the new Mesa
mesa
- new major release (22.2.x)
- new HW support, like AMD RDNA3, Intel DG2
spirv-headers
- needed by s-l-t-15
spirv-llvm-translator-14
- needed to bootstrap libclc from llvm
spirv-llvm-translator-15
- needed for the actual libclc-15 after initial bootstrap
Bootstrapping plan:
- s-l-t-14 built from NEW
- llvm-15 built with s-l-t-14
- s-l-t-15 built against llvm-15
- llvm-15 built again with s-l-t-15
-> mesa ready for building
[Test case]
Install the new mesa on various hw, see that everything still works like
before or better.
spirv-headers:
- test reverse-build-deps that they still build
Reverse-Build-Depends
* glslang
* intel-graphics-compiler
* spirv-llvm-translator-14
* spirv-llvm-translator-15
* spirv-tools
* vkbasalt
* vkd3d
* vulkan-validationlayers
[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll backport
the final stable release of 22.2.x in order to minimize the chance for those.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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
