[Touch-packages] [Bug 2037210] Re: unable to add PPA by its sources.list line
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+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 2034656] Re: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time)
@juliank : can we not spread the load over 24h without systemd timers ? With a random sleep for example ? Surely people were spreading tasks over a specific period before systemd got invented. Also you say "they shouldn't then see more load than the archive mirror" but archive mirrors and ESM mirrors are vastly different, in terms of traffic, in terms of hardware, but also because ESM mirrors are HTTPS- only with an authentication backend whereas the archive mirrors are HTTP-only without authentication. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time) Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
I wouldn't even mind if the package was installed by default, but easily uninstallable. It is unfortunately not the case, since it prompts that it will also remove `xubuntu-desktop`, amongst many other packages. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 2037323] Re: gst-plugins-bad1.0 fails to build: netsim test failing
** Changed in: gst-plugins-bad1.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037323 Title: gst-plugins-bad1.0 fails to build: netsim test failing Status in gst-plugins-bad: New Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Status in gst-plugins-bad1.0 package in Debian: Confirmed Bug description: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command: GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good: gst-plugins-ugly:gst-libav:libnice:gst-plugins-bad@/<>/obj-x86_64-linux-gnu GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0: /usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_PLUGIN_SCANNER_1_0=/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner GST_STATE_IGNORE_ELEMENTS='' CK_DEFAULT_TIMEOUT=20 GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/elements_netsim.registry MALLOC_PERTURB_=119 GST_PLUGIN_SYSTEM_PATH_1_0='' LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/gst-libs/gst/basecamerabinsrc: /<>/obj-x86_64-linux-gnu/gst-libs/gst/uridownloader: /<>/obj-x86_64-linux-gnu/gst-libs/gst/interfaces: /usr/lib/libeatmydata /<>/obj-x86_64-linux-gnu/tests/check/elements_netsim --- stdout --- Running suite(s): netsim Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) 0%: Checks: 2, Failures: 2, Errors: 0 ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress_delayed:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Check suite netsim ran in 0.240s (tests failed: 2) To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-bad/+bug/2037323/+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 2018171] Re: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess return
** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2018171 Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post- installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: Upgrading from 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-common-525 525.105.17-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Apr 29 19:33:35 2023 ErrorMessage: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-22 (158 days ago) InstallationMedia: Ubuntu-Server 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018171/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Tags added: rls-mm-incoming -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2018171] Re: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess return
Commit 035190cc4385c0441dddc1bbaba000cf7f1f179b (released in initramfs- tools 0.141) introduced this kernel compression support check. Let's make mkinitramfs skip the compression support check if the kernel config is missing. ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => In Progress -- 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/2018171 Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post- installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: Upgrading from 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-common-525 525.105.17-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Apr 29 19:33:35 2023 ErrorMessage: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-22 (158 days ago) InstallationMedia: Ubuntu-Server 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018171/+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 2018255] Re: Failed to upgrade to release 23
*** This bug is a duplicate of bug 2018171 *** https://bugs.launchpad.net/bugs/2018171 The relevant dpkg terminal log is: update-initramfs: Generating /boot/initrd.img-4.13.0-21-generic grep: /boot/config-4.13.0-21-generic: No such file or directory W: xz compression (CONFIG_RD_XZ) not supported by kernel, using gzip grep: /boot/config-4.13.0-21-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by kernel update-initramfs: failed for /boot/initrd.img-4.13.0-21-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 The 4.13.0-21-generic Linux kernel is probably not available. Please remove that kernel. This particular bug has already been reported and is a duplicate of bug #2018171, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2018171 package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2018255 Title: Failed to upgrade to release 23 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to upgrade to Kubuntu 23. I've now rebooted so I can't tell which exact package failed; here's the last capture I have: dependency problems - leaving unconfigured Errors were encountered while processing: linux-firmware linux-image-generic linux-generic ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sddm 2282 F wireplumber /dev/snd/controlC1: sddm 2282 F wireplumber /dev/snd/seq:sddm 2281 F pipewire CasperMD5CheckResult: unknown Date: Tue May 2 07:20:56 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=67788873-0ab9-4395-880f-57ebe65682ce InstallationDate: Installed on 2018-01-23 (1924 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-41-generic root=/dev/mapper/vg500G4-lvKubuntuRoot ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-01 (0 days ago) dmi.bios.date: 10/30/2008 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd10/30/2008:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 2037323] Re: gst-plugins-bad1.0 fails to build: netsim test failing
** Changed in: gst-plugins-bad Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037323 Title: gst-plugins-bad1.0 fails to build: netsim test failing Status in gst-plugins-bad: New Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Status in gst-plugins-bad1.0 package in Debian: Unknown Bug description: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command: GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good: gst-plugins-ugly:gst-libav:libnice:gst-plugins-bad@/<>/obj-x86_64-linux-gnu GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0: /usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_PLUGIN_SCANNER_1_0=/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner GST_STATE_IGNORE_ELEMENTS='' CK_DEFAULT_TIMEOUT=20 GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/elements_netsim.registry MALLOC_PERTURB_=119 GST_PLUGIN_SYSTEM_PATH_1_0='' LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/gst-libs/gst/basecamerabinsrc: /<>/obj-x86_64-linux-gnu/gst-libs/gst/uridownloader: /<>/obj-x86_64-linux-gnu/gst-libs/gst/interfaces: /usr/lib/libeatmydata /<>/obj-x86_64-linux-gnu/tests/check/elements_netsim --- stdout --- Running suite(s): netsim Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) 0%: Checks: 2, Failures: 2, Errors: 0 ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress_delayed:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Check suite netsim ran in 0.240s (tests failed: 2) To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-bad/+bug/2037323/+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 2037325] [NEW] Sudden screen freeze
Public bug reported: Out of nowhere screen got frozen and didn't respond to any input, although I could get my pointer moving with touchpad. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Mon Sep 25 23:03:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (158 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037325 Title: Sudden screen freeze Status in xorg package in Ubuntu: New Bug description: Out of nowhere screen got frozen and didn't respond to any input, although I could get my pointer moving with touchpad. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Mon Sep 25 23:03:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (158 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 2037323] Re: gst-plugins-bad1.0 fails to build: netsim test failing
** Bug watch added: Debian Bug tracker #1052660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052660 ** Also affects: gst-plugins-bad1.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052660 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037323 Title: gst-plugins-bad1.0 fails to build: netsim test failing Status in gst-plugins-bad: Unknown Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Status in gst-plugins-bad1.0 package in Debian: Unknown Bug description: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command: GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good: gst-plugins-ugly:gst-libav:libnice:gst-plugins-bad@/<>/obj-x86_64-linux-gnu GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0: /usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_PLUGIN_SCANNER_1_0=/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner GST_STATE_IGNORE_ELEMENTS='' CK_DEFAULT_TIMEOUT=20 GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/elements_netsim.registry MALLOC_PERTURB_=119 GST_PLUGIN_SYSTEM_PATH_1_0='' LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/gst-libs/gst/basecamerabinsrc: /<>/obj-x86_64-linux-gnu/gst-libs/gst/uridownloader: /<>/obj-x86_64-linux-gnu/gst-libs/gst/interfaces: /usr/lib/libeatmydata /<>/obj-x86_64-linux-gnu/tests/check/elements_netsim --- stdout --- Running suite(s): netsim Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) 0%: Checks: 2, Failures: 2, Errors: 0 ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress_delayed:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Check suite netsim ran in 0.240s (tests failed: 2) To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-bad/+bug/2037323/+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 2037323] [NEW] gst-plugins-bad1.0 fails to build: netsim test failing
Public bug reported: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command: GST_PLUGIN_LOADING_WHITELIST=gstreamer:gst-plugins-base:gst-plugins-good: gst-plugins-ugly:gst-libav:libnice:gst-plugins-bad@/<>/obj-x86_64-linux-gnu GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0: /usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_PLUGIN_SCANNER_1_0=/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner GST_STATE_IGNORE_ELEMENTS='' CK_DEFAULT_TIMEOUT=20 GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/elements_netsim.registry MALLOC_PERTURB_=119 GST_PLUGIN_SYSTEM_PATH_1_0='' LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/gst-libs/gst/basecamerabinsrc: /<>/obj-x86_64-linux-gnu/gst-libs/gst/uridownloader: /<>/obj-x86_64-linux-gnu/gst-libs/gst/interfaces: /usr/lib/libeatmydata /<>/obj-x86_64-linux-gnu/tests/check/elements_netsim --- stdout --- Running suite(s): netsim Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Stack trace: gst_debug_get_stack_trace (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b3e6db) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8961a9f) g_logv (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddc0c) g_log (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f89ddebf) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4a072) ?? (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b4c2c2) gst_pad_push (/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0.2205.0:0x7f94f8b53b44) ?? (/usr/lib/x86_64-linux-gnu/libgstcheck-1.0.so.0.2205.0:0x7f94f8967b62) ?? (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.0:0x7f94f8a029dd) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f87fa3e8) ?? (/usr/lib/x86_64-linux-gnu/libc.so.6:0x7f94f887aa28) 0%: Checks: 2, Failures: 2, Errors: 0 ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event ../libs/gst/check/gstcheck.c:286:F:general:netsim_stress_delayed:0: Unexpected critical/warning: ../gst/gstpad.c:4427:gst_pad_chain_data_unchecked: Got data flow before stream-start event Check suite netsim ran in 0.240s (tests failed: 2) ** Affects: gst-plugins-bad Importance: Unknown Status: Unknown ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs mantic ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #3000 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3000 ** Also affects: gst-plugins-bad via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3000 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2037323 Title: gst-plugins-bad1.0 fails to build: netsim test failing Status in gst-plugins-bad: Unknown Status in gst-plugins-bad1.0 package in Ubuntu: Triaged Bug description: gst-plugin-bad1.0's elements_netsim build test began failing after July 6 (when 1.22.4 was uploaded) but before August 15. This is a regression caused by a change in one of its build dependencies. === 91/109 === test: elements_netsim start time: 12:04:11 duration: 1.31s result: exit status 2 command:
[Touch-packages] [Bug 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
OK, thanks for looking at this issue!
I am already looking forward to Ubuntu 24.04 :>.
--
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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
@Daniel: Maybe I answered a bit hasty. I see this issue over and over again without any Nvidia driver. But I do have a Nvidia card, if that may be related. Not sure about the root cause of this bug. We know that it happens with the Ubuntu font and that that font was changed in the mantic cycle. But is the font change to blame, or is it maybe some inability in Gtk/Pango/whatever to deal with a font change smoothly? Or is it a limitation in fontconfig? Would the issue show up if some other font in use had been changed, even if it was not set via the font-name dconf value? Those are thoughts in my head. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
The issue is that those flags are pretty new, so v253 does not make use
of them. Current upstream systemd will try to use them if available[1].
Since this is just a warning from the kernel[2], and since we are late
in the Mantic cycle, I do not think there is justification to fix this
in systemd.
[1] https://github.com/systemd/systemd/blob/main/src/basic/memfd-util.c#L23-L36
[2] https://elixir.bootlin.com/linux/v6.5.5/source/mm/memfd.c#L318
** Changed in: systemd (Ubuntu)
Importance: Low => Wishlist
** 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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034656] Re: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time)
Unfortunately as far as trusty is concerned, it uses the legacy cron job and not the new systemd timers which spread the load over 24h, so it only is able to randomize over 30 minutes starting from the cron.daily run time (6am IIRC, probably UTC as everyone runs servers in UTC). I don't think anyone remembers why we didn't backport the switch to timers to it (did we not have [working] timers in 18.04), but also they shouldn't then see more load than the archive mirror, this shouldn't be a new problem in that sense. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time) Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
>Is this affecting your system in any way?
No.
>Or are you just reporting the fact that a message is logged?
That is the problem. A system with messy logs is harder to debug.
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
New
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+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 2034656] Re: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time)
@esj : Hi ! Thanks for chiming in. I think doing APT activities once a day is fine indeed. However, I think even if we had ESM archives in cloud mirrors, having a large amount of clients do their updates all at the same time would lead to said cloud mirrors being overwhelmed, unless we throw an absurd amount of resources at the problem - resources that wouldn't be used during the rest of the day. I think we do need both : spread updates throughout the day (this bug), and have ESM archives in cloud mirrors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time) Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2034656] Re: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time)
** Summary changed: - Update Ubuntu ESM cache only once daily? + ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: ESM archive getting DoSed with legitimate traffic every day at 06:25 (cron.daily time) Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Hi folks, I landed here while investigating issues running Ubuntu 22.04 (Jammy) on WSL2. I tested the proposed version and have mixed results. NetworkManager is not installed. systemd-network is enabled, but I don't know if WSL actually uses it. Like 249.11-0ubuntu3.10, 249.11-0ubuntu3.11 also times out for me when run as follows: mosullivan@MITCH-PC:~$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link 2 Found link 1 lo: link is ignored eth0: link is not managed by networkd (yet?). Timeout occurred while waiting for network connectivity. However, on 249.11-0ubuntu3.11, but not on 249.11-0ubuntu3.10, I can use the --ignore option and the program exits immediately and successfully when appropriate: mosullivan@MITCH-PC:~$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --ignore=eth0 --timeout=10 Found link 2 Found link 1 lo: link is ignored eth0: link is ignored This is probably indicative that Microsoft ought to tweak their integration but I thought I'd share anyway. I'm fine for now to override ExecStart (i.e. to include --ignore) so that things work smoothly again using the latest version. Kind regards, Mitchell O'Sullivan -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
Is this affecting your system in any way? Or are you just reporting the
fact that a message is logged?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on Razer Blade 16. Please help -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot
** Description changed: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. + + + [ Impact ] + * An explanation of the effects of the bug on users and + * justification for backporting the fix to the stable release. + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [ Test Plan ] + * detailed instructions how to reproduce the bug + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + * if other testing is appropriate to perform before landing this update, +this should also be described here. + + [ Where problems could occur ] + * Think about what the upload changes in the software. Imagine the change is +wrong or breaks something else: how would this show up? + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + * This must '''never''' be "None" or "Low", or entirely an argument as to why +your upload is low risk. + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [ Other Info ] + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- 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/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [ Test Plan ] * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. * if other testing is appropriate to perform before landing this update, this should also be described here. [ Where problems could occur ] * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must '''never''' be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the SRU team that the risks have been considered, and provides guidance to
[Touch-packages] [Bug 2037186] Re: Update cairo to 1.18.0
** Description changed: Impact -- Ubuntu 23.10 includes cairo 1.17.8, the final pre-release snapshot of what eventually became the stable 1.18.0. It would be nicer to include the stable release than a beta release. + + Debian's autopkgtests completed successfully. News https://cairographics.org/news/cairo-1.18.0/ Detailed changelog -- https://gitlab.freedesktop.org/cairo/cairo/-/compare/1.17.8...1.18.0 Why This Didn't Land Sooner -- I was told by cairo upstream developers to expect cairo 1.18.0 in August 2023. It was released September 23 instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/2037186 Title: Update cairo to 1.18.0 Status in cairo package in Ubuntu: Confirmed Bug description: Impact -- Ubuntu 23.10 includes cairo 1.17.8, the final pre-release snapshot of what eventually became the stable 1.18.0. It would be nicer to include the stable release than a beta release. Debian's autopkgtests completed successfully. News https://cairographics.org/news/cairo-1.18.0/ Detailed changelog -- https://gitlab.freedesktop.org/cairo/cairo/-/compare/1.17.8...1.18.0 Why This Didn't Land Sooner -- I was told by cairo upstream developers to expect cairo 1.18.0 in August 2023. It was released September 23 instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2037186/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot
** Tags added: foundations-todo ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 1885388] Re: E: Failed to fetch store Hash Sum mismatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: Confirmed Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
*** This bug is a duplicate of bug 518056 *** https://bugs.launchpad.net/bugs/518056 I was on 18.04 and that was not an issue for me. Using US intl. alt. keyboard I could always get ç (cedilha). Now that I've upgrade to 23.04, this problem came back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/228077 Title: libgtk2 immodules has cedilla disabled in en locales Status in gnome-control-center: Confirmed Status in GTK+: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+2.0 package in Ubuntu: Invalid Status in gnome-control-center package in Fedora: Won't Fix Bug description: Binary package hint: libgtk2.0-0 philsf@philsf-laptop:~$ lsb_release -rd Description: Ubuntu 8.04 Release: 8.04 philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0 libgtk2.0-0: Installed: 2.12.9-3ubuntu3 One can't use dead keys to input a c+cedilla in en_US (probably other en_* locales). I had this on Gutsy. Now in Hardy, I thought I should report, since it's annoying, and the fix is documented. Steps to reproduce: - enable deadkeys - Open gnome-terminal (or firefox) and enter ' + c What you should get: ç What you do get: ć Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ): Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and include ":en" in the cedilla line 6c6 < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa" --- > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/228077/+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 2034656] Re: Update Ubuntu ESM cache only once daily?
i do think somehow randomizing the actual times so not all machines ping at the same time would be good i would not be in favor of greatly reducing the frequency though the real solution, however, is ESM archives in cloud mirrors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: Update Ubuntu ESM cache only once daily? Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => High ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Tags added: systemd-sru-next -- 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/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2037186] Re: Update cairo to 1.18.0
cairo 1.17.8 has an unfortunate regression reported at
https://gitlab.freedesktop.org/cairo/cairo/-/issues/806 ("Font Family corrupted
string on export").
Hopefully, Ubuntu 23.10 can have this bug fixed by the time of its official
release.
** Bug watch added: gitlab.freedesktop.org/cairo/cairo/-/issues #806
https://gitlab.freedesktop.org/cairo/cairo/-/issues/806
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2037186
Title:
Update cairo to 1.18.0
Status in cairo package in Ubuntu:
Confirmed
Bug description:
Impact
--
Ubuntu 23.10 includes cairo 1.17.8, the final pre-release snapshot of what
eventually became the stable 1.18.0. It would be nicer to include the stable
release than a beta release.
News
https://cairographics.org/news/cairo-1.18.0/
Detailed changelog
--
https://gitlab.freedesktop.org/cairo/cairo/-/compare/1.17.8...1.18.0
Why This Didn't Land Sooner
--
I was told by cairo upstream developers to expect cairo 1.18.0 in August
2023. It was released September 23 instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2037186/+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 2034656] Re: Update Ubuntu ESM cache only once daily?
@juliank : would you know how a trusty machine does its daily apt activities (including ESM) ? Are the downloads spread out during the day, or is everything done in cron.daily ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: Update Ubuntu ESM cache only once daily? Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Description changed: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: - dhcpd-10.0.2 starting + dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot - dhcpd exited + dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. - Executing dhcpd now correctly gets IP addresses, but I don't know how to - continue the boot from there. + Executing dhcpcd now correctly gets IP addresses, but I don't know how + to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2034656] Re: Update Ubuntu ESM cache only once daily?
Also @orndorffgrant "Do we have control over any of the offending machines?" sadly no... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: Update Ubuntu ESM cache only once daily? Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2034656] Re: Update Ubuntu ESM cache only once daily?
Thanks both for your updates, I'll try to see if someone at Azure can help. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2034656 Title: Update Ubuntu ESM cache only once daily? Status in cloud-images: New Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Hi, We're seeing frequent alerts on the Ubuntu ESM archive servers due to surges in requests. On two systems, I'm seeing this: | Sep 6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches. | Sep 7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM caches... | Sep 7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches. On another: | Sep 6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. | Sep 7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM caches... | Sep 7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM caches. This is all from `/usr/lib/systemd/system/esm-cache.service` which calls `/usr/lib/ubuntu-advantage/esm_cache.py`. Can we please have this run less frequent? Perhaps only once daily which aligns with APT and apt-daily-upgrade.service / unattended- upgrades? Perhaps check existence of a file and run if not, then age of that same file and only run if it's older than a day? I think, from what I can see, this may be triggered from /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm- hook.conf? See also LP:1554848 which was for APT. On Trusty and Xenial clients we only seem to update daily, but the problem is worse as it's a cron.daily job, so all clients fire simultaneously - could we get this changed to a cron.d job with a randomised firing time instead? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2037281] [NEW] Shutdown when triggering daemon-reload eary in boot
Public bug reported: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037281 Title: Shutdown when triggering daemon-reload eary in boot Status in systemd package in Ubuntu: New Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2027858] Re: [nouveau] Corrupt text rendering in Blender
Fixed in mesa master, 23.1.7 and 23.2.0-rc4. Mantic currently has 23.1.7, closing. ** Changed in: mesa (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2027858 Title: [nouveau] Corrupt text rendering in Blender Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: I use the nouveau graphic driver: in general, it works well, but when using Blender, recently, it shows garbled text. I have already reported the bug on Blender, they state it's an issue of the graphic driver I don't use Blender often, but about a month ago I remember it worked correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Sat Jul 15 17:27:41 2023 DistUpgraded: 2022-08-11 20:30:54,046 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:830f] InstallationDate: Installed on 2020-10-02 (1015 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-11 (337 days ago) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2027858/+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 384001] Re: ssh forwarded glx returns "Error: couldn't find RGB GLX visual or fbconfig" against older servers
** Project changed: xorg-server => mesa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/384001 Title: ssh forwarded glx returns "Error: couldn't find RGB GLX visual or fbconfig" against older servers Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading to Jaunty 9.04 from Hardy remote glx rendering (over ssh or just network) against older servers is not working anymore. Currently i've only tested against two X servers: X-Win32 Mac OSX Leopard X11 Server Both of which works fine on the same machine when rebooted into Hardy (still available on another partition) glxinfo outputs: > name of display: localhost:10.0 > Xlib: extension "Generic Event Extension" missing on display "localhost:10.0". > Error: couldn't find RGB GLX visual or fbconfig xdpyinfo outputs that i have SGI-GLX and GLX extension, will attach the full output later. I suspect that newer glx client side libs must be needing something not provided by the older servers. Let me know what other types of logs that are of interest [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03) Subsystem: AOPEN Inc. Device [a0a0:062d] --- Architecture: i386 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory MachineType: AOpen i965GMx-IF Package: mesa (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=0f9b4a48-eec1-46c2-a350-078a0eed0034 ro quiet splash ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-22-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video dmi.bios.date: 12/11/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: i965GMx-IF dmi.board.vendor: AOpen dmi.board.version: 558EX10I690 dmi.chassis.type: 3 dmi.chassis.vendor: AOpen dmi.chassis.version: i965GMx-IF dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/11/2007:svnAOpen:pni965GMx-IF:pvrAO1JW:rvnAOpen:rni965GMx-IF:rvr558EX10I690:cvnAOpen:ct3:cvri965GMx-IF: dmi.product.name: i965GMx-IF dmi.product.version: AO1JW dmi.sys.vendor: AOpen glxinfo: Error: couldn't find RGB GLX visual or fbconfig name of display: localhost:10.0 system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/384001/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Tested 249.11-0ubuntu3.11 on Ubuntu Server 22.04 (Jammy) and now I have no delay on boot. Also the following command now returns immediately: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link 9 Found link 8 Found link 7 Found link 6 Found link 5 Found link 4 Found link 3 Found link 2 Found link 1 enp4s0: link is ignored eno1: link is ignored enp3s0: link is ignored enp5s0: link is ignored lo: link is ignored eno2: link is ignored enp7s0: link is ignored enp2s0: link is ignored enp6s0: link is ignored Thanks! -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
On 2023-09-25 03:15, Daniel van Vugt wrote: > is it specific to Nvidia desktops like bug 1876632? No. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Confirmed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
