[Touch-packages] [Bug 2097611] Re: Please merge with version 16.2-1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~pushkarnk/ubuntu/+source/gdb/+git/gdb/+merge/480894 -- 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/2097611 Title: Please merge with version 16.2-1 from Debian unstable Status in gdb package in Ubuntu: New Bug description: Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2097611/+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 2097611] Re: Please merge with version 16.2-1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~pushkarnk/ubuntu/+source/gdb/+git/gdb/+merge/480898 -- 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/2097611 Title: Please merge with version 16.2-1 from Debian unstable Status in gdb package in Ubuntu: New Bug description: Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2097611/+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 2097787] Re: Pulseaudio fills up /var/log folder
** Changed in: pulseaudio (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2097787 Title: Pulseaudio fills up /var/log folder Status in pulseaudio package in Ubuntu: New Status in pulseaudio package in Debian: New Bug description: Pulseaudio 15.0 crashed and filled up /var/log/syslog /var/log/user.log /var/log/messages /var/log/user.log.1 and /var/log/syslog.1 with the the following error pulseaudio[1210]: ICE I/O error handler called The files together are 25GB, I am using OS 5.16.0-kali7-amd64 pulseaudio version 15.0, The crash caused the /var directory to run out of space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2097787/+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 2089800] Re: Ubuntu desktop is unstable under memory pressure due to undesireable OOMScoreAdjust values
The Problem The problem is obviously system instability due to memory pressure, but what can an admin do about it? Some options exist to configure the priority of processes killed due to memory pressure. Non-snap processes can be configured via systemd using OOMScoreAdjust[1] (kernel OOM[2]) and ManagedOOMMemoryPressureLimit[3][4] (userspace OOM[5]). Snap has no support for configuring userspace OOM priority. Snap has a setting[6] for setting kernel OOM priority. While the setting may be logical within the snap ecosystem, it has deficiencies when integrating with the rest of Ubuntu: 1) This setting provides no ability to set specific kernel OOM scores, which is required to set priority with respect to non-snap processes. 2) The current user interface does not allow a user to __increase__ the likelihood of cgroup being killed (please kill my browser before a component of my desktop). 3) The default snap setting makes snap-based processes (and snapd itself) less likely to be killed than core system services on which snap processes depend - a priority inversion. Proposed solution - Ubuntu ships with both DEBs and snaps, therefore a solution that allows snaps to configure OOM priority with respect to the rest of the OS would be best. In the near term, providing snap users with the ability to set the values of ManagedOOMMemoryPressureLimit and OOMScoreAdjust for snaps would empower users to tune their system to achieve better stability under memory pressure. In the long term in order to provide the best system behavior under memory pressure it would benefit Ubuntu to ship with more appropriate defaults (desktop / server personality, snaps using a more sensible default). Definitions --- [1] OOMScoreAdjust - a systemd directive which systemd uses to set the the kernel OOM score[7], defaults to 0 [2] Kernel OOM - action taken when the kernel runs out of memory to allocate and memory reclaim hasn't returned enough memory - kernel kills a processes based on a metric derived from the OOM score and amount of memory used by each process [3][4] ManagedOOMMemoryPressureLimit - a systemd threshold used by systemd-oomd, it represents the fraction of time in a 10 second window in which all tasks in the control group were delayed - defaults to 60% [5] systemd-oomd - a system service that uses cgroups-v2 and pressure stall information (PSI[8]) to monitor and take corrective action before an OOM occurs in the kernel space [6] `snap set system resilience.vitality-hint=snapA,snapB,snapC` [7] /proc//oom_score_adj - a procfs file containing OOM score of a process [8] PSI (Pressure Stall Information) - counters exported to user-space which indicate memory pressure - available since linux version 4.20 References -- [1] https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#OOMScoreAdjust= [2] https://www.kernel.org/doc/gorman/html/understand/understand016.html [3] https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html#ManagedOOMMemoryPressureLimit= [4] https://www.freedesktop.org/software/systemd/man/latest/oomd.conf.html# [5] https://www.freedesktop.org/software/systemd/man/latest/systemd-oomd.service.html [6] https://snapcraft.io/docs/system-options#heading--resilience [7] https://man7.org/linux/man-pages/man5/proc_pid_oom_score_adj.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/2089800 Title: Ubuntu desktop is unstable under memory pressure due to undesireable OOMScoreAdjust values Status in lxd: Unknown Status in snapd: New Status in dbus package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: A logic error in some code I wrote caused lxd to spawn many qemu VMs which caused memory pressure. This caused the OOM killer to be invoked, which killed gnome-character. Because the DefaultOOMPolicy is set to "stop", this caused dbus.service to stop. My system user slice wasn't able to handle running without dbus.service, and it subsequently crashed. Crashing my user session is better than locking up my whole system, I guess, but it still would have been much preferred for a single application (a VM or browser, preferrablky) to have been killed rather than loose all work in process and have to log back in. I think that we can provide a more stable Ubuntu desktop environment. tl;dr = We should take a holistic view of the oom_score_adjust / OOMScoreAdjust settings of various systemd services and rethink the priority of these services that is required for a stable linux desktop. History === Back in 2018, Linux kernel release 4.20 gained a new interface which improved the ability of the linux kernel to identify memory pressure[1][2]. Fast forward to 202
[Touch-packages] [Bug 2095074] Re: [SRU] Upgrade to media driver version 24.3.4 in Noble
Thanks for the clarification. Would 24.3.4+dfsg1-0ubuntu1~24.04 work? I see that's how it's been done over on Mesa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2095074 Title: [SRU] Upgrade to media driver version 24.3.4 in Noble Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in intel-gmmlib source package in Noble: New Status in intel-media-driver source package in Noble: New Status in intel-media-driver-non-free source package in Noble: New Status in libva source package in Noble: New Bug description: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware-enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. * Beyond Intel's extensive in-house testing, we have done our own testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration for encode and decode at 1080p and 4K. In addition to Lunar Lake and Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake and found no regressions across these platforms [ Other Info ] * This would ideally land at the same time as the libvpl version bump SRU here: https://bugs.launchpad.net/ubuntu/+source/onevpl/+bug/2096823 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/2095074/+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 2095597] Re: apparmor: removal of Python standard libraries in Python 3.13
** Changed in: apparmor (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2095597 Title: apparmor: removal of Python standard libraries in Python 3.13 Status in apparmor package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: Confirmed Status in apparmor package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1084647: Source: apparmor Severity: important User: debian-pyt...@lists.debian.org Usertags: pep-594-deprecation-313 Dear maintainer(s), Python 3.13 removes a large amount of so called 'dead battery' libraries from the standard library. As such, code that imports these libraries will no longer work in Python 3.13, which is the targeted version for Trixie. The following removed libraries were found in this package: cgitb: utils/apparmor/fail.py:11 See this link for more details: https://peps.python.org/pep-0594/#deprecated-modules Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2095597/+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 2097623] Re: Support Dracut as alternative initrd tool
This bug was fixed in the package ubuntu-meta - 1.545 --- ubuntu-meta (1.545) plucky; urgency=medium * Refreshed dependencies * Added dracut as alternative to initramfs-tools to desktop-minimal-recommends (LP: #2097623) -- Benjamin Drung Mon, 10 Feb 2025 14:15:47 + ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released -- 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/2097623 Title: Support Dracut as alternative initrd tool Status in germinate package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: We want to switch to Dracut. See https://discourse.ubuntu.com/t/spec- switch-to-dracut/54776 So please support dracut as alternative to initramfs-tools. Following binary packages depend on initramfs-tools: * ubuntu-budgie-desktop * ubuntu-budgie-desktop-minimal * ubuntucinnamon-desktop * ubuntucinnamon-desktop-minimal Following binary packages recommend initramfs-tools: * ubuntu-desktop * ubuntu-desktop-minimal * ubuntu-mate-core * ubuntu-mate-desktop * ubuntukylin-desktop * ubuntukylin-desktop-minimal Please change their dependency/recommendation to "initramfs-tools | dracut" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2097623/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop
a 503 from launchpad caused /cdrom/casper/minimal.standard.live.squashfs to not get copied into the image build, causing the entire iso to not work, as described in this bug. ** Also affects: ubuntu-cdimage Importance: Undecided Status: New ** Changed in: ubuntu-cdimage Status: New => In Progress ** Changed in: ubuntu-cdimage Assignee: (unassigned) => Tim Andersson (andersson123) -- 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/2031899 Title: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop Status in Ubuntu CD Images: In Progress Status in ubuntu-desktop-installer: Invalid Status in initramfs-tools package in Ubuntu: Invalid Bug description: Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error reported when attempting to boot live installation media - File system layers missing:\n '/cdrom/casper/minimal.standard.live.squashfs .. see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2031899/+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 2097769] Re: Installation of ubuntu-desktop-minimal breaks DNS
Can you please provide resolvectl output at various stages (e.g. when DNS is working, and when it's not), as well as systemd-resolved journal output (journalctl -u systemd-resolved -b > resolved.log). ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/2097769 Title: Installation of ubuntu-desktop-minimal breaks DNS Status in systemd package in Ubuntu: Incomplete Bug description: After performing an autoinstall with Ubuntu Server ISO and rebooting, trying to automate the installation of ubuntu-desktop-minimal causes DNS settings to be lost. For our specific use-case, we are installing ubuntu server (fully automated), then using Puppet to install desktop packages. This was working without any manual interaction previously on both Ubuntu 22.04 and 24.04 For the last week or so, deployments of 24.04 (22.04 is still fine) are getting stuck after installing ubuntu-desktop-minimal. The DNS server settings are lost, but IP connectivity remains. Step-by-step 1) Install Ubuntu Server with default network configuration using autoinstall. 2) Reboot and install network-manager (note that everything is still working normally) 3) Install ubuntu-desktop-minimal DNS settings are now lost on the primary interface, yet IP connectivity remains. networkd is still managing the interface, but "netplan get" reports that NetworkManager is the current renderer. ``` network: version: 2 renderer: NetworkManager ethernets: enp1s0: critical: true nameservers: addresses: - 172.16.1.100 - 172.18.1.100 dhcp-identifier: "mac" dhcp4: true ``` We can workaround the problem forcing an extra reboot after installing ubuntu-desktop-minimal. But previously this workflow was fine without rebooting until the very end of the config. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Mon Feb 10 10:47:43 2025 InstallationDate: Installed on 2025-02-10 (0 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-52-generic root=/dev/mapper/vg00-root ro RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2021 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.18227214.B64.2106252220 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+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 1681993] Re: Systemd service for packages without support
This is something we are tracking, because systemd is dropping support for the systemd-sysv-generator in v258. Debian also has a report tracking these packages, and bugs open to get native systemd services defined: https://people.debian.org/~zeha/missing_systemd_service_by_source.html. We will need to have some kind of upgrade logic for packages that have not made the final switch by then. ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Medium => High ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Tags added: foundations-todo -- 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/1681993 Title: Systemd service for packages without support Status in systemd package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: This bug is a little (just a little!?) crazy: First I done some shell- fu: apt-file search /lib/systemd/system/|grep service|cut -d: -f1|uniq > systemd_service.txt apt-file search /etc/init.d/|cut -d: -f1|uniq > sysvinit_service.txt diff systemd_service.txt sysvinit_service.txt|grep '^\+' >just_sysvinit.txt The first command created a list with the packages with systemd services. I considered as systemd service any package with a .service file under /lib/systemd/system/. The second command created a list with the packages with sysvinit services. I considered a sysvinit service any package with a file under /etc/init.d/. The third command compares the two files and only select the packages with sysvinit service, but without a correspondent systemd service. This packages should have support for systemd too because systemd is now native on new Ubuntu releases. I don't think need hurry to change all packages because sysvinit support on systemd is solid, but I think we need to think about this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681993/+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 2097623] Re: Support Dracut as alternative initrd tool
** Merge proposal linked: https://code.launchpad.net/~bdrung/germinate/+git/germinate/+merge/480940 -- 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/2097623 Title: Support Dracut as alternative initrd tool Status in germinate package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: We want to switch to Dracut. See https://discourse.ubuntu.com/t/spec- switch-to-dracut/54776 So please support dracut as alternative to initramfs-tools. Following binary packages depend on initramfs-tools: * ubuntu-budgie-desktop * ubuntu-budgie-desktop-minimal * ubuntucinnamon-desktop * ubuntucinnamon-desktop-minimal Following binary packages recommend initramfs-tools: * ubuntu-desktop * ubuntu-desktop-minimal * ubuntu-mate-core * ubuntu-mate-desktop * ubuntukylin-desktop * ubuntukylin-desktop-minimal Please change their dependency/recommendation to "initramfs-tools | dracut" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2097623/+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 2097623] Re: Support Dracut as alternative initrd tool
I prepared ubuntu-meta 1.545 which I created with the modified germinate and faked dracut being in main. The newly add dracut should pull it into main. -- 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/2097623 Title: Support Dracut as alternative initrd tool Status in germinate package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: We want to switch to Dracut. See https://discourse.ubuntu.com/t/spec- switch-to-dracut/54776 So please support dracut as alternative to initramfs-tools. Following binary packages depend on initramfs-tools: * ubuntu-budgie-desktop * ubuntu-budgie-desktop-minimal * ubuntucinnamon-desktop * ubuntucinnamon-desktop-minimal Following binary packages recommend initramfs-tools: * ubuntu-desktop * ubuntu-desktop-minimal * ubuntu-mate-core * ubuntu-mate-desktop * ubuntukylin-desktop * ubuntukylin-desktop-minimal Please change their dependency/recommendation to "initramfs-tools | dracut" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2097623/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop
This resurfaced in the following build: https://ubuntu-archive-team.ubuntu.com/cd-build-logs/ubuntu/noble/daily-live-20250210.log -- 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/2031899 Title: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop Status in Ubuntu CD Images: In Progress Status in ubuntu-desktop-installer: Invalid Status in initramfs-tools package in Ubuntu: Invalid Bug description: Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error reported when attempting to boot live installation media - File system layers missing:\n '/cdrom/casper/minimal.standard.live.squashfs .. see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2031899/+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 2095074] Re: [SRU] Upgrade to media driver version 24.3.4 in Noble
Zixing, can you please elaborate? It looks to me like the version is the same as in Oracular: -intel-media-driver (24.3.4+dfsg1-0ubuntu1) oracular; urgency=medium +intel-media-driver (24.3.4+dfsg1-0ubuntu1) noble; urgency=medium Is there a reason it needs to be different for the Noble SRU? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2095074 Title: [SRU] Upgrade to media driver version 24.3.4 in Noble Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in intel-gmmlib source package in Noble: New Status in intel-media-driver source package in Noble: New Status in intel-media-driver-non-free source package in Noble: New Status in libva source package in Noble: New Bug description: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware-enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. * Beyond Intel's extensive in-house testing, we have done our own testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration for encode and decode at 1080p and 4K. In addition to Lunar Lake and Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake and found no regressions across these platforms [ Other Info ] * This would ideally land at the same time as the libvpl version bump SRU here: https://bugs.launchpad.net/ubuntu/+source/onevpl/+bug/2096823 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/2095074/+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 2032824] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2032824 Title: Veth pairs fail activation on Jammy Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Released Bug description: [ Impact ] * Network Manager 1.36 has a bug that prevents it to activate veth pairs. * The problem was found in the Netplan's CI with the new support for veths in Netplan v0.107. * We cherry-pick upstream patches to fix the issue: - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/07e0ab48d194b8bd6663a34887c2e753720ae4d3 - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/50f738bde5b441b5ca52024c1a0998399b87337b [ Test Plan ] * Run netplan.io's autopkgtests against the new network-manager package and make sure it passes the veth tests, especially those two: - test_create_veth_pair (__main__.TestNetworkManager) - test_create_veth_pair_with_ip_address (__main__.TestNetworkManager) * In addition to that, reproduce the steps from this bug report: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were activated, and created in the system. Also, check the systemd journal and you should NOT see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists [ Where problems could occur ] * We're pulling upstream patchces to modify NetworkManager's src/core/devices/nm-device-veth.c file. This could have side-effects on veth functionality in general when NetworkManager is in use. [ Other Info ] * This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 * Danilo created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager === Original bug report === Network Manager 1.36 has a bug that prevents it to activate veth pairs. The problem was found in the Netplan's CI with the new support for veths in Netplan (because we run the tests on Jammy). How to reproduce the problem: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were not activated, even though both interfaces were created in the system. Also, check the systemd journal and you should see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists Try the very same steps on Lunar and you'll see that the connections will be activated just fine. This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 I created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager If you run the same steps again on Jammy w
[Touch-packages] [Bug 2032824] Re: Veth pairs fail activation on Jammy
This bug was fixed in the package network-manager - 1.36.6-0ubuntu2.1 --- network-manager (1.36.6-0ubuntu2.1) jammy; urgency=medium [ Danilo Egea Gondolfo ] * debian/patches/lp2032824 (LP: #2032824) Fix for VETHs pairs activation on startup. [ Jeremy Bicha ] * debian/watch: Watch for 1.36.x releases -- Lukas Märdian Wed, 11 Dec 2024 15:48:05 +0100 ** Changed in: network-manager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2032824 Title: Veth pairs fail activation on Jammy Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Released Bug description: [ Impact ] * Network Manager 1.36 has a bug that prevents it to activate veth pairs. * The problem was found in the Netplan's CI with the new support for veths in Netplan v0.107. * We cherry-pick upstream patches to fix the issue: - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/07e0ab48d194b8bd6663a34887c2e753720ae4d3 - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/50f738bde5b441b5ca52024c1a0998399b87337b [ Test Plan ] * Run netplan.io's autopkgtests against the new network-manager package and make sure it passes the veth tests, especially those two: - test_create_veth_pair (__main__.TestNetworkManager) - test_create_veth_pair_with_ip_address (__main__.TestNetworkManager) * In addition to that, reproduce the steps from this bug report: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were activated, and created in the system. Also, check the systemd journal and you should NOT see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists [ Where problems could occur ] * We're pulling upstream patchces to modify NetworkManager's src/core/devices/nm-device-veth.c file. This could have side-effects on veth functionality in general when NetworkManager is in use. [ Other Info ] * This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 * Danilo created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager === Original bug report === Network Manager 1.36 has a bug that prevents it to activate veth pairs. The problem was found in the Netplan's CI with the new support for veths in Netplan (because we run the tests on Jammy). How to reproduce the problem: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were not activated, even though both interfaces were created in the system. Also, check the systemd journal and you should see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists Try the very same steps on Lunar and you'll see that the connections will be activated just fine. This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 I created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager If you run the same steps again on Jammy
[Touch-packages] [Bug 2095074] Re: [SRU] Upgrade to media driver version 24.3.4 in Noble
The version number forms part of the deb file name. If you had two debs with slightly different contents (even due to rebuilding the same source) then you wouldn't be able to tell which one it was. So the version number needs forking in Noble. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2095074 Title: [SRU] Upgrade to media driver version 24.3.4 in Noble Status in intel-gmmlib package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in intel-media-driver-non-free package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in intel-gmmlib source package in Noble: New Status in intel-media-driver source package in Noble: New Status in intel-media-driver-non-free source package in Noble: New Status in libva source package in Noble: New Bug description: [ Description ] Intel has requested us to update the media driver (free and non-free) to 24.3.4 due to the need to have Lunar Lake (LNL) and Battle Mage (BMG) support. This request has a strong dependency on an intel-gmmlib version bump to 22.5.2 and a libva version bump to 2.22.0. [ Impact ] * Users with Lunar Lake or Battlemage currently do not have an LTS support option, which is not a good option for some users, as seen here: https://github.com/canonical/intel-graphics-preview/issues/8 * Users with Lunar Lake or Battlemage hardware will not have hardware-enabled media support, which can effect the power consumption and CPU utilization of the machine during encode/decode/transcode operations, video calls, streaming, etc. [ Test Plan ] # On a Lunar Lake or Battlemage machine # Required at this time to get baseline enablement sudo add-apt-repository ppa:kobuk-team/intel-graphics-testing sudo apt update # Get the original versions back sudo apt install -y intel-media-va-driver-non-free=24.1.0+ds1-1 libva2=2.20.0-2build1 libigdgmm12=22.3.17+ds1-1 vainfo=2.12.0+ds1-1 libva-drm2=2.20.0-2build1 libva-wayland2=2.20.0-2build1 libva-x11-2=2.20.0-2build1 # This should result in an error sudo vainfo sudo add-apt-repository -y ppa:mckeesh/testing && sudo apt -y update # Only upgrade the media packages sudo apt install -y intel-media-va-driver-non-free=24.3.4+ds1-0ubuntu1 libva2=2.22.0-1ubuntu1 libigdgmm12=22.5.2-0ubuntu1 libva-drm2=2.22.0-1ubuntu1 libva-wayland2=2.22.0-1ubuntu1 libva-x11-2=2.22.0-1ubuntu1 vainfo=2.12.0+ds1-1 # This should no longer result in an error sudo vainfo [ Where problems could occur ] * This is a sizable change, and while significant testing goes into making sure the media stack does not regress, it's always a risk. Ubuntu has a large user base with many, many corner cases, and media stack bumps can always accidentally regress a less popular codec on an older platform. However, we can address any smaller regressions that might arise when the benefit is enablement of LNL and BMG. * Beyond Intel's extensive in-house testing, we have done our own testing via FFMPEG to check for AV1, VP9, and H264 hardware acceleration for encode and decode at 1080p and 4K. In addition to Lunar Lake and Battlemage, we have also tested Alder Lake, Comet Lake, and Gemini Lake and found no regressions across these platforms [ Other Info ] * This would ideally land at the same time as the libvpl version bump SRU here: https://bugs.launchpad.net/ubuntu/+source/onevpl/+bug/2096823 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/2095074/+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 2097800] Re: [MIR] libva
lintian log with pedantic: W: libva-dev: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva-dev/changelog.Debian.gz:1] W: libva-drm2: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva-drm2/changelog.Debian.gz:1] W: libva-glx2: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva-glx2/changelog.Debian.gz:1] W: libva-wayland2: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva-wayland2/changelog.Debian.gz:1] W: libva-x11-2: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva-x11-2/changelog.Debian.gz:1] W: libva2: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/libva2/changelog.Debian.gz:1] W: va-driver-all: changelog-distribution-does-not-match-changes-file unstable != plucky [usr/share/doc/va-driver-all/changelog.Debian.gz:1] W: libva changes: distribution-and-changes-mismatch plucky unstable ** Changed in: libva (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/2097800 Title: [MIR] libva Status in libva package in Ubuntu: Incomplete Bug description: [Availability] The package libva is already in Ubuntu universe. The package libva build for the architectures it is designed to work on. It currently builds and works for all Ubuntu architectures Link to package https://launchpad.net/ubuntu/+source/libva [Rationale] - The package libva is required in Ubuntu main for gnome-remote-desktop - The package libva will generally be useful for a large part of our user base - The package libva is a new runtime dependency of package gnome-remote-desktop that we already support - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The binary package TBD needs to be in main to achieve keeping gnome-remote-desktop up-to-date and supported. - The package libva is required in Ubuntu main no later than February 20 due to Ubuntu 25.04 Feature Freeze. Practically, we will likely need a Feature Freeze Exception for this. [Security] - Had 1 security issue in the past https://ubuntu.com/security/CVE-2023-39929 https://security-tracker.debian.org/tracker/CVE-2023-39929 The CVE is unclear; it might not have affected Ubuntu. - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Security has been kept in mind and common isolation/risk-mitigation patterns are in place utilizing the following features: + apparmor profile copied from evince - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs + Ubuntu https://bugs.launchpad.net/ubuntu/+source/libva + Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libva + Upstream https://github.com/intel/libva/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because none is provided upstream because it is difficult to test hardware accelerated video processing with build tests. - The package does not run an autopkgtest because it is difficult to test hardware accelerated video processing with autopkgtests. RULE: - If no build tests nor autopkgtests are included, and/or if the package RULE: requires specific hardware to perform testing, the subscribed team RULE: must provide a written test plan in a comment to the MIR bug, and RULE: commit to running that test either at each upload of the package or RULE: at least once each release cycle. In the comment to the MIR bug, RULE: please link to the codebase of these tests (scripts or doc of manual RULE: steps) and attach a full log of these test runs. This is meant to RULE: assess their validity (e.g. not just superficial). RULE: If possible such things should stay in universe. Sometimes that is RULE: impossible due to the way how features/plugins/dependencies work RULE: but if you are going to ask for promotion of something untestable RULE: please outline why it couldn't provide its value (e.g. by splitting RULE: binaries) to users from universe. RULE: This is a balance that is hard to strike well, the request is that all RULE: options have been exploited before giving up. Look for more details R
[Touch-packages] [Bug 2097800] [NEW] [MIR] libva
Public bug reported: [Availability] The package libva is already in Ubuntu universe. The package libva build for the architectures it is designed to work on. It currently builds and works for all Ubuntu architectures Link to package https://launchpad.net/ubuntu/+source/libva [Rationale] - The package libva is required in Ubuntu main for gnome-remote-desktop - The package libva will generally be useful for a large part of our user base - The package libva is a new runtime dependency of package gnome-remote-desktop that we already support - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The binary package TBD needs to be in main to achieve keeping gnome-remote-desktop up-to-date and supported. - The package libva is required in Ubuntu main no later than February 20 due to Ubuntu 25.04 Feature Freeze. Practically, we will likely need a Feature Freeze Exception for this. [Security] - Had 1 security issue in the past https://ubuntu.com/security/CVE-2023-39929 https://security-tracker.debian.org/tracker/CVE-2023-39929 The CVE is unclear; it might not have affected Ubuntu. - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Security has been kept in mind and common isolation/risk-mitigation patterns are in place utilizing the following features: + apparmor profile copied from evince - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs + Ubuntu https://bugs.launchpad.net/ubuntu/+source/libva + Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libva + Upstream https://github.com/intel/libva/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because none is provided upstream because it is difficult to test hardware accelerated video processing with build tests. - The package does not run an autopkgtest because it is difficult to test hardware accelerated video processing with autopkgtests. RULE: - If no build tests nor autopkgtests are included, and/or if the package RULE: requires specific hardware to perform testing, the subscribed team RULE: must provide a written test plan in a comment to the MIR bug, and RULE: commit to running that test either at each upload of the package or RULE: at least once each release cycle. In the comment to the MIR bug, RULE: please link to the codebase of these tests (scripts or doc of manual RULE: steps) and attach a full log of these test runs. This is meant to RULE: assess their validity (e.g. not just superficial). RULE: If possible such things should stay in universe. Sometimes that is RULE: impossible due to the way how features/plugins/dependencies work RULE: but if you are going to ask for promotion of something untestable RULE: please outline why it couldn't provide its value (e.g. by splitting RULE: binaries) to users from universe. RULE: This is a balance that is hard to strike well, the request is that all RULE: options have been exploited before giving up. Look for more details RULE: and backgrounds https://github.com/canonical/ubuntu-mir/issues/30 RULE: Just like in the SRU process it is worth to understand what the RULE: consequences a regression (due to a test miss) would be. Therefore RULE: if being untestable we ask to outline what consequences this would RULE: have for the given package. And let us be honest, even if you can RULE: test you are never sure you will be able to catch all potential RULE: regressions. So this is mostly to force self-awareness of the owning RULE: team than to make a decision on. TODO: - The package can not be well tested at build or autopkgtest time TODO: because TBD. To make up for that: TODO-A: - We have access to such hardware in the team TODO-B: - We have allocated budget to get this hardware, but it is not here TODO-B: yet TODO-C: - We have checked with solutions-qa and will use their hardware TODO-C: through testflinger TODO-D: - We have checked with other team TBD and will use their hardware TODO-D: through TBD (eg. MAAS) TODO-E: - We have checked and found a simulator which covers this case TODO-E: sufficiently for testing, our plan to use it is TBD TODO-F: - We have engaged with the upstream community and due to that TODO-F: can tests new package builds via TBD TODO-G: - We have engaged with our user community and due to that TODO-G: can tests new package builds via TBD TODO-H: - We have engaged with the hardware manuf
[Touch-packages] [Bug 2097787] Re: Pulseaudio fills up /var/log folder
** Bug watch added: Debian Bug tracker #100 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100 ** Also affects: pulseaudio (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100 Importance: Unknown Status: Unknown ** Package changed: alsa-lib (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2097787 Title: Pulseaudio fills up /var/log folder Status in pulseaudio package in Ubuntu: New Status in pulseaudio package in Debian: Unknown Bug description: Pulseaudio 15.0 crashed and filled up /var/log/syslog /var/log/user.log /var/log/messages /var/log/user.log.1 and /var/log/syslog.1 with the the following error pulseaudio[1210]: ICE I/O error handler called The files together are 25GB, I am using OS 5.16.0-kali7-amd64 pulseaudio version 15.0, The crash caused the /var directory to run out of space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2097787/+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 2097736] [NEW] A broken service in the repository 24.04(gvm)
Public bug reported: OpenVAS (Open Vulnerability Assessment System) aka Greenbone which is installed in Ubuntu by the: apt install gvm sudo gvm-setup does not work The developer claims that it has not been working since version 22: https://forum.greenbone.net/t/setup-on-ubuntu-22-10-url-not-found/14124 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Summary changed: - A broken service in the repository (gvm) + A broken service in the repository 24.04(gvm) -- 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/2097736 Title: A broken service in the repository 24.04(gvm) Status in apport package in Ubuntu: New Bug description: OpenVAS (Open Vulnerability Assessment System) aka Greenbone which is installed in Ubuntu by the: apt install gvm sudo gvm-setup does not work The developer claims that it has not been working since version 22: https://forum.greenbone.net/t/setup-on-ubuntu-22-10-url-not- found/14124 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2097736/+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 2078759] Re: Ability to use comments in YAML generated by Netplan
Moving this bug/feature request to the upstream Netplan project. ** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: Triaged => Invalid ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Medium -- 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/2078759 Title: Ability to use comments in YAML generated by Netplan Status in Netplan: Triaged Status in OEM Priority Project: Confirmed Status in netplan.io package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Invalid Bug description: On ubuntu desktop 24.04 image, run the operations below 1. $ nmcli d wifi connect password 2. $ nmcli c delete 3. $ sudo debsums -s Then the error is happened debsums: changed file /lib/netplan/00-network-manager-all.yaml (from ubuntu-settings package) it seems the netplan update the file belonged to ubuntu-settings that cause the debsums failed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04a-next-20240902-67 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-09-02 (1 days ago) InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20240829) Package: netplan.io 1.0.1-1ubuntu2~24.04.1 PackageArchitecture: amd64 ProcVersionSignature: User Name 6.8.0-1012.12-oem 6.8.12 Tags: noble Uname: Linux 6.8.0-1012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2078759/+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 2083129] Re: [Lenovo Ubuntu 22.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip
Setting to "Incomplete" while waiting on confirmation of the workaround finding of a reliable reproducer. ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: [Lenovo Ubuntu 22.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip Status in netplan.io package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Status in netplan.io source package in Jammy: New Status in network-manager source package in Jammy: Invalid Bug description: On Ubuntu 22.04.4, to configure a system to use static address assignment, create a netplan configuration in the file, like /etc/netplan/00-installer-config.yaml. After assigning the network configuration abstraction renderer to NetworkManager not networkd in /etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the NIC interface lost their static ip in some reboot cycles when the rendered is NetworkManager, but networkd as a renderer is works well, all NIC interfaces can get their corresponding IP that configured in netplan confile file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2083129/+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 2055333] Re: netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy
Thanks for the summary. Closing. ** Changed in: netplan.io (Ubuntu) Status: New => Won't Fix ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/2055333 Title: netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy Status in netplan.io package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Attempting to add additional loopback addresses to 22.04 jammy fails with the latest netplan.io package. Previous versions (.104) work correctly as well as newer versions (0.107) in 23.10 mantic. Behavior does not change if default loopback addresses are or are not present in the address list (127.0.0.1/8 and ::1/128). Netplan is configured via cloudinit in our environment but for simplicity I'll provide output from a manual configuration on a test vm in virtual box. root@ubuntu-jammy-test:~# cat /etc/netplan/10-loopback.yaml network: version: 2 ethernets: lo: addresses: - 10.10.10.10/32 match: macaddress: 00:00:00:00:00:00 set-name: lo root@ubuntu-jammy-test:~# netplan apply WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running. root@ubuntu-jammy-test:~# ip addr show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever root@ubuntu-jammy-test:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp0s3 etherroutableconfigured 2 links listed. root@ubuntu-jammy-test:~# apt-get install -y --allow-downgrades netplan.io=0.104-0ubuntu2 libnetplan0=0.104-0ubuntu2 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: network-manager | wpasupplicant openvswitch-switch The following packages will be DOWNGRADED: libnetplan0 netplan.io 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. Need to get 0 B/181 kB of archives. After this operation, 163 kB disk space will be freed. dpkg: warning: downgrading netplan.io from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 (Reading database ... 69845 files and directories currently installed.) Preparing to unpack .../netplan.io_0.104-0ubuntu2_amd64.deb ... Unpacking netplan.io (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... dpkg: warning: downgrading libnetplan0:amd64 from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 Preparing to unpack .../libnetplan0_0.104-0ubuntu2_amd64.deb ... Unpacking libnetplan0:amd64 (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... Setting up libnetplan0:amd64 (0.104-0ubuntu2) ... Setting up netplan.io (0.104-0ubuntu2) ... Processing triggers for libc-bin (2.35-0ubuntu3.6) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. root@ubuntu-jammy-test:~# netplan apply root@ubuntu-jammy-test:~# ip addr show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 10.10.10.10/32 scope global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever root@ubuntu-jammy-test:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback routableconfigured 2 enp0s3 etherroutableconfigured 2 links listed. root@ubuntu-jammy-test:~# apt-get upgrade -y Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnetplan0 net
[Touch-packages] [Bug 2097168] Re: Launchpad can't process crash reports
As schopin mentioned, this issue seems to be caused by an unknown LF line-break expectation in Launchpad's "FileBugDataParser", which caused the error when the apport package's requests with LF line-breaks were fixed into CRLF line-breaks. Since the apport package has been reverted, this bug has also been technically fixed in Launchpad. All-in-all, we will work to fix this problematic expectation issue, as it doesn't confer to the RFC standards and because it blocks further work on upgrades that expect those standards. ** Changed in: launchpad Importance: Undecided => Critical ** Changed in: launchpad Status: New => Fix Released -- 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/2097168 Title: Launchpad can't process crash reports Status in Launchpad itself: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: I was trying to add a new crash report for an Ubuntu package, but the system keeps on telling: Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete and the crash report isn't processed anymore To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/2097168/+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 2097736] Re: A broken service in the repository 24.04(gvm)
Those are two different components of the software stack based on different technologies (C and JavaScript) and which can be found here: GitHub - greenbone/gsad: Greenbone Security Assistant HTTP Server - The server talking to the Greenbone Vulnerability Management daemon (gvmd). 47 GitHub - greenbone/gsa: Greenbone Security Assistant - The web frontend for the Greenbone Community Edition 58 and why did Ubuntu not provide the missing JS-package? Greenbone doesn’t have any knowledge on the Ubuntu side (Greenbone isn’t involved in any 3rd party packaging), that question would need to be forwarded to the Ubuntu packaging team. -- 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/2097736 Title: A broken service in the repository 24.04(gvm) Status in apport package in Ubuntu: New Bug description: OpenVAS (Open Vulnerability Assessment System) aka Greenbone which is installed in Ubuntu by the: apt install gvm sudo gvm-setup does not work The developer claims that it has not been working since version 22: https://forum.greenbone.net/t/setup-on-ubuntu-22-10-url-not- found/14124 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2097736/+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 2096327] Re: apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token missing from http response -> "assert ticket"
Removing 24.04.2 milestone. ** Changed in: apport (Ubuntu Noble) Milestone: ubuntu-24.04.2 => None -- 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/2096327 Title: apport cannot upload blobs to launchpad - X-Launchpad-Blob-Token missing from http response -> "assert ticket" Status in Apport: Fix Committed Status in Launchpad itself: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: New Status in apport source package in Jammy: New Status in apport source package in Noble: Confirmed Status in apport source package in Oracular: Confirmed Bug description: [ Impact ] The apport code, through the use of Python's `email` package, isn't HTTP 1.1 compliant when crafting the payload to the LP +storeblob endpoint, using LF as a line separator rather than CRLF. A recent update to the `multipart` dependency of LP made it stricter when parsing this kind of payload, making any attempt to file a bug through Apport (e.g. `ubuntu-bug foo`) fail miserably. The issue was worked around by rolling back that update, but it's not a longterm solution, as it's probably better for everyone if LP stays up-to-date on its dependencies. This impacts 24.04.2 as the workaround needs to stay in place as long as our "default" ISOs ship a buggy apport. [ Test plan ] We're using the chaos-marmosets package since it's maintained by members of the Apport team so nobody should be too annoyed by the noise. First step: contact the LP team to make sure we have an environment with the newer multipart available. Let's assume that environment is qastaging. ``` # File a bug in qastaging, and manually inspect the contents of the attached files APPORT_LAUNCHPAD_INSTANCE=qastaging ubuntu-bug chaos-marmosets # Do the same on the prod instance as a control experiment. # Don't forget to close the bug afterwards ;) ubuntu-bug chaos-marmosets ``` [ Where problems could occur ] Fixing the problem with the new dependency could regress against the workaround, which is why the test plan tests against both prod and qastaging. Messing with the way the payload is crafted could potentially corrupt the attached files, which is why the tester must actually *look* at the attached data. [ Original report ] The tale is slightly convoluted. After doing an "apt upgrade" yesterday, xsane and simple-scan started failing: scanner detected, but could not scan. Trying to report it with ubuntu-bug then crashed with the following error: $ sudo ubuntu-bug simple-scan Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 650, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 917, in run_argv return self.run_report_bug() ^ File "/usr/lib/python3/dist-packages/apport/ui.py", line 740, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1788, in file_report upthread.exc_raise() File "/usr/lib/python3/dist-packages/apport/REThread.py", line 67, in exc_raise raise self._exception[1].with_traceback(self._exception[2]) File "/usr/lib/python3/dist-packages/apport/REThread.py", line 42, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 222, in upload ticket = upload_blob(blob_file, progress_callback, hostname=self.get_hostname()) ^^^ File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 1246, in upload_blob assert ticket ^^ AssertionError This is a blocker for me. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2096327/+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 2097469] Re: Prepare base-files update for .2 release
This bug was fixed in the package base-files - 13ubuntu10.2
---
base-files (13ubuntu10.2) noble; urgency=medium
* /etc/issue{,.net}, /etc/{lsb,os}-release: bump version to 24.04.2.
(LP: #2097469)
-- Florent 'Skia' Jacquet Wed, 05 Feb
2025 17:08:58 +0100
** Changed in: base-files (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2097469
Title:
Prepare base-files update for .2 release
Status in base-files package in Ubuntu:
Invalid
Status in base-files source package in Noble:
Fix Released
Bug description:
Prepare base-files update for /etc/issue{,.net}, /etc/{lsb,os}-release
files to bump version to 24.04.2 - the upcoming Noble point release.
Past example: https://launchpad.net/ubuntu/+source/base-
files/13ubuntu10.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2097469/+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 2097469] Update Released
The verification of the Stable Release Update for base-files has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2097469
Title:
Prepare base-files update for .2 release
Status in base-files package in Ubuntu:
Invalid
Status in base-files source package in Noble:
Fix Released
Bug description:
Prepare base-files update for /etc/issue{,.net}, /etc/{lsb,os}-release
files to bump version to 24.04.2 - the upcoming Noble point release.
Past example: https://launchpad.net/ubuntu/+source/base-
files/13ubuntu10.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2097469/+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 2075337] Re: [SRU] py3clean fails when using alternate character set
** Merge proposal linked: https://code.launchpad.net/~hyask/britney/+git/hints-ubuntu/+merge/480924 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/2075337 Title: [SRU] py3clean fails when using alternate character set Status in a2d package in Ubuntu: New Status in apertium-apy package in Ubuntu: New Status in autopilot package in Ubuntu: New Status in blueman package in Ubuntu: New Status in borgmatic package in Ubuntu: New Status in btchip-python package in Ubuntu: New Status in condor package in Ubuntu: Invalid Status in cpupower-gui package in Ubuntu: New Status in debomatic package in Ubuntu: New Status in dell-recovery package in Ubuntu: New Status in deluge package in Ubuntu: New Status in depthcharge-tools package in Ubuntu: New Status in dhcpy6d package in Ubuntu: New Status in dkimpy-milter package in Ubuntu: New Status in fenrir package in Ubuntu: Invalid Status in galileo package in Ubuntu: New Status in glances package in Ubuntu: New Status in graphite-carbon package in Ubuntu: New Status in grokmirror package in Ubuntu: New Status in guerillabackup package in Ubuntu: New Status in ionit package in Ubuntu: New Status in jupyterhub package in Ubuntu: New Status in liquidctl package in Ubuntu: Invalid Status in localslackirc package in Ubuntu: Invalid Status in logdata-anomaly-miner package in Ubuntu: Invalid Status in lomiri package in Ubuntu: Invalid Status in mailman3 package in Ubuntu: Invalid Status in matrix-sydent package in Ubuntu: Invalid Status in mom package in Ubuntu: Invalid Status in mopidy package in Ubuntu: Invalid Status in mpd-sima package in Ubuntu: Invalid Status in nordugrid-arc package in Ubuntu: Invalid Status in notus-scanner package in Ubuntu: Invalid Status in nrpe-ng package in Ubuntu: Invalid Status in onionprobe package in Ubuntu: Invalid Status in openscap-daemon package in Ubuntu: Invalid Status in ospd-openvas package in Ubuntu: Invalid Status in pagekite package in Ubuntu: Invalid Status in pagure package in Ubuntu: Invalid Status in pglistener package in Ubuntu: Invalid Status in policyd-rate-limit package in Ubuntu: Invalid Status in postfix-mta-sts-resolver package in Ubuntu: Invalid Status in powa-collector package in Ubuntu: Invalid Status in prelude-correlator package in Ubuntu: Invalid Status in prometheus-pgbouncer-exporter package in Ubuntu: Invalid Status in prometheus-xmpp-alerts package in Ubuntu: Invalid Status in pyro5 package in Ubuntu: Incomplete Status in pyroman package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Fix Released Status in r4d package in Ubuntu: Invalid Status in razercfg package in Ubuntu: Invalid Status in sgt-launcher package in Ubuntu: Fix Released Status in sms4you package in Ubuntu: Invalid Status in supervisor package in Ubuntu: Invalid Status in syncplay package in Ubuntu: Invalid Status in timekpr-next package in Ubuntu: Fix Released Status in twms package in Ubuntu: Invalid Status in vanguards package in Ubuntu: Incomplete Status in vaultlocker package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Invalid Status in voctomix-outcasts package in Ubuntu: Invalid Status in weborf package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Status in condor source package in Jammy: Invalid Status in fenrir source package in Jammy: Invalid Status in liquidctl source package in Jammy: Invalid Status in localslackirc source package in Jammy: Invalid Status in logdata-anomaly-miner source package in Jammy: Invalid Status in lomiri source package in Jammy: Invalid Status in mailman3 source package in Jammy: Invalid Status in matrix-sydent source package in Jammy: Invalid Status in mom source package in Jammy: Invalid Status in mopidy source package in Jammy: Invalid Status in mpd-sima source package in Jammy: Invalid Status in nordugrid-arc source package in Jammy: Invalid Status in notus-scanner source package in Jammy: Invalid Status in nrpe-ng source package in Jammy: Invalid Status in onionprobe source package in Jammy: Invalid Status in openscap-daemon source package in Jammy: Invalid Status in ospd-openvas source package in Jammy: Invalid Status in pagekite source package in Jammy: Invalid Status in pagure source package in Jammy: Invalid Status in pglistener source package in Jammy: Invalid Status in policyd-rate-limit source package in Jammy: Invalid Status in postfix-mta-sts-resolver source package in Jammy: Invalid Status in powa-collector source package in Jammy: Invalid Status in prelude-correlator source package in Jammy: Invalid Status in prometheus-pgbouncer-exporter source package in Jammy: Invalid Status in prometheus-xmpp-alerts source package in Jammy: Inval
[Touch-packages] [Bug 2097786] [NEW] [USB-Audio Mic no audio pickup ( TONOR TD520 Dynamic )
You have been subscribed to a public bug: The Mic/headset combo does not pickup audio. The speaker headset (works fine) is connected to the microphone by a plug. The whole is connected to the pc by a usb cable. Ubuntu Desktop recornize the mic/headset combo but no audio pickup. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 19:25:02 2025 InstallationDate: Installed on 2025-01-14 (27 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. OptiPlex 7020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Mic failed Symptom_AlsaRecordingTestStderr: F a i l u r e t o s u s p e n d : N o s u c h e n t i t y Symptom_Card: TONOR TD520 Dynamic Mic - TONOR TD520 Dynamic Mic Symptom_Type: None of the above Title: [USB-Audio - TONOR TD520 Dynamic Mic, recording] Recording problem UpgradeStatus: Upgraded to noble on 2025-01-16 (25 days ago) dmi.bios.date: 04/25/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 08WKV3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/25/2014:br4.6:svnDellInc.:pnOptiPlex7020:pvr01:rvnDellInc.:rn08WKV3:rvrA00:cvnDellInc.:ct6:cvr:skuOptiPlex7020: dmi.product.name: OptiPlex 7020 dmi.product.sku: OptiPlex 7020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2025-02-07T20:24:31.980825 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- [USB-Audio Mic no audio pickup ( TONOR TD520 Dynamic ) https://bugs.launchpad.net/bugs/2097786 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2097787] [NEW] Pulseaudio fills up /var/log folder
Public bug reported: Pulseaudio 15.0 crashed and filled up /var/log/syslog /var/log/user.log /var/log/messages /var/log/user.log.1 and /var/log/syslog.1 with the the following error pulseaudio[1210]: ICE I/O error handler called The files together are 25GB, I am using OS 5.16.0-kali7-amd64 pulseaudio version 15.0, The crash caused the /var directory to run out of space. ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/2097787 Title: Pulseaudio fills up /var/log folder Status in alsa-lib package in Ubuntu: New Bug description: Pulseaudio 15.0 crashed and filled up /var/log/syslog /var/log/user.log /var/log/messages /var/log/user.log.1 and /var/log/syslog.1 with the the following error pulseaudio[1210]: ICE I/O error handler called The files together are 25GB, I am using OS 5.16.0-kali7-amd64 pulseaudio version 15.0, The crash caused the /var directory to run out of space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/2097787/+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 2097786] Re: [USB-Audio Mic no audio pickup ( TONOR TD520 Dynamic )
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2097786 Title: [USB-Audio Mic no audio pickup ( TONOR TD520 Dynamic ) Status in alsa-driver package in Ubuntu: New Bug description: The Mic/headset combo does not pickup audio. The speaker headset (works fine) is connected to the microphone by a plug. The whole is connected to the pc by a usb cable. Ubuntu Desktop recornize the mic/headset combo but no audio pickup. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 19:25:02 2025 InstallationDate: Installed on 2025-01-14 (27 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Dell Inc. OptiPlex 7020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Mic failed Symptom_AlsaRecordingTestStderr: F a i l u r e t o s u s p e n d : N o s u c h e n t i t y Symptom_Card: TONOR TD520 Dynamic Mic - TONOR TD520 Dynamic Mic Symptom_Type: None of the above Title: [USB-Audio - TONOR TD520 Dynamic Mic, recording] Recording problem UpgradeStatus: Upgraded to noble on 2025-01-16 (25 days ago) dmi.bios.date: 04/25/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 08WKV3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/25/2014:br4.6:svnDellInc.:pnOptiPlex7020:pvr01:rvnDellInc.:rn08WKV3:rvrA00:cvnDellInc.:ct6:cvr:skuOptiPlex7020: dmi.product.name: OptiPlex 7020 dmi.product.sku: OptiPlex 7020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2025-02-07T20:24:31.980825 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2097786/+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 2097792] [NEW] Don't ship 10-dns-resolved.conf within network-manager bin:pkg
Public bug reported: Currently network-manager bin:pkg on Ubuntu 24.04 and up ships /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which forces NetworkManger to configure systemd-resolved as DNS resolver. However network-manager does not Depends: on systemd-resolved bin:pkg, which can lead to a situation where /etc/resolv.conf points to non-existent systemd-resolved. Since it's possible to use NetworkManager without systemd-resolved, we should not enforce the use of systemd-resolved from network-manager bin:pkg. Instead, I think it might be more appropriate to ship this file from systemd-resolved bin:pkg instead. It might look strange, but I think it's an OK thing to do. If NetworkManger is not installed, then nothing happens. But if NetworkManger is installed, then NetworkManager will start using systemd-resolved. What do you think? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2097792 Title: Don't ship 10-dns-resolved.conf within network-manager bin:pkg Status in network-manager package in Ubuntu: New Bug description: Currently network-manager bin:pkg on Ubuntu 24.04 and up ships /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which forces NetworkManger to configure systemd-resolved as DNS resolver. However network-manager does not Depends: on systemd-resolved bin:pkg, which can lead to a situation where /etc/resolv.conf points to non-existent systemd-resolved. Since it's possible to use NetworkManager without systemd-resolved, we should not enforce the use of systemd-resolved from network-manager bin:pkg. Instead, I think it might be more appropriate to ship this file from systemd-resolved bin:pkg instead. It might look strange, but I think it's an OK thing to do. If NetworkManger is not installed, then nothing happens. But if NetworkManger is installed, then NetworkManager will start using systemd-resolved. What do you think? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2097792/+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 2097623] Re: Support Dracut as alternative initrd tool
germinate needs to learn to support alternatives in recommends. ** Also affects: germinate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2097623 Title: Support Dracut as alternative initrd tool Status in germinate package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: We want to switch to Dracut. See https://discourse.ubuntu.com/t/spec- switch-to-dracut/54776 So please support dracut as alternative to initramfs-tools. Following binary packages depend on initramfs-tools: * ubuntu-budgie-desktop * ubuntu-budgie-desktop-minimal * ubuntucinnamon-desktop * ubuntucinnamon-desktop-minimal Following binary packages recommend initramfs-tools: * ubuntu-desktop * ubuntu-desktop-minimal * ubuntu-mate-core * ubuntu-mate-desktop * ubuntukylin-desktop * ubuntukylin-desktop-minimal Please change their dependency/recommendation to "initramfs-tools | dracut" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2097623/+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 2097769] [NEW] Installation of ubuntu-desktop-minimal breaks DNS
Public bug reported: After performing an autoinstall with Ubuntu Server ISO and rebooting, trying to automate the installation of ubuntu-desktop-minimal causes DNS settings to be lost. For our specific use-case, we are installing ubuntu server (fully automated), then using Puppet to install desktop packages. This was working without any manual interaction previously on both Ubuntu 22.04 and 24.04 For the last week or so, deployments of 24.04 (22.04 is still fine) are getting stuck after installing ubuntu-desktop-minimal. The DNS server settings are lost, but IP connectivity remains. Step-by-step 1) Install Ubuntu Server with default network configuration using autoinstall. 2) Reboot and install network-manager (note that everything is still working normally) 3) Install ubuntu-desktop-minimal DNS settings are now lost on the primary interface, yet IP connectivity remains. networkd is still managing the interface, but "netplan get" reports that NetworkManager is the current renderer. ``` network: version: 2 renderer: NetworkManager ethernets: enp1s0: critical: true nameservers: addresses: - 172.16.1.100 - 172.18.1.100 dhcp-identifier: "mac" dhcp4: true ``` We can workaround the problem forcing an extra reboot after installing ubuntu-desktop-minimal. But previously this workflow was fine without rebooting until the very end of the config. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Mon Feb 10 10:47:43 2025 InstallationDate: Installed on 2025-02-10 (0 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-52-generic root=/dev/mapper/vg00-root ro RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2021 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.18227214.B64.2106252220 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2097769 Title: Installation of ubuntu-desktop-minimal breaks DNS Status in systemd package in Ubuntu: New Bug description: After performing an autoinstall with Ubuntu Server ISO and rebooting, trying to automate the installation of ubuntu-desktop-minimal causes DNS settings to be lost. For our specific use-case, we are installing ubuntu server (fully automated), then using Puppet to install desktop packages. This was working without any manual interaction previously on both Ubuntu 22.04 and 24.04 For the last week or so, deployments of 24.04 (22.04 is still fine) are getting stuck after installing ubuntu-desktop-minimal. The DNS server settings are lost, but IP connectivity remains. Step-by-step 1) Install Ubuntu Server with default network configuration using autoinstall. 2) Reboot and install network-manager (note that everything is still working normally) 3) Install ubuntu-desktop-minimal DNS settings are now lost on the primary interface, yet IP connectivity remains. networkd is still managing the interface, but "netplan get" reports that NetworkManager is the current renderer. ``` network: version: 2
[Touch-packages] [Bug 2089800] Re: Ubuntu desktop is unstable under memory pressure due to undesireable OOMScoreAdjust values
** Description changed: A logic error in some code I wrote caused lxd to spawn many qemu VMs which caused memory pressure. This caused the OOM killer to be invoked, which killed gnome-character. Because the DefaultOOMPolicy is set to "stop", this caused dbus.service to stop. My system user slice wasn't able to handle running without dbus.service, and it subsequently crashed. Crashing my user session is better than locking up my whole system, I guess, but it still would have been much preferred for a single application (a VM or browser, preferrablky) to have been killed rather than loose all work in process and have to log back in. I think that we can provide a more stable Ubuntu desktop environment. tl;dr = We should take a holistic view of the oom_score_adjust / OOMScoreAdjust settings of various systemd services and rethink the priority of these services that is required for a stable linux desktop. History === Back in 2018, Linux kernel release 4.20 gained a new interface which improved the ability of the linux kernel to identify memory pressure[1][2]. Fast forward to 2020, and systemd 247[3] added experimental support for a new service, systemd-oomd[4], which combines cgroup data with the kernel interface for a more flexible and intelligent approach for killing user processes when faced with memory pressure. This runs by default today. OOM Score = The linux kernel provides an interface[5] which allows setting whether a process is more or less preferred when selecting a process to kill. The way that oom_score_adj works is approximately: -1000 means "never kill me, and 1000 means "always kill me". Systemd exposes this setting to developers[6] for use in systemd units. Unfortunately developers are posed the question "would you like your process to be killed earlier when under memory pressure?" the answer is typically "no", and so those units which set this value typically configure themselves to be _less likely_ than other processes to be killed, or remain unconfigured and inherit the default value. Consider an 24.10 Desktop = This table gets printed shortly before a task is killed, sorted by oom score: [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name [ 1027] 0 1027 8057 803 662 141 086016 160 -1000 systemd-udevd [ 2887] 0 288738273 210 32 178 073728 64 -1000 lxcfs [ 2814] 103 2814 2961 1040 902 138 069632 192 -900 dbus-daemon [ 2868] 0 286821222 272 96 176 0 143360 384 -900 virtlockd [ 2873] 0 287321223 319 96 223 0 147456 384 -900 virtlogd [ 160354] 135 160354 4251 567 160 407 077824 0 -900 systemd-oomd [ 178363] 0 178363 515293 4179 4138 41 0 425984 160 -900 snapd [ 165522] 0 16552212524 981 256 725 0 131072 32 -250 systemd-journal [ 2811] 0 281180606 419 256 163 0 126976 224 0 accounts-daemon [ 2812] 113 2812 1609 112 32 80 053248 32 0 avahi-daemon [ 2813] 0 2813 3124 226 32 194 073728 96 0 bluetoothd [ 2818] 992 2818 129054 363 160 203 0 212992 416 0 gnome-remote-de [ 2828] 995 282895844 1071 905 166 0 126976 160 0 polkitd [ 2842] 0 2842 2596 366 160 206 061440 224 0 smartd [ 2847] 0 284780150 241 64 177 0 131072 96 0 switcheroo-cont [ 2850] 0 2850 4385 405 177 228 073728 128 0 systemd-logind [ 2852] 0 2852 4220 263 96 167 073728 96 0 systemd-machine [ 2862] 0 2862 118000 1616 1429 187 0 167936 384 0 udisksd [ 2875] 0 287542224 417 224 193 098304 96 0 zed [ 2898] 104 289855022 898 727 171 094208 224 0 rsyslogd [ 2904] 113 2904 1495 184 34 150 053248 32 0 avahi-daemon [ 2958] 0 295887896 2074 1839 235 0 192512 288 0 NetworkManager [ 2989] 0 2989 4118 305 96 209 069632
Re: [Touch-packages] [Bug 2097769] Re: Installation of ubuntu-desktop-minimal breaks DNS
No problem, I'll try and grab these logs tomorrow when I do my next rebuild test. On 10/02/2025 15:44, Nick Rosbrook wrote: > Can you please provide resolvectl output at various stages (e.g. when > DNS is working, and when it's not), as well as systemd-resolved journal > output (journalctl -u systemd-resolved -b > resolved.log). > > ** Changed in: systemd (Ubuntu) > Status: New => Incomplete > -- James McKenzie Linux Support Officer EMBL-EBI ITS ServiceDesk Team, Thornton Building, AC265 European Bioinformatics Institute (EMBL-EBI) Wellcome Trust Genome Campus Hinxton Cambridge CB10 1SD (+44) 1223 494606 -- 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/2097769 Title: Installation of ubuntu-desktop-minimal breaks DNS Status in systemd package in Ubuntu: Incomplete Bug description: After performing an autoinstall with Ubuntu Server ISO and rebooting, trying to automate the installation of ubuntu-desktop-minimal causes DNS settings to be lost. For our specific use-case, we are installing ubuntu server (fully automated), then using Puppet to install desktop packages. This was working without any manual interaction previously on both Ubuntu 22.04 and 24.04 For the last week or so, deployments of 24.04 (22.04 is still fine) are getting stuck after installing ubuntu-desktop-minimal. The DNS server settings are lost, but IP connectivity remains. Step-by-step 1) Install Ubuntu Server with default network configuration using autoinstall. 2) Reboot and install network-manager (note that everything is still working normally) 3) Install ubuntu-desktop-minimal DNS settings are now lost on the primary interface, yet IP connectivity remains. networkd is still managing the interface, but "netplan get" reports that NetworkManager is the current renderer. ``` network: version: 2 renderer: NetworkManager ethernets: enp1s0: critical: true nameservers: addresses: - 172.16.1.100 - 172.18.1.100 dhcp-identifier: "mac" dhcp4: true ``` We can workaround the problem forcing an extra reboot after installing ubuntu-desktop-minimal. But previously this workflow was fine without rebooting until the very end of the config. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.5 ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12 Uname: Linux 6.8.0-52-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Mon Feb 10 10:47:43 2025 InstallationDate: Installed on 2025-02-10 (0 days ago) InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-52-generic root=/dev/mapper/vg00-root ro RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2021 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.18227214.B64.2106252220 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop
** Merge proposal linked: https://code.launchpad.net/~andersson123/ubuntu-cdimage/+git/ubuntu-cdimage/+merge/480945 -- 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/2031899 Title: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop Status in Ubuntu CD Images: In Progress Status in ubuntu-desktop-installer: Invalid Status in initramfs-tools package in Ubuntu: Invalid Bug description: Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error reported when attempting to boot live installation media - File system layers missing:\n '/cdrom/casper/minimal.standard.live.squashfs .. see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2031899/+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
