[Touch-packages] [Bug 2081110] Re: FTBFS for oracular 2:4.35-1.1ubuntu1
** Also affects: nspr (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: nspr (Ubuntu Plucky) Importance: Undecided Assignee: Lena Voytek (lvoytek) Status: In Progress ** Description changed: [Impact] Builds of nspr fail in oracular due to GCC-14 standards, which raises issues due to incompatible pointer types and function calls. This should be backported to Oracular to fix the pr testsuite and simplify future package rebuilds. The issue is fixed by a reformatted upstream commit which fixes the type conversions and function calls. [Test Plan] Since this is an FTBFS, the bug can be reproduced by attempting to build in oracular. A successful build should show that the bug is fixed, as it both compiles testfile.c and runs the test suite that uses it during runtime with: cd nspr/pr/tests && grep -v '^\(fdcach\|gethost\|getproto\|nblayer\|peek\|socket\|vercheck\)$' ./runtests.sh | sh - /<>/nspr/dist [Where problems could occur] If problems were to occur, they would arise when running the nspr/pr test suite. This patch modifies testfile.c, which is used by the majority of tests to read and write data as they run. Due to upstream reformatting the file prior to the commit that fixes the issue, the patch had to be cleaned up to apply against the previous format. This could cause changes to logic if the patch were mis-applied. [Other Info] - - The fix should be added to Oracular as a "zero-day" SRU. + + Adding to Plucky once the archive is available, then backporting to + oracular [Original Description] nspr currently fails to build in oracular with the following: testfile.c:126:41: error: passing argument 3 of ‘pthread_create’ from incompatible pointer type This should be fixed upstream with https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1 Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1904395 Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075322 ** Changed in: nspr (Ubuntu Oracular) Status: New => In Progress ** Changed in: nspr (Ubuntu Oracular) Assignee: (unassigned) => Lena Voytek (lvoytek) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2081110 Title: FTBFS for oracular 2:4.35-1.1ubuntu1 Status in NSPR: Fix Released Status in nspr package in Ubuntu: In Progress Status in nspr source package in Oracular: In Progress Status in nspr source package in Plucky: In Progress Status in nspr package in Debian: Confirmed Bug description: [Impact] Builds of nspr fail in oracular due to GCC-14 standards, which raises issues due to incompatible pointer types and function calls. This should be backported to Oracular to fix the pr testsuite and simplify future package rebuilds. The issue is fixed by a reformatted upstream commit which fixes the type conversions and function calls. [Test Plan] Since this is an FTBFS, the bug can be reproduced by attempting to build in oracular. A successful build should show that the bug is fixed, as it both compiles testfile.c and runs the test suite that uses it during runtime with: cd nspr/pr/tests && grep -v '^\(fdcach\|gethost\|getproto\|nblayer\|peek\|socket\|vercheck\)$' ./runtests.sh | sh - /<>/nspr/dist [Where problems could occur] If problems were to occur, they would arise when running the nspr/pr test suite. This patch modifies testfile.c, which is used by the majority of tests to read and write data as they run. Due to upstream reformatting the file prior to the commit that fixes the issue, the patch had to be cleaned up to apply against the previous format. This could cause changes to logic if the patch were mis-applied. [Other Info] Adding to Plucky once the archive is available, then backporting to oracular [Original Description] nspr currently fails to build in oracular with the following: testfile.c:126:41: error: passing argument 3 of ‘pthread_create’ from incompatible pointer type This should be fixed upstream with https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1 Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1904395 Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075322 To manage notifications about this bug go to: https://bugs.launchpad.net/nspr/+bug/2081110/+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 2059734] Re: Tar fails to extract archives that include folders with certain permissions on armhf
Dropping ubuntu-sponsors, please re-subscribe when there's a new patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2059734 Title: Tar fails to extract archives that include folders with certain permissions on armhf Status in libseccomp package in Ubuntu: New Status in tar package in Ubuntu: Invalid Status in libseccomp source package in Jammy: In Progress Status in libseccomp source package in Mantic: Won't Fix Status in tar source package in Mantic: Won't Fix Status in libseccomp source package in Noble: Invalid Status in tar source package in Noble: Invalid Bug description: Thank you @loganbussell-msft for the bug report! [Impact] Currently running containers using modern versions of glibc such as the one available in noble on older hosts causes permissions issues inside the container. This is due to newer versions of glibc expecting the fchmodat2 syscall to be available and to return ENOSYS in case it is not. However docker seccomp profile defaults to returning EPERM for all non defined syscalls and writing an entry for fchmodat2 in the docker seccomp profile to return ENOSYS does not work on systems where libseccomp does not have support for fchmodat2. Running armhf noble docker containers on arm64 jammy hosts has been seen to exhibit this behavior and a patch to libseccomp for jammy is required to fix the issue. Other architectures may also be affected by this issue that such as ppc64le as reported by @mark-elvers. I have backported a fix from upstream that adds the missing syscalls to libseccomp and verified it on an ampere arm machine as well as on a raspberry pi 4 [Test Plan] 1- On an ARM 64 machine install the latest version of docker on a jammy host by following the official docker documentation. [https://docs.docker.com/engine/install/ubuntu/] 2- Create an armhf noble docker container: $ docker run --rm -it --platform linux/arm/v7 --entrypoint bash ubuntu.azurecr.io/ubuntu:noble 3- inside the docker container execute the following commands to create a new tar file and then extract it: mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 4- you will see the following errors: tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors 5- When libseccomp is patched the command will run with no permission issues [Where problems could occur] * the issue might still occur on other platforms * if using an older version of docker the issue will still occur [Original Description] When running Ubuntu Noble in an arm32 Docker container, on certain hosts (Azure VM CI agents), tar fails to extract certain archives that include folders with specific permissions set. Here's a concise repro. The error occurs in when building the Dockerfile. I can only get this to work on Azure VMs, but can't find out why. ```Dockerfile FROM ubuntu.azurecr.io/ubuntu:noble # Create the problematic archive RUN mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . # Extracting it gives an error RUN mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 ``` What I expected to happen: The test.tar.gz archive should be successfully extracted to the /test2 directory. What happened instead: Tar throws the following error: ``` tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors ``` The Ubuntu container is running as root so there shouldn't be any permission errors. Since this is running in a container, I observed this happening on the following kernel: `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024` As well as `Linux 6.5.0-1017-azure #17~22.04.1-Ubuntu SMP Sat Mar 9 10:04:07 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux` I was not able to reproduce it using Ubuntu 22.04 Jammy (ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above. Additionally I was not able to reproduce this on the kernel `Linux cb0507859b24 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`, which is running on my work machine, using Docker qemu emulation for the arm32 image. Ubuntu version: Ubuntu Noble Numbat (development branch) 24.04 (from ub
[Touch-packages] [Bug 2059734] Re: Tar fails to extract archives that include folders with certain permissions on armhf
I think it's short-sighted to only include arm and ppc here given that the upstream solution sets the syscall number for all archs, and the syscall is defined for all archs even if glibc happens to not be relying on this syscall on archs other than ppc and arm. Please adjust the patch to match upstream. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/2059734 Title: Tar fails to extract archives that include folders with certain permissions on armhf Status in libseccomp package in Ubuntu: New Status in tar package in Ubuntu: Invalid Status in libseccomp source package in Jammy: In Progress Status in libseccomp source package in Mantic: Won't Fix Status in tar source package in Mantic: Won't Fix Status in libseccomp source package in Noble: Invalid Status in tar source package in Noble: Invalid Bug description: Thank you @loganbussell-msft for the bug report! [Impact] Currently running containers using modern versions of glibc such as the one available in noble on older hosts causes permissions issues inside the container. This is due to newer versions of glibc expecting the fchmodat2 syscall to be available and to return ENOSYS in case it is not. However docker seccomp profile defaults to returning EPERM for all non defined syscalls and writing an entry for fchmodat2 in the docker seccomp profile to return ENOSYS does not work on systems where libseccomp does not have support for fchmodat2. Running armhf noble docker containers on arm64 jammy hosts has been seen to exhibit this behavior and a patch to libseccomp for jammy is required to fix the issue. Other architectures may also be affected by this issue that such as ppc64le as reported by @mark-elvers. I have backported a fix from upstream that adds the missing syscalls to libseccomp and verified it on an ampere arm machine as well as on a raspberry pi 4 [Test Plan] 1- On an ARM 64 machine install the latest version of docker on a jammy host by following the official docker documentation. [https://docs.docker.com/engine/install/ubuntu/] 2- Create an armhf noble docker container: $ docker run --rm -it --platform linux/arm/v7 --entrypoint bash ubuntu.azurecr.io/ubuntu:noble 3- inside the docker container execute the following commands to create a new tar file and then extract it: mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 4- you will see the following errors: tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors 5- When libseccomp is patched the command will run with no permission issues [Where problems could occur] * the issue might still occur on other platforms * if using an older version of docker the issue will still occur [Original Description] When running Ubuntu Noble in an arm32 Docker container, on certain hosts (Azure VM CI agents), tar fails to extract certain archives that include folders with specific permissions set. Here's a concise repro. The error occurs in when building the Dockerfile. I can only get this to work on Azure VMs, but can't find out why. ```Dockerfile FROM ubuntu.azurecr.io/ubuntu:noble # Create the problematic archive RUN mkdir /test \ && chmod 775 /test \ && cd /test \ && mkdir 775 \ && chmod 775 775 \ && touch 775/test.txt \ && chmod 644 775/test.txt \ && tar -czvf /test.tar.gz . # Extracting it gives an error RUN mkdir -p /test2 \ && tar -tzvf /test.tar.gz \ && tar -oxzf /test.tar.gz -C /test2 ``` What I expected to happen: The test.tar.gz archive should be successfully extracted to the /test2 directory. What happened instead: Tar throws the following error: ``` tar: ./775: Cannot change mode to rwxrwxr-x: Operation not permitted tar: Exiting with failure status due to previous errors ``` The Ubuntu container is running as root so there shouldn't be any permission errors. Since this is running in a container, I observed this happening on the following kernel: `Linux version 5.15.148.2-2.cm2 (root@CBL-Mariner) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Feb 23 23:38:33 UTC 2024` As well as `Linux 6.5.0-1017-azure #17~22.04.1-Ubuntu SMP Sat Mar 9 10:04:07 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux` I was not able to reproduce it using Ubuntu 22.04 Jammy (ubuntu.azurecr.io/ubuntu:jammy), using the same kernel as above. Additionally I was not able to reproduce this on the kernel `Linux cb0507859b24 5.15.146.1-microsoft-stan
[Touch-packages] [Bug 2081110] Re: FTBFS for oracular 2:4.35-1.1ubuntu1
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/nspr/+git/nspr/+merge/475533 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2081110 Title: FTBFS for oracular 2:4.35-1.1ubuntu1 Status in NSPR: Fix Released Status in nspr package in Ubuntu: In Progress Status in nspr source package in Oracular: In Progress Status in nspr source package in Plucky: In Progress Status in nspr package in Debian: Confirmed Bug description: [Impact] Builds of nspr fail in oracular due to GCC-14 standards, which raises issues due to incompatible pointer types and function calls. This should be backported to Oracular to fix the pr testsuite and simplify future package rebuilds. The issue is fixed by a reformatted upstream commit which fixes the type conversions and function calls. [Test Plan] Since this is an FTBFS, the bug can be reproduced by attempting to build in oracular. A successful build should show that the bug is fixed, as it both compiles testfile.c and runs the test suite that uses it during runtime with: cd nspr/pr/tests && grep -v '^\(fdcach\|gethost\|getproto\|nblayer\|peek\|socket\|vercheck\)$' ./runtests.sh | sh - /<>/nspr/dist [Where problems could occur] If problems were to occur, they would arise when running the nspr/pr test suite. This patch modifies testfile.c, which is used by the majority of tests to read and write data as they run. Due to upstream reformatting the file prior to the commit that fixes the issue, the patch had to be cleaned up to apply against the previous format. This could cause changes to logic if the patch were mis-applied. [Other Info] Adding to Plucky once the archive is available, then backporting to oracular [Original Description] nspr currently fails to build in oracular with the following: testfile.c:126:41: error: passing argument 3 of ‘pthread_create’ from incompatible pointer type This should be fixed upstream with https://hg.mozilla.org/projects/nspr/rev/e178d3d9b47b2479f22f208d6225eda81918dae1 Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1904395 Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075322 To manage notifications about this bug go to: https://bugs.launchpad.net/nspr/+bug/2081110/+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 2085144] [NEW] the gjs application permanently consumes more than 100% of a processor
Public bug reported: Hello. I just upgraded from version 24.04.1 to version 24.10. Since I connected, I constantly hear the noise of the fan. Using the top command, I notice that the gjs application consumes more than 100% of a processor. This doesn't seem normal to me and I don't know what to look for to explain this behavior. If I kill the application, it automatically regenerates and has the same behavior. THANKS. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.10 Release:24.10 Codename: oracular a@p:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu oracular InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu oracular-updates InRelease Atteint :3 http://fr.archive.ubuntu.com/ubuntu oracular-backports InRelease Atteint :4 http://security.ubuntu.com/ubuntu oracular-security InRelease Tous les paquets sont à jour. Tâches: 320 total, 2 en cours, 318 en veille, 0 arrêté, 0 zombie %Cpu(s): 26,0 ut, 2,9 sy, 0,0 ni, 71,0 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 5815,2 total,175,8 libr, 2573,2 util, 3748,5 tamp/cache MiB Éch: 0,0 total, 0,0 libr, 0,0 util. 3242,0 dispo Mem PID UTIL. PR NIVIRTRESSHR S %CPU %MEMTEMPS+ COM. 4403 a 20 0 3203764 348396 43932 R 102,3 5,9 43:28.44 gjs 19664 a 20 0 1584276 167812 103900 S 8,6 2,8 0:18.41 gnome-text-edit 2732 a 20 0 4481976 325760 142840 S 4,0 5,5 2:03.18 gnome-shell 17 root 20 0 0 0 0 I 0,3 0,0 0:01.09 rcu_preempt 3764 a 20 0 561932 60444 44492 S 0,3 1,0 0:16.09 gnome-terminal- 18721 root 20 0 0 0 0 I 0,3 0,0 0:01.40 kworker/2:3-i915-unordered 19802 a 20 0 14828 5888 3712 R 0,3 0,1 0:00.09 top 1 root 20 0 25056 16544 10272 S 0,0 0,3 0:05.61 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.00 pool_workqueue_release 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_g 5 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_p 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-slub_ 7 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-netns 9 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:0H-events_highpri 12 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-mm_pe 13 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_kthread a@p:~$ ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2085144 Title: the gjs application permanently consumes more than 100% of a processor Status in ubuntu-keyring package in Ubuntu: New Bug description: Hello. I just upgraded from version 24.04.1 to version 24.10. Since I connected, I constantly hear the noise of the fan. Using the top command, I notice that the gjs application consumes more than 100% of a processor. This doesn't seem normal to me and I don't know what to look for to explain this behavior. If I kill the application, it automatically regenerates and has the same behavior. THANKS. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.10 Release: 24.10 Codename: oracular a@p:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu oracular InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu oracular-updates InRelease Atteint :3 http:
[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Thanks Matthew and Andreas! Very much appreciate getting the fix released for Noble, Jammy, and Focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Released Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2076084] Re: Additional drivers tab cause uncancellable operation that prevents the program from closing
Thank you for your help, Andreas, I do not think we will SRU that to older releases so all is on the right tracks. -- 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/2076084 Title: Additional drivers tab cause uncancellable operation that prevents the program from closing Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Oracular: New Status in software-properties source package in Plucky: In Progress Bug description: Start software-properties-gtk, switch to additional drivers tab. The program will start consuming 100% CPU for quite some time (many seconds or minutes depending on the machine). There is however no way to cancel the operation other than killing software-properties. Trying to close the window or clicking Close button hangs. Test plans -- 1. Start software-properties-gtk 1.1. Go to additional drivers tab. 1.2. Click close at the south-east corner or close the window via your window manager. Expected. Window closes immediately. 4. Start software-properties-gtk 4.1. Go to additional drivers tab and wait. Expected: The viewport will at the end say that either no drivers are available or show a list of drivers such as in the drivers-list.png attachment. The cancel/retry buttons are gone in the latter case. 2. Start software-properties-gtk and 'top' in a terminal 2.1. Go to additional drivers tab. Expected: The 'python3' command starts consuming 100% CPU. 2.2. Click cancel. Expected: The aforementioned process is no longer hogging the CPU, indicating that the driver scan really stopped. The button is now retry, clickable. 2.3. Click retry. Expected: The 'python3' command starts consuming 100% CPU. The button is now cancel. 3. Start software-properties-gtk and 'top' in a terminal 3.1. Go to additional drivers tab. 3.2. Get the PID of the 'python3' process consuming 100% CPU and kill it with kill -29 PID Expected: The viewport reports the error. Retry is clickable. 5. Start software-properties-gtk 5.1. Introduce a unconditional exception in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py:system_device_drivers, e.g.: ---> --- /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py +++ /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py @@ -866,4 +866,5 @@ def system_device_drivers(apt_cache=None, sys_path=None, freeonly=False): +print(fooo) '''Get by-device driver packages that are available for the system. <--- 5.2. Go to additional drivers tab. Expected: "An error occurred while searching for drivers."; In the terminal, the backtrace is shown: ---> Traceback (most recent call last): File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1456, in detect_drivers raise(self.p.exception) Exception: Traceback (most recent call last): File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 121, in run multiprocessing.Process.run(self) File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1437, in wrapper_system_device_drivers devices = detect.system_device_drivers(cache) ^^^ File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 919, in system_device_drivers print(fo) ^^ NameError: name 'fo' is not defined <--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2076084/+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 2085086] [NEW] Update dfx-mgr package to xlnx_rel_v2024.2
Public bug reported: This request is created to inform team to update dfx-mgr package to release xlnx_rel_v2024.2 https://github.com/Xilinx/dfx-mgr/tree/xlnx_rel_v2024.2 ** Affects: dfx-mgr (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => dfx-mgr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2085086 Title: Update dfx-mgr package to xlnx_rel_v2024.2 Status in dfx-mgr package in Ubuntu: New Bug description: This request is created to inform team to update dfx-mgr package to release xlnx_rel_v2024.2 https://github.com/Xilinx/dfx-mgr/tree/xlnx_rel_v2024.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dfx-mgr/+bug/2085086/+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 2066157] Re: cpio 2.13+dfsg-2ubuntu0.4 breaks zfs build (alien command fails)
Adding to my comment above: cpio from Ubuntu 24.04.1 works
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cpio in Ubuntu.
https://bugs.launchpad.net/bugs/2066157
Title:
cpio 2.13+dfsg-2ubuntu0.4 breaks zfs build (alien command fails)
Status in cpio package in Ubuntu:
Confirmed
Bug description:
I'm not sure where the true fault is but the problem only happens
after updating the cpio package from 2.13+dfsg-2ubuntu0.3 to
2.13+dfsg-2ubuntu0.4. The zfs build creates .rpms which are then
converted to .debs. The failure message is:
```
name=zfs; \
version=2.1.15-1; \
arch=`rpm -qp ${name}-kmod-${version}.src.rpm --qf %{arch} | tail -1`; \
debarch=`dpkg --print-architecture`; \
pkg1=kmod-${name}*${version}.${arch}.rpm; \
fakeroot alien --bump=0 --scripts --to-deb --target=$debarch $pkg1 || exit 1;
\
rm -f $pkg1
kmod-zfs-5.15.0-107-generic_2.1.15-1_amd64.deb generated
kmod-zfs-devel_2.1.15-1_amd64.deb generated
Unpacking of 'kmod-zfs-devel-5.15.0-107-generic-2.1.15-1.x86_64.rpm' failed
at /usr/share/perl5/Alien/Package/Rpm.pm line 168, line 315.
```
Looking at the alien source the command that fails is:
```
$this->do("rpm2cpio '".$this->filename."' | (cd $workdir; $decomp
cpio --extract --make-directories --no-absolute-filenames
--preserve-modification-time) 2>&1")
or die "Unpacking of '".$this->filename."' failed";
```
Examining the content of the .rpm:
```
# rpm -qlv kmod-zfs-devel-5.4.0-174-lowlatency-2.1.15-1.x86_64.rpm
lrwxrwxrwx1 rootroot 34 May 20 09:14
/usr/src/spl-2.1.15/5.4.0-174-lowlatency -> ../zfs-2.1.15/5.4.0-174-lowlatency
drwxr-xr-x2 rootroot0 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency
-rw-r--r--1 rootroot 164782 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency/Module.symvers
lrwxrwxrwx1 rootroot 11 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl.release -> zfs.release
lrwxrwxrwx1 rootroot 12 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl_config.h -> zfs_config.h
-rw-r--r--1 rootroot9 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency/zfs.release
-rw-r--r--1 rootroot28937 May 20 09:14
/usr/src/zfs-2.1.15/5.4.0-174-lowlatency/zfs_config.h
```
Changing the command being executed for testing purposes:
```
# apt-cache policy cpio; rm -rf /tmp/x; mkdir /tmp/x ; rpm2cpio
kmod-zfs-devel-5.4.0-174-lowlatency-2.1.15-1.x86_64.rpm | (cd /tmp/x; cpio -v
--extract --make-directories --no-absolute-filenames
--preserve-modification-time) ; echo $?
cpio:
Installed: 2.13+dfsg-2ubuntu0.3
Candidate: 2.13+dfsg-2ubuntu0.4
Version table:
2.13+dfsg-2ubuntu0.4 500
500
https://apt-mirror-00.example.com/apt/2024-05-19/archive.ubuntu.com/ubuntu
focal-updates/main amd64 Packages
500
https://apt-mirror-00.example.com/apt/2024-05-19/security.ubuntu.com/ubuntu
focal-security/main amd64 Packages
*** 2.13+dfsg-2ubuntu0.3 100
100 /var/lib/dpkg/status
2.13+dfsg-2 500
500
https://apt-mirror-00.example.com/apt/2024-05-19/archive.ubuntu.com/ubuntu
focal/main amd64 Packages
./usr/src/spl-2.1.15/5.4.0-174-lowlatency
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/Module.symvers
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl.release
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl_config.h
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/zfs.release
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/zfs_config.h
381 blocks
0
```
vs
```
# apt-cache policy cpio; rm -rf /tmp/x; mkdir /tmp/x ; rpm2cpio
kmod-zfs-devel-5.4.0-174-lowlatency-2.1.15-1.x86_64.rpm | (cd /tmp/x; cpio -v
--extract --make-directories --no-absolute-filenames
--preserve-modification-time) ; echo $?
cpio:
Installed: 2.13+dfsg-2ubuntu0.4
Candidate: 2.13+dfsg-2ubuntu0.4
Version table:
*** 2.13+dfsg-2ubuntu0.4 500
500
https://apt-mirror-00.example.com/apt/2024-05-19/archive.ubuntu.com/ubuntu
focal-updates/main amd64 Packages
500
https://apt-mirror-00.example.com/apt/2024-05-19/security.ubuntu.com/ubuntu
focal-security/main amd64 Packages
100 /var/lib/dpkg/status
2.13+dfsg-2 500
500
https://apt-mirror-00.example.com/apt/2024-05-19/archive.ubuntu.com/ubuntu
focal/main amd64 Packages
cpio: ./usr/src/spl-2.1.15/5.4.0-174-lowlatency: Cannot open: No such file or
directory
./usr/src/spl-2.1.15/5.4.0-174-lowlatency
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/Module.symvers
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl.release
./usr/src/zfs-2.1.15/5.4.0-174-lowlatency/spl_config.h
./usr/src/zfs-2.1.15
[Touch-packages] [Bug 2073628] Re: imjournal module works with rsyslog package of ubuntu 22.04 but not with ubuntu 24.04
Thanks, I'll add it to my batch of fixes for the upcoming stable release update (SRU). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2073628 Title: imjournal module works with rsyslog package of ubuntu 22.04 but not with ubuntu 24.04 Status in rsyslog package in Ubuntu: Confirmed Status in rsyslog source package in Noble: Confirmed Status in rsyslog source package in Oracular: Confirmed Bug description: imjournal module fails to create /var/spool/rsyslog/journal-state file in ubuntu 24.04, rsyslog version(8.2312.0) x86 and s390x both, but works well in ubuntu 22.04 , rsyslog version(8.2112.0) x86 and s390x *** Ubuntu 24.04 s390x lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 # apt-cache policy rsyslog rsyslog: Installed: 8.2312.0-3ubuntu9 Candidate: 8.2312.0-3ubuntu9 Version table: *** 8.2312.0-3ubuntu9 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main s390x Packages 100 /var/lib/dpkg/status Have below line in /etc/rsyslog.conf module(load="imjournal" fileCreateMode="0666" PersistStateInterval="999" StateFile="/var/spool/rsyslog/journal_state") ul 19 18:39:35 latest-logs systemd[1]: Starting rsyslog.service - System Logging Service... Jul 19 18:39:35 latest-logs rsyslogd[8647]: rsyslogd's groupid changed to 102 Jul 19 18:39:35 latest-logs rsyslogd[8647]: rsyslogd's userid changed to 102 Jul 19 18:39:35 latest-logs systemd[1]: Started rsyslog.service - System Logging Service. Jul 19 18:39:35 latest-logs rsyslogd[8647]: [origin software="rsyslogd" swVersion="8.2312.0" x-pid="8647" x-info="https://www.rsyslog.com";] start Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: No statefile exists, /var/spool/rsyslog/journal_state will be created (ignore if this is first run): No such file or directory > Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: Journal indicates no msgs when positioned at head. [v8.2312.0 try https://www.rsyslog.com/e/0 ] Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: journal files changed, reloading... [v8.2312.0 try https://www.rsyslog.com/e/0 ] Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: No statefile exists, /var/spool/rsyslog/journal_state will be created (ignore if this is first run): No such file or directory > Jul 19 18:39:35 latest-logs rsyslogd[8647]: imjournal: Journal indicates no msgs when positioned at head. [v8.2312.0 try https://www.rsyslog.com/e/0 ] lines 1-25/25 (END) FIle /var/spool/rsyslog/journal_state should have created and logs should have redirected to rsyslog server ** In Ubuntu 22.04 all is working as expected # lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 #apt-cache policy rsyslog rsyslog: Installed: 8.2112.0-2ubuntu2.2 Candidate: 8.2112.0-2ubuntu2.2 Version table: *** 8.2112.0-2ubuntu2.2 100 100 /var/lib/dpkg/status Use the same line as above in /etc/rsyslog.conf restart service. it did gave error about fileCreateMode which got ignored and proceeded to create the journal-state file and continued without any error Jul 19 18:44:37 systemd[1]: Starting System Logging Service... Jul 19 18:44:37 rsyslogd[13664]: error during parsing file /etc/rsyslog.conf, on or before line 16: parameter 'fileCreateMode' not known -- typo in co> Jul 19 18:44:37 systemd[1]: Started System Logging Service. Jul 19 18:44:37 rsyslogd[13664]: rsyslogd's groupid changed to 111 Jul 19 18:44:37 rsyslogd[13664]: rsyslogd's userid changed to 104 Jul 19 18:44:37 rsyslogd[13664]: [origin software="rsyslogd" swVersion="8.2112.0" x-pid="13664" x-info="https://www.rsyslog.com";] start Jul 19 18:44:37 rsyslogd[13664]: imjournal: journal files changed, reloading... [v8.2112.0 try https://www.rsyslog.com/e/0 ] /var/spool/rsyslog# ls journal_state * please help with this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2073628/+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 2085157] Re: mkinitramfs fails with copy_file binary ... not found
modified the hook-functions script (at line 252 ff) a bit to gather some
more details and yes:
$ grep -A 10 "copy_libgcc()" /usr/share/initramfs-tools/hook-functions
copy_libgcc() {
local libdir library
libdir="$1"
echo "1" "$1"
for library in "${libdir}"/libgcc_s.so.[1-9]; do
echo "2" "${libdir}"
copy_exec "${library}" || return
echo "3" "${library}"
done
}
$ sudo update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-6.11.0-8-generic
1 /lib/s390x-linux-gnu
2 /lib/s390x-linux-gnu
3 /lib/s390x-linux-gnu/libgcc_s.so.1
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
1
2
mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device for LD-IPL: dm-0.
Done.
$ ls -l /lib/s390x-linux-gnu/libgcc_s.so.1
-rw-r--r-- 1 root root 80176 Sep 8 15:50 /lib/s390x-linux-gnu/libgcc_s.so.1
$
** Summary changed:
- mkinitramfs fails with copy_file binary ... not found
+ mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found
** Tags added: rls-oo-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/2085157
Title:
mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found
Status in initramfs-tools package in Ubuntu:
New
Bug description:
I recently did an 24.10 install (on s390x, but I think this doesn't
matter) and was surprised that the system hangs during the post-
install reboot.
Investigation showed that this happens if the installer applies
updates, which is done by default, if there is proper network
connectivity and archive access.
In case of an install where I disabled the network, hence an offline
install was done, the installation incl. post-install reboot was
successful.
So I took such a successfully installed system (where no updates were
applied) and noticed that currently the available updates are:
$ apt list --upgradable
iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2]
linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from:
6.11.0-8.8]
linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from:
6.11.0-8.8]
linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from:
6.11.0-8.8]
So seemed to be kernel related, hence tried to update the kernel manually:
$ sudo apt install linux-image-generic/oracular-updates
Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for
'linux-image-generic'
Upgrading:
linux-generic linux-image-generic linux-tools-common
linux-headers-generic linux-libc-dev
Installing dependencies:
linux-headers-6.11.0-9 linux-modules-extra-6.11.0-9-generic
linux-headers-6.11.0-9-generic linux-tools-6.11.0-9
linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic
linux-modules-6.11.0-9-generic
Suggested packages:
fdutils linux-tools
Summary:
Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1
Download size: 65.3 MB
Space needed: 165 MB / 21.2 GB available
└─ in /boot: 43.1 MB / 1,876 MB available
Continue? [Y/n] Y
...
Setting up linux-generic (6.11.0-9.9) ...
Progress: [ 96%] [███▋ ]
Progress: [ 96%] [███▋ ]
Progress: [ 96%] [███▋ ]
update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ]
mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Preparing boot device for LD-IPL: dm-0.
Done.
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic
mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
/etc/kernel/postinst.d/zz-zipl:
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper 252:1
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Run /lib/s390-too
[Touch-packages] [Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
This bug was fixed in the package linux - 6.11.0-9.9 --- linux (6.11.0-9.9) oracular; urgency=medium * oracular/linux: 6.11.0-9.9 -proposed tracker (LP: #2084250) * re-enable Ubuntu FAN in the Noble kernel (LP: #2064508) - SAUCE: fan: add VXLAN implementation - SAUCE: fan: Fix NULL pointer dereference - SAUCE: fan: support vxlan strict length validation * update for V3 kernel bits and improved multiple fan slice support (LP: #1470091) // re-enable Ubuntu FAN in the Noble kernel (LP: #2064508) - SAUCE: fan: tunnel multiple mapping mode (v3) * Setting I/O scheduler to 'none' causes error in oracular (LP: #2083845) - block: Fix elv_iosched_local_module handling of "none" scheduler * Miscellaneous Ubuntu changes - [Config] Update toolchain versions -- Timo Aaltonen Mon, 14 Oct 2024 14:20:00 +0300 ** Changed in: linux (Ubuntu Oracular) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in iproute2 source package in Noble: Invalid Status in linux source package in Noble: Fix Released Status in iproute2 source package in Oracular: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] In LP: #2063298, we have opted to deprecate Ubuntu FAN support because of the maintenance overhead and the possibility of regressions / conflicts with the new networking eBPF APIs in kernels >= 6.8. However, we cannot disable this feature in HWE/backport kernels, so it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN at some point in the future. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2064508/+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 2052137] Re: bonded link goes down on reconfigure
I understand. Thank you for the time spent on that issue, we appreciate the effort. Have a nice day =) -- 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/2052137 Title: bonded link goes down on reconfigure Status in systemd: Fix Released Status in netplan.io package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Jammy: Invalid Status in systemd source package in Jammy: Confirmed Bug description: systemd-networkd brings down member interfaces of a bond when they get reconfigured Jan 31 15:43:46 unique-slug systemd-networkd[2430]: pn1: Bringing link down This has a result that a server has complete downtime for a few seconds, this has also been reported upstream https://github.com/systemd/systemd/issues/31165. A pull request has been opened to fix this https://github.com/systemd/systemd/pull/31172 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/2052137/+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 1972708] Re: Wired connection is off after resuming from sleep
Same bug on Intel I225-V wired adapter, but on different Ubuntu version.
It was working OK up to 24.04.4, the bug occured starting after 24.10 upgrade.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1972708
Title:
Wired connection is off after resuming from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When coming out of sleep mode, the wired connection is always off,
fresh installation of 22.04. It goes up easily by toggling it on from
the UI ("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0:
Suspend timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0:
Suspend notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4217] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4218] device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4445] dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
set default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4638] manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5495] manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5520] device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51 olivier-desktop ModemManager[753]: [base-manager]
couldn't che
[Touch-packages] [Bug 1972708] Re: Wired connection is off after resuming from sleep
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1972708
Title:
Wired connection is off after resuming from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When coming out of sleep mode, the wired connection is always off,
fresh installation of 22.04. It goes up easily by toggling it on from
the UI ("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0:
Suspend timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0:
Suspend notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4217] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4218] device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4445] dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
set default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4638] manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5495] manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5520] device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51 olivier-desktop ModemManager[753]: [base-manager]
couldn't check suppor
[Touch-packages] [Bug 2085127] [NEW] lxc/1:5.0.3-2ubuntu7 ADT test failure with linux/6.8.0-48.48
Public bug reported: This is a scripted bug report about ADT failures while running lxc tests for linux/6.8.0-48.48 on noble. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. The "exercise" test fails one of its sub-tests on s390x: 430s FAIL: lxc-tests: /usr/bin/lxc-test-usernic 430s --- 430s fatal: The user `usernic-user' does not exist. 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s xx2:2:veth1001_R0qf:128 430s xx3:3:veth1001_SVp8:129 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s FAIL: unable to create nic after destroying the old 430s FAIL 430s FAIL 430s --- 430s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec 430s PASS: lxc-tests: /usr/bin/lxc-test-utils 430s 430s SUMMARY: pass=54, fail=1, ignored=1 Not sure the "quota reached" is from trying to create the usernic-user or the interface. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/l/lxc/20241018_130950_b0c48@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: lxc (Ubuntu Noble) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: This is a scripted bug report about ADT failures while running lxc tests for linux/6.8.0-48.48 on noble. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. + The "exercise" test fails one of its sub-tests on s390x: + + 430s FAIL: lxc-tests: /usr/bin/lxc-test-usernic + 430s --- + 430s fatal: The user `usernic-user' does not exist. + 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached + 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached + 430s xx2:2:veth1001_R0qf:128 + 430s xx3:3:veth1001_SVp8:129 + 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached + 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached + 430s FAIL: unable to create nic after destroying the old + 430s FAIL + 430s FAIL + 430s --- + 430s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec + 430s PASS: lxc-tests: /usr/bin/lxc-test-utils + 430s + 430s SUMMARY: pass=54, fail=1, ignored=1 + + Not sure the "quota reached" is from trying to create the usernic-user + or the interface. + Testing failed on: - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/l/lxc/20241018_130950_b0c48@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/l/lxc/20241018_130950_b0c48@/log.gz ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2085127 Title: lxc/1:5.0.3-2ubuntu7 ADT test failure with linux/6.8.0-48.48 Status in linux package in Ubuntu: New Status in lxc package in Ubuntu: New Status in linux source package in Noble: New Status in lxc source package in Noble: New Bug description: This is a scripted bug report about ADT failures while running lxc tests for linux/6.8.0-48.48 on noble. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. The "exercise" test fails one of its sub-tests on s390x: 430s FAIL: lxc-tests: /usr/bin/lxc-test-usernic 430s --- 430s fatal: The user `usernic-user' does not exist. 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s xx2:2:veth1001_R0qf:128 430s xx3:3:veth1001_SVp8:129 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s FAIL: unable to create nic after destroying the old 430s FAIL 430s FAIL 430s --- 430s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec 430s PASS: lxc-tests: /usr/bin/lxc-test-utils 430s 430s SUMMARY: pass=54, fail=1, ignored=1 Not sure the "quota reached" is from trying to create the usernic-user or the interface. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/l/lxc/20241018_130950_b0c48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085127/+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/ListHe
[Touch-packages] [Bug 2085127] Re: lxc/1:5.0.3-2ubuntu7 ADT test failure with linux/6.8.0-48.48
** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Canonical LXD team (canonical-lxd) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2085127 Title: lxc/1:5.0.3-2ubuntu7 ADT test failure with linux/6.8.0-48.48 Status in linux package in Ubuntu: New Status in lxc package in Ubuntu: New Status in linux source package in Noble: New Status in lxc source package in Noble: New Bug description: This is a scripted bug report about ADT failures while running lxc tests for linux/6.8.0-48.48 on noble. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. The "exercise" test fails one of its sub-tests on s390x: 430s FAIL: lxc-tests: /usr/bin/lxc-test-usernic 430s --- 430s fatal: The user `usernic-user' does not exist. 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s xx2:2:veth1001_R0qf:128 430s xx3:3:veth1001_SVp8:129 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s ../src/lxc/cmd/lxc_user_nic.c: 1211: main: Quota reached 430s FAIL: unable to create nic after destroying the old 430s FAIL 430s FAIL 430s --- 430s PASS: lxc-tests: /usr/bin/lxc-test-usernsexec 430s PASS: lxc-tests: /usr/bin/lxc-test-utils 430s 430s SUMMARY: pass=54, fail=1, ignored=1 Not sure the "quota reached" is from trying to create the usernic-user or the interface. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/l/lxc/20241018_130950_b0c48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085127/+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 1972708] Re: Wired connection is off after resuming from sleep
Looking at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301
(same issue for atheros cards in the past) it may be a kernel issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1972708
Title:
Wired connection is off after resuming from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When coming out of sleep mode, the wired connection is always off,
fresh installation of 22.04. It goes up easily by toggling it on from
the UI ("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0:
Suspend timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0:
Suspend notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4217] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4218] device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4445] dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
set default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4638] manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5495] manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5520] device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51 olivier-desktop ModemManager[753]: [base-manager]
couldn't check support
[Touch-packages] [Bug 1972708] Re: Wired connection is off after resuming from sleep
Workaround found :
sudo modprobe -r igc
sudo modprobe igc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1972708
Title:
Wired connection is off after resuming from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When coming out of sleep mode, the wired connection is always off,
fresh installation of 22.04. It goes up easily by toggling it on from
the UI ("Turn On")
Relevant /var/log/syslog messages:
May 9 17:11:49 olivier-desktop kernel: [12935.927375] Bluetooth: hci0: Timed
out waiting for suspend events
May 9 17:11:49 olivier-desktop kernel: [12935.927381] Bluetooth: hci0:
Suspend timeout bit: 6
May 9 17:11:49 olivier-desktop kernel: [12935.927395] Bluetooth: hci0:
Suspend notifier action (3) failed: -110
May 9 17:11:49 olivier-desktop kernel: [12935.927420] Freezing user space
processes ... (elapsed 0.003 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.931100] OOM killer disabled.
May 9 17:11:49 olivier-desktop kernel: [12935.931101] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
May 9 17:11:49 olivier-desktop kernel: [12935.932442] printk: Suspending
console(s) (use no_console_suspend to debug)
May 9 17:11:49 olivier-desktop kernel: [12935.933372] nuvoton-cir 00:01:
disabled
May 9 17:11:49 olivier-desktop kernel: [12935.933511] e1000e: EEE TX LPI
TIMER: 0011
[...]
May 9 17:11:49 olivier-desktop ModemManager[753]: [sleep-monitor]
system is resuming
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4217] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4218] device (enp0s25): state change: activated -> unmanaged (reas
on 'sleeping', sys-iface-state: 'managed')
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.] dhcp4 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4445] dhcp4 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): canceled DHCP transaction
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): activation: beginning transaction (timeout
in 45 seconds)
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4448] dhcp6 (enp0s25): state changed no lease
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 192.168.1.39 on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv4 with address 192.168.1.39.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv4 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:5c93:eaf1:5741:587a on enp0s25.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:5
c93:eaf1:5741:587a.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Joining mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset search domain list.
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
set default route setting: no
May 9 17:11:49 olivier-desktop systemd-resolved[521]: enp0s25: Bus client
reset DNS server list.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.4638] manager: NetworkManager state is now CONNECTED_GLOBAL
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Interface enp0s25.IPv6 no
longer relevant for mDNS.
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Leaving mDNS multicast
group on interface enp0s25.IPv6 with address 2a01:cb04:5e3:5f00:c
e9a:6874:2c00:f41c.
May 9 17:11:49 olivier-desktop kernel: [12936.658740] e1000e :00:19.0
enp0s25: NIC Link is Down
May 9 17:11:49 olivier-desktop avahi-daemon[633]: Withdrawing address record
for 2a01:cb04:5e3:5f00:ce9a:6874:2c00:f41c on enp0s25.
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5495] manager: NetworkManager state is now DISCONNECTED
May 9 17:11:49 olivier-desktop NetworkManager[644]:
[1652109109.5520] device (enp0s25): state change: unmanaged -> unavailable (re
ason 'managed', sys-iface-state: 'external')
[...]
May 9 17:11:51 olivier-desktop ModemManager[753]: [base-manager]
couldn't check support for device '/sys/devices/pci:00/:0
0:1c.3/:02:00.0': not supported b
[Touch-packages] [Bug 1860500] Re: consider disabling apt-secure's Label check in Ubuntu
** Changed in: apt (Ubuntu) Status: Confirmed => Won't Fix -- 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/1860500 Title: consider disabling apt-secure's Label check in Ubuntu Status in apt package in Ubuntu: Won't Fix Bug description: As of 1.5 (per apt-secure(8)) apt checks and warns if a repository's Label value changes. This probably makes sense for Debian, where folks may be tracking stable instead of buster, and will want to be warned when stable starts pointing somewhere else. However, Ubuntu doesn't have such repository aliases and, furthermore, for PPAs, the Label value is populated from the "display name" of the PPA. This means that a PPA owner, fixing what they may assume is a simple typo, will require their users to take action before they receive further updates from the PPA, which is less than ideal. Please consider disabling this check by default in Ubuntu, if only for PPAs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1860500/+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 2085142] [NEW] /project/ubuntu-archive-keyring.gpg is outdated
Public bug reported: http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg and http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg.sig are timestamped 2008-02-13 and 2013-06-28 respectively. This is clearly out of date with respect to the version shipped by ubuntu-keyring. Could we get this updated? I don't remember how the .sig file was generated - it seems to be a signature from the master key. I think putting new copies of these files in place would need to be done by Canonical IS, by updating them in (I think) /srv/launchpad/archives/ubuntu-archive/ubuntu/project/ on the production launchpad-ftpmaster-publisher unit; last I checked they weren't currently stored in any database. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2085142 Title: /project/ubuntu-archive-keyring.gpg is outdated Status in ubuntu-keyring package in Ubuntu: New Bug description: http://archive.ubuntu.com/ubuntu/project/ubuntu-archive-keyring.gpg and http://archive.ubuntu.com/ubuntu/project/ubuntu-archive- keyring.gpg.sig are timestamped 2008-02-13 and 2013-06-28 respectively. This is clearly out of date with respect to the version shipped by ubuntu-keyring. Could we get this updated? I don't remember how the .sig file was generated - it seems to be a signature from the master key. I think putting new copies of these files in place would need to be done by Canonical IS, by updating them in (I think) /srv/launchpad/archives/ubuntu-archive/ubuntu/project/ on the production launchpad-ftpmaster-publisher unit; last I checked they weren't currently stored in any database. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/2085142/+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 2085147] [NEW] Wrong timezone detection (always UTC)
Public bug reported:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released in
Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now() };
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata 2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata 2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug block-proposed package-from-proposed plucky
wayland-session
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
New
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+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 2085147] Re: Wrong timezone detection (always UTC)
Funny `UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)`,
btw, but this is unrelated. :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2085147
Title:
Wrong timezone detection (always UTC)
Status in tzdata package in Ubuntu:
New
Bug description:
With tzdata 2024b-1ubuntu1 (plucky-proposed), the timezone is wrongly
detected to be UTC, no matter what I do.
This is working fine with 2024a-4ubuntu1, which is what was released
in Oracular.
Simple reproducer:
```cpp
#include
#include
int main() {
const std::chrono::zoned_time cur_time{ std::chrono::current_zone(),
std::chrono::system_clock::now()
};
std::cout << cur_time << '\n';
}
```
Compiled with `g++ -std=c++20 main.cpp`
```
$ ./a.out
2024-10-21 16:14:17.489489001 UTC
$ dpkg-query -W tzdata
tzdata2024b-1ubuntu1
$ sudo apt install tzdata/oracular
[...]
$ dpkg-query -W tzdata
tzdata2024a-4ubuntu1
$ ./a.out
2024-10-21 18:16:25.554620585 CEST
```
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: tzdata 2024b-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Oct 21 14:11:36 2024
InstallationDate: Installed on 2023-08-02 (446 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=alacritty
XDG_RUNTIME_DIR=
SourcePackage: tzdata
UpgradeStatus: Upgraded to plucky on 2024-06-12 (131 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2085147/+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 2079966] Re: tzdata 2024b release
I'm not running Oracular anymore, so can't really confirm, but Plucky is still pretty close (like almost identical), so this SRU might be hitting bug 2085147. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2079966 Title: tzdata 2024b release Status in tzdata package in Ubuntu: Fix Committed Status in tzdata source package in Focal: New Status in tzdata source package in Jammy: New Status in tzdata source package in Noble: New Status in tzdata source package in Oracular: Fix Committed Bug description: [ Impact ] The 2024b release contains the following changes: * Improve historical data for Mexico, Mongolia, and Portugal. * System V names are now obsolescent. * The main data form now uses %z. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024b * python-icu: test_2024b (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). There are backward-incompatible changes included: Names present only for compatibility with UNIX System V (last released in the 1990s) have been moved to 'backward'. These names, which for post-1970 timestamps mostly just duplicate data of geographical names, were confusing downstream uses. Names moved to 'backward' are now Links to geographical names if there is an exact match since 1970, and remain Zones otherwise. Those needing the previous TZDB behavior, which does not match any real-world clocks, can find the old entries in 'backzone'. (Problem reported by Justin Grant.) We need to exclude this change for the SRU since it can/will break user setup (e. g. the user from bug #2055718) and it will break a handful of tests (including dateparser, pandas, posrtesql-16). See https://bugs.debian.org/1084190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2079966/+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 2085192] [NEW] Backport of openldap for plucky
Public bug reported: Backport openldap to plucky once the update for plucky has been completed. [Impact] TBD [Major Changes] TBD [Test Plan] TBD [Regression Potential] Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. ** Affects: openldap (Ubuntu) Importance: Wishlist Status: New ** Affects: openldap (Ubuntu Plucky) Importance: Wishlist Status: New ** Tags: needs-sru-backport ** Changed in: openldap (Ubuntu) Importance: Undecided => Wishlist ** Changed in: openldap (Ubuntu) Milestone: None => ubuntu-25.02 ** Also affects: openldap (Ubuntu Plucky) Importance: Wishlist Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/2085192 Title: Backport of openldap for plucky Status in openldap package in Ubuntu: New Status in openldap source package in Plucky: New Bug description: Backport openldap to plucky once the update for plucky has been completed. [Impact] TBD [Major Changes] TBD [Test Plan] TBD [Regression Potential] Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2085192/+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 2085162] [NEW] Bluetooth headphones connect erratically
You have been subscribed to a public bug: Description of the problem A pair of Sony Sony WH-H900N Bluetooth headphones often refuses to re-connect with a Lenovo V15 G2 ALC laptop. These headphones pair without trouble to a MacBook Pro and an Android phone. Step to reproduce: 1. Put the headphones into discovery mode. 2. Go to Settings -> Bluetooth and connect to the headphones. 3. Reboot the laptop. 4. Go to Settings -> Bluetooth 5. Click on the headphones. 6. Try to connect to the headphones. 7. If step 6. fails try to disconnect. 8. Go to step 6. Expected result: After step 6 for headphones to be connected and for headphones to announce "Bluetooth connected". Actual result: Sometimes the "connected" slider slides back to unconnected. Sometimes the slider remains "on" but the headphones don't announce that they are connected and no headphones appear in sound settings. How reproducible is the problem: Fairly reproducible. It can sometimes takes 30 or more connection attempts before a real connection is established. Version information: Ubuntu 24.10 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:sitsofe8130 F pipewire /dev/snd/controlC0: sitsofe8136 F wireplumber /dev/snd/controlC1: sitsofe8136 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 21:34:28 2024 InstallationDate: Installed on 2024-10-14 (7 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82KD PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN42WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G2 ALC dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC: dmi.product.family: V15 G2 ALC dmi.product.name: 82KD dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC dmi.product.version: Lenovo V15 G2 ALC dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- Bluetooth headphones connect erratically https://bugs.launchpad.net/bugs/2085162 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2085162] Re: Bluetooth headphones connect erratically
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2085162 Title: Bluetooth headphones connect erratically Status in alsa-driver package in Ubuntu: New Bug description: Description of the problem A pair of Sony Sony WH-H900N Bluetooth headphones often refuses to re-connect with a Lenovo V15 G2 ALC laptop. These headphones pair without trouble to a MacBook Pro and an Android phone. Step to reproduce: 1. Put the headphones into discovery mode. 2. Go to Settings -> Bluetooth and connect to the headphones. 3. Reboot the laptop. 4. Go to Settings -> Bluetooth 5. Click on the headphones. 6. Try to connect to the headphones. 7. If step 6. fails try to disconnect. 8. Go to step 6. Expected result: After step 6 for headphones to be connected and for headphones to announce "Bluetooth connected". Actual result: Sometimes the "connected" slider slides back to unconnected. Sometimes the slider remains "on" but the headphones don't announce that they are connected and no headphones appear in sound settings. How reproducible is the problem: Fairly reproducible. It can sometimes takes 30 or more connection attempts before a real connection is established. Version information: Ubuntu 24.10 ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:sitsofe8130 F pipewire /dev/snd/controlC0: sitsofe8136 F wireplumber /dev/snd/controlC1: sitsofe8136 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 21:34:28 2024 InstallationDate: Installed on 2024-10-14 (7 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: LENOVO 82KD PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN42WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G2 ALC dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC: dmi.product.family: V15 G2 ALC dmi.product.name: 82KD dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC dmi.product.version: Lenovo V15 G2 ALC dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085162/+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 2085236] [NEW] Merge init-system-helpers from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 1.67 Ubuntu: 1.66ubuntu1 foundations team has maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### init-system-helpers (1.67) unstable; urgency=medium [ Mark Hindley ] * Don't manually set status symlinks for native openrc-run scripts. For native openrc-run scripts, fiddling with the links before the script is run actually prevents it from running as openrc-run detects the status has been changed and considers the script as already started. (Closes: #1081994) [ Luca Boccassi ] * d/control: bump Standards-Version to 4.7.0, no changes -- Luca Boccassi Tue, 17 Sep 2024 17:07:33 +0200 init-system-helpers (1.66) unstable; urgency=medium [ Samuel Thibault ] * Add hurd-amd64 case. [ Gioele Barabucci ] * d/init.lintian-overrides: Silence warning about 'Important' field `Important: yes` instructs APT to warn the user before removing this package. [ Johannes Schauer Marin Rodrigues ] * script/update-rc.d: DPKG_ROOT support for sysvinit [ Ansgar ] * Add 'Protected: yes' to package 'init' The 'Protected' field does the same as 'Important' already did in apt, but is also understood by dpkg (since dpkg 1.20.1). [ Luca Boccassi ] * Bump Standards-Version to 4.6.2, no changes * Override Lintian warning for Protected: yes * deb-systemd-invoke: support reload/reexec. This is useful for the --user case, to provide a shortcut that loops over all active user sessions over D-Bus. * deb-systemd-invoke: support --no-dbus for reload/reexec. Provide common implementation for SIGHUP/SIGRTMIN+25 to reload/reexec the system or user instances. -- Luca Boccassi Sun, 26 Nov 2023 20:42:28 + init-system-helpers (1.65.2) unstable; urgency=low * Undo yet another hostile and baseless NMU. -- Luca Boccassi Sun, 18 Sep 2022 02:53:19 +0100 init-system-helpers (1.65.1) unstable; urgency=low * Undo hostile NMU. -- Luca Boccassi Sun, 18 Sep 2022 01:53:32 +0100 init-system-helpers (1.65) unstable; urgency=low * Upload to unstable. -- Luca Boccassi Sat, 17 Sep 2022 21:11:07 +0100 init-system-helpers (1.65~exp2) experimental; urgency=medium * fakechroot tests: skip on architectures where it is not available -- Luca Boccassi Thu, 15 Sep 2022 21:14:08 +0100 init-system-helpers (1.65~exp1) experimental; urgency=medium [ Luca Boccassi ] * Drop outdated conflict with file-rc * Add myself to Uploaders * d/rules: use execute_after instead of override * Add a dependency on usrmerge | usr-is-merged to complete the transition. As per ctte decision and discussion at: https://lists.debian.org/debian-ctte/2022/07/msg00019.html https://lists.debian.org/debian-ctte/2022/07/msg00061.html https://lists.debian.org/debian-ctte/2022/08/msg6.html [ Victor Westerhuis ] * Make deb-systemd-helper work on template units with DefaultInstance. DefaultInstance only influences the meaning of WantedBy/RequiredBy. Alias and Also are not impacted. This patch does not enable changing template instantiations, so `deb-systemd-helper enable getty@tty2.service` will still fail. * Fix tests depending on ordering of lines in state file. The previous commit changes the order in which lines are written to the state file. Because correctness does not depend on the order in which the state file is written, ignore the order in the test. -- Luca Boccassi Sat, 10 Sep 2022 13:27:16 +0100 init-system-helpers (1.64) unstable; urgency=medium * Team upload. * d-s-h: break infinite recursion on symlinks. (Closes: #1014119) * Bump Standards-Version to 4.6.1, no changes * Update date ranges in d/copyright ### Old Ubuntu Delta ### init-system-helpers (1.66ubuntu1) noble; urgency=medium * Merge from Debian unstable. Remaining changes: - Drop dependency on usrmerge. -- Steve Langasek Tue, 05 Dec 2023 23:50:15 -0800 ** Affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/2085236 Title: Merge init-system-helpers from Debian unstable for jammy Status in init-system-helpers package in Ubuntu: New Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.67 Ubuntu: 1.66ubuntu1 foundations team has maintained this package's merge in the past. If it turns out this needs a sync rather than a merge
[Touch-packages] [Bug 2085235] [NEW] Merge heimdal from Debian unstable for jammy
Public bug reported: Upstream: tbd Debian: 7.8.git20221117.28daf24+dfsg-8 Ubuntu: 7.8.git20221117.28daf24+dfsg-8ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### heimdal (7.8.git20221117.28daf24+dfsg-8) unstable; urgency=medium [ Andreas Hasenack ] * Fix FTBFS with autoconf 2.72. Closes: #1078494. -- Brian May Mon, 12 Aug 2024 10:55:53 +1000 heimdal (7.8.git20221117.28daf24+dfsg-7) unstable; urgency=medium * Add include and includedir patch that was accidentally omitted. * Rename pkg-config to pkgconf in dependancy. [ Andreas Hasenack ] * Add support for include and includedir directives to krb5.conf. -- Brian May Thu, 08 Aug 2024 10:42:42 +1000 heimdal (7.8.git20221117.28daf24+dfsg-6) unstable; urgency=medium * Fix FTBFS due to not linking with crypt correctly. Applied patch from https://github.com/heimdal/heimdal/pull/1085. Closes: #1075064. [ Andreas Hasenack ] * Add a kinit DEP8 test which relies on the includedir support. -- Brian May Thu, 25 Jul 2024 16:19:48 +1000 heimdal (7.8.git20221117.28daf24+dfsg-5) unstable; urgency=medium * Apply NMU patches. Closes: #1065373. -- Brian May Sat, 09 Mar 2024 11:01:27 +1100 heimdal (7.8.git20221117.28daf24+dfsg-4.2) unstable; urgency=medium [ Matthias Klose ] * Filter-out -Werror=implicit-function-declaration, unconditionally set by abi=time64. -- Steve Langasek Fri, 08 Mar 2024 08:21:09 + heimdal (7.8.git20221117.28daf24+dfsg-4.1) unstable; urgency=medium * Non-maintainer upload. * Rename libraries for 64-bit time_t transition. Closes: #1064097 -- Lukas Märdian Wed, 28 Feb 2024 08:36:52 + heimdal (7.8.git20221117.28daf24+dfsg-4) unstable; urgency=medium * Always build the rk_strlcat and rk_strlcpy symbols even if included in glibc. Closes: #1055316. -- Brian May Wed, 03 Jan 2024 11:43:58 +1100 heimdal (7.8.git20221117.28daf24+dfsg-3) unstable; urgency=medium * Fix random 'Ticket expired' and 'Clock skew too great' errors by setting kdc_offset correctly. Closes: #1039992. -- Brian May Tue, 04 Jul 2023 10:09:56 +1000 heimdal (7.8.git20221117.28daf24+dfsg-2) unstable; urgency=medium * Fix incorrect license of Debian files. * Fix deprecated dependancies. * gsskrb5: fix accidental logic inversions (CVE-2022-45142) (Closes: #1030849) - change applied from NMU version 7.8.git20221117.28daf24+dfsg-1.1 * Add ro.po file. Closes: #1031897. -- Brian May Sat, 25 Feb 2023 09:32:57 +1100 heimdal (7.8.git20221117.28daf24+dfsg-1) unstable; urgency=medium * New upstream release. -- Brian May Sat, 10 Dec 2022 16:29:20 +1100 heimdal (7.8.git20221115.a6cf945+dfsg-3) unstable; urgency=medium * Source-only upload to enable migration to testingi (2nd attempt). -- Brian May Sun, 04 Dec 2022 09:56:06 +1100 heimdal (7.8.git20221115.a6cf945+dfsg-2) unstable; urgency=medium * Source-only upload to enable migration to testing. -- Brian May Sun, 04 Dec 2022 09:09:44 +1100 heimdal (7.8.git20221115.a6cf945+dfsg-1) unstable; urgency=medium * New upstream version. * Numerous security fixes (Closes: #1024187). * asn1: Invalid free in ASN.1 codec (CVE-2022-44640) * krb5: PAC parse integer overflows (CVE-2022-42898) * gsskrb5: Use constant-time memcmp() for arcfour unwrap (CVE-2022-3437) * gsskrb5: Use constant-time memcmp() in unwrap_des3() (CVE-2022-3437) * gsskrb5: Don't pass NULL pointers to memcpy() in DES unwrap ### Old Ubuntu Delta ### heimdal (7.8.git20221117.28daf24+dfsg-8ubuntu1) oracular; urgency=medium * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. -- Gianfranco Costamagna Mon, 12 Aug 2024 14:50:58 +0200 ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version ** Changed in: heimdal (Ubuntu) Milestone: None => ubuntu-25.01 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2085235 Title: Merge heimdal from Debian unstable for jammy Status in heimdal package in Ubuntu: New Bug description: Upstream: tbd Debian: 7.8.git20221117.28daf24+dfsg-8 Ubuntu: 7.8.git20221117.28daf24+dfsg-8ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions availabl
[Touch-packages] [Bug 2085261] [NEW] Merge openssh from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 1:9.9p1-2 Ubuntu: 1:9.7p1-7ubuntu4 foundations team has maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### openssh (1:9.9p1-2) unstable; urgency=medium * Don't prefer host-bound public key signatures if there was no initial host key, as is the case when using GSS-API key exchange (closes: #1041521). * Use runuser rather than sudo in autopkgtests where possible, avoiding a dependency. -- Colin Watson Mon, 21 Oct 2024 18:24:07 +0100 openssh (1:9.9p1-1) unstable; urgency=medium * Alias the old Debian-specific SetupTimeOut client option to ConnectTimeout rather than to ServerAliveInterval. * New upstream release (https://www.openssh.com/releasenotes.html#9.9p1): - ssh(1): remove support for pre-authentication compression. - ssh(1), sshd(8): processing of the arguments to the 'Match' configuration directive now follows more shell-like rules for quoted strings, including allowing nested quotes and /-escaped characters. - ssh(1), sshd(8): add support for a new hybrid post-quantum key exchange based on the FIPS 203 Module-Lattice Key Enapsulation mechanism (ML-KEM) combined with X25519 ECDH as described by https://datatracker.ietf.org/doc/html/draft-kampanakis-curdle-ssh-pq-ke-03 This algorithm 'mlkem768x25519-sha256' is available by default. - ssh(1): the ssh_config 'Include' directive can now expand environment as well as the same set of %-tokens 'Match Exec' supports. - sshd(8): add a sshd_config 'RefuseConnection' option that, if set will terminate the connection at the first authentication request. - sshd(8): add a 'refuseconnection' penalty class to sshd_config PerSourcePenalties that is applied when a connection is dropped by the new RefuseConnection keyword. - sshd(8): add a 'Match invalid-user' predicate to sshd_config Match options that matches when the target username is not valid on the server. - ssh(1), sshd(8): update the Streamlined NTRUPrime code to a substantially faster implementation. - ssh(1), sshd(8): the hybrid Streamlined NTRUPrime/X25519 key exchange algorithm now has an IANA-assigned name in addition to the '@openssh.com' vendor extension name. This algorithm is now also available under this name 'sntrup761x25519-sha512' - ssh(1), sshd(8), ssh-agent(1): prevent private keys from being included in core dump files for most of their lifespans. This is in addition to pre-existing controls in ssh-agent(1) and sshd(8) that prevented coredumps. - All: convert key handling to use the libcrypto EVP_PKEY API, with the exception of DSA. - sshd(8): add a random amount of jitter (up to 4 seconds) to the grace login time to make its expiry unpredictable. - sshd(8): fix regression introduced in openssh-9.8 that swapped the order of source and destination addresses in some sshd log messages. - sshd(8): do not apply authorized_keys options when signature verification fails. Prevents more restrictive key options being incorrectly applied to subsequent keys in authorized_keys. - ssh-keygen(1): include pathname in some of ssh-keygen's passphrase prompts. Helps the user know what's going on when ssh-keygen is invoked via other tools. - ssh(1), ssh-add(1): make parsing user@host consistently look for the last '@' in the string rather than the first. This makes it possible to more consistently use usernames that contain '@' characters. - ssh(1), sshd(8): be more strict in parsing key type names. Only allow short names (e.g 'rsa') in user-interface code and require full SSH protocol names (e.g. 'ssh-rsa') everywhere else. - regress: many performance and correctness improvements to the re-keying regression test. - ssh-keygen(1): clarify that ed25519 is the default key type generated and clarify that rsa-sha2-512 is the default signature scheme when RSA is in use. - sshd(8): fix minor memory leak in Subsystem option parsing. - All: additional hardening and consistency checks for the sshbuf code. - sshd(8): reduce default logingrace penalty to ensure that a single forgotten login that times out will be below the penalty threshold. - ssh(1): fix proxy multiplexing (-O proxy) bug. If a mux started with ControlPersist then later has a forwarding added using mux proxy connection and the forwarding was used, then when the mux proxy session terminated, the mux master process would issue
[Touch-packages] [Bug 2085255] [NEW] Merge net-tools from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 2.10-1.1 Ubuntu: 2.10-1.1ubuntu1 There is nothing yet to merge for net-tools currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### net-tools (2.10-1.1) unstable; urgency=medium * Non-maintainer upload. * Release to unstable. (Closes: #1059409) -- Chris Hofstaedtler Mon, 22 Apr 2024 01:55:29 +0200 net-tools (2.10-1) experimental; urgency=medium * Move to /usr-merge (DEP17). -- Utkarsh Gupta Thu, 23 Nov 2023 14:41:07 + net-tools (2.10-0.1) unstable; urgency=medium * Non-maintainer upload. * Update Martina's name and email address. * Drop DECnet support (Closes: #1024730) * Revert 'Fix d/watch to point to upstream git repository' * New upstream version 2.10 (Closes: #1000281) -- Bastian Germann Fri, 25 Nov 2022 15:15:20 +0100 net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium * New upstream version 1.60+git20181103.0eebece - Fix nstrcmp() to prevent ifconfig from showing duplicate interfaces. (Closes: #812886) * Fix d/watch to point to upstream git repository * Add patch to fix decoding of MII vendor ids. (Closes: #549397) - Thanks, Ben Hutchings, for the patch. * Add patch to fix Japanese translation which uses a wrong Kanji character. (Closes: #621752) - Thanks, Takeshi Hamasaki, for the patch. * Add patch to fix wrong indentation of 'collisions' in the Japanese translation. (Closes: #653117) - Thanks, NODA, Kai, for the patch. * Fix Uploaders' field. - Add myself as an uploader. - Fix Tina's details. -- Utkarsh Gupta Fri, 02 Oct 2020 15:01:04 +0530 net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium * New upstream snapshot * Refresh patches. * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and Dr. Tobias Quathamer for the patch. Closes: #900962. -- Martina Ferrari Mon, 24 Sep 2018 19:08:57 + net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium * Update maintainer email address. Closes: #899617. * Update Standards-Version with no changes. -- Martina Ferrari Mon, 24 Sep 2018 17:16:31 + net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium * debian/control: Update Vcs-* and Standards-Version. * debian/control: remove references to ancient package ja-trans. * debian/gbp.conf: Update repo layout. -- Martina Ferrari Tue, 31 Jul 2018 19:09:00 + net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium * Fix typo in French manpage. Thanks to Michel Grigaut for the patch. * Add manpage for iptunnel, thanks to Sergio Durigan Junior. Closes: #88910 * Rename patches so CME does not choke on them. * Automated cme fixes; packaging improvements. * Remove unused and ancient patch. -- Martina Ferrari Sun, 11 Feb 2018 17:29:24 + net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium * New upstream snapshot. * Re-synced translations.patch. * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the fixes and uploads. Closes: 846509. * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561. + Really assign CC for cross compilation. + Use triplet prefixed pkg-config. * Add debian/NEWS warning about changing output in net-tools commands. Closing bugs that reported problems in 3rd-party scripts arising from these changes. Closes: #845153, #843892, #820212. * Update Standards-Version, with no changes. -- Martina Ferrari Mon, 26 Dec 2016 05:58:42 + net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium * Non-maintainer upload. * Apply an additional fix for the previous FTBFS for some architectures. -- Andrey Rahmatullin Thu, 01 Dec 2016 22:49:27 +0500 ### Old Ubuntu Delta ### net-tools (2.10-1.1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2064431). Remaining changes: - Ubuntu_unit_conversion.patch (LP #240073): + Ubuntu Policy: output using standard SI unit multiples: KB (10^3), MB (10^6), GB (10^9), TB (10^12), and PB (10^15). Includes manpage update to remove comment about IEC units. - Add new DEP8 tests for hostname and ifconfig (LP #1679346). -- Lena Voytek Wed, 22 May 2024 14:13:01 -0700 ** Affects: net-tools (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-merge upgrade-software-version ** Changed in: net-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch
[Touch-packages] [Bug 2085260] [NEW] Merge openldap from Debian unstable for jammy
Public bug reported:
Upstream: tbd
Debian: 2.5.18+dfsg-32.6.8+dfsg-1~exp4
Ubuntu: 2.6.8+dfsg-1~exp4ubuntu1
Debian new has 2.6.8+dfsg-1~exp4, which may be available for merge soon.
If it turns out this needs a sync rather than a merge, please change the
tag 'needs-merge' to 'needs-sync', and (optionally) update the title as
desired.
If this merge pulls in a new upstream version, also consider adding an
entry to the Jammy Release Notes:
https://discourse.ubuntu.com/c/release/38
### New Debian Changes ###
openldap (2.5.18+dfsg-3) unstable; urgency=medium
* Fix FTBFS on 32-bit architectures. (ITS#10253) (Closes: #1078822)
-- Ryan Tandy Wed, 21 Aug 2024 20:38:08 -0700
openldap (2.5.18+dfsg-2) unstable; urgency=medium
* Apply upstream patch to fix back-perl linking with libperl.
(ITS#10221, LP: #2072976)
* Add a superficial autopkgtest to ensure back_perl can be loaded.
-- Ryan Tandy Sun, 14 Jul 2024 14:37:43 -0700
openldap (2.5.18+dfsg-1) unstable; urgency=medium
[ Ryan Tandy ]
* New upstream release.
* Drop patch smbk5pwd-implicit-declaration, applied upstream.
[ Sergio Durigan Junior ]
* d/control: B-D on pkgconf instead of pkg-config.
[ Helmut Grohne ]
* Move systemd drop-in to /usr (DEP17). (Closes: #1073059)
-- Ryan Tandy Wed, 12 Jun 2024 19:23:12 -0700
openldap (2.5.17+dfsg-1) unstable; urgency=medium
* New upstream release.
- fixed slapo-dynlist so it can't be global (ITS#10091) (Closes: #1040382)
* debian/copyright: Exclude doc/guide/admin/guide.html from the upstream
source, because the tool required to build it from source is not packaged
in Debian. Fixes a Lintian error (source-is-missing).
* Update Swedish debconf translation. (Closes: #1056955)
Thanks to Martin Bagge and Anders Jonsson.
* debian/salsa-ci.yml: Enable Salsa CI pipeline.
-- Ryan Tandy Fri, 26 Apr 2024 16:09:29 -0700
openldap (2.5.16+dfsg-2) unstable; urgency=medium
* debian/patches/64-bit-time-t-compat: handle sizeof(time_t) >
sizeof(long) in format strings.
-- Steve Langasek Tue, 12 Mar 2024 06:26:07 +
openldap (2.5.16+dfsg-1) unstable; urgency=medium
[ Ryan Tandy ]
* New upstream release.
- fixed possible null pointer dereferences if strdup fails
(ITS#9904) (Closes: #1036995, CVE-2023-2953)
- fixed unaligned accesses in LMDB on sparc64
(ITS#9916) (Closes: #1020319)
* Update Turkish debconf translation. (Closes: #1029758)
Thanks to Atila KOÇ.
* Add Romanian debconf translation. (Closes: #1033177)
Thanks to Remus-Gabriel Chelu.
* Create an autopkgtest covering basic TLS functionality.
Thanks to John Scott.
* Drop transitional package slapd-smbk5pwd. (Closes: #1032742)
* Drop dbgsym migration for slapd-dbg.
* Build and install the ppm module in slapd-contrib. (Closes: #1039740)
* Fix implicit declaration of kadm5_s_init_with_password_ctx.
(Closes: #1065633)
[ Sergio Durigan Junior ]
* d/control: Bump Standards-Version to 4.6.2; no changes needed.
* d/control: Bump debhelper-compat to 13.
* d/control: Drop lsb-base from slapd's Depends.
* Enable SASL/GSSAPI tests.
Thanks to Andreas Hasenack
-- Ryan Tandy Fri, 08 Mar 2024 21:46:26 -0800
openldap (2.5.13+dfsg-5) unstable; urgency=medium
* Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
(Closes: #1030814)
* Disable flaky test test069-delta-multiprovider-starttls.
-- Ryan Tandy Tue, 07 Feb 2023 17:56:12 -0800
openldap (2.5.13+dfsg-4) unstable; urgency=medium
[ Andreas Hasenack ]
* d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817)
* d/t/sha2-contrib: add test for sha2 module
-- Ryan Tandy Mon, 06 Feb 2023 19:21:05 -0800
openldap (2.5.13+dfsg-3) unstable; urgency=medium
[ Ryan Tandy ]
* Disable flaky test test063-delta-multiprovider. Mitigates #1010608.
[ Gioele Barabucci ]
* slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes: #1016185)
### Old Ubuntu Delta ###
openldap (2.6.8+dfsg-1~exp4ubuntu1) oracular; urgency=medium
* Merge with Debian unstable (LP: #2078261). Remaining changes:
- Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
+ d/rules: use dh_apparmor
+ d/control: Build-Depends on dh-apparmor
+ d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
+ d/control: suggest ufw.
+ d/rules: install ufw profile.
+ d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Add apport hook.
- d/t/smbk5pwd: Allow the openldap user to read the Heimdal master key in
the
smbk5pwd DEP8 test (LP #2004560)
[ Partially incorporated by Debian. ]
- debian/rules: fix buildability under pkg.openldap.noslapd profile.
- debian/rules: drop override of dh_missing, --fail-missing is the default
with debhelper compat 13.
- d/control: make libldap2 depend on libldap-common. (LP #2063161)
-- Sergio Durigan Junior
[Touch-packages] [Bug 2085244] [NEW] Merge libseccomp from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 2.5.5-1 Ubuntu: 2.5.5-1ubuntu4 foundations team has maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### Old Ubuntu Delta ### libseccomp (2.5.5-1ubuntu4) oracular-proposed; urgency=medium * LP: #2076340: No-change rebuild to pick up changed build flags on ppc64el and s390x. -- Matthias Klose Thu, 08 Aug 2024 14:55:38 +0200 libseccomp (2.5.5-1ubuntu3) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 07:58:07 + libseccomp (2.5.5-1ubuntu2) noble; urgency=medium * No-change rebuild to build with python3.12 only. -- Matthias Klose Sat, 16 Mar 2024 23:14:35 +0100 libseccomp (2.5.5-1ubuntu1) noble; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests * Added changes: - d/t/test-filter: generate syscalls list from src/syscalls.csv rather than shipping a static list to ensure all get tested via autopkgtests * Dropped changes: - d/t/data/all-5.16-rc1.filter: remove static syscall list -- Alex Murray Fri, 02 Feb 2024 13:30:43 +1030 ** Affects: libseccomp (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-merge upgrade-software-version ** Changed in: libseccomp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2085244 Title: Merge libseccomp from Debian unstable for jammy Status in libseccomp package in Ubuntu: Incomplete Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 2.5.5-1 Ubuntu: 2.5.5-1ubuntu4 foundations team has maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### Old Ubuntu Delta ### libseccomp (2.5.5-1ubuntu4) oracular-proposed; urgency=medium * LP: #2076340: No-change rebuild to pick up changed build flags on ppc64el and s390x. -- Matthias Klose Thu, 08 Aug 2024 14:55:38 +0200 libseccomp (2.5.5-1ubuntu3) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 07:58:07 + libseccomp (2.5.5-1ubuntu2) noble; urgency=medium * No-change rebuild to build with python3.12 only. -- Matthias Klose Sat, 16 Mar 2024 23:14:35 +0100 libseccomp (2.5.5-1ubuntu1) noble; urgency=medium * Merge from Debian unstable; remaining changes: - Add autopkgtests * Added changes: - d/t/test-filter: generate syscalls list from src/syscalls.csv rather than shipping a static list to ensure all get tested via autopkgtests * Dropped changes: - d/t/data/all-5.16-rc1.filter: remove static syscall list -- Alex Murray Fri, 02 Feb 2024 13:30:43 +1030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2085244/+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 2085257] [NEW] Merge nspr from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 2:4.35-1.1 Ubuntu: 2:4.35-1.1ubuntu1 If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### nspr (2:4.35-1.1) unstable; urgency=medium * Non-maintainer upload * Avoid libreswan build failures on mipsel (Closes: #854472) -- Daniel Kahn Gillmor Wed, 22 Feb 2023 15:00:34 -0500 nspr (2:4.35-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Sun, 18 Sep 2022 06:29:06 +0900 nspr (2:4.34.1-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 24 Aug 2022 06:54:43 +0900 nspr (2:4.34-1) unstable; urgency=medium * New upstream release. * debian/libnspr4.symbols: Add PR_GetPrefLoopbackAddrInfo to symbols file. -- Mike Hommey Wed, 01 Jun 2022 06:21:09 +0900 nspr (2:4.33-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 06 Apr 2022 09:13:06 +0900 nspr (2:4.32-3) unstable; urgency=medium * nspr/configure.in: Fix AC_CONFIG_AUX_DIR. -- Mike Hommey Sun, 21 Nov 2021 09:06:33 +0900 nspr (2:4.32-2) unstable; urgency=medium * debian/libnspr4-dev.links.in, debian/control: Remove xulrunner-nspr.pc, which breaks libxmlsec1-dev (<= 1.2.33-1). * debian/copyright: Use secure copyright file specification URI. * debian/compat, debian/control: - Bump debhelper from deprecated 9 to 13. - Set debhelper-compat version in Build-Depends. * debian/rules: Drop transition for old debug package migration. * debian/*lintian-overrides*: - Remove unused copyright-refers-to-versionless-license-file. - s/shlib-without-versioned-soname/shared-library-lacks-version/ - s/dev-pkg-without-shlib-symlink/lacks-unversioned-link-to-shared-library/ * debian/watch: Upgrade watch file to version 4. * debian/rules: - Build with `make -s` when DEB_BUILD_OPTIONS contains terse. - Enable all hardnening options. * debian/control: - Add Rules-Requires-Root: no. - Upgrade Standards-Version to 4.6.0. - Remove conflict with libnspr3-0d. The last Debian version with libnspr3-0d was jessie, and it had a newer version anyways. - Remove now unnecessary autotools-dev build dependency. * debian/libnspr4.symbols: Add Build-Depends-Package in symbols file. * debian/control, debian/rules: Always set Multi-Arch: same. * debian/upstream/metadata: Add upstream bug tracking metadata. * debian/libnspr4.triggers: Remove ldconfig trigger, dh_makeshlibs adds it automatically. * debian/not-installed: Don't install compile-et.pl and prerr.properties. -- Mike Hommey Sun, 21 Nov 2021 07:09:06 +0900 nspr (2:4.32-1) unstable; urgency=medium * New upstream release. Closes: #991234. -- Mike Hommey Mon, 19 Jul 2021 06:13:28 +0900 nspr (2:4.29-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 21 Oct 2020 07:58:38 +0900 nspr (2:4.28-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Thu, 03 Sep 2020 10:45:34 +0900 nspr (2:4.27-1) unstable; urgency=medium * New upstream release. -- Mike Hommey Wed, 29 Jul 2020 16:47:26 +0900 nspr (2:4.25-1) unstable; urgency=medium * New upstream release. * debian/rules: Adapt to changes to runtests.sh. ### Old Ubuntu Delta ### nspr (2:4.35-1.1ubuntu1) oracular; urgency=medium * Drop explicit -Wl,--as-needed linker flag. It's the default. * Drop explicit CFLAGS that are checked by configure. * Also use non-hardening flags from dpkg-buildflags to pick up flags like -fno-omit-frame-pointer. -- Benjamin Drung Mon, 22 Jul 2024 11:39:40 +0200 nspr (2:4.35-1.1build1) noble; urgency=high * No change rebuild for 64-bit time_t and frame pointers. -- Julian Andres Klode Mon, 08 Apr 2024 18:14:31 +0200 ** Affects: nspr (Ubuntu) Importance: Undecided Status: New ** Tags: needs-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nspr in Ubuntu. https://bugs.launchpad.net/bugs/2085257 Title: Merge nspr from Debian unstable for jammy Status in nspr package in Ubuntu: New Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 2:4.35-1.1 Ubuntu: 2:4.35-1.1ubuntu1 If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### nspr (2:4.35-1.1) unstable; urgency=medium * Non-maintainer upload * Avoid libre
[Touch-packages] [Bug 2085219] [NEW] Merge bridge-utils from Debian unstable for jammy
Public bug reported: Scheduled-For: Backlog Upstream: tbd Debian: 1.7.1-2 Ubuntu: 1.7.1-2ubuntu1 There is nothing yet to merge for bridge-utils currently, but this ticket is filed prospectfully for tracking purposes in case a merge does become available later this cycle. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Jammy Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### bridge-utils (1.7.1-2) unstable; urgency=low [ Debian Janitor ] * Trim trailing whitespace. * Update standards version to 4.6.2, no changes needed. [ Chris Hofstaedtler ] * Install files into /usr instead of /. (Closes: #1059394) -- Santiago García Mantiñán Fri, 01 Mar 2024 23:09:33 +0100 bridge-utils (1.7.1-1) unstable; urgency=low * New upstream version. Only some fixes for compilation warnings and the man page. * Update standards version to 4.6.1, no changes needed. * Set debhelper-compat version in Build-Depends. * Trim trailing whitespace. -- Santiago García Mantiñán Wed, 25 Jan 2023 22:11:52 +0100 bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 bridge-utils (1.7-1) unstable; urgency=medium * New upstream version. Only messages related changes and compilation fixes. * Remove preserve_gcc_flags patch (in upstream now). * Bump standards, no change needed. * Clarify portprio and fix example. * Update upstream url. * Fix NEWS versioning of last entry :-? -- Santiago Garcia Mantinan Wed, 24 Feb 2021 12:34:03 +0100 bridge-utils (1.6-6) unstable; urgency=medium * Fix IPv6 address getting assigned on hotplug devices. Closes: #980752. * Fix waiting so that DAD works again. Closes: #982943. * Move mac setting before brctl addif to ensure mac setting. Closes: #980856. * Update documentation and add examples. Closes: #765098. * Update manpages. Closes: #981253. * Add a note on MTU settings. Closes: #292088. * Hook also on down to recreate the bridge so that multiple stanzas work Ok on ifdown. Closes: #319832. -- Santiago Garcia Mantinan Tue, 16 Feb 2021 13:29:04 +0100 bridge-utils (1.6-5) unstable; urgency=low * Overload bridge_hw to allow do specify an interface as well as the MAC address. Closes: #966244. * Change man page for bridge-utils-interfaces and news fileto document this overloading. -- Santiago Garcia Mantinan Fri, 22 Jan 2021 11:08:47 +0100 bridge-utils (1.6-4) unstable; urgency=low * Add en* to the device regex so that all catches them. Closes: #966319. * Document MAC address changes on news. Closes: #980505. -- Santiago Garcia Mantinan Thu, 21 Jan 2021 10:51:31 +0100 bridge-utils (1.6-3) unstable; urgency=medium * Support VLAN aware setups where we need vlan filtering. Thanks Benedikt Spranger for the patch. Closes: #950879. * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. -- Santiago Garcia Mantinan Thu, 30 Apr 2020 10:06:38 +0200 bridge-utils (1.6-2) unstable; urgency=medium * Bump Standards-Version. * Preserve gcc flags set when building the lib. -- Santiago Garcia Mantinan Mon, 28 Jan 2019 00:25:14 +0100 bridge-utils (1.6-1) unstable; urgency=low * New upstream version. * Change default back to not hotplug. Closes: #892277. * Allow mtu to be set on the bridge by propagating it to the bridged interfaces. Closes: #661711. * Remove kernel headers from the package. ### Old Ubuntu Delta ### bridge-utils (1.7.1-2ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2064391). Remaining changes: - debian/bridge-network-interface.sh: Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up (LP: 1003656). - debian/ifupdown.sh: Handle bridge params which use port and value (LP: 1576876). - debian/bridge-utils-interface.5: Update unsettable gcint value for newer kernels (LP: 1576858). -- Miriam España Acebal Mon, 27 May 2024 17:13:05 +0200 ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-merge upgrade-software-version ** Changed in: bridge-utils (Ubunt
[Touch-packages] [Bug 2085183] [NEW] wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu b
You have been subscribed to a public bug: wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu budgie 24.04. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: network-manager 1.48.8-1ubuntu3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Tue Oct 22 06:49:21 2024 InstallationDate: Installed on 2024-07-14 (100 days ago) InstallationMedia: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' RfKill: 6: phy6: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to oracular on 2024-10-10 (11 days ago) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2024-10-22T05:42:53.350445 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN METERED running 1.48.8 connected started full enabled enabled enabled missing enabled no (guessed) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu budgie 24.04. https://bugs.launchpad.net/bugs/2085183 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2085314] Re: systemd-netowrk segfault (question #819069)
This is systemd bug whitch was issued here: https://github.com/systemd/systemd/issues/32254 ** Bug watch added: github.com/systemd/systemd/issues #32254 https://github.com/systemd/systemd/issues/32254 -- 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/2085314 Title: systemd-netowrk segfault (question #819069) Status in systemd package in Ubuntu: New Bug description: [545051.196840] systemd-network[1395597]: segfault at 7ffd0b106ff8 ip 732937dbbb9c sp 7ffd0b107000 error 6 in libsystemd-shared-255.so[1bbb9c,732937c6a000+247000] likely on CPU 15 (core 15, socket 0) [545051.196849] Code: 49 01 c1 41 f6 c1 07 75 7d 49 8b 01 49 89 42 08 48 83 c4 08 89 d0 5b 41 5c 41 5d 5d c3 90 83 e1 04 0f 84 97 00 00 00 8b 77 28 af e5 ff ff 41 89 02 89 c2 41 89 41 28 83 fa ff 74 31 41 0f b6 [270850.754339] systemd-network[700716]: segfault at 7ffd54bfbff8 ip 717ac19bb897 sp 7ffd54bfc000 error 6 in libsystemd-shared-255.so[1bb897,717ac186a000+247000] likely on CPU 10 (core 10, socket 0) [270850.754347] Code: 00 00 b8 f4 ff ff ff e9 45 ff ff ff 0f 1f 80 00 00 00 00 49 89 f2 48 85 ff 0f 84 54 04 00 00 55 49 89 f9 48 89 e5 41 55 41 54 <53> 48 83 ec 08 0f b6 4f 2f 89 c8 83 e0 03 3c 01 0f 84 13 01 00 00 [292219.943345] systemd-network[755659]: segfault at 7fff00f4eff8 ip 7442d3fc4118 sp 7fff00f4f000 error 6 in libsystemd-shared-255.so[1c4118,7442d3e6a000+247000] likely on CPU 2 (core 2, socket 0) [292219.943350] Code: 35 53 eb 0f 00 48 8d 3d 36 d2 12 00 e8 41 64 00 00 e8 3c a2 ea ff e8 17 fd ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 e5 <41> 55 49 89 d5 41 54 49 89 cc 53 48 89 fb 48 83 ec 08 e8 51 77 ff [296437.649671] systemd-network[766382]: segfault at 7ffc7a3a5ff8 ip 7d1ca4dc4122 sp 7ffc7a3a6000 error 6 in libsystemd-shared-255.so[1c4122,7d1ca4c6a000+247000] likely on CPU 5 (core 5, socket 0) [296437.649677] Code: 12 00 e8 41 64 00 00 e8 3c a2 ea ff e8 17 fd ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 e5 41 55 49 89 d5 41 54 49 89 cc <53> 48 89 fb 48 83 ec 08 e8 51 77 ff ff 83 f8 ff 0f 84 88 00 00 00 More and more segfaults. Please update systemd package in 24.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.4 [modified: usr/lib/systemd/system/rc-local.service] Uname: Linux 6.11.3-x64v4-xanmod2 x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Tue Oct 22 06:40:50 2024 InstallationDate: Installed on 2024-10-08 (14 days ago) InstallationMedia: Ubuntu-Server 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911.4) MachineType: Gigabyte Technology Co., Ltd. X670 GAMING X AX V2 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.3-x64v4-xanmod2 root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off nosmt amd_pstate=disable RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-10-08 (14 days ago) dmi.bios.date: 05/22/2024 dmi.bios.release: 5.34 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X670 GAMING X AX V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF30:bd05/22/2024:br5.34:svnGigabyteTechnologyCo.,Ltd.:pnX670GAMINGXAXV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX670GAMINGXAXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X670 MB dmi.product.name: X670 GAMING X AX V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2085314/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
No worries Krister, I'm sorry that it dragged out as long as it did, but we got there in the end. Thanks for tracking down the bug in the first place and getting the patch merged upstream! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: Fix Released Status in e2fsprogs source package in Jammy: Fix Released Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: Won't Fix Status in e2fsprogs source package in Noble: Fix Released Status in e2fsprogs source package in Oracular: Fix Released Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2085157] [NEW] mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found
Public bug reported: I recently did an 24.10 install (on s390x, but I think this doesn't matter) and was surprised that the system hangs during the post-install reboot. Investigation showed that this happens if the installer applies updates, which is done by default, if there is proper network connectivity and archive access. In case of an install where I disabled the network, hence an offline install was done, the installation incl. post-install reboot was successful. So I took such a successfully installed system (where no updates were applied) and noticed that currently the available updates are: $ apt list --upgradable iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2] linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from: 6.11.0-8.8] So seemed to be kernel related, hence tried to update the kernel manually: $ sudo apt install linux-image-generic/oracular-updates Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for 'linux-image-generic' Upgrading: linux-generic linux-image-generic linux-tools-common linux-headers-generic linux-libc-dev Installing dependencies: linux-headers-6.11.0-9 linux-modules-extra-6.11.0-9-generic linux-headers-6.11.0-9-generic linux-tools-6.11.0-9 linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic linux-modules-6.11.0-9-generic Suggested packages: fdutils linux-tools Summary: Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1 Download size: 65.3 MB Space needed: 165 MB / 21.2 GB available └─ in /boot: 43.1 MB / 1,876 MB available Continue? [Y/n] Y ... Setting up linux-generic (6.11.0-9.9) ... Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ] mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. Scanning processes... Scanning processor microcode... Scanning linux images... Pending kernel upgrade! Running kernel version: 6.11.0-8-generic Diagnostics: The currently running kernel version is not the expected kernel version 6.11.0-9-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. Failed to check for processor microcode upgrades. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. I noticed these two lines, that have been spit out by update-initramfs: update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ] mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Hence I tried to ran update-initramfs on the release kernel 6.11.0-8-8 and it happened there as well: $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-6.11.0-8-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL:
[Touch-packages] [Bug 2085157] Re: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found
$ env --unset=LD_PRELOAD ldd /usr/lib/s390x-linux-gnu/libgcc_s.so.1 linux-vdso64.so.1 (0x03ffca8fe000) libc.so.6 => /lib/s390x-linux-gnu/libc.so.6 (0x03ffabd0) /lib/ld64.so.1 (0x03ffac08) $ -- 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/2085157 Title: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found Status in initramfs-tools package in Ubuntu: New Bug description: I recently did an 24.10 install (on s390x, but I think this doesn't matter) and was surprised that the system hangs during the post- install reboot. Investigation showed that this happens if the installer applies updates, which is done by default, if there is proper network connectivity and archive access. In case of an install where I disabled the network, hence an offline install was done, the installation incl. post-install reboot was successful. So I took such a successfully installed system (where no updates were applied) and noticed that currently the available updates are: $ apt list --upgradable iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2] linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from: 6.11.0-8.8] So seemed to be kernel related, hence tried to update the kernel manually: $ sudo apt install linux-image-generic/oracular-updates Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for 'linux-image-generic' Upgrading: linux-generic linux-image-generic linux-tools-common linux-headers-generic linux-libc-dev Installing dependencies: linux-headers-6.11.0-9 linux-modules-extra-6.11.0-9-generic linux-headers-6.11.0-9-generic linux-tools-6.11.0-9 linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic linux-modules-6.11.0-9-generic Suggested packages: fdutils linux-tools Summary: Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1 Download size: 65.3 MB Space needed: 165 MB / 21.2 GB available └─ in /boot: 43.1 MB / 1,876 MB available Continue? [Y/n] Y ... Setting up linux-generic (6.11.0-9.9) ... Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ] mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. Scanning processes... Scanning processor microcode... Scanning linux images... Pending kernel upgrade! Running kernel version: 6.11.0-8-generic Diagnostics: The currently running kernel version is not the expected kernel version 6.11.0-9-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. Failed to check for processor microcode upgrades. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. I noticed these two lines, that have been spit out by update-initramfs: update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr
[Touch-packages] [Bug 2064435] Re: Merge openssh from Debian unstable for oracular
** Tags removed: needs-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2064435 Title: Merge openssh from Debian unstable for oracular Status in openssh package in Ubuntu: Fix Released Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1:9.7p1-4 Ubuntu: 1:9.6p1-3ubuntu13 Other teams have maintained this package's merge in the past. If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. If this merge pulls in a new upstream version, also consider adding an entry to the Oracular Release Notes: https://discourse.ubuntu.com/c/release/38 ### New Debian Changes ### openssh (1:9.7p1-4) unstable; urgency=medium * Rework systemd readiness notification and socket activation patches to not link against libsystemd (the former via an upstream patch). * Force -fzero-call-used-regs=used not to be used on ppc64el (it's unsupported, but configure fails to detect this). -- Colin Watson Wed, 03 Apr 2024 12:06:08 +0100 openssh (1:9.7p1-3) unstable; urgency=medium * Fix gssapi-keyex declaration further (thanks, Andreas Hasenack; LP: #2053146). * Extend -fzero-call-used-regs check to catch m68k gcc bug (closes: #1067243). * debian/tests/regress: Set a different IP address for UNKNOWN. * Re-enable ssh-askpass-gnome on all architectures. * regress: Redirect conch stdin from /dev/zero (re-enables conch interop tests). * Drop 'Work around RSA SHA-2 signature issues in conch' patch (no longer needed now that Twisted is fixed). -- Colin Watson Sun, 31 Mar 2024 11:55:38 +0100 openssh (1:9.7p1-2) unstable; urgency=medium [ Simon McVittie ] * d/control, d/rules: Disable ssh-askpass-gnome on 32-bit, except i386 (closes: #1066847). -- Colin Watson Thu, 14 Mar 2024 11:45:12 + openssh (1:9.7p1-1) unstable; urgency=medium * Add the isolation-container restriction to the 'regress' autopkgtest. Our setup code wants to ensure that the haveged service is running, and furthermore at least the agent-subprocess test assumes that there's an init to reap zombie processes and doesn't work in (e.g.) autopkgtest-virt-unshare. * New upstream release (https://www.openssh.com/releasenotes.html#9.7p1): - ssh(1), sshd(8): add a 'global' ChannelTimeout type that watches all open channels and will close all open channels if there is no traffic on any of them for the specified interval. This is in addition to the existing per-channel timeouts added recently. This supports situations like having both session and x11 forwarding channels open where one may be idle for an extended period but the other is actively used. The global timeout could close both channels when both have been idle for too long (closes: #165185). - All: make DSA key support compile-time optional, defaulting to on. - sshd(8): don't append an unnecessary space to the end of subsystem arguments (bz3667) - ssh(1): fix the multiplexing 'channel proxy' mode, broken when keystroke timing obfuscation was added. (GHPR#463) - ssh(1), sshd(8): fix spurious configuration parsing errors when options that accept array arguments are overridden (bz3657). - ssh-agent(1): fix potential spin in signal handler (bz3670) - Many fixes to manual pages and other documentation. - Greatly improve interop testing against PuTTY. * Skip utimensat test on ZFS, since it seems to leave the atime set to 0. * Allow passing extra options to debian/tests/regress, for debugging. * Fix gssapi-keyex declaration, broken when rebasing onto 8.9p1 (LP: #2053146). -- Colin Watson Thu, 14 Mar 2024 10:47:58 + openssh (1:9.6p1-5) unstable; urgency=medium * Restore systemd template unit for per-connection sshd instances, although without any corresponding .socket unit for now; this is mainly for use with the forthcoming systemd-ssh-generator (closes: #1061516). It's now called sshd@.service, since unlike the main service there's no need to be concerned about compatibility with the slightly confusing 'ssh' service name that Debian has traditionally used. -- Colin Watson Wed, 06 Mar 2024 09:45:56 + openssh (1:9.6p1-4) unstable; urgency=medium * Add sshd_config checksums for 1:9.2p1-1 to ucf reference file, and add a test to ensure it doesn't get out of date again. * Drop manual adjustment of OpenSSL dependencies; OpenSSH relaxed its checks for OpenSSL >= 3 in 9.4p1. * Build-depend on pkgconf rather than pkg-config. * Adjust debian/copyright to handle the
[Touch-packages] [Bug 2085183] Re: wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu bud
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2085183 Title: wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu budgie 24.04. Status in network-manager package in Ubuntu: New Bug description: wifi disconnects randomly every few moments after logging in and have to detach and insert wifi adapter to fix it and this problem didn't ever happened in ubuntu budgie 24.04. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: network-manager 1.48.8-1ubuntu3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Tue Oct 22 06:49:21 2024 InstallationDate: Installed on 2024-07-14 (100 days ago) InstallationMedia: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' RfKill: 6: phy6: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to oracular on 2024-10-10 (11 days ago) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2024-10-22T05:42:53.350445 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN METERED running 1.48.8 connected started full enabled enabled enabled missing enabled no (guessed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2085183/+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 2085314] [NEW] systemd-netowrk segfault (question #819069)
Public bug reported: [545051.196840] systemd-network[1395597]: segfault at 7ffd0b106ff8 ip 732937dbbb9c sp 7ffd0b107000 error 6 in libsystemd-shared-255.so[1bbb9c,732937c6a000+247000] likely on CPU 15 (core 15, socket 0) [545051.196849] Code: 49 01 c1 41 f6 c1 07 75 7d 49 8b 01 49 89 42 08 48 83 c4 08 89 d0 5b 41 5c 41 5d 5d c3 90 83 e1 04 0f 84 97 00 00 00 8b 77 28 af e5 ff ff 41 89 02 89 c2 41 89 41 28 83 fa ff 74 31 41 0f b6 [270850.754339] systemd-network[700716]: segfault at 7ffd54bfbff8 ip 717ac19bb897 sp 7ffd54bfc000 error 6 in libsystemd-shared-255.so[1bb897,717ac186a000+247000] likely on CPU 10 (core 10, socket 0) [270850.754347] Code: 00 00 b8 f4 ff ff ff e9 45 ff ff ff 0f 1f 80 00 00 00 00 49 89 f2 48 85 ff 0f 84 54 04 00 00 55 49 89 f9 48 89 e5 41 55 41 54 <53> 48 83 ec 08 0f b6 4f 2f 89 c8 83 e0 03 3c 01 0f 84 13 01 00 00 [292219.943345] systemd-network[755659]: segfault at 7fff00f4eff8 ip 7442d3fc4118 sp 7fff00f4f000 error 6 in libsystemd-shared-255.so[1c4118,7442d3e6a000+247000] likely on CPU 2 (core 2, socket 0) [292219.943350] Code: 35 53 eb 0f 00 48 8d 3d 36 d2 12 00 e8 41 64 00 00 e8 3c a2 ea ff e8 17 fd ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 e5 <41> 55 49 89 d5 41 54 49 89 cc 53 48 89 fb 48 83 ec 08 e8 51 77 ff [296437.649671] systemd-network[766382]: segfault at 7ffc7a3a5ff8 ip 7d1ca4dc4122 sp 7ffc7a3a6000 error 6 in libsystemd-shared-255.so[1c4122,7d1ca4c6a000+247000] likely on CPU 5 (core 5, socket 0) [296437.649677] Code: 12 00 e8 41 64 00 00 e8 3c a2 ea ff e8 17 fd ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 e5 41 55 49 89 d5 41 54 49 89 cc <53> 48 89 fb 48 83 ec 08 e8 51 77 ff ff 83 f8 ff 0f 84 88 00 00 00 More and more segfaults. Please update systemd package in 24.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.4 [modified: usr/lib/systemd/system/rc-local.service] Uname: Linux 6.11.3-x64v4-xanmod2 x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Tue Oct 22 06:40:50 2024 InstallationDate: Installed on 2024-10-08 (14 days ago) InstallationMedia: Ubuntu-Server 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911.4) MachineType: Gigabyte Technology Co., Ltd. X670 GAMING X AX V2 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.3-x64v4-xanmod2 root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off nosmt amd_pstate=disable RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-10-08 (14 days ago) dmi.bios.date: 05/22/2024 dmi.bios.release: 5.34 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X670 GAMING X AX V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF30:bd05/22/2024:br5.34:svnGigabyteTechnologyCo.,Ltd.:pnX670GAMINGXAXV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX670GAMINGXAXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X670 MB dmi.product.name: X670 GAMING X AX V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble systemd -- 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/2085314 Title: systemd-netowrk segfault (question #819069) Status in systemd package in Ubuntu: New Bug description: [545051.196840] systemd-network[1395597]: segfault at 7ffd0b106ff8 ip 732937dbbb9c sp 7ffd0b107000 error 6 in libsystemd-shared-255.so[1bbb9c,732937c6a000+247000] likely on CPU 15 (core 15, socket 0) [545051.196849] Code: 49 01 c1 41 f6 c1 07 75 7d 49 8b 01 49 89 42 08 48 83 c4 08 89 d0 5b 41 5c 41 5d 5d c3 90 83 e1 04 0f 84 97 00 00 00 8b 77 28 af e5 ff ff 41 89 02 89 c2 41 89 41 28 83 fa ff 74 31 41 0f b6 [270850.754339] systemd-network[700716]: segfault at 7ffd54bfbff8 ip 717ac19bb897 sp 7ffd54bfc000 error 6 in libsystemd-shared-255.so[1bb897,717ac186a000+247000] likely on CPU 10 (core 10, socket 0) [270850.754347] Code: 00 00 b8 f4 ff ff ff e9 45 ff ff ff 0f 1f 80 00 00 00 00 49 89 f2 48 85 ff 0f 84 54 04 00 00 55 49 89 f9 48 89 e5 41 55 41 54 <53> 48 83 ec 08 0f b6 4f 2f 89 c8 83 e0 03 3c 01 0f 84
[Touch-packages] [Bug 2085157] Re: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found
This is re-createable all time, a system is in place for further investigation (remote access) and testing. -- 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/2085157 Title: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found Status in initramfs-tools package in Ubuntu: New Bug description: I recently did an 24.10 install (on s390x, but I think this doesn't matter) and was surprised that the system hangs during the post- install reboot. Investigation showed that this happens if the installer applies updates, which is done by default, if there is proper network connectivity and archive access. In case of an install where I disabled the network, hence an offline install was done, the installation incl. post-install reboot was successful. So I took such a successfully installed system (where no updates were applied) and noticed that currently the available updates are: $ apt list --upgradable iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2] linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8] linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from: 6.11.0-8.8] So seemed to be kernel related, hence tried to update the kernel manually: $ sudo apt install linux-image-generic/oracular-updates Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for 'linux-image-generic' Upgrading: linux-generic linux-image-generic linux-tools-common linux-headers-generic linux-libc-dev Installing dependencies: linux-headers-6.11.0-9 linux-modules-extra-6.11.0-9-generic linux-headers-6.11.0-9-generic linux-tools-6.11.0-9 linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic linux-modules-6.11.0-9-generic Suggested packages: fdutils linux-tools Summary: Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1 Download size: 65.3 MB Space needed: 165 MB / 21.2 GB available └─ in /boot: 43.1 MB / 1,876 MB available Continue? [Y/n] Y ... Setting up linux-generic (6.11.0-9.9) ... Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] Progress: [ 96%] [███▋ ] update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ] mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Building bootmap in '/boot' Adding IPL section 'ubuntu' (default) Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Run /lib/s390-tools/zipl_helper.device-mapper 252:1 Preparing boot device for LD-IPL: dm-0. Done. Scanning processes... Scanning processor microcode... Scanning linux images... Pending kernel upgrade! Running kernel version: 6.11.0-8-generic Diagnostics: The currently running kernel version is not the expected kernel version 6.11.0-9-generic. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. Failed to check for processor microcode upgrades. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. I noticed these two lines, that have been spit out by update-initramfs: update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋ ] mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found Hence I tried to
