[Touch-packages] [Bug 2041779] Re: lscpu shows wrong L3 Cache size on NVIDIA Orin Nano
We tried lscpu 2.37.2, and it could also show correct information. So the fix change should be merged during 2.34 to 2.37. Please help on this issue to backport the fix change to 2.34 for Ubuntu focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2041779 Title: lscpu shows wrong L3 Cache size on NVIDIA Orin Nano Status in util-linux package in Ubuntu: New Bug description: For NVIDIA Orin Nano, L3 all cache size is 4M. But we got different result via lscpu comes from different version of util-linux: lscpu from util-linux 2.34 which is the default version in Ubuntu focal (20.04) and shows wrong information: # lscpu -C// lscpu bin from util-linux 2.34 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL L1d 64K 384K4 Data1 L1i 64K 384K4 Instruction 1 L2 256K 1.5M8 Unified 2 L3 2M 2M 16 Unified 3 # lscpu L1d cache: 384 KiB L1i cache: 384 KiB L2 cache:1.5 MiB L3 cache:2 MiB lscpu from util-linux 2.39 shows correct information, and this version is only packaged for Ubuntu mantic (23.10): # lscpu -C// lscpu bin from util-linux 2.39 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL SETS PHY-LINE COHERENCY-SIZE L1d 64K 384K4 Data1 256 64 L1i 64K 384K4 Instruction 1 256 64 L2 256K 1.5M8 Unified 2 512 64 L3 2M 4M 16 Unified 3 2048 64 # lscpu Caches (sum of all): L1d: 384 KiB (6 instances) L1i: 384 KiB (6 instances) L2:1.5 MiB (6 instances) L3:4 MiB (2 instances) Looks like there was a fix during version 2.34 to 2.39, but we need to use Ubuntu 20.04. Can you please backport the fix change to 2.34 then we can get correct information using default lscpu for Ubuntu 20.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2041779/+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 2040051] Re: systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument"
cgroupsv2 has been the default for a few releases now, so it's odd that you are running cgroupsv1. Can you share /proc/cmdline? I haven't looked close enough to see if this would actually cause this error, but since this error seems odd as it is, I wouldn't be surprised. -- 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/2040051 Title: systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument" Status in systemd package in Ubuntu: New Bug description: # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # aptitude show systemd Package: systemd Version: 253.5-1ubuntu6 State: installed systemd-networkd-wait-online terminates with "Could not create manager: Invalid argument". This lets the corresponding service (systemd-networkd-wait- online.service) fail as well. The error also appears when one directly invokes /lib/systemd/systemd-networkd-wait-online from a shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2040051/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2042587] [NEW] jammy's version breaks existing dhcp scripts with relay
Public bug reported: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp-script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: New Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
Updated regression potential with theoretical issues, and other info with status in main for protection-domain-mapper and qrtr. ** Description changed: [ Impact ] - * ubuntu-seeds were changed since last meta update - * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release + * ubuntu-seeds were changed since last meta update + * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] - * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to + * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] - * This is automatically generated change + * This is automatically generated change based on ubuntu-seeds commit + [1]. + + * Theoretically, regressions would occur if new desktop-minimal-recommends +dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): +- have issues on install during release-upgrade; +- have issues on regular system usage (after installed). [ Other Info ] - - * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + + * ubuntu-meta was not uploaded during final freeze, to prevent + rebuilding all images as changes affect arm64 only, which is a brand new + release image + + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- + seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. - * Theoretically, regressions would occur if new desktop-minimal-recommends -dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): -- have issues on install during release-upgrade; -- have issues on regular system usage (after installed). + * Theoretically, regressions would occur if new desktop-minimal-recommends + dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): + - have issues on install during release-upgrade; + - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image + * protection-domain-mapper and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a ** Description changed: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image - * protection-domain-mapper and qrtr moved from universe to main in Mantic. - * flash-kernel is/was already in main. + * protection-domain-mapper [2] and qrtr moved from universe to main in Mantic. + * flash-kernel is/was already in main. - [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu- - seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a + [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory + [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta
[Touch-packages] [Bug 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
The changes are not yet in the development release (Noble). Submitted MR [1] with noble series update + these changes. [1] https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu- meta/+git/ubuntu-meta/+merge/455081 ** Merge proposal linked: https://code.launchpad.net/~mfo/ubuntu/+source/ubuntu-meta/+git/ubuntu-meta/+merge/455081 ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Status: New => Confirmed ** Changed in: ubuntu-meta (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: ubuntu-meta (Ubuntu Noble) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- 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/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-meta source package in Noble: Confirmed Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2040108] Re: error "contains an invalid sample specification."
** Description changed: After upgrade network audio stop working. - On the remote side in log i see: - "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid s - ample specification." + On the client side in log i see: + "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/2040108 Title: error "contains an invalid sample specification." Status in pulseaudio package in Ubuntu: New Bug description: After upgrade network audio stop working. On the client side in log i see: "CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series' contains an invalid sample specification." Microphone sink work, but playback not. I tried as client ubuntu 23.04 and 23.10, so I suppose issue in zeroconf-publish Just specifying env PULSE_SERVER play sound fine. Also will be great if zeroconf-publish can filter what to export, at least disable microphone. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio-module-zeroconf 1:16.1+dfsg1-2ubuntu4 Uname: Linux 6.2.16-060216-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vova 1822 F wireplumber /dev/snd/controlC2: vova 1822 F wireplumber /dev/snd/controlC1: vova 1822 F wireplumber /dev/snd/seq:vova 1820 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Oct 22 17:04:30 2023 InstallationDate: Installed on 2023-04-01 (204 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230401) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to mantic on 2023-10-15 (7 days ago) dmi.bios.date: 08/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FEb dmi.board.asset.tag: Default string dmi.board.name: B550 AORUS ELITE V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrFEb:bd08/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 AORUS ELITE V2 dmi.product.sku: Default
[Touch-packages] [Bug 2042583] [NEW] apt show, info inadvertently do not support various options such as --snapshot
Public bug reported: Most commands inherit their arguments from apt-get or apt-cache functions, but these apt show/info (as well as apt list) are special and do not inherit anything, this needs fixing, it also seems likely apt list would want to support stuff like target-release that is generally supported by apt-cache. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2042583 Title: apt show, info inadvertently do not support various options such as --snapshot Status in apt package in Ubuntu: New Bug description: Most commands inherit their arguments from apt-get or apt-cache functions, but these apt show/info (as well as apt list) are special and do not inherit anything, this needs fixing, it also seems likely apt list would want to support stuff like target-release that is generally supported by apt-cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2042583/+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 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
Hi Alex. Have you tried applying the workaround I mentioned above before
attempting the update, namely `sudo find /etc/apparmor.d/cache/* -type d
-exec rm -r {} \;`? Using that allowed the update of many instances to
work without any related problems.
--
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/2032851
Title:
package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new
apparmor package pre-installation script subprocess returned error
exit status 1
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Focal:
In Progress
Bug description:
[ Impact ]
* During an apparmor package upgrade, the cache files were
deleted, but there could also be directories under
/etc/apparmor.d/cache/ which the pre installation scripts did
not account for. The upgrade would then fail with the
following error message because it would not be able to remove
the directories:
package:apparmor:2.12-4ubuntu5.3
Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
dpkg: error processing archive
/tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit
status 1
ErrorMessage: new apparmor package pre-installation script subprocess
returned error exit status 1
[ Test Plan ]
* On a bionic machine, create a directory under
/etc/apparmor.d/cache
sudo mkdir /etc/apparmor.d/cache/test
* To simulate a system upgrade to focal, you can run the following
steps
1. Add the focal archive
sudo bash -c "cat
[Touch-packages] [Bug 2042549] [NEW] Xorg crash
Public bug reported: Have a constant random crashes of Xwayland on almost idle PC. Never had any GUI crash issues with 20.04 on the exactly same hardware (same pc). As a result all applications are killed and work is not saved... [146226.831803] nouveau :01:00.0: gr: TRAP ch 2 [00ffe45000 Xwayland[3977]] [146226.831818] nouveau :01:00.0: gr: GPC0/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831825] nouveau :01:00.0: gr: GPC0/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b020020 [] [146226.831833] nouveau :01:00.0: gr: GPC0/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831838] nouveau :01:00.0: gr: GPC0/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831844] nouveau :01:00.0: gr: GPC0/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831849] nouveau :01:00.0: gr: GPC0/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b030020 [] [146226.831857] nouveau :01:00.0: gr: GPC1/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831862] nouveau :01:00.0: gr: GPC1/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b030020 [] [146226.831870] nouveau :01:00.0: gr: GPC1/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831875] nouveau :01:00.0: gr: GPC1/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831880] nouveau :01:00.0: gr: GPC1/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831885] nouveau :01:00.0: gr: GPC1/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831894] nouveau :01:00.0: gr: GPC2/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831899] nouveau :01:00.0: gr: GPC2/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b010020 [] [146226.831906] nouveau :01:00.0: gr: GPC2/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831912] nouveau :01:00.0: gr: GPC2/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831917] nouveau :01:00.0: gr: GPC2/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831922] nouveau :01:00.0: gr: GPC2/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831929] nouveau :01:00.0: gr: GPC2/TPC3/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831935] nouveau :01:00.0: gr: GPC2/TPC3/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831967] nouveau :01:00.0: fifo: fault 00 [VIRT_READ] at 0be02000 engine 40 [gr] client 01 [GPC0/T1_1] reason 00 [PDE] on channel 2 [00ffe45000 Xwayland[3977]] [146226.831971] nouveau :01:00.0: fifo:00:0002:[Xwayland[3977]] rc scheduled [146226.831972] nouveau :01:00.0: fifo:00: rc scheduled [146226.831981] nouveau :01:00.0: fifo:00:0002:0002:[Xwayland[3977]] errored - disabling channel [146226.831985] nouveau :01:00.0: Xwayland[3977]: channel 2 killed! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 12:22:56 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1650 SUPER] [1043:874b] InstallationDate: Installed on 2023-01-15 (290 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=81faac01-c5d9-4543-8547-d6a0cbee36fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A 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.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M.
[Touch-packages] [Bug 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances
As far as I can tell we are facing this issue: https://github.com/systemd/systemd/issues/25813 This was fixed in systemd 253 with the following patch https://github.com/systemd/systemd/commit/ab3aed4a0349bbaa26f53340770c1b59b463e05d (and https://github.com/systemd/systemd/commit/2f96a29c2c55bdd67cdd8e0b0cfd6971968e4bca to fix a regression introduced by the first patch). If all managed interfaces have RequiredForOnline=no, and the rest are unmanaged, this issue pops up. ** Bug watch added: github.com/systemd/systemd/issues #25813 https://github.com/systemd/systemd/issues/25813 -- 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/2039083 Title: "optional: true" flag introduces problem it's meant to fix in certain circumstances Status in netplan: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: Hello! This bug is in relation to the situation where the "systemd-networkd- wait-online.service" hangs for several minutes on boot before eventually failing. I guess I don't know if this flag was introduced specifically for this situation, but I do know that one of the fixes for this issue is to add "optional: true" to any non-critical interfaces (as per the docs[1]). While this may be the case, it just so happens that adding this flag to an interface when it's the only configured interface in netplan can actually INTRODUCE the issue as well. Example: --- :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: enp5s0: dhcp4: true optional: true --- The above config will cause the service hang/failure, and the removal of the flag will resolve the issue. I primarily opened this bug report with the idea that we might update aforementioned documentation to include a caveat that you want to avoid adding this flag to the only configured interface. However, it was also discussed that we might consider having the netplan config parser complain about such a setup and consider it invalid, which it kinda is. I believe in a situation where you may have a server that should have NO network connectivity, you would simply leave netplan unconfigured and/or stop any relevant services, rather than try to configure all interfaces as optional. My original test was on Jammy, though I tested this also on Focal and Bionic, and neither of those appear to be affected by this - setting the only interface as optional in either of those does not cause the "systemd-networkd-wait-online" service to hang and the system boots normally. Let me know if you'd like/need any more info from me! Thank you! [1] https://netplan.io/faq#prevent-waiting-for-interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2039083/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Same for me, my default Google 2FA option is a security key, that's probably the common denominator here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2042483] Re: jconfig.h: No such file or directory
Thank you for your bug report, indeed that header is under the subdirectory for some reason. The package in Debian has the same issue ** Changed in: libjpeg-turbo (Ubuntu) Importance: Undecided => Low ** Changed in: libjpeg-turbo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/2042483 Title: jconfig.h: No such file or directory Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: A compiler can't find jconfig.h libjpeg.pc contains only /usr/include includedir, but the jconfig.h is located in /usr/include/x86_64-linux-gnu/ Maybe it's wrong location? libjpeg-turbo from git places all the headers in /usr/include To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/2042483/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
That was it, thanks! It looks very much like it is unable to load the 2FA page if there is a YubiKey configured. When I click Refresh, I see the 2FA page, but the YubiKey is not recognised (that's why I hate these embedded login pages -- why not just use the normal browser??). I can select "try a different way" and then log in with either TOTP or confirmation from my phone. However, when I select YubiKey in that list, I have the same problem again: page loads forever until I hit Refresh. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2025339] Re: FDE image fails to run e2fsck
** Description changed: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. + + [Fix] + + This SRU is disabling 2 features (orphan_file and metadata_csum_seed) + from ext4 to generate filesystems compatible with older series. Fixes + come from debian (fixing #1031622, #1030939). This is only disabling the + feature by default. One can still generate a filesystem with this + feature by explicitly listing them when invoking mkfs.ext4. + [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Jammy: Confirmed Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Unknown Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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
