[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
While retries on DNS resolution failures does not work for cloud- init.service for environments running NetworkManager.service (desktop live ISOs), I have found that the retries work where systemd-networkd is bringing up network config (server live ISOs). This is because cloud- init.service is After=systemd-network-wait-online.service which provides systemd-resolved with viable network interfaces which are up and providing access to functional DNS configuration. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011615] Re: BIOS
Can you take a photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011615 Title: BIOS Status in Ubuntu: Incomplete Bug description: It seems to me that BIOS has driver problem. When booting the error BIOS message it is showed every time. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-37.38-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 15:01:32 2023 DistUpgraded: 2023-02-23 21:00:51,671 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:16cd] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:16cd] InstallationDate: Installed on 2022-10-08 (157 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X555LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-37-generic root=UUID=893b4641-08f2-4efe-9a19-676c2512bbe7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-02-24 (18 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LD.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LD.403:bd01/23/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX555LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2011615/+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 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
This bug was fixed in the package systemd - 252.5-2ubuntu2 --- systemd (252.5-2ubuntu2) lunar; urgency=medium * network/dhcp4: accept local subnet routes from DHCP (LP: #2004478) File: debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b9aaaf37b8ca7c9febe5f0ebc4b82d0f895cbbd3 * sd-netlink: skip test_rtnl_set_link_name when altnames are not supported. This has already been fixed upstream by a larger commit, so this patch can be dropped when we have a new enough upstream version. File: debian/patches/sd-netlink-skip-test_rtnl_set_link_name-when-altnames-are.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=195985ee5aa2cfdbbac178a07e5b43b83f0550d0 -- Nick Rosbrook Wed, 08 Mar 2023 12:51:51 -0500 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Committed Bug description: [Impact] If a DHCP server pushes down a local subnet route with a null gateway, the systemd-networkd DHCP client does not correctly install the route. Instead, the route is ignored. [Test Plan] Taken from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2. * Start a Jammy LXD container: $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash * Create a veth pair: $ ip link add veth0 up type veth peer name veth1 $ ip addr add 172.20.0.1/24 dev veth0 $ cat > /etc/netplan/60-veth1.yaml
[Touch-packages] [Bug 2011575] Re: Cursor used during log in after boot still on screen after log in on desktop
This is/was a common issue on AMD systems. I think the 5.14 OEM kernel here is missing this fix: https://gitlab.gnome.org/GNOME/mutter/-/issues/1344#note_932943 But if it's still happening in later kernels then it might be related to: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470 ** Tags added: amdgpu cursor ** Package changed: xorg (Ubuntu) => linux-oem-5.14 (Ubuntu) ** Summary changed: - Cursor used during log in after boot still on screen after log in on desktop + [amdgpu] Cursor used during log in after boot still on screen after log in on desktop ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1344 https://gitlab.gnome.org/GNOME/mutter/-/issues/1344 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6470 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6470 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011575 Title: [amdgpu] Cursor used during log in after boot still on screen after log in on desktop Status in linux-oem-5.14 package in Ubuntu: New Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/2011575/+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 2008952] Re: DNS failure while trying to fetch user-data
This issue with NetworkManager.service and systemd is reminiscent of the related feature request against systemd-networkd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912 that also points out the ordering issues. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
I have HP EliteBook 860 G9. The earliest kernel version where ALC245 worked with speakers is 6.1.8 (Arch Linux 2023.02.01). dmesg | grep -i speaker [ 26.424223] input: PC Speaker as /devices/platform/pcspkr/input/input12 [ 28.118123] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 28.118132] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) dmesg | grep cs35 [ 27.600774] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: Cirrus Logic CS35L41 (35a40), Revision: B2 [ 27.602358] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Reset line busy, assuming shared reset [ 27.630214] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), Revision: B2 [ 27.904834] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3 [ 27.904838] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: cirrus/cs35l41-dsp1-spk-prot-103c8973.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe Daylight Time [ 27.979060] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 v0.43.1, 2 algorithms [ 27.979965] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94 YM@e [ 27.979973] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176 YM@0 [ 27.979979] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: E:\Amp Tuning\HP\860\0527 LS R754 UPDATE THERMAL\103C8973_220527.bin [ 28.010672] snd_hda_codec_realtek ehdaudio0D0: bound spi1-CSC3551:00-cs35l41-hda.0 (ops cs35l41_hda_comp_ops [snd_hda_scodec_cs35l41]) [ 28.019060] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: Firmware version: 3 [ 28.019068] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: cirrus/cs35l41-dsp1-spk-prot-103c8973.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe Daylight Time [ 28.081793] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: Firmware: 400a4 vendor: 0x2 v0.43.1, 2 algorithms [ 28.083137] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: 0: ID cd v29.63.1 XM@94 YM@e [ 28.083157] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: 1: ID f20b v0.1.0 XM@176 YM@0 [ 28.083168] cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: DSP1: spk-prot: E:\Amp Tuning\HP\860\0527 LS R754 UPDATE THERMAL\103C8973_220527.bin [ 28.116386] snd_hda_codec_realtek ehdaudio0D0: bound spi1-CSC3551:00-cs35l41-hda.1 (ops cs35l41_hda_comp_ops [snd_hda_scodec_cs35l41]) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller -
[Touch-packages] [Bug 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts
The attachment "isc-dhcp-apparmor-scripts-disable-fix.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2011628 Title: Apparmor Disallows Disabling Dhclient Scripts Status in isc-dhcp package in Ubuntu: New Bug description: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 1972790] Re: Can't connect to hotspot created on ubuntu
Also affected. Downgrading to 2.9 worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 2008952] Re: DNS failure while trying to fetch user-data
TLDR: My earlier suggestion to retry in cloud-init.service while awaiting DNS is not viable when thinking about NetworkManager. NetworkManager.service is After=sysinit.target due to After=dbus.service and cloud-init.service is Before=sysinit.target. NetworkManager is the only service bringing up the primary NIC in desktop images which gives cloud-init access to a functional DNS. Unless we can move NetworkManager.service before sysinit.target, I don't think we don't think we can leverage DNS. In review of a KVM live desktop boot in which cloud-init.service defines After=systemd-resolved.service We can see that cloud-init.service still blocks start of NetworkManager (due to After=sysinit.target) and DNS is not active until enp1s0 is actually brought up by NetworkManager. Here are snippets of the journalctl logs on a local KVM boot where we can see systemd-resolved coming up, then cloud-init.service with 30 retries and finally NetworkManager.service starting after cloud-init.service failed to download the metadata due to DNS resolution errors: 1. systemd-resolved "starts" @22:14:42.302181, which unblocks cloud-init.service 2. cloud-init.service @22:14:42.690949 (which emits that enp1s0's link is not actually up yet so no viable DNS at that time) 3. NetworkManager.service starting @22:15:16.012686up only after cloud-init.service finishes 30 seconds of retries @22:15:16.012686 4. systemd-resolved finally getting a viable DNS route through enp1s0 @22:15:19.630090 ubuntu systemd-resolved[1136]: enp1s0: Bus client set DNS server list to: 192.168.122.1 5. Network manager finally sees enp1s0 device activated @22:15:19.632846 6. NetworkManager-wait-online.service finally gets to CONNECTED status @22:15:19.637543 --- journalctl -b 0 -o short-precise | egrep 'enp1s0|resolved|NetworkManager|ci-info' Mar 14 22:14:39.167190 ubuntu kernel: virtio_net virtio0 enp1s0: renamed from eth0 Mar 14 22:14:41.451373 ubuntu systemd[1]: Starting systemd-resolved.service - Network Name Resolution... Mar 14 22:14:42.253268 ubuntu systemd-resolved[1136]: Positive Trust Anchors: Mar 14 22:14:42.253583 ubuntu systemd-resolved[1136]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Mar 14 22:14:42.253685 ubuntu systemd-resolved[1136]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Mar 14 22:14:42.300435 ubuntu systemd-resolved[1136]: Using system hostname 'ubuntu'. Mar 14 22:14:42.302181 ubuntu systemd[1]: Started systemd-resolved.service - Network Name Resolution. ### cloud-init noticing enp1s0 has no link Mar 14 22:14:42.690949 ubuntu cloud-init[1341]: ci-info: | enp1s0 | False | . | . | . | 52:54:00:5b:ba:d5 | Mar 14 22:15:16.012686 ubuntu systemd[1]: Starting NetworkManager.service - Network Manager... Mar 14 22:15:16.285604 ubuntu NetworkManager[1546]: [1678832116.2854] NetworkManager (version 1.40.12) is starting... (boot:1f3e11ab-fea1-4f3e-a6ef-fb9d48b0c4d6) Mar 14 22:15:16.285972 ubuntu NetworkManager[1546]: [1678832116.2859] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf) Mar 14 22:15:16.302542 ubuntu systemd[1]: Started NetworkManager.service - Network Manager. Mar 14 22:15:16.303605 ubuntu NetworkManager[1546]: [1678832116.3035] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Mar 14 22:15:16.316514 ubuntu systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online... Mar 14 22:15:16.354249 ubuntu NetworkManager[1546]: [1678832116.3542] manager[0x5629cd53f000]: monitoring kernel firmware directory '/lib/firmware'. Mar 14 22:15:16.354423 ubuntu NetworkManager[1546]: [1678832116.3544] monitoring ifupdown state file '/run/network/ifstate'. Mar 14 22:15:16.356985 ubuntu dbus-daemon[1490]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.14' (uid=0 pid=1546 comm="/usr/sbin/NetworkManager --no-daemon" label="unconfined") Mar 14 22:15:16.527848 ubuntu NetworkManager[1546]: [1678832116.5278] hostname: hostname: using hostnamed Mar 14 22:15:16.527869 ubuntu NetworkManager[1546]: [1678832116.5278] hostname: static hostname changed from (none) to "ubuntu" Mar 14 22:15:16.528346 ubuntu NetworkManager[1546]: [1678832116.5283] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved Mar 14
[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
The fix/commit is applied in v5.12, thus available on Jammy (v5.15-based). https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4 ~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4 v5.12-rc1-dontuse~7^2~13 ** Also affects: parted (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: parted (Ubuntu Jammy) Status: New => Invalid ** No longer affects: parted (Ubuntu Jammy) ** No longer affects: snapd (Ubuntu Jammy) ** No longer affects: udev (Ubuntu Jammy) ** No longer affects: systemd (Ubuntu Jammy) -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: This is reproducible in Bionic and late. Here's an example running 'focal': $ lsb_release -cs focal $ uname -r 5.3.0-24-generic The error is: blk_update_request: I/O error, dev loop2, sector 0 and on more recent kernel: kernel: [18135.185709] blk_update_request: I/O error, dev loop18, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 How to trigger it: $ sosreport -o block or more precisely the cmd causing the situation inside the block plugin: $ parted -s $(losetup -f) unit s print https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52 but if I run it on the next next unused loop device, in this case /dev/loop3 (which is also unused), no errors. While I agree that sosreport shouldn't query unused loop devices, there is definitely something going on with the next unused loop device. What is differentiate loop2 and loop3 and any other unused ones ? 3 things so far I have noticed: * loop2 is the next unused loop device (losetup -f) * A reboot is needed (if some loop modification (snap install, mount loop, ...) has been made at runtime * I have also noticed that loop2 (or whatever the next unused one is) have some stat as oppose to other unused loop devices. The stat exist already right after the system boot for the next unused loop device. /sys/block/loop2/stat :: 2 0 10 0 1 0 0 0 0 0 0 2 = number of read I/Os processed 10 = number of sectors read 1 = number of write I/Os processed Explanation of each column: https://www.kernel.org/doc/html/latest/block/stat.html while /dev/loop3 doesn't /sys/block/loop3/stat :: 0 0 0 0 0 0 0 0 0 0 0 Which tells me that something during the boot process most likely acquired (on purpose or not) the next unused loop and possibly didn't released it well enough. If loop2 is generating errors, and I install a snap, the snap squashfs will take loop2, making loop3 the next unused loop device. If I query loop3 with 'parted' right after, no errors. If I reboot, and query loop3 again, then no I'll have an error. To triggers the errors it need to be after a reboot and it only impact the first unused loop device available (losetup -f). This was tested with focal/systemd whic his very close to latest upstream code. This has been test with latest v5.5 mainline kernel as well. For now, I don't think it's a kernel problem, I'm more thinking of a userspace misbehaviour dealing with loop device (or block device) at boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 2008952] Re: DNS failure while trying to fetch user-data
I can confirm Dan's validation that After=systemd-resolved.service doesn't buy us anything here because, although systemd-resolved.service is up, NetworkManager.service && NetworkManager-wait-online.service don't finish bringing link up for related network devices until After=dbus.service timeframe. So blocking on systemd-resolved.service tells us only that the service is running, not that it provides useful DNS lookups. Since dbus.service is After=sysinit.target and sysinit.target is After=cloud-init.service we have an ordering cycle for NetworkManager that doesn't exist for systemd-networkd controlled environments. Any attempts to include After=NetworkManager-wait-online.service in cloud-init.service definition result in ordering cycles. Even if we try to add DefaultDependecies=no to both NetworkManager.service and NetworkManager-wait-online.service to prevent them from pulling in `After=sysinit.target` for ordering. NetworkManager images (desktop) differ from cloud-init's systemd-networkd managed images (server) because systemd-networkd-wait-online.service doesn't have a strict After=dbus.service config systemd-networkd can poll for dbus availability and use it once it's available. But, it doesn't seem NetworkManager has that facility though I haven't dug deeply into NM yet. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts
Debdiff in the attached enables dhclient to execute dhclient with -sf /bin/true ** Patch added: "isc-dhcp-apparmor-scripts-disable-fix.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+attachment/5654529/+files/isc-dhcp-apparmor-scripts-disable-fix.debdiff -- 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/2011628 Title: Apparmor Disallows Disabling Dhclient Scripts Status in isc-dhcp package in Ubuntu: New Bug description: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2011628] [NEW] Apparmor Disallows Disabling Dhclient Scripts
Public bug reported: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- 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/2011628 Title: Apparmor Disallows Disabling Dhclient Scripts Status in isc-dhcp package in Ubuntu: New Bug description: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
Found this guy, thanks him - https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/libgweather -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Fix Released Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: Confirmed Status in libgweather source package in Focal: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
Good day. As I understand, I should somehow change libgweather to 3.36.2. Is there any instruction manual for that? I can see some tarball in repo https://download.gnome.org/sources/libgweather/3.36/libgweather-3.36.2.tar.xz but have no idea how to proceed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Fix Released Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: Confirmed Status in libgweather source package in Focal: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 2008952] Re: DNS failure while trying to fetch user-data
I'm also going back to the tabular network state printed out by in cloud-init.service shows: that the primary network interface is still down at this point in boot, which it shouldn't be. cloud-init should be waiting on the presence of link up before starting it's cloud- init.service (network boot stage). I'm working on the hypothesis that we are missing an `After=NetworkManager-wait-online.service` which wasn't present in cloud-init because it didn't have to cope with non systemd- networkd managed devices in ubuntu-server installs. ci-info: | enp0s31f6 | False | . | . | . | 6c:24:08:9e:54:e6 | Running a couple of tests in a manifactured Desktop Live iso installer now to confirm -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011615] Re: BIOS
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011615 Title: BIOS Status in xorg package in Ubuntu: New Bug description: It seems to me that BIOS has driver problem. When booting the error BIOS message it is showed every time. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-37.38-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 15:01:32 2023 DistUpgraded: 2023-02-23 21:00:51,671 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:16cd] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:16cd] InstallationDate: Installed on 2022-10-08 (157 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X555LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-37-generic root=UUID=893b4641-08f2-4efe-9a19-676c2512bbe7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-02-24 (18 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LD.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LD.403:bd01/23/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX555LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2011615/+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 2011615] [NEW] BIOS
You have been subscribed to a public bug: It seems to me that BIOS has driver problem. When booting the error BIOS message it is showed every time. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-37.38-generic 5.19.17 Uname: Linux 5.19.0-37-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 15:01:32 2023 DistUpgraded: 2023-02-23 21:00:51,671 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:16cd] Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:16cd] InstallationDate: Installed on 2022-10-08 (157 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. X555LD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-37-generic root=UUID=893b4641-08f2-4efe-9a19-676c2512bbe7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-02-24 (18 days ago) dmi.bios.date: 01/23/2019 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LD.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LD.403:bd01/23/2019:br4.6:svnASUSTeKCOMPUTERINC.:pnX555LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X555LD dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ubuntu wayland-session -- BIOS https://bugs.launchpad.net/bugs/2011615 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 2011622] [NEW] rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace interpretation
Public bug reported:
Commands like this:
rsync -a host.example.org:\{this,that} .
have worked for decades, in multiple Ubuntu versions, but were broken by the
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type
that command).
(To be clear, the backslash there quotes the '{' so that it is sent to
the remote rsync rather than being interpreted by the local shell.)
("What happens instead?" It now says "rsync: link_stat
"/home/flaps/{this,that}" failed: No such file or directory (2)".)
** Affects: rsync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2011622
Title:
rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace
interpretation
Status in rsync package in Ubuntu:
New
Bug description:
Commands like this:
rsync -a host.example.org:\{this,that} .
have worked for decades, in multiple Ubuntu versions, but were broken by the
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type
that command).
(To be clear, the backslash there quotes the '{' so that it is sent to
the remote rsync rather than being interpreted by the local shell.)
("What happens instead?" It now says "rsync: link_stat
"/home/flaps/{this,that}" failed: No such file or directory (2)".)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2011622/+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 1964636] Re: Incorrect handling of apparmor `bpf` capability
Focal is in soft freeze atm, once the soft freeze is lifted this should
land
--
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/1964636
Title:
Incorrect handling of apparmor `bpf` capability
Status in apparmor package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Incomplete
Status in apparmor source package in Focal:
Fix Committed
Bug description:
[ Impact ]
The apparmor_parser before the 3.0 release would build its capability list
from the installed kernel headers. The apparmor_parser was built against a
kernel without support for cap 'bpf'
This was fixed in 3.0 by having a static caps list (with full mapping info)
and the dynamic auto-generated list (against the kernel headers) that is used
to check that the static list has not become stale. In addition the parser can
pull kernel supported caps straight from the apparmor kernel module (it will
however be missing the mapping info).
Backporting the patches from 3.0 fixes the issue.
[ Test Plan ]
Before the fix, the following profile fails loading:
# echo "profile foo { capability bpf, }" | apparmor_parser -Q
AppArmor parser error, in stdin line 1: Invalid capability bpf.
# echo $?
1
After the fix, it works as expected:
# echo "profile foo { capability bpf, }" | apparmor_parser -Q
# echo $?
0
[ Where problems could occur ]
With these changes, the parser can change its behavior based on a few things.
1. the kernel its built against. This would not change behavior when run in a
container vs at system level.
2. If a feature-file is specified, via --features-file, --policy-
features, or --kernel-features. This allows overriding the normal
policy and kernel examination that the parser does when compiling
policy.
3. If /sys/kernel/security/apparmor/features is not available. The
parser will fallback to an old set of features available in a kernel
before the kernel module started exporting what the kernel module
supports on the running kernel.
[ Other Info ]
The patches for focal (apparmor-2.13) can be found at:
https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
As mentioned before, these patches are already running on apparmor-3.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964636/+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 1993353] Re: Add posix message queue IPC mediation
Focal is in soft freeze atm, once that is lifted this should land -- 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/1993353 Title: Add posix message queue IPC mediation Status in apparmor package in Ubuntu: New Status in apparmor source package in Focal: Fix Committed Status in apparmor source package in Jammy: Fix Released Bug description: [ Impact ] We need to add IPC mediation support in the userspace tools, starting with posix message queue. This would improve security and lower the attack surface for applications There is already a proposal upstream: https://gitlab.com/apparmor/apparmor/-/merge_requests/858 [ Test Plan ] In the merge request in the description there are several tests added. There are parser tests that can be run with "make -C parser check" in the project source tree. There are also tests for the python tools that can be run ith "make -C utils check" in the project source tree. There are also regression tests in tests/regression/apparmor. They run with the whole test suite when you run with "sudo make tests", but they can also be run individually with "sudo ./posix_mq.sh" [ Where problems could occur ] There could be problems related to Bug 1728130, where a policy was developed for a set of rules supported by a specific kernel, and if new mediation is available on newer kernels, then there will be some denied rules. Therefore we need to also prevent that from happening. This is already available in apparmor-3.+, but for older versions could be done by backporting the abi patches from apparmor-3.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1993353/+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 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'
The verification passed for jammy: ``` william@william-Latitude-E7470 ~ apt-cache policy udev udev: Installed: 249.11-0ubuntu3.7 Candidate: 249.11-0ubuntu3.8 Version table: *** 249.11-0ubuntu3.8 500 500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages william@william-Latitude-E7470 ~ ls -al /dev/sgx_vepc crw--- 1 root root 10, 125 Mar 14 14:01 /dev/sgx_vepc william@william-Latitude-E7470 ~ apt-cache policy udev udev: Installed: 249.11-0ubuntu3.8 Candidate: 249.11-0ubuntu3.8 Version table: *** 249.11-0ubuntu3.8 500 500 http://us.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages william@william-Latitude-E7470 ~ ls -al /dev/sgx_vepc crw-rw 1 root sgx 10, 125 Mar 14 14:01 /dev/sgx_vepc ``` ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2009502 Title: Enable /dev/sgx_vepc access for the group 'sgx' Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Bug description: [ Impact ] On systems where Intel SGX is available, access to a specific device node (/dev/sgx_vepc) must be enforced, with a specific permission (0660) and group (sgx). This allows KVM-based virtual machines to use such feature (the SGX "enclaves") in a proper fashion. Without this, a manual udev rule needs to be created. [ Test Plan ] As the patch itself only tailors the permissions/group to the device node, in a system with Intel-SGX enabled, merely `ls -la` against the device node should show if the permissions and group are seen as expected. [ Where problems could occur ] N/A. This seems to be a very straightforward inclusion, very specific to access enablement to the SGX reserved memory used for hosting enclaves. [ Other Info ] N/A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied
Is this issue blocked by something?
--
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/1728130
Title:
Policy needs improved feature versioning to ensure it is correctly
being applied
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Focal:
Fix Committed
Bug description:
[ Impact ]
Currently allows pinning a single feature abi or running in a
developer mode where the full abi available of the current kernel is
enforced.
However this can result in breaking applications in undesirable ways.
If an application is shipped with its own policy, that policy might be
different than the pinned feature abi, which can either result in
denials because features the policy was not developed for are being
enforced.
If the feature version is not pinned then the most recent kernel abi
is taken and applied to policy, which has not been updated. This can
result in denials for userspace effectively breaking userspace. This
is less than ideal for most users as it leads to a bad experience than
they have not opted into and can lead to them disabling security
protections.
[ Test Plan ]
The test can be done with several features. Here we are using mqueue as an
example.
Verify that the kernel that has mqueue mediation support:
root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ]
&& echo "supports mqueue"
supports mqueue
cd /tmp
pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
cd apparmor-2.13.3/tests/regression/apparmor/
USE_SYSTEM=1 make
Using the parser from the mqueue-sru PPA, load the profile.
echo "
abi ,
include
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
}
" | apparmor_parser -q -r
Run the test, which should fail.
./posix_mq_rcv -c ./posix_mq_snd
FAIL - could not open mq: Permission denied
Now use an abi that does not have mqueue. This simulates a scenario
where a policy was developed before mqueue support was added, so posix
message queues should be allowed by default.
echo "
abi ,
include
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
}
" | apparmor_parser -q -r
Run the test again, it should pass.
./posix_mq_rcv -c ./posix_mq_snd
PASS
[ Where problems could occur ]
ABI pinning forces policies that don't have abi specified in their
profile to use the ABI pinned in parser.conf. When the ABI is pinned
and the user is trying to use mediation that is not in the pinned ABI,
they might be confused why it is always being allowed. This can be
circumvented by specifying the correct abi in the profile.
[ Other Info ]
The patches for focal (apparmor-2.13) can be found at:
https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
apparmor-3.0 already has this feature.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728130/+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 1964636] Re: Incorrect handling of apparmor `bpf` capability
Is there something blocking the release for focal?
--
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/1964636
Title:
Incorrect handling of apparmor `bpf` capability
Status in apparmor package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Incomplete
Status in apparmor source package in Focal:
Fix Committed
Bug description:
[ Impact ]
The apparmor_parser before the 3.0 release would build its capability list
from the installed kernel headers. The apparmor_parser was built against a
kernel without support for cap 'bpf'
This was fixed in 3.0 by having a static caps list (with full mapping info)
and the dynamic auto-generated list (against the kernel headers) that is used
to check that the static list has not become stale. In addition the parser can
pull kernel supported caps straight from the apparmor kernel module (it will
however be missing the mapping info).
Backporting the patches from 3.0 fixes the issue.
[ Test Plan ]
Before the fix, the following profile fails loading:
# echo "profile foo { capability bpf, }" | apparmor_parser -Q
AppArmor parser error, in stdin line 1: Invalid capability bpf.
# echo $?
1
After the fix, it works as expected:
# echo "profile foo { capability bpf, }" | apparmor_parser -Q
# echo $?
0
[ Where problems could occur ]
With these changes, the parser can change its behavior based on a few things.
1. the kernel its built against. This would not change behavior when run in a
container vs at system level.
2. If a feature-file is specified, via --features-file, --policy-
features, or --kernel-features. This allows overriding the normal
policy and kernel examination that the parser does when compiling
policy.
3. If /sys/kernel/security/apparmor/features is not available. The
parser will fallback to an old set of features available in a kernel
before the kernel module started exporting what the kernel module
supports on the running kernel.
[ Other Info ]
The patches for focal (apparmor-2.13) can be found at:
https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
As mentioned before, these patches are already running on apparmor-3.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964636/+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 1993353] Re: Add posix message queue IPC mediation
Is there something blocking the release for focal? Thanks -- 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/1993353 Title: Add posix message queue IPC mediation Status in apparmor package in Ubuntu: New Status in apparmor source package in Focal: Fix Committed Status in apparmor source package in Jammy: Fix Released Bug description: [ Impact ] We need to add IPC mediation support in the userspace tools, starting with posix message queue. This would improve security and lower the attack surface for applications There is already a proposal upstream: https://gitlab.com/apparmor/apparmor/-/merge_requests/858 [ Test Plan ] In the merge request in the description there are several tests added. There are parser tests that can be run with "make -C parser check" in the project source tree. There are also tests for the python tools that can be run ith "make -C utils check" in the project source tree. There are also regression tests in tests/regression/apparmor. They run with the whole test suite when you run with "sudo make tests", but they can also be run individually with "sudo ./posix_mq.sh" [ Where problems could occur ] There could be problems related to Bug 1728130, where a policy was developed for a set of rules supported by a specific kernel, and if new mediation is available on newer kernels, then there will be some denied rules. Therefore we need to also prevent that from happening. This is already available in apparmor-3.+, but for older versions could be done by backporting the abi patches from apparmor-3.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1993353/+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 2008952] Re: DNS failure while trying to fetch user-data
Thank you all for your attention on this bug. Sorry my earlier comment on this bug was ill-informed and incorrect. I'm able to reproduce this as well through the server installer qemu/kvm based installs as well so I can confirm as well that this isn't/wasn't NetworkManager and systemd-networkd related. Also, I am concerned with cloud-init.service being ordered specifically after sytemd-resolved.service on all deployments as we will be affecting all boots and delaying them on the systemd-resolved setup of DNS when only specific use-cases such NoCloudNet with an FQDN as kernel cmdline directive may need that service to be active. Some other datasources like GCP do rely on DNS resolution of the instance metadata service (GCP), but cloud-images inject a config into /etc/hosts to resolve that locally in absence of active DNS in early boot. Ec2 does also define instance-data:8773 as a potential fallback IMDS definition, but both IPv4 and IPv6 endpoints are defined earlier in the search order, so we never get back to that DNS lookup in all practical deployments. We may be able to avoid the cost of a strict `After=systemd-resolved.service` clause in cloud-init.service if we can add the following logic to nocloud by adding sensible retries in the NoCloud datasource. 1. Check if seed URLs `netloc` is an ip address. If IP, no retries on failure. 2a. When seed URL is non-IP, retry on specific 'network resolution error' URLError raised and retry X times for that failure mode - or - 2b . When seed URL is non-IP, invoke socket.getaddrinfo to validate DNS resolution prior to attempting to download metadata, if not resolvable, retry only as long as systemd.resolved.services isn't yet active. These retry approaches should allow us to avoid impacting typical boots on most systems, yet still support DNS-based needs for datasource detection in early boot if FQDN is used for IMDS. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
I played with a two variation of dropping in some after directives, but obtained similar failing results where the network state was not what cloud-init wanted at the time it started. @Chad - what's your thoughts on some service reordering? -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011347] Re: language-pack-fr (1:23.04+20230310) breaks at least g-c-c
*** This bug is a duplicate of bug 2011313 *** https://bugs.launchpad.net/bugs/2011313 ** This bug has been marked a duplicate of bug 2011313 gnome-control-center crashes after launch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-fr in Ubuntu. https://bugs.launchpad.net/bugs/2011347 Title: language-pack-fr (1:23.04+20230310) breaks at least g-c-c Status in language-pack-fr package in Ubuntu: New Bug description: Hi, Since this update: $ gnome-control-center 18:44:17.3415 **[27440]: WARNING: Couldn't get locale for language: (null) Erreur de segmentation (core dumped) Was ok in previous one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-fr/+bug/2011347/+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 2008952] Re: DNS failure while trying to fetch user-data
FWIW you can test this out by adding a drop-in config: $ cat > /etc/systemd/system/cloud-init.service.d/10-after-systemd-resolved.conf << EOF [Service] After=systemd-resolved.service EOF -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011575] Re: Cursor used during log in after boot still on screen after log in on desktop
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2011575 Title: Cursor used during log in after boot still on screen after log in on desktop Status in xorg package in Ubuntu: New Bug description: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2011575/+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 2011575] [NEW] Cursor used during log in after boot still on screen after log in on desktop
You have been subscribed to a public bug: After booting up my laptop and logging in, the cursor that is used during the log in phase just freezes on the spot it last was after pressing the enter key to log in and stays there the whole usage time. It only disappears when I restart or shut down the laptop. It doesn't impair the usage of the desktop cursor, but stays on the screen, in front of every open window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21 Uname: Linux 5.14.0-1058-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 14 13:53:12 2023 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1681] (rev d1) (prog-if 00 [VGA controller]) MachineType: LENOVO 21CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1058-oem root=UUID=5579c05a-7872-4f21-8412-a225bea53a66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2022 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET62W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: ThinkPad dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.25:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1: dmi.product.family: ThinkPad P16s Gen 1 dmi.product.name: 21CKCTO1WW dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1 dmi.product.version: ThinkPad P16s Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Cursor used during log in after boot still on screen after log in on desktop https://bugs.launchpad.net/bugs/2011575 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 2008952] Re: DNS failure while trying to fetch user-data
It appears we have the following *ordering* relationship between systemd-resolved.service, cloud-init.service, network.target, and network-online.target: network-online.target / \ /.. \ /.\ network.target cloud-init.service / / / systemd-resolved.service See attached graph for more details. This is consistent with the timeline shown in comment #13. Since cloud-init.service apparently requires DNS, I would simply try to add `After=systemd-resolved.service` to `cloud-init.service`. ** Attachment added: "systemd-analyze-dot.svg" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654458/+files/systemd-analyze-dot.svg -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
This bug was fixed in the package gnome-shell-extension-appindicator - 53-1 --- gnome-shell-extension-appindicator (53-1) experimental; urgency=medium * New upstream release * appIndicator: Wait for style change if no stage is set * appIndicator: Reuse already imported namespaces * appIndicator Use Clutter to load RGBA Pixmap textures natively * appIndicator: Simplify loading of custom image files (LP: #784055, #1973358) * dbusMenu: Use more dbus async methods * interfaces-xml: Comment out the signal definitions (avoids gjs signals) * dbusMenu: Do not update menu items while the menu is closed * Util: Do not recreate the default theme each time * appIndicator: Only update icon size when it matters * appIndicator: Only perform updating actions if we're fully ready * appIndicator: Ensure St.Icon loading icon size matches theme and preferences * appIndicator: return the previous GIcon if something failed * appIndicator: Refactor named icons lookup and loading * appIndicator: Use correct update frequency on signals accumulator * appIndicator: Ensure that property emissions are queued together * dbusMenu: Use cancellable's to handle subsequent requests * dbusMenu: Populate menus in chunked idles * statusNotifierWatcher: Properly handle null services * dbusUtil: Filter introspectable bus by interfaces if provided * dbusUtils: Use more reasonable timeout for introspection * util: Use a recursive async generator to get introspection results * statusNotifierWatcher: Remove idle promise on bus seeking * debian/patches: Drop applied upstream -- Marco Trevisan (Treviño) Mon, 13 Mar 2023 20:21:32 +0100 ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 2007421] Re: Please merge sysvinit 3.06-2 (main) from Debian unstable (main)
This bug was fixed in the package sysvinit - 3.06-2ubuntu1 --- sysvinit (3.06-2ubuntu1) lunar; urgency=medium * Merge with Debian unstable (LP: #2007421). Remaining changes: - When building for Ubuntu, skip all binaries except for sysvinit-utils - Fix absence of changelog.Debian.gz in sysvinit-utils binary package - Adjust debian/rules to fix an arch: all build failure - d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu -- Olivier Gayot Thu, 16 Feb 2023 14:53:59 +0100 ** Changed in: sysvinit (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2007421 Title: Please merge sysvinit 3.06-2 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: Debian moved from 3.05-7 to new upstream 3.06-2. As usual, we still only want to build sysvinit-utils and not the other binary packages. https://salsa.debian.org/debian/sysvinit/-/merge_requests/8 has not yet been merged so we need to carry the following patch: d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2007421/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI
** Tags added: focal jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1735002 Title: Allow configuring Wi-Fi MAC Randomization feature from GUI Status in gnome-control-center: Confirmed Status in NetworkManager: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: Recent versions of NetworkManager have a feature enabled by default to use a random MAC address when scanning for available Wi-Fi networks for privacy. My understanding is that the spoofed MAC address is not used when actually connecting to a network. This feature was disabled in Ubuntu 17.10 because it broke scanning with some Wi-Fi drivers. My understanding is that there is a bug in some drivers when attempting to change the MAC address. See LP: #1681513. The bug might not be as big of an issue with the latest version of NetworkManager because 1) There are helpful commits like this (it was not backported to 17.04): https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1 2) It is also possible now to selectively disable Wi-Fi MAC Randomization for specific drivers. https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9 However, I'm really hesitant to re-enable this feature as long as A) we don't know for sure which drivers are affected, B) and more importantly, there is no GUI way to turn the feature on or off. Asking users to edit config files isn't very nice. The MAC Address Randomization feature is really nice (Windows 10 has a similar feature) but I think we need a GUI on/off switch in Settings > Wi-Fi or Settings > Privacy. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 1998321] Re: tzdata 2022g release
Attached the wrong debdiff. 2022g-0ubuntu0.16.04+esm1 is the correct
one.
** Patch added: "tzdata_2022g-0ubuntu0.16.04+esm1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5654400/+files/tzdata_2022g-0ubuntu0.16.04+esm1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Attached debdiff for xenial and also pushed to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata
** Patch added: "tzdata_2022g-0ubuntu0.18.04.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5654397/+files/tzdata_2022g-0ubuntu0.18.04.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Jammy:
Fix Released
Status in tzdata source package in Kinetic:
Fix Released
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "cloud-init.log" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654393/+files/cloud-init.log -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
I attached some logs that might be useful. After checking it again I realized that the syslog timestamps are a little off when compared to the systemd journal. As shown in the timeline.txt (attached), cloud-init and systemd-resolved are starting at the same time. So the name resolution might not be working yet when cloud-init needs it. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "timeline.txt" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654394/+files/timeline.txt -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2008952] Re: DNS failure while trying to fetch user-data
** Attachment added: "systemd_journal.txt" https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654392/+files/systemd_journal.txt -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 2011574] [NEW] rsyslogd: /dev/console permission errors
Public bug reported: See: https://bugs.launchpad.net/bugs/1890177 I am opening a new ticket because I believe there may have been a regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still see this issue. /etc/rsyslog.d/90-google.conf: # Google Compute Engine default console logging. # # daemon: logging from Google provided daemons. # kern: logging information in case of an unexpected crash during boot. # daemon,kern.* /dev/console Logs are filled with: rsyslogd: action 'action-8-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ] rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ] $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2011574 Title: rsyslogd: /dev/console permission errors Status in rsyslog package in Ubuntu: New Bug description: See: https://bugs.launchpad.net/bugs/1890177 I am opening a new ticket because I believe there may have been a regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still see this issue. /etc/rsyslog.d/90-google.conf: # Google Compute Engine default console logging. # # daemon: logging from Google provided daemons. # kern: logging information in case of an unexpected crash during boot. # daemon,kern.* /dev/console Logs are filled with: rsyslogd: action 'action-8-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ] rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ] $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2011574/+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 2009756] Re: backups fail since latest rsync security update
** Changed in: rsync (Ubuntu Jammy) Status: New => Invalid ** Changed in: rsync (Ubuntu Kinetic) Status: New => Invalid ** Changed in: rsync (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: Invalid Status in backintime source package in Jammy: Fix Released Status in rsync source package in Jammy: Invalid Status in backintime source package in Kinetic: Fix Released Status in rsync source package in Kinetic: Invalid Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: Invalid Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 2009756] Re: backups fail since latest rsync security update
This bug was fixed in the package backintime - 1.2.1-3ubuntu0.3 --- backintime (1.2.1-3ubuntu0.3) jammy-security; urgency=medium * Fix compatibility with rsync security update (LP: #2009756) - debian/patches/rsync_compat.patch: fix changes to argument protection in common/config.py, common/snapshots.py, common/sshtools.py, common/test/test_sshtools.py, common/test/test_takeSnapshot.py, common/tools.py. -- Marc Deslauriers Thu, 09 Mar 2023 08:02:57 -0500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: New Status in backintime source package in Jammy: Fix Released Status in rsync source package in Jammy: New Status in backintime source package in Kinetic: Fix Released Status in rsync source package in Kinetic: New Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: New Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 2009756] Re: backups fail since latest rsync security update
This bug was fixed in the package backintime - 1.3.2-0.1ubuntu0.2 --- backintime (1.3.2-0.1ubuntu0.2) kinetic-security; urgency=medium * Fix compatibility with rsync security update (LP: #2009756) - debian/patches/rsync_compat.patch: fix changes to argument protection in common/config.py, common/snapshots.py, common/sshtools.py, common/test/test_sshtools.py, common/test/test_takeSnapshot.py, common/tools.py. -- Marc Deslauriers Thu, 09 Mar 2023 07:41:05 -0500 ** Changed in: backintime (Ubuntu Kinetic) Status: In Progress => Fix Released ** Changed in: backintime (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: New Status in backintime source package in Jammy: Fix Released Status in rsync source package in Jammy: New Status in backintime source package in Kinetic: Fix Released Status in rsync source package in Kinetic: New Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: New Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 2008952] Re: DNS failure while trying to fetch user-data
** Changed in: netplan Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps
No crash reports from gnome-shell 44 yet. I'm hopeful this was fixed
by/around the same time as https://gitlab.gnome.org/GNOME/gnome-
shell/-/commit/1559f03a82317e06aa0596bf12feb8b761a58f52
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1994010
Title:
gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
mozilla::detail::IntrinsicMemoryOps::load()
Status in gjs package in Ubuntu:
Confirmed
Status in gnome-shell package in Ubuntu:
Confirmed
Status in mozjs102 package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
gnome-shell crashed with SIGSEGV:
#0 std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
__b = std::memory_order_relaxed
#1 mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at
.././debian/build/dist/include/mozilla/Atomics.h:195
No locals.
#2 mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at
.././debian/build/dist/include/mozilla/Atomics.h:340
No locals.
#3 js::gc::CellWithTenuredGCPointer::headerPtr
(this=0x0) at .././js/src/gc/Cell.h:802
No locals.
#4 JSObject::shape (this=, this=) at
.././js/src/vm/JSObject.h:99
No locals.
#5 JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
No locals.
#6 JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at
.././js/src/vm/JSContext-inl.h:318
No locals.
#7 JSAutoRealm::JSAutoRealm (this=, cx=,
target=, this=, cx=,
target=) at .././js/src/jsapi.cpp:519
No locals.
#8 0x7f9b4910db2a in gjs_object_set_gproperty (object=,
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at
../gi/gobject.cpp:209
priv =
cx = 0x561efe351c00
js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0},
}, >> =
{ >> =
{, void>> = {}, }, }, ptr = 0x0}
ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
...
https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 2008952] Re: DNS failure while trying to fetch user-data
Maybe we need some additional systemd service ordering, to make systemd- resolved start before calling into the DHCP client, so that it can properly receive the DNS servers. -- 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/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+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 1998267] Re: glib not aware of snap confinement
The upstream PR has been merged and we got the new glib serie in Lunar so assuming it's fixed there ** Changed in: glib2.0 (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: New Status in glib2.0 source package in Kinetic: New Status in glib2.0 source package in Lunar: Fix Released Bug description: [ Impact] glib is not aware of snap confinement and this causes the internal logic to decide when to use portals to not work as designed. One important case is the gsettings backend, which should use a keyfile when confined rather than using dconf. When using a fully confined desktop this is required, as dconf is not suitable for sharing between snaps. This has been fixed in glib main: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020 [ Test Plan ] 1. Install gnome-calculator snap: $ snap install gnome-calculator 2. Disconnect gsettings interface: $ snap disconnect gnome-calculator:gsettings 3. Run gnome-calculator 4. Change mode from basic to advanced 5. Close and re-open gnome-calculator Expected result: Mode change remembered on second run. gnome-calculator settings written to ~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile Observed result: Mode change not remembered on second run, errors shown in console about accessing dconf: (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied. dconf will not work properly. [ Where problems could occur ] - New bug introduced in glib causing a crash. - Security issue introduced in glib due to accessing snapctl. - Unexpected behaviour change when running snaps with updated glib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+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 1966905] Re: Memory access errors in gnome-shell from accountsservice
The #1 gnome-shell crash in 23.04 is currently: https://errors.ubuntu.com/problem/fa3beeb1c25d862ecb2a0900c2b2519503a6109d which actually sounds like this bug. See also bug 2011429. -- 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/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance
