[Touch-packages] [Bug 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in mesa package in Ubuntu: Confirmed Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1946621/+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 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe
Given that llvm12 is in main for Focal and Impish maybe it should be for Hirsute too? ** Description changed: - It's not possible to install libgl1-mesa-dri from hirsute-updates on a - system that does not have universe enabled because it depends on - libllvm12 from universe. This was not the case with the version of - libgl1-mesa-dri in the release pocket because it depended upon - libllvm11. + It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU + bug 1932311) on a system that does not have universe enabled because it + depends on libllvm12 from universe. This was not the case with the + version of libgl1-mesa-dri in the release pocket because it depended + upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable + libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 - Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), + Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 ** Changed in: mesa (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1949116 Title: libgl1-mesa-dri depends on libllvm12 from universe Status in mesa package in Ubuntu: New Bug description: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 To manage notifications abo
[Touch-packages] [Bug 1949116] [NEW] libgl1-mesa-dri depends on libllvm12 from universe
Public bug reported: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 ** Affects: mesa (Ubuntu) Importance: Critical Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1949116 Title: libgl1-mesa-dri depends on libllvm12 from universe Status in mesa package in Ubuntu: New Bug description: It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU bug 1932311) on a system that does not have universe enabled because it depends on libllvm12 from universe. This was not the case with the version of libgl1-mesa-dri in the release pocket because it depended upon libllvm11. (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not installable E: Unable to correct problems, you have held broken packages. (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri Package: libgl1-mesa-dri Architecture: amd64 Version: 21.0.3-0ubuntu0.3 Multi-Arch: same Priority: optional Section: libs Source: mesa Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian X Strike Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 37016 Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4) Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb This is blocking some CPC builds: https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1949116/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
Hello Dimitri, or anyone else affected, Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.664.32 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: New Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Committed Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: New Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1920836] Re: Show Extended Security Maintenence status
@robert, @chad.smith - would you like me to revert the commit from the ubuntu/focal branch for this https://git.launchpad.net/software- properties ? -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
I followed the test case on a focal chroot whoose sources.list file I modified to impish and the package install did not fail. Preparing to unpack .../7-libsignon-glib2_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking libsignon-glib2:amd64 (2.1-3ubuntu0.21.10) ... Selecting previously unselected package gir1.2-signon-2.0:amd64. Preparing to unpack .../8-gir1.2-signon-2.0_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.10) ... Replacing files in old package gir1.2-signon-1.0 (1.14+17.04.20161117-0ubuntu5) ... Preparing to unpack .../9-libsignon-glib-dev_2.1-3ubuntu0.21.10_amd64.deb ... Unpacking libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.10) over (1.14+17.04.20161117-0ubuntu5) ... Setting up libtirpc-common (1.3.2-2) ... Setting up libsepol1-dev:amd64 (3.1-1ubuntu2) ... Setting up libfakeroot:amd64 (1.25.3-1.1ubuntu2) ... Setting up fakeroot (1.25.3-1.1ubuntu2) ... Setting up rpcsvc-proto (1.4.2-0ubuntu5) ... Setting up libffi8:amd64 (3.4.2-1ubuntu5) ... Setting up libc-dev-bin (2.34-0ubuntu3) ... Setting up libtirpc3:amd64 (1.3.2-2) ... Setting up libselinux1-dev:amd64 (3.1-3build2) ... Setting up libglib2.0-0:amd64 (2.68.4-1ubuntu1) ... No schema files found: doing nothing. Setting up libglib2.0-bin (2.68.4-1ubuntu1) ... Setting up libsignon-glib2:amd64 (2.1-3ubuntu0.21.10) ... Setting up libtirpc-dev:amd64 (1.3.2-2) ... Setting up libnsl2:amd64 (1.3.0-2build1) ... Setting up libgirepository-1.0-1:amd64 (1.68.0-1build2) ... Setting up libglib2.0-dev-bin (2.68.4-1ubuntu1) ... Setting up gir1.2-glib-2.0:amd64 (1.68.0-1build2) ... Setting up libnsl-dev:amd64 (1.3.0-2build1) ... Setting up gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.10) ... Setting up libc6-dev:amd64 (2.34-0ubuntu3) ... Setting up libmount-dev:amd64 (2.36.1-8ubuntu2) ... Setting up libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.10) ... Setting up libglib2.0-dev:amd64 (2.68.4-1ubuntu1) ... Processing triggers for libc-bin (2.34-0ubuntu3) ... ** Tags removed: verification-needed verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Committed Status in libsignon-glib source package in Impish: Fix Committed Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
I followed the test case on a focal system whose sources.list file I changed to hirsute and had no issues. Preparing to unpack .../8-gir1.2-signon-2.0_2.1-3ubuntu0.21.04_amd64.deb ... Unpacking gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.04) ... Replacing files in old package gir1.2-signon-1.0 (1.14+17.04.20161117-0ubuntu5) ... Preparing to unpack .../9-libsignon-glib-dev_2.1-3ubuntu0.21.04_amd64.deb ... Unpacking libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.04) over (1.14+17.04.20161117-0ubuntu5) ... Setting up libtirpc-common (1.3.1-1build1) ... Setting up libsepol1-dev:amd64 (3.1-1ubuntu1) ... Setting up libffi8ubuntu1:amd64 (3.4~20200819gead65ca871-0ubuntu5) ... Setting up libfakeroot:amd64 (1.25.3-1.1ubuntu2) ... Setting up fakeroot (1.25.3-1.1ubuntu2) ... Setting up rpcsvc-proto (1.4.2-0ubuntu4) ... Setting up libc-dev-bin (2.33-0ubuntu5) ... Setting up libtirpc3:amd64 (1.3.1-1build1) ... Setting up libselinux1-dev:amd64 (3.1-3build1) ... Setting up libglib2.0-0:amd64 (2.68.1-1~ubuntu21.04.1) ... No schema files found: doing nothing. Setting up libglib2.0-bin (2.68.1-1~ubuntu21.04.1) ... Setting up libsignon-glib2:amd64 (2.1-3ubuntu0.21.04) ... Setting up libtirpc-dev:amd64 (1.3.1-1build1) ... Setting up libnsl2:amd64 (1.3.0-0ubuntu3) ... Setting up libgirepository-1.0-1:amd64 (1.66.1-1build1) ... Setting up libglib2.0-dev-bin (2.68.1-1~ubuntu21.04.1) ... Setting up gir1.2-glib-2.0:amd64 (1.66.1-1build1) ... Setting up libnsl-dev:amd64 (1.3.0-0ubuntu3) ... Setting up gir1.2-signon-2.0:amd64 (2.1-3ubuntu0.21.04) ... Setting up libc6-dev:amd64 (2.33-0ubuntu5) ... Setting up libmount-dev:amd64 (2.36.1-7ubuntu2) ... Setting up libsignon-glib-dev:amd64 (2.1-3ubuntu0.21.04) ... Setting up libglib2.0-dev:amd64 (2.68.1-1~ubuntu21.04.1) ... Processing triggers for libc-bin (2.33-0ubuntu5) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Committed Status in libsignon-glib source package in Impish: Fix Committed Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/rsync/+git/rsync/+merge/410962 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Won't Fix Status in rsync source package in Bionic: In Progress Status in rsync source package in Focal: In Progress Bug description: Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: MATE Date: Fri Sep 18 18:27:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (621 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1896251/+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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
** Description changed:
+ ** SRU TEMPLATE DRAFT **
+
+ [Impact]
+
+
+ [Test Plan]
+
+
+ [Where problems could occur]
+
+
+ [Other Info]
+
+
+ [Original Description]
+
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
+ I believe the current behaviour is buggy. This is confirmed when the
+ following line is executed:
- I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
+ if (loop_timeout >= 0 &&
+ now.tv_sec - start >= loop_timeout) {
+ printf("IP-Config: no response after %d "
+ "secs - giving up\n", loop_timeout);
+ rc = -1;
+ goto bail;
+ }
-
- if (loop_timeout >= 0 &&
- now.tv_sec - start >= loop_timeout) {
- printf("IP-Config: no response after %d "
-"secs - giving up\n", loop_timeout);
- rc = -1;
- goto bail;
- }
-
-
- 'loop_timeout' is the user-specified time-out. With a value of 2, in case of
error, this line prints:
+ 'loop_timeout' is the user-specified time-out. With a value of 2, in
+ case of error, this line prints:
IP-Config: no response after 2 secs - giving up
-
- So it thinks that it waited 2 seconds - however, in reality it had actually
waited for 10 seconds.
+ So it thinks that it waited 2 seconds - however, in reality it had
+ actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually used
never exceeds the user-specified timeout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
New
Bug description:
** SRU TEMPLATE DRAFT **
[Impact]
[Test Plan]
[Where problems could occur]
[Other Info]
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is ex
[Touch-packages] [Bug 1942385] Re: [SOF - sof-bytcht rt5640, playback] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1942385 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing beep sound and audio from zoom, firefox, or vlc. It might play media for some seconds then beep. This has something to do with pipewire and sof driver and S16_LE format.( I read online). If I switch the profile Play HiFi quality Music in pavucontrol it does correct the beep sound for some few seconds then it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bret 1249 F pulseaudio /dev/snd/pcmC0D0c: bret 1249 F...m pulseaudio /dev/snd/pcmC0D0p: bret 1249 F...m pulseaudio /dev/snd/timer: bret 1249 f pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Sep 2 05:25:01 2021 InstallationDate: Installed on 2021-08-29 (3 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210612) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - sof-bytcht rt5640 Symptom_PulseAudioLog: Sep 02 05:24:14 toshiba systemd[826]: pulseaudio.service: Deactivated successfully. Sep 02 05:24:25 toshiba systemd[826]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2015 dmi.bios.release: 5.20 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.20 dmi.board.name: 0700 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 5.20 dmi.modalias: dmi:bvnINSYDECorp.:bvr5.20:bd11/02/2015:br5.20:efr5.20:svnTOSHIBA:pnSATELLITEClickMiniL9W-B:pvrPDW0FE-002005EN:skuINVALID:rvnFF50:rn0700:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE Click Mini L9W-B dmi.product.sku: INVALID dmi.product.version: PDW0FE-002005EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1942385/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** Tags added: rls-jj-incoming -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1943530] Re: link libkrb5 with openssl
** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1943530 Title: link libkrb5 with openssl Status in krb5 package in Ubuntu: Incomplete Bug description: In Ubuntu we provide a cryptographic core based on a small set of packages that we FIPS certify [0]. Applications and libraries should not bundle their own crypto code but should use the cryptographic core to benefit from the certification, but also importantly to reduce bugs due to small cryptographic libraries that that are not studied as much as more popular counterparts. This bug is to change libkrb5 to use the openssl crypto code instead of bundling its own on the next ubuntu release. [0]. https://ubuntu.com/security/fips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1943530/+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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
New
Bug description:
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in case of
error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had actually
waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+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 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
Ubuntu focuses on netplan with systemd-networkd or Network Manager, and ifupdown isn't really supported any more except for edge cases not supported by netplan. Since vlan is supported by netplan, I'm therefore marking this Won't Fix for the Ubuntu development release. Note that ifupdown in Ubuntu barely differs from Debian now, so it seems likely to me that there would be no difference in behaviour from Debian here. ** Changed in: ifupdown (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 ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention Status in ifupdown package in Ubuntu: Won't Fix Bug description: The regular expressions used in /etc/network/if-post-down.d/vlan and /etc/network/if-pre-up.d/vlan do not match the name of my network card enp4s0f0. This can be fixed by broadening the regular expression. This is only a problem when the device is a vlan device! See below for the fix that worked on my system. if-pre-up: #!/bin/sh # Most of this stuff is to enable vlans case "$IFACE" in # Ignore any alias (#272891) which uses : *:*) exit 0 ;; vlan0*) vconfig set_name_type VLAN_PLUS_VID VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*) vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*) vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; *.0*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *.*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *) exit 0 ;; esac if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then if [ ! -x /sbin/vconfig ]; then exit 0 fi if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE" exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi # This is not vlan specific, and should actually go somewhere else. if [ -n "$IF_HW_MAC_ADDRESS" ]; then ip link set $IFACE address $IF_HW_MAC_ADDRESS fi if-post-down: #!/bin/sh # If IFACE is an automagic vlan interface (without the vlan-raw-device # parameter) then let's try to discover the magic here.. Another way would be # to just probe for the right device name in /proc/net/vlan case "$IFACE" in # Ignore any alias (#272891) *:*) exit 0 ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; # Test for vlan raw device (#196890, #292648) *) [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 ;; esac if [ ! -x /sbin/vconfig ]; then exit 0 fi vconfig rem $IFACE To manage notifications about this
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
@Khaled El Mously (kmously)
I don't see this piece of code in the klibc upstream project[0]
Is this something you only reproduce in Bionic/18.04LTS ?
Since your fix is not found anywhere else, I would be tempted to assume that it
could be affecting other releases of Ubuntu and possibly more.
Could you please erport a bug and submit your patch by making sure the
upstream klibc project adopts it ? It would help get some traction in
order to SRU this patch into Ubuntu.
If it needs to be a UBUNTU_SAUCE only, please provide rationale.
- Eric
[0] - https://git.kernel.org/pub/scm/libs/klibc/klibc.git/about/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
New
Bug description:
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in case of
error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had actually
waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+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 1948698] Re: Update tzdata to version 2021e
This bug was fixed in the package tzdata - 2021e-0ubuntu0.21.04
---
tzdata (2021e-0ubuntu0.21.04) hirsute; urgency=medium
* New upstream release (LP: #1948698), affecting the following timestamp:
- Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.
* Update ICU timezone data files which are utilized by php to 2021a3.
* Dropped the patches which were cherry-picked from upstream as the
situation is somewhat less confused now.
-- Brian Murray Mon, 25 Oct 2021 16:17:48 -0700
** Changed in: tzdata (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1948698] Re: Update tzdata to version 2021e
This bug was fixed in the package tzdata - 2021e-0ubuntu0.18.04
---
tzdata (2021e-0ubuntu0.18.04) bionic; urgency=medium
* New upstream release (LP: #1948698), affecting the following timestamp:
- Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.
* Dropped the patches which were cherry-picked from upstream as the
situation is somewhat less confused now.
-- Brian Murray Tue, 26 Oct 2021 09:03:37 -0700
--
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/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1948698] Re: Update tzdata to version 2021e
This bug was fixed in the package tzdata - 2021e-0ubuntu0.21.10
---
tzdata (2021e-0ubuntu0.21.10) impish; urgency=medium
* New upstream release (LP: #1948698), affecting the following timestamp:
- Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.
* Update ICU timezone data files which are utilized by php to 2021a3.
* Dropped the patches which were cherry-picked from upstream as the
situation is somewhat less confused now.
-- Brian Murray Mon, 25 Oct 2021 15:52:44 -0700
** Changed in: tzdata (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
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/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1948698] Update Released
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1948698] Re: Update tzdata to version 2021e
This bug was fixed in the package tzdata - 2021e-0ubuntu0.20.04
---
tzdata (2021e-0ubuntu0.20.04) focal; urgency=medium
* New upstream release (LP: #1948698), affecting the following timestamp:
- Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.
* Update ICU timezone data files which are utilized by php to 2021a3.
* Dropped the patches which were cherry-picked from upstream as the
situation is somewhat less confused now.
-- Brian Murray Mon, 25 Oct 2021 16:58:28 -0700
** Changed in: tzdata (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1948698
Title:
Update tzdata to version 2021e
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Hirsute:
Fix Released
Status in tzdata source package in Impish:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
$region/$timezone = Asia/Gaza
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Asia/Gaza 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Pacific/Apia'));
print(str(tz.utcoffset(datetime(2021, 9, 26'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1948698/+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 1949089] [NEW] systemd randomly fails to activate mount units in Ubuntu Core 18
Public bug reported: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc-flip- flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Attachment added: "journald log" https://bugs.launchpad.net/bugs/1949089/+attachment/5536819/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1946513] Re: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
I don't know much, but this issue affects my Core2Duo E8200 system as well. Every Ubuntu and it's official flavors fail to install on this C2D E8200 system of mine. And I am doing fresh/clean install, not upgrades, which also are failing for some people with the same "initramfs-tools error, exit code 1" as can be found on google search But on my i7 2630qm system, Ubuntu and flavors complete fresh install nicely. No error to be found anywhere. And I have no reason to believe that doing upgrades from previous Ubuntu versions would fail in my Core i7 2630QM system. I marked another bug (1947854) as this one's duplicate, because I believe the issue to be the same, though that person who filed bug 1947854 has provided lots of logs and files, I believe him to be more of a technical person than I am. What that person (Ymir) is doing is not fresh install but is an upgrade from previous version. To the bug squashers, please forgive me for my lack of technical know how and for the lengthy comment. -- 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/1946513 Title: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 21.10 Package: initramfs-tools 0.140ubuntu6 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 8 12:36:07 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946513/+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 1947854] Re: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 1946513 *** https://bugs.launchpad.net/bugs/1946513 I believe bug 1946513 is related to this. I have marked this bug as duplicate of 1946513. If it happens to be not one, please forgive me, as it's my first time ever reporting or confirming a bug. -- 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/1947854 Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Installed via Gnome software, hangs on decrypting volume after reboot. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ymirv 12352 F pulseaudio /dev/snd/controlC3: ymirv 12352 F pulseaudio /dev/snd/controlC2: ymirv 12352 F pulseaudio /dev/snd/controlC0: ymirv 12352 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 20 09:28:09 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-01-16 (276 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82FN ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_u6oi4d@/vmlinuz-5.11.0-37-generic root=ZFS=rpool/ROOT/ubuntu_u6oi4d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to impish on 2021-10-18 (1 days ago) dmi.bios.date: 10/06/2020 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: FFCN15WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: 3192 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ARE05 dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrFFCN15WW(V1.03):bd10/06/2020:br1.15:efr1.15:svnLENOVO:pn82FN:pvrYoga613ARE05:skuLENOVO_MT_82FN_BU_idea_FM_Yoga613ARE05:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct31:cvrYoga613ARE05: dmi.product.family: Yoga 6 13ARE05 dmi.product.name: 82FN dmi.product.sku: LENOVO_MT_82FN_BU_idea_FM_Yoga 6 13ARE05 dmi.product.version: Yoga 6 13ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1947854/+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 1947854] Re: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 1946513 *** https://bugs.launchpad.net/bugs/1946513 ** This bug has been marked a duplicate of bug 1946513 package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1947854 Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Installed via Gnome software, hangs on decrypting volume after reboot. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ymirv 12352 F pulseaudio /dev/snd/controlC3: ymirv 12352 F pulseaudio /dev/snd/controlC2: ymirv 12352 F pulseaudio /dev/snd/controlC0: ymirv 12352 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 20 09:28:09 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-01-16 (276 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82FN ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_u6oi4d@/vmlinuz-5.11.0-37-generic root=ZFS=rpool/ROOT/ubuntu_u6oi4d ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-20-generic 5.13.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to impish on 2021-10-18 (1 days ago) dmi.bios.date: 10/06/2020 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: FFCN15WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: 3192 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ARE05 dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrFFCN15WW(V1.03):bd10/06/2020:br1.15:efr1.15:svnLENOVO:pn82FN:pvrYoga613ARE05:skuLENOVO_MT_82FN_BU_idea_FM_Yoga613ARE05:rvnLENOVO:rnLNVNB161216:rvr3192WIN:cvnLENOVO:ct31:cvrYoga613ARE05: dmi.product.family: Yoga 6 13ARE05 dmi.product.name: 82FN dmi.product.sku: LENOVO_MT_82FN_BU_idea_FM_Yoga 6 13ARE05 dmi.product.version: Yoga 6 13ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1947854/+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 1946513] Re: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1946513 Title: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 21.10 Package: initramfs-tools 0.140ubuntu6 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 8 12:36:07 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946513/+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 1949075] [NEW] Bluetooth headset not autoconnecting on power-on on 21.10
Public bug reported: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: Bluetooth headset not autoconnecting on power-on on 21.10 Status in bluez package in Ubuntu: New Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.pr
[Touch-packages] [Bug 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has m
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libnih (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: Confirmed Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has m
Same error, upgrading from updated 20.04. Jay's easy fix solved it good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances Status in libnih package in Ubuntu: Confirmed Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb /tmp/apt-dpkg-install-S93V5u/405-libnih1_1.0.3-12_amd64.deb Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libnih1 1.0.3-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 21 18:10:42 2021 DuplicateSignature: package:libnih1:1.0.3-6ubuntu2 Unpacking libnetaddr-ip-perl (4.079+dfsg-1build6) over (4.079+dfsg-1build5) ... dpkg: error processing archive /tmp/apt-dpkg-install-S93V5u/404-libnih-dbus1_1.0.3-12_amd64.deb (--unpack): package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-dbus1 which has multiple installed instances ErrorMessage: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: libnih Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed instances UpgradeStatus: Upgraded to impish on 2021-10-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+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 1949054] [NEW] Despite being enabled, `Mouse Keys` stops working after reboot
Public bug reported: if it is enabled and I reboot my device, `Mouse Keys` stops working i.e. when `Num Lock` is disabled, the numeric pad acts like the arrow keys; when `Num Lock` is enabled, the numeric pad can be used to input digits and arithmetic symbols in other words, `Mouse Keys` is completely ignored as if it wasn't enabled in the first place I expected the `Mouse Keys` function to be retained even after a reboot in order to make it work again, I have to disable `Mouse Keys` and enable it back ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libatk1.0-0 2.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 09:53:42 2021 InstallationDate: Installed on 2021-10-10 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: atk1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: atk1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to atk1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949054 Title: Despite being enabled, `Mouse Keys` stops working after reboot Status in atk1.0 package in Ubuntu: New Bug description: if it is enabled and I reboot my device, `Mouse Keys` stops working i.e. when `Num Lock` is disabled, the numeric pad acts like the arrow keys; when `Num Lock` is enabled, the numeric pad can be used to input digits and arithmetic symbols in other words, `Mouse Keys` is completely ignored as if it wasn't enabled in the first place I expected the `Mouse Keys` function to be retained even after a reboot in order to make it work again, I have to disable `Mouse Keys` and enable it back ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libatk1.0-0 2.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 09:53:42 2021 InstallationDate: Installed on 2021-10-10 (17 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: atk1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atk1.0/+bug/1949054/+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 1945288] Re: Search domains missing from resolv.conf stub
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1945288 Title: Search domains missing from resolv.conf stub Status in systemd package in Ubuntu: Confirmed Bug description: System is Mint 20.2, with the relevant packages taken from Ubuntu Focal. This is the output of `systemd-resolv --status vpn0`: Link 7 (vpn0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 10.0.0.53 DNS Servers: 10.0.0.53 DNS Domain: example.com example.com.rpz privatelink.blob.core.windows.net node.prd.lan.example.com node.stg.lan.example.com node.dev.lan.example.com However that last domain is missing from `/etc/resolv.conf` (symlink to `/run/systemd/resolve/stub-resolv.conf`), instead there is a line # Too many search domains configured, remaining ones ignored. According to resolv.conf(5) since glibc 2.26 the number of search domains should be unlimited, and installed is 2.31-0ubuntu9.3 VPN is PaloAlto GlobalProtect through the OpenConnect plugin on NetworkManager. Exact same setup and behaviour for a colleague using Pop!_OS 20.04 -- systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 Version table: *** 245.4-4ubuntu3.13 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3.11 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages libc-bin: Installed: 2.31-0ubuntu9.3 Candidate: 2.31-0ubuntu9.3 Version table: *** 2.31-0ubuntu9.3 100 100 /var/lib/dpkg/status 2.31-0ubuntu9.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 2.31-0ubuntu9 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945288/+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
