[Touch-packages] [Bug 2038994] [NEW] systemd-networkd: Unable to acquire IPv6 DNS server address
Public bug reported: I found that starting from Ubuntu 22, when using systemd-networkd as the netplan backend, the IPV6 DNS server cannot be obtained through DHCPv6. I reported the issue to the systemd team and they located and fixed the issue. How can I get these updates in ubuntu packages? issue details: https://github.com/systemd/systemd/issues/28566 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Oct 11 03:58:58 2023 InstallationDate: Installed on 2023-10-09 (1 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708406/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708407/+files/Dependencies.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708408/+files/Lspci.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708409/+files/Lspci-vt.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708410/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708411/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708412/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708413/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708414/+files/ProcModules.txt ** Attachment removed: "SystemdDelta.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708415/+files/SystemdDelta.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708416/+files/UdevDb.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2038994/+attachment/5708417/+files/acpidump.txt ** Description changed: I found that starting from Ubuntu 22, when using systemd-networkd as the netplan backend, the IPV6 DNS server cannot be obtained through DHCPv6. I reported the issue to the systemd team and they located and fixed the issue. How can I get these updates in ubuntu packages? issue details: https://github.com/systemd/systemd/issues/28566 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Oct 11 03:58:58 2023 InstallationDate: Installed on 2023-10-09 (1 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) - Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Lsusb-t: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M - MachineType: QEMU Standard PC (i440FX + PIIX, 1996) - ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-86-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro - SourcePackage: systemd - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 02/06/2015 - dmi.bios.release: 0.0 - dmi.bios.vendor: EFI Development Kit II / OVMF - dmi.bios.version: 0.0.0 - dmi.chassis.type: 1 - dmi.chassis.vendor: QEMU - dmi.chassis.version: pc-i440fx-5.2 - dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2:sku: - dmi.product.name: Standard PC (i440FX + PIIX,
[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
** Attachment added: "mediatek.conf" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+attachment/5708343/+files/mediatek.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in initramfs-tools package in Ubuntu: New Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Ubuntu Version] Jammy [initramfs-tools] 0.140ubuntu13.4 [Kernel version] 5.15 -> 6.2 (Generate initrd.img-6.2.0 on 5.15 kernel.) [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2034996] Re: Mantic amd64 daily ISO also installs i386 packages
Yes? $ apt-cache show gamemode | grep Recommends Recommends: libgamemode0:i386, libgamemodeauto0:i386 $ So what's the bug? ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034996 Title: Mantic amd64 daily ISO also installs i386 packages Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: Mantic amd64 daily ISO installed these i386 packages libgcc-s1:i386 gcc-13-base:i386 libc6:i386 libcap2:i386 libcom- err2:i386 libdbus-1-3:i386 libgamemode0:i386 libgamemodeauto0:i386 libgcrypt20:i386 libgpg-error0:i386 libgssapi-krb5-2:i386 libidn2-0:i386 libk5crypto3:i386 libkeyutils1:i386 libkrb5-3:i386 libkrb5support0:i386 liblz4-1:i386 liblzma5:i386 libnsl2:i386 libnss- nis:i386 libnss-nisplus:i386 libssl3:i386 libsystemd0:i386 libtirpc3:i386 libunistring2:i386 libzstd1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034996/+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 2034986] Re: some text became unreadable during a distribution upgrade
Besides the very minor Firefox issue, I didn't see any font issues when I tested 23.04 -> 23.10 basic upgrades today of - Ubuntu Desktop - Ubuntu Budgie - Kubuntu - Lubuntu - Xubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade
Sorry for the noise about Lubuntu. There is a very minor issue seen during the upgrade if Firefox is running (regardless of whether the desktop is Lubuntu). It's recommended to not run other apps during the upgrade. In this case, restarting Firefox is usually enough to fix the issue. If not, restarting after the upgrade completes does fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Changed in: cloud-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Marking cloud-images and maas-images as fixed with the roll of util- linux, and confirmation from fginther ** Changed in: maas-images Status: Confirmed => Fix Released ** Changed in: cloud-images Status: New => 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in cloud-images: Fix Released Status in maas-images: Fix Released Status in The Ubuntu-power-systems project: Invalid Status in Release Notes for Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Invalid Status in systemd source package in Mantic: Invalid Status in util-linux source package in Mantic: Fix Released Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2038964] Re: raspi ethernet rename is racy
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038964 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from unaffected 2B (rev 1.2)" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708342/+files/unaffected.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy
** Attachment added: "kern.log from affected 3B+" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708341/+files/affected.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] [NEW] raspi ethernet rename is racy
Public bug reported: The renaming of the ethernet interface (controlled by 10-raspi-eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image ** Tags added: raspi-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2038964 Title: raspi ethernet rename is racy Status in ubuntu-settings package in Ubuntu: New Bug description: The renaming of the ethernet interface (controlled by 10-raspi- eth0.link in ubuntu-raspi-settings) turns out to be racy. Specifically, in the final mantic server images (but not the desktop images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any other supported board, including the 3B), the interface renames several times during boot. By the end, the interface is left in the enxMACMACMAC state and the netplan configuration fails to apply. Will attach kern.log from an affected platform, and another from an unaffected platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2037497]
FEDORA-2023-86e10b6cae has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Fix Released Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497] Re: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Changed in: mesa (Fedora) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashes on Intel Ice Lake with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Fix Released Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2034986] Re: some text became unreadable during a distribution upgrade
I just ran an errand, and thought about that font workaround. The MATE
issue makes me doubt about running the code for all the flavors.
We know that the root cause is changes to the Ubuntu font. That font is
explicitly used for desktop in standard Ubuntu and MATE. But is it used
for desktop by any other flavor?
I fear that we for other flavors mess with their settings unnecessarily.
If the reset succeeds, it doesn't matter much, but maybe more flavors
have not enabled the required systemd integration, and then our
'temporary' change gets persistent. Which may or may not matter in
practice.
So maybe it would be better to only run the code for flavors where we
know that it makes a difference. Something like:
is_mate = False
desktops = os.getenv('XDG_CURRENT_DESKTOP', '').split(':')
if 'MATE' in desktops:
schema = 'org.mate.interface'
is_mate = True
else if 'GNOME' in desktops:
schema = 'org.gnome.desktop.interface'
else if 'xxx' in desktops:
schema = 'yyy'
else:
return
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986
Title:
some text became unreadable during a distribution upgrade
Status in Ubuntu MATE:
New
Status in ubuntu-meta package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
In Progress
Status in ubuntu-meta source package in Mantic:
Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
In Progress
Bug description:
I was upgrading from Lunar to Mantic the other day and left a couple
of applications open during the upgrade process. During the upgrade
the text in audacious became unreadable (I'll attach a screenshot) and
I seem to recall the title bar of Firefox being unreadable but the
contents of web pages still being readable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.5
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 8 15:39:27 2023
InstallationDate: Installed on 2018-08-10 (1855 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat',
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code
126: Error executing command as another user: Request dismissed
VarLogDistupgradeTermlog:
mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Also affects: systemd (Ubuntu Mantic) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: New Status in systemd source package in Mantic: New Bug description: In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. Ubuntu 23.10 debug ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0 4096
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Tags added: foundations-todo ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: New Bug description: In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. Ubuntu 23.10 debug ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0
[Touch-packages] [Bug 1552230] Re: gdb man page doesn't mention option "--args"
This has been addressed as of 12.1-0ubuntu1~22.04 in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1552230 Title: gdb man page doesn't mention option "--args" Status in gdb package in Ubuntu: Confirmed Bug description: gdb manpage doesn't list --args as a possible command line argument. This very important option allows one to pass an executable name with /its/ command line, and is possibly one of the most generally useful of gdb's arguments. It is documented in the info file, but unaccountably missing from the man page. Description:Ubuntu 15.10 Release:15.10 gdb: Installed: 7.10-1ubuntu2 Candidate: 7.10-1ubuntu2 Version table: *** 7.10-1ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1552230/+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 2038650] Re: crash reports not sent to the Error Tracker
** Changed in: apport (Ubuntu Lunar) Milestone: None => lunar-updates ** Changed in: apport (Ubuntu Lunar) Importance: Undecided => High ** Changed in: apport (Ubuntu Lunar) Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Confirmed Status in apport source package in Mantic: Fix Released Bug description: From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2034986] Re: some text became unreadable during a distribution upgrade
I filed the Lubuntu equivalent of this bug as https://launchpad.net/bugs/2038946 Minor issue, didn't affect the upgrade itself or most apps. Easy workaround for Firefox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy
Hi Prashanth, Unless there's a good reason, the Jammy/Focal version of openssh will stay the version it is. Likely, any changes to this package will be specific commits which will have to go through the SRU process[0] if it can be justified. Is there a reason you are trying to test the latest openssl on Jammy? Unless something happens, the openssl version in Jammy should remain the version it is, excluding SRUs which are mentioned above, so Jammy shouldn't need to support OpenSSL 3.1.X. [0] - https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2038561 Title: Requesting Ubuntu package manager to release openssh updates to focal and jammy Status in openssh package in Ubuntu: Incomplete Bug description: We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and 20.04 machines because the machine gets bricked and loses SSH after installation of OpenSSL 3.1.2. This is because SSHD gets restarted when OpenSSL 3.1 gets installed. But it fails to come up and we lose SSH access to the box. Debug logging on SSHD shows the below error when it tries to start : OpenSSL version mismatch. Built against 3020, you have 30100020 After researching in online forums, it appears that this is an OpenSSH bug and it's been fixed in version 9.4p1 and 9.5p1 via this fix : https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237 However, it appears that only 8.9p1 version of openssh-client and openssh-server are available in Ubuntu packages. Requesting you to please release openssh versions 9.4p1 or 9.5p1 on Jammy and Focal which will help us move past this bug and start testing OpenSSL 3.1 for our use cases. Additional information about our environment: $ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 $ apt-cache policy openssh-server openssh-server: Installed: 1:8.9p1-3ubuntu0.4 Candidate: 1:8.9p1-3ubuntu0.4 Version table: *** 1:8.9p1-3ubuntu0.4 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:8.9p1-3ubuntu0.3 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:8.9p1-3 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: In Progress Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 2024864] Re: systemd-networkd crashes with SIGSEGV
This bug was fixed in the package below, available under Ubuntu Pro
18.04.
systemd (237-3ubuntu10.57+esm1) bionic; urgency=medium
* d/p/lp2024864-add-missing-null-check.patch:
- Add NULL check on link_drop_foreign_request (LP: #2024864)
-- Tiago Pasqualini Fri, 23 Jun 2023
16:51:01 -0300
** Changed in: ubuntu-pro/18.04
Status: In Progress => 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/2024864
Title:
systemd-networkd crashes with SIGSEGV
Status in systemd:
Fix Released
Status in Ubuntu Pro:
Fix Released
Status in Ubuntu Pro 18.04 series:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
Customer reported that this issue happens randomly during their
automated regression runs. It's not consistent and hard to reproduce.
They have shared a coredump:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x555962aa1c34 in link_drop_foreign_config
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
2741 ../src/network/networkd-link.c: No such file or directory.
(gdb) bt
#0 0x555962aa1c34 in link_drop_foreign_config
(link=link@entry=0x555963583f30) at ../src/network/networkd-link.c:2741
#1 0x555962aa233d in link_carrier_lost.lto_priv.328 (link=, link=) at ../src/network/networkd-link.c:3462
#2 0x555962a8e9b2 in link_update (m=0x5559635702c0, link=)
at ../src/network/networkd-link.c:3698
#3 manager_rtnl_process_link (rtnl=, message=0x5559635702c0,
userdata=) at ../src/network/networkd-manager.c:713
#4 0x555962a48a16 in process_match (m=0x5559635702c0,
rtnl=0x55596355d990) at ../src/libsystemd/sd-netlink/sd-netlink.c:388
#5 process_running (ret=0x0, rtnl=0x55596355d990) at
../src/libsystemd/sd-netlink/sd-netlink.c:418
#6 sd_netlink_process (rtnl=0x55596355d990, ret=ret@entry=0x0) at
../src/libsystemd/sd-netlink/sd-netlink.c:452
#7 0x555962a48cb3 in time_callback (s=, usec=, userdata=) at ../src/libsystemd/sd-netlink/sd-netlink.c:759
#8 0x555962a4dbae in source_dispatch (s=s@entry=0x55596355dce0) at
../src/libsystemd/sd-event/sd-event.c:2311
#9 0x555962a4de2a in sd_event_dispatch (e=,
e@entry=0x55596355bf70) at ../src/libsystemd/sd-event/sd-event.c:2663
#10 0x555962a4dfb9 in sd_event_run (e=,
e@entry=0x55596355bf70, timeout=timeout@entry=18446744073709551615) at
../src/libsystemd/sd-event/sd-event.c:2723
#11 0x555962a4e1fb in sd_event_loop (e=) at
../src/libsystemd/sd-event/sd-event.c:2744
#12 0x555962a223d6 in main (argc=, argv=)
at ../src/network/networkd.c:158
This can be fixed by simply null checking link->network before doing anything
with it. Upstream has fixed it on this commit:
https://github.com/systemd/systemd/commit/b1b0b42e48303134731e017a108c6c334ef5f4c8
[ Test Plan ]
Since this issue is hard to reproduce, I was able trigger it on gdb,
by adding a breakpoint once the manager is setup, getting the loopback
device and running link_drop_foreign_config on the loopback device:
(gdb) b src/network/networkd.c:150
Breakpoint 1 at 0x2f38f: file ../src/network/networkd.c, line 150.
(gdb) r
Starting program: /lib/systemd/systemd-networkd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
eth0: IPv6 successfully enabled
eth0: Gained IPv6LL
Breakpoint 1, main (argc=, argv=) at
../src/network/networkd.c:152
152 log_info("Enumeration completed");
(gdb) p *m->links
$1 = {b = {hash_ops = 0x5578f230 , {indirect = {storage
= 0x2e, hash_key = "\200\376yUUU\000\000\001\000\000\000\000\000\000",
n_entries = 1434074992, n_buckets = 21845, idx_lowest_entry = 256,
_pad = "\000\000"}, direct = {
storage =
".\000\000\000\000\000\000\000\200\376yUUU\000\000\001\000\000\000\000\000\000\000p?zUUU\000\000\000\001\000\000\000\000"}},
type = HASHMAP_TYPE_PLAIN, has_indirect = false, n_direct_entries = 2,
from_pool = true}}
(gdb) set $mylink = (Link **) malloc(sizeof(Link *))
(gdb) call link_get(m, 1, $mylink)
$2 = 0
(gdb) p *$mylink
$3 = (Link *) 0x557a3f70
(gdb) p **$mylink
$4 = {manager = 0x55796940, n_ref = 2, ifindex = 1, master_ifindex = 0,
ifname = 0x557a0060 "lo", kind = 0x0, iftype = 772,
state_file = 0x5579c670 "/run/systemd/netif/links/1", mac =
{ether_addr_octet = "\000\000\000\000\000"}, ipv6ll_address = {__in6_u = {
__u6_addr8 = '\000' , __u6_addr16 = {0, 0, 0, 0, 0,
0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, mtu = 65536, udev_device = 0x0,
flags = 65609, kernel_operstate = 0 '\000', network = 0x0, state =
LINK_STATE_UNMANAGED, operstate = LINK_OPERSTATE_CARRIER, address_messages = 0,
address_label_messages = 0, route_messages = 0,
routing_policy_rule_messages = 0,
[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
I'm attaching the debdiff that fixes this issue on the apparmor pre- install script. ** Description changed: + [ Impact ] + + * During an apparmor package upgrade, the cache files were +deleted, but there could also be directories under +/etc/apparmor.d/cache/ which the pre installation scripts did +not account for. The upgrade would then fail with the +following error message because it would not be able to remove +the directories: + + package:apparmor:2.12-4ubuntu5.3 + Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... + rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory + dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): + new apparmor package pre-installation script subprocess returned error exit status 1 + ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 + + [ Test Plan ] + + * On a bionic machine, create a directory under + /etc/apparmor.d/cache + + sudo mkdir /etc/apparmor.d/cache/test + + * To simulate a system upgrade to focal, you can run the following + steps + + 1. Add the focal archive + + sudo bash -c "cat
[Touch-packages] [Bug 2038925] [NEW] Many hangs during apt full-upgrade
Public bug reported: Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has resulted in many hangs of up to a minute or so during the upgrade procedure. These seem to happen at random and unpredictable steps during the upgrade. Running it just now, it hung for around a minute on this line: Installing new version of config file /etc/lsb-release ... At around the same time, the following was logged to /var/log/syslog, which may or may not be related: 2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/73400498" It then hung again for about a minute at: Setting up apport (2.27.0-0ubuntu5) ... but nothing was logged to syslog. These hangs did not happen on 23.04. I appreciate that this is all a bit vague, so am happy to do further debugging if someone can advise me what to do. I also appreciate that apt might not be the correct package to file this bug against - feel free to reassign it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 10 06:41:34 2023 InstallationDate: Installed on 2020-07-14 (1183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038925 Title: Many hangs during apt full-upgrade Status in apt package in Ubuntu: New Bug description: Since upgrading to Ubuntu 23.10, running "apt full-upgrade" has resulted in many hangs of up to a minute or so during the upgrade procedure. These seem to happen at random and unpredictable steps during the upgrade. Running it just now, it hung for around a minute on this line: Installing new version of config file /etc/lsb-release ... At around the same time, the following was logged to /var/log/syslog, which may or may not be related: 2023-10-10T06:38:33.162713-07:00 albatross hud-service[3499]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/73400498" It then hung again for about a minute at: Setting up apport (2.27.0-0ubuntu5) ... but nothing was logged to syslog. These hangs did not happen on 23.04. I appreciate that this is all a bit vague, so am happy to do further debugging if someone can advise me what to do. I also appreciate that apt might not be the correct package to file this bug against - feel free to reassign it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3 Uname: Linux 6.5.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 10 06:41:34 2023 InstallationDate: Installed on 2020-07-14 (1183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: apt UpgradeStatus: Upgraded to mantic on 2023-09-16 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2038925/+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 1399945] Re: Settings, Preferences, ect. - All keyboard input is added twice
** Changed in: winff (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1399945 Title: Settings, Preferences, ect. - All keyboard input is added twice Status in Winff: Unknown Status in ibus package in Ubuntu: New Status in winff package in Ubuntu: Fix Released Bug description: Test Case: Open winff Try to edit or add something using keyboard. All characters are doubled Screen shows attempt to add /Videos to Output Folder box ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: winff 1.5.3-4ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:32:03 2014 InstallationDate: Installed on 2014-11-16 (20 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) PackageArchitecture: all SourcePackage: winff UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/winff/+bug/1399945/+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 2038922] [NEW] Sudden screen crash
Public bug reported: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2038922 Title: Sudden screen crash Status in xorg package in Ubuntu: New Bug description: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18
[Touch-packages] [Bug 2038740] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: o subprocesso do pacote apparmor, novo script pre-installation retornou erro do status de saída 1
*** This bug is a duplicate of bug 2032851 *** https://bugs.launchpad.net/bugs/2032851 ** This bug has been marked a duplicate of bug 2032851 package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 -- 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/2038740 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: o subprocesso do pacote apparmor, novo script pre-installation retornou erro do status de saída 1 Status in apparmor package in Ubuntu: New Bug description: Diversos problemas nos programas do libreoffice ProblemType: Package DistroRelease: Ubuntu 20.04 Package: apparmor 2.12-4ubuntu5.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: apparmor:amd64: Install libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 7 20:19:20 2023 DpkgHistoryLog: Start-Date: 2023-10-07 20:19:11 Commandline: packagekit role='install-files' Requested-By: ubuntu (1000) Upgrade: libreoffice-common:amd64 (1:6.0.7-0ubuntu0.18.04.13, 1:6.4.7-0ubuntu0.20.04.8), apparmor:amd64 (2.12-4ubuntu5.3, 2.13.3-7ubuntu5.2) DpkgTerminalLog: A preparar para desempacotar .../apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: não foi possível remover '/etc/apparmor.d/cache/e10c1cf9.0': É um diretório dpkg: erro ao processar o arquivo /var/cache/apt/archives/apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): o subprocesso do pacote apparmor, novo script pre-installation retornou erro do status de saída 1 ErrorMessage: o subprocesso do pacote apparmor, novo script pre-installation retornou erro do status de saída 1 InstallationDate: Installed on 2023-09-01 (36 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-163-generic root=UUID=8a1d548e-ad1e-40f1-ab36-082b4bd2d1e4 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: apparmor Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: o subprocesso do pacote apparmor, novo script pre-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2023-09-23 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038740/+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 2037642] Re: [FFe] Raspberry Pi 5 support
Added text to the release notes [1] detailing Pi 5 support, including the planned SRU of libcamera support. Can others double-check the raspberry pi sections look reasonable, and let me know if we want to mention anything else specific? I've also updated the "known issues" section, removing a couple of bits (totem now works and the audio output selection is now sane out of the box), and adding others (slide corruption on the pi4 during installation). Again, if there's anything missing that should be mentioned please either let me know or feel free to add it yourself! [1]: https://discourse.ubuntu.com/t/mantic-minotaur-release-notes/35534 ** Changed in: ubuntu-release-notes Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: In Progress Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2038918] [NEW] package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaard
Public bug reported: I get this while with an Odroid. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: initramfs-tools 0.142ubuntu2.2 Uname: Linux 4.9.337-138 aarch64 NonfreeKernelModules: spidev spi_meson_spicc ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Oct 10 13:43:00 2023 ErrorMessage: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug UpgradeStatus: Upgraded to lunar on 2023-10-10 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2038918 Title: package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug Status in initramfs-tools package in Ubuntu: New Bug description: I get this while with an Odroid. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: initramfs-tools 0.142ubuntu2.2 Uname: Linux 4.9.337-138 aarch64 NonfreeKernelModules: spidev spi_meson_spicc ApportVersion: 2.26.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Oct 10 13:43:00 2023 ErrorMessage: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug UpgradeStatus: Upgraded to lunar on 2023-10-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038918/+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 2038807] Re: /usr/libexec/packagekitd:6:g_assertion_message:g_assertion_message_expr:pk_transaction_dispose:pk_transaction_dispose:g_object_unref
It's currently the top error.u.c report for mantic ** Changed in: packagekit (Ubuntu) Importance: Undecided => High ** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2038807 Title: /usr/libexec/packagekitd:6:g_assertion_message:g_assertion_message_expr:pk_transaction_dispose:pk_transaction_dispose:g_object_unref Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.7-1, the problem page at https://errors.ubuntu.com/problem/cd0c285c1cd4d44fe17fb5ad9952d5921959f195 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2038807/+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 2038650] Re: crash reports not sent to the Error Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2038650 Title: crash reports not sent to the Error Tracker Status in apport package in Ubuntu: Fix Released Status in apport source package in Lunar: Confirmed Status in apport source package in Mantic: Fix Released Bug description: From what I can tell when I click the send button to send a crash report to the Error Tracker the crash doesn't actually get sent. My testing process follows: 1) Launch xeyes 2) pkill -11 xeyes 3) Click send in the apport dialog 4) ls -lh /var/crash I would expect there to be three files in /var/crash: -rw-r- 1 bdmurray whoopsie 3370567 Oct 6 11:53 _usr_bin_xeyes.1000.crash -rw-rw-r-- 1 bdmurray bdmurray0 Oct 6 11:53 _usr_bin_xeyes.1000.upload -rw--- 1 whoopsie whoopsie 37 Oct 6 11:53 _usr_bin_xeyes.1000.uploaded However, after step #4 I'm only seeing the .crash file and not a .upload or .uploaded. I was able to get the .upload and .uploaded files created if I chose to "View Report" and then click "Send". It's worth noting though that I did notice the size of the .crash file increase after clicking "Send" so some post-processing was done. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 +0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 12:12:46 2023 InstallationDate: Installed on 2022-01-07 (637 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2038650/+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 2016318] Re: free command: in Italian header is misaligned and wrongly translated
@mapreri I made the changes as you indicated, also accepting @enzotib proposals. Words are now aligned correctly with numbers ** Changed in: procps (Ubuntu) Assignee: (unassigned) => Salvatore Cocuzza (salvatorecocuzza) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2016318 Title: free command: in Italian header is misaligned and wrongly translated Status in Ubuntu Translations: Confirmed Status in procps package in Ubuntu: Confirmed Bug description: free command: in Italian header is misaligned and wrongly translated gratuiti is 'for free' or 'gratis' or 'toll free' 'free' may be translated with 'liberi' total = totali ... ok used = usati ... ok free = liberi ... to be changed shared = condivisi ... ok buff/cache ... ok available = disponibili ... ok corrado@corrado-n4-ll-beta:~$ free totalusedfree shared buff/cache available Mem:16151400 223667211599888 517412 3171440 13914728 Swap:8388604 0 8388604 corrado@corrado-n4-ll-beta:~$ corradi@corrado-n4-ll-beta:~$ free buff/cache condivisi gratuiti totali utilizzati disponibili Mem:16151400 175200411850636 333144 3227540 14399396 Swap:8388604 0 8388604 corradi@corrado-n4-ll-beta:~$ ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: procps 2:4.0.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 18:34:49 2023 InstallationDate: Installed on 2023-03-31 (14 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2016318/+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 2038901] [NEW] Ubuntu default/minimal installation should be smaller
Public bug reported: Ubuntu default/minimal installation should be made smaller in future. It's a little too close to the full install size right now. As of mantic 2023-10-10, the default/minimal install ends up 8.4 GB whereas the full install is 9.4 GB. https://docs.google.com/spreadsheets/d/e/2PACX-1vSmQLXuDO0E-tKnWcgjL3Ua2bWDeUg4ICZIfuMrrZndBrYjbVLKAWlKuiZLZ9EOrj4N1WV37DRg8GyW/pubchart?oid=2040836911=interactive ** Affects: ubuntu-meta (Ubuntu) Importance: Wishlist Status: New ** Tags: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2038901 Title: Ubuntu default/minimal installation should be smaller Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu default/minimal installation should be made smaller in future. It's a little too close to the full install size right now. As of mantic 2023-10-10, the default/minimal install ends up 8.4 GB whereas the full install is 9.4 GB. https://docs.google.com/spreadsheets/d/e/2PACX-1vSmQLXuDO0E-tKnWcgjL3Ua2bWDeUg4ICZIfuMrrZndBrYjbVLKAWlKuiZLZ9EOrj4N1WV37DRg8GyW/pubchart?oid=2040836911=interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2038901/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature
The attachment "0001-UBUNTU-SAUCE-no-up-apparmor- disable-1ea37b26d720-UBU.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Triaged Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session
** Summary changed:
- df: /sys/firmware/efi/efivars: Invalid argument causes installation crash
+ df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live
session
** Description changed:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
of the live session - I note subsequently that at the end of the
installation curtin fails due to an efivars error - looking at syslog I
saw various efivars errors so I'm filing this with the kernel since this
is the first instance.
+
+ Note - raised separate issue for the installation crash which has now
+ been duplicated against
+ https://bugs.launchpad.net/subiquity/+bug/2003222
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/2038765
Title:
df: /sys/firmware/efi/efivars: Invalid argument causes error on
login/live session
Status in lightdm package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
df: /sys/firmware/efi/efivars: Invalid argument appears on first
display of the live session - I note subsequently that at the end of
the installation curtin fails due to an efivars error - looking at
syslog I saw various efivars errors so I'm filing this with the kernel
since this is the first instance.
Note - raised separate issue for the installation crash which has now
been duplicated against
https://bugs.launchpad.net/subiquity/+bug/2003222
i.e. running grep efivars /var/log/*
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 2077 F wireplumber
/dev/snd/seq:ubuntu-budgie 2074 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CasperVersion: 1.486
CurrentDesktop: Budgie:GNOME
Date: Sun Oct 8 16:27:29 2023
LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64
(20231008.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-7-generic N/A
linux-backports-modules-6.5.0-7-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 0.1
[Touch-packages] [Bug 2038892] Re: How To Contact +1(202-960-2084) McAfee Customer Service Number?
** Package changed: cups (Ubuntu) => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 2038892] [NEW] How To Contact +1(202-960-2084) McAfee Customer Service Number?
Private bug reported: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. ** Affects: null-and-void Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 2028082] Autopkgtest regression report (glib2.0/2.76.4-0ubuntu1)
All autopkgtests for the newly accepted glib2.0 (2.76.4-0ubuntu1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: adsys/0.11.0 (arm64) balsa/2.6.4-2 (arm64) cmake-extras/1.6-1 (armhf) firewalld/1.3.0-1 (arm64) libsoup3/3.4.0-1 (amd64) slurm-wlm/22.05.8-3 (armhf) surf/2.1+git20221016-4build1 (armhf) udisks2/2.9.4-4 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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
