[Touch-packages] [Bug 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
I've tested 0.96.24.32.20 on 18.04, activating ubuntu pro through the magic workflow, detachig and activating again using the manual token one, it works as expected, marked as verified on B ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done verification-done-bionic verification-done-focal -- 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/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released 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 Jammy: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
** No longer affects: pam (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1977493 Title: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam- modules Status in Ubuntu on IBM z Systems: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in pam source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] Upgrade from Ubuntu 21.10 to 22.4 fails if pam_tally is present in the system's PAM config I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com [Test plan] Test 1 -- The pre-build.sh script run prior to generation of the upload tarball runs the test suite which includes an added test for this quirk to verify its correct operation. Test 2 -- Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed. Verify that the upgrade completes successfully with the addition of the new quirk, which should have no effect on a default install. Test 3 -- On an impish system, run 'do-release-upgrade -p' to use the tarball from -proposed. Verify that the upgrade completes successfully. [Where problems could occur] The addition of a quirk could prevent some users from upgrading, in which case a further SRU will be necessary. The new code is run very early in the upgrader and it should not be possible for the new code to leave the system in an inconsistent state mid-upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+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 1998470] Re: [23.04] re-add s390x vectorized crc32 support to zlib in lunar
** Summary changed: - re-add s390x vectorized crc32 support to zlib in lunar + [23.04] re-add s390x vectorized crc32 support to zlib in lunar ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1998470 Title: [23.04] re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
└─$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 42 not upgraded. Need to get 0 B/280 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: warning: files list file for package 'libpaper1:amd64' missing; assuming package has no files currently inst alled (Reading database ... 272799 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unava ilable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1977493 Title: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam- modules Status in Ubuntu on IBM z Systems: Fix Released Status in pam package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in pam source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] Upgrade from Ubuntu 21.10 to 22.4 fails if pam_tally is present in the system's PAM config I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com [Test plan] Test 1 -- The pre-build.sh script run prior to generation of the upload tarball runs the test suite which includes an added test for this quirk to verify its correct operation. Test 2 -- Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is
[Touch-packages] [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
** Also affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1977493 Title: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam- modules Status in Ubuntu on IBM z Systems: Fix Released Status in pam package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in pam source package in Jammy: New Status in ubuntu-release-upgrader source package in Jammy: Fix Released Bug description: [Impact] Upgrade from Ubuntu 21.10 to 22.4 fails if pam_tally is present in the system's PAM config I run do-release-upgrade and I got a message upgrade completed with errors. I rebooted the server and it is now in an undefined state between 21.10 and 22.04. Not all packages have been installed. I attach apt log and output of some commands: root@tuxmaker:~# cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=impish root@tuxmaker:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@tuxmaker:~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 1.4.0-11ubuntu2 is installed Recommends: update-motd but it is not installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@tuxmaker:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libpam-modules The following packages will be upgraded: libpam-modules 1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded. 4 not fully installed or removed. Need to get 0 B/279 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 401827 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack): new libpam-modules:s390x package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = pp...@de.ibm.com [Test plan] Test 1 -- The pre-build.sh script run prior to generation of the upload tarball runs the test suite which includes an added test for this quirk to verify its correct operation. Test 2 -- Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed. Verify that the upgrade completes successfully with the addition of the new quirk, which should have no effect on a default install. Test 3 -- On an impish system, run 'do-release-upgrade -p' to use the tarball from -proposed. Verify that the upgrade completes successfully. [Where problems could occur] The addition of a quirk could prevent some users from upgrading, in which case a further SRU will be necessary. The new code is run very early in the upgrader and it should not be possible for the new code to leave the system in an inconsistent state mid-upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+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 2003025] Re: systemd/resolved can't enable mdns permanently
# journalctl -b 0 --grep eno1 | cut -c22- kernel: igb :02:00.0 eno1: renamed from eth1 systemd-networkd[763]: eno1: Link UP kernel: igb :02:00.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX systemd-networkd[763]: eno1: Gained carrier kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready avahi-daemon[742]: Joining mDNS multicast group on interface eno1.IPv6 with address fe80::201:c0ff:fe21:3400. avahi-daemon[742]: New relevant interface eno1.IPv6 for mDNS. systemd-networkd[763]: eno1: Gained IPv6LL avahi-daemon[742]: Registering new address record for fe80::... on eno1.*. avahi-daemon[742]: Leaving mDNS multicast group on interface eno1.IPv6 with address fe80:: avahi-daemon[742]: Joining mDNS multicast group on interface eno1.IPv6 with address 2a02: avahi-daemon[742]: Registering new address record for 2a02:... on eno1.*. avahi-daemon[742]: Withdrawing address record for fe80::... on eno1. avahi-daemon[742]: Registering new address record for fdfc:... on eno1.*. systemd-networkd[763]: eno1: DHCPv4 address 192.168/24 via 192.168 avahi-daemon[742]: Joining mDNS multicast group on interface eno1.IPv4 with address 192.168. avahi-daemon[742]: New relevant interface eno1.IPv4 for mDNS. avahi-daemon[742]: Registering new address record for 192.168 on eno1.IPv4. systemd-networkd-wait-online[809]: managing: eno1 # resolvectl mdns Global: yes Link 2 (enp1s0): no Link 3 (eno1): no ... -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
Launchpad has imported 30 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1941170. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-03-20T15:49:58+00:00 isaac.bernadus wrote: Description of problem: Systemd-oomd is very aggressive when it comes to memory management. In fedora 33 I've been able to run quite a few apps without a problem but in fedora 34, the apps get killed way too quickly. Here's an example of atom getting killed by systemd-oomd: Mar 20 22:18:34 x505za systemd-oomd[1020]: Memory pressure for /user.slice/user-1000.slice/user@1000.service is greater than 10 for more than 10 seconds and there was reclaim activity Mar 20 22:18:34 x505za systemd[1604]: app-gnome-atom-11930.scope: systemd-oomd killed 47 process(es) in this unit. Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Deactivated successfully. Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Consumed 7.557s CPU time This event is triggered when around 70-80% of my memory is filled up despite still having space in swap. Version-Release number of selected component (if applicable): systemd 248 (v248~rc4-1.fc34) How reproducible: Always Steps to Reproduce: 1. Load up a bunch of apps to fill up memory 2. Wait for systemd-oomd to trigger reclaim activity 3. Actual results: Apps get killed very quickly Expected results: Apps to run normally until memory and swap is almost full Additional info: System Specs: Ryzen 3 2200u 4GB RAM Kernel 5.11.7-300.fc34.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/0 On 2021-03-20T16:44:30+00:00 isaac.bernadus wrote: Seems like if the memory gets filled fast enough, systemd will even decide to kill Gnome Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/1 On 2021-03-23T14:59:38+00:00 red wrote: Same problem here. The fedora defaults are too aggressive. They make systemd-oomd very trigger-happy (ManagedOOMMemoryPressureLimit=10% for 10 seconds) With 4GB and zram, you can barely use anything. With 2GB it is a task- massacre all the time. The defaults suggested in the manual (60% & 30s) still prevent excessive spinning while working way more predictably. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/2 On 2021-03-24T22:59:27+00:00 iolo wrote: I've noticed this too while testing Fedora Workstation 34 this week. I'll leave Netbeans or Brave running to go do something else, and I've got maybe about 4 GB of free RAM out of 8 GB total at that point. Then, some time later, I will try to go back to Netbeans or Brave, or whatever it is, only to find that it's been killed. I've never had anything like this happen before. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/3 On 2021-03-25T07:12:19+00:00 the.anitazha wrote: I will work on updating the pressure defaults now that the test week results have come in. I agree that the defaults are a bit aggressive, but that's what the test week and beta was meant to iron out. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/4 On 2021-03-30T09:04:29+00:00 the.anitazha wrote: I've submitted https://src.fedoraproject.org/rpms/systemd/pull- request/58# to bump pressure defaults to 50% for 20s. Hopefully these more conservative values will perform better for most people. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/5 On 2021-03-31T09:18:33+00:00 updates wrote: FEDORA-2021-8595b30af3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/comments/6 On 2021-04-01T02:04:06+00:00 updates wrote: FEDORA-2021-8595b30af3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8595b30af3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more
[Touch-packages] [Bug 2003644] Re: Cannot install python3-venv (broken dependence)
Sounds like a mirror issue. ** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/2003644 Title: Cannot install python3-venv (broken dependence) Status in python3-defaults package in Ubuntu: Invalid Bug description: When running `sudo apt-get install python3-venv` I get an error The following packages have unmet dependencies: python3.10-venv : Depends: python3.10 (= 3.10.6-1~22.04) but 3.10.6-1~22.04.2 is to be installed E: Unable to correct problems, you have held broken packages. The output of `apt policy python3.10` is below. My OS is Ubuntu 22.04.1 LTS. python3.10: Installed: 3.10.6-1~22.04.2 Candidate: 3.10.6-1~22.04.2 Version table: *** 3.10.6-1~22.04.2 100 100 /var/lib/dpkg/status 3.10.6-1~22.04 500 500 http://ubuntu.mirror.su.se/ubuntu jammy-updates/main amd64 Packages 3.10.4-3ubuntu0.1 500 500 http://ubuntu.mirror.su.se/ubuntu jammy-security/main amd64 Packages 3.10.4-3 500 500 http://ubuntu.mirror.su.se/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: python3-venv (not installed) ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 22 13:13:33 2023 InstallationDate: Installed on 2022-11-26 (56 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2003644/+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 2003527] Please test proposed package
Hello Sebastien, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.20 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- 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/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released 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 Jammy: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 1993370] Re: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic
** Changed in: software-properties (Ubuntu) Status: Fix Released => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/1993370 Title: Cannot install proprietary Broadcom WiFi drivers on Ubuntu Studio Kinetic Status in software-properties package in Ubuntu: Fix Committed Bug description: Hardware: HP Elitebook 8570p, 16 GB RAM, 120 GB SSD, 3rd Gen Intel Core i5, UEFI, no secure boot, Broadcom WiFi. OS: Ubuntu Studio Kinetic, Final ISO Steps to reproduce: 1. Boot the Ubuntu Studio ISO on a system with Broadcom WiFi, and install the system normally. (No encryption, allow Internet access during installation using some method of connectivity other than WiFi.) 2. Reboot and log into the newly installed system. 3. Open a terminal and run "sudo software-properties-kde". 4. Click "Additional Drivers" in the window that pops up. 5. Click "Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary)". Expected result: The Apply Changes button should become clickable, allowing the user to install the driver. Actual result: The button remains grayed out, and the following error message is printed in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 1063, in on_driver_selection_changed modules_package_obj = self.apt_cache[modules_package] TypeError: Expected a string or a pair of strings ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: software-properties-qt 0.99.27 ProcVersionSignature: Ubuntu 5.19.0-1007.7-lowlatency 5.19.7 Uname: Linux 5.19.0-1007-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Oct 18 21:33:51 2022 InstallationDate: Installed on 2022-10-19 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1993370/+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 1998324] Re: Missing changelog.Debian.gz from sysvinit-utils
This bug was fixed in the package sysvinit - 3.05-7ubuntu2 --- sysvinit (3.05-7ubuntu2) lunar; urgency=medium * d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu (LP: #2002789) -- Olivier Gayot Fri, 13 Jan 2023 11:33:36 +0100 ** Changed in: sysvinit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998324 Title: Missing changelog.Debian.gz from sysvinit-utils Status in sysvinit package in Ubuntu: Fix Released Bug description: The binary package sysvinit-utils does not include the changelog.Debian.gz file. Lintian reports it as an error: E: sysvinit-utils: no-changelog usr/share/doc/sysvinit- utils/changelog.Debian.gz (non-native package) I looked in the sysvinit-utils package in all releases of Ubuntu >= Bionic [1] and could not file anywhere ; whereas it's present in Debian [2]: It strongly suggests that our Delta from Debian is faulty. [1] https://packages.ubuntu.com/kinetic/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/jammy/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/focal/amd64/sysvinit-utils/filelist https://packages.ubuntu.com/bionic/amd64/sysvinit-utils/filelist [2] https://packages.debian.org/bullseye/amd64/sysvinit-utils/filelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998324/+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 2002789] Re: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1
This bug was fixed in the package sysvinit - 3.05-7ubuntu2 --- sysvinit (3.05-7ubuntu2) lunar; urgency=medium * d/rules: fix installation of 50-ubuntu-logging when building on Ubuntu (LP: #2002789) -- Olivier Gayot Fri, 13 Jan 2023 11:33:36 +0100 ** Changed in: sysvinit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2002789 Title: Missing 50-ubuntu-logging in sysvinit-utils 3.05-7ubuntu1 Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit package in Debian: New Bug description: The following file used to be provided by the lsb-base package in Ubuntu and it now supposed to be provided by the sysvinit-utils package. * lsb/init-functions.d/50-ubuntu-logging The file is Ubuntu specific but is not included in Ubuntu using a delta from Debian. Instead, the debian source tree includes the file but conditional statements in debian/rules makes it absent from the binary packages in Debian. Sadly, when moving the file from src:lsb to src:sysvinit, the conditional statements are not consistent anymore, resulting in the file being absent from the Ubuntu binary package as well. Affected version: sysvinit-utils 3.05-7ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2002789/+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 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar
This bug was fixed in the package zlib - 1:1.2.13.dfsg-1ubuntu4 --- zlib (1:1.2.13.dfsg-1ubuntu4) lunar; urgency=medium * Add d/p/1390.patch to not update strm.adler for raw streams on s390x (DFLTCC), otherwise libxml2 gets broken on s390x. LP: #2002511 -- Frank Heimes Wed, 11 Jan 2023 18:02:34 +0100 ** Changed in: zlib (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: Fix Committed Status in zlib package in Ubuntu: Fix Released Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
This bug was fixed in the package zlib - 1:1.2.13.dfsg-1ubuntu4
---
zlib (1:1.2.13.dfsg-1ubuntu4) lunar; urgency=medium
* Add d/p/1390.patch to not update strm.adler for raw streams on s390x
(DFLTCC), otherwise libxml2 gets broken on s390x. LP: #2002511
-- Frank Heimes Wed, 11 Jan 2023 18:02:34
+0100
** Changed in: zlib (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
In Progress
Status in zlib:
Fix Released
Status in zlib package in Ubuntu:
Fix Released
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
Fix Released
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 2003025] Re: systemd/resolved can't enable mdns permanently
Are there any errors in your journal about the config? Check journalctl -b 0 --grep eno1 for starters. Also just to double check, you are running the latest version of systemd in jammy, right? It should be 249.11-0ubuntu3.6. -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Thomas and Marc, thanks for the guidance and time spent here. :) I'll look into the SRU process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: Won't Fix Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
I've discussed this with mapreri who is another person on the backporters team. Given the API/ABI changes that happen during OpenSSL microreleases that break packages integrations AND that this will add a security delta (-backports doesn't receive Security Team support so if they change and patch a CVE in -security or -updates it remains unpatched in -backports which introduces a significant Security risk. Additionally, if it's only 3 or 4 commits to fix SSL_OP_LEGACY_SERVER_CONNECT then you need to follow the SRU process, not the Backports process. Rejecting this backport as "Won't Fix" due to the aforementioned reasons. Additionally, the Backporters Team are going to blacklist `openssl` for backport requests unless it comes from Security at this time. ** Changed in: openssl (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: Won't Fix Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Minor OpenSSL releases have historically introduced a whole lot of behaviour and API changes that required fixing dozens of other packages in the archive. I don't recommend putting 3.0.5 in backports. What I suggest is to actually SRU the 3-4 commits that fix SSL_OP_LEGACY_SERVER_CONNECT to the version currently in Jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: New Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Mark, are you asking this to be backported in -backports or in -updates and -security? This is one of the packages that if we do this in -backports any security patches applied by the Security team for OpenSSL in -security and -updates would be ignored with the higher version of this in -backports. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: New Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003903] Re: [BPO] openssl/3.0.5-2ubuntu2 from kinetic
OpenSSL is one of those tricky things out there I would like to get a Security insight for before we do any kind of backporting of it. There's other things this could impact, backports or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: New Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 2003025] Re: systemd/resolved can't enable mdns permanently
It shows # resolvectl mdns Global: yes Link 2 (enp1s0): no Link 3 (eno1): no Link 4 (lan): no Link 5 (finnland): no Link 6 (docker0): no Link 8 (veth21cf34c5): no In other words: No. -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 2003903] [NEW] [BPO] openssl/3.0.5-2ubuntu2 from kinetic
Public bug reported: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] >From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2003903 Title: [BPO] openssl/3.0.5-2ubuntu2 from kinetic Status in openssl package in Ubuntu: New Bug description: Humbly requesting backporting OpenSSL 3.0.5-2ubuntu2 from kinetic to jammy. [Impact] From the OpenSSL 3.0 migration guide: (https://www.openssl.org/docs/man3.0/man7/migration_guide.html) "Secure renegotiation is now required by default for TLS connections Support for RFC 5746 secure renegotiation is now required by default for SSL or TLS connections to succeed. Applications that require the ability to connect to legacy peers will need to explicitly set SSL_OP_LEGACY_SERVER_CONNECT. Accordingly, SSL_OP_LEGACY_SERVER_CONNECT is no longer set as part of SSL_OP_ALL." OpenSSL 3.0.2 doesn't allow you to enable UnsafeLegacyServerConnect in the openssl.cnf file. The OpenSSL team documented this option but forgot to implement it (https://github.com/openssl/openssl/pull/18296). Users are recommending enabling UnsafeLegacyRenegotiation (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/comments/32) (see more examples in "Other Info") When this is enabled, it makes OpenSSL 3 less secure than 1.1.1 (which is what the previous LTS, Focal, uses). Backporting the newer OpenSSL 3.0.5 would allow users to enable UnsafeLegacyConnect, while keeping UnsafeLegacyRenegotiation disabled. [Scope] Backport OpenSSL 3.0.5-2ubuntu2 from kinetic Backport to jammy [Other Info] Other places where users are recommending enabling UnsafeLegacyRenegotiation: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834/comments/6 https://ubuntuforums.org/showthread.php?t=2474436=14094091#post14094091 https://www.reddit.com/r/Ubuntu/comments/ufalf4/cannot_connect_to_eduroam_since_2204_update/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2003903/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Can we reopen this and potentially backport OpenSSL 3.0.5 from kinetic
to jammy?
The "UnsafeLegacyServerConnect" option was mentioned above in #3.
Unfortunately, that option was documented but not implemented in the
3.0.2 OpenSSL release available in the jammy repos. (See
https://github.com/openssl/openssl/pull/18296)
Enabling UnsafeLegacyRenegotiation is not acceptable and shouldn't be
done. This is actually less secure than version 1.1.1 (which is what the
previous LTS focal has available)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
Won't Fix
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
[Touch-packages] [Bug 2003025] Re: systemd/resolved can't enable mdns permanently
The option doesn't literally get appended to the original file, but when the settings are applied it will use the drop-in conf as well. What does resolvectl mdns show? The rest of your output looks expected (networkctl status won't mention the use of the drop-in config). I have tested this on 22.04 server and it works, so please double check everything. -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/436344 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 2003889] Re: Please merge wpa 2.10-10 from Debian
** Summary changed: - Pleae merge wpa 2.10-10 from Debian + Please merge wpa 2.10-10 from Debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Please merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 1895416] Re: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Cross-reference, among others: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1988299 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1355026 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1360556 -- 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/1895416 Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 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: This occurred doing a cli apt upgrade. May be due to /boot being too full, may not. Saw write permission problems on the screen. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chuck 3514 F pulseaudio CasperMD5CheckResult: skip Date: Sat Sep 12 17:46:20 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=53b045cd-14a6-40e2-bda3-8b25923c8c21 InstallationDate: Installed on 2013-10-19 (2519 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root 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.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-47-generic 5.4.0-47.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2020-07-24 (50 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895416/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian
Hey Simon! Thanks for your quick response. Apparently this changelog bug has already been released in the ubuntu1 version[1], sorry I didn't notice it. Yes let me forward that to Debian, thanks for the reminder. [1]: http://launchpadlibrarian.net/604422811/wpa_2%3A2.10-9_2%3A2.10-9ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Please merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
PPD file from 18.04. The MD5 does not match the other one so it is definitely different somehow. Note that the name is nearly identical but has an extra underscore at the end for some reason. Also there are two print queues for this printer on the old machine. I didn't try the other one. It's PPD file is 10x the size of this one. ** Attachment added: "HP_LaserJet_100_colorMFP_M175nw_61F41D_.ppd" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643469/+files/HP_LaserJet_100_colorMFP_M175nw_61F41D_.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Error log from 18.04. The command I ran was: lp -d HP_LaserJet_100_colorMFP_M175nw_61F41D_ -o print-scaling=none 170x230.pdf I also previously tried it without the print-scaling option (not logged), and result was the same. Very close to the correct size both times. ** Attachment added: "error_log_18_04" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643468/+files/error_log_18_04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
More cases where the same linker flags caused issues https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1860601 https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1898006 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
The bionic upload failed to include a recent fix and failed verification, I uploaded 0.96.24.32.20 to address the problem now -- 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/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released 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 Jammy: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian
Hi Nathan! I have no problem with the patch, given the author. That being said, it would be useful to send this delta up to Debian if at all possible. Please consider it. :) Also, it's best not to modify changelog entries that exist in Debian. I'm dropping this before uploading: wpa (2:2.10-9) unstable; urgency=medium - [ Sebastien Bacher ] * debian/patches/allow-legacy-renegotiation.patch: -Allow legacy renegotiation to fix PEAP issues with some servers -(Closes: #1010603, LP: #1962541) +allow legacy renegotiation to fix PEAP issues with some servers +(Closes: #1010603) - -- Andrej Shadura Thu, 05 May 2022 11:23:33 +0100 + -- Sebastien Bacher Thu, 05 May 2022 11:31:26 +0200 Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Pleae merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
Note: when testing this package with autopkgtest (or sbuild) locally, you need to remove the .git directory (if there is one) or the build will fail. One of the make files will detect the directory exists and set the environment variable DYNAMIC to no. Because of that, static binaries will be generated and the command chrpath in debian/rules will fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 2003025] Re: systemd/resolved can't enable mdns permanently
I'm currently away from this particular network for some time, I'm currently jumping between different countries. If this just merges these settings into the systemd file generated by netplan without the need of netplan to be able to deal with mdns, this should do the job. But I wasn't aware that there is this way of appending settings by opening a .d/ directory and putting additional settings in it. However, it doesn't seem to work. I just tested this on a different machine (22.04 server) in a different network, where mdns is usually not used. I've enabled mdns on /etc/systemd/resolv.conf, resolvectl mdns Global: yes Link 2 (enp1s0): no Link 3 (eno1): no the default interface connected to the lan is eno1. Therefore, I created /etc/systemd/network/10-netplan-eno1.network.d/mdns.conf with [Match] Name=eno1 [Network] MulticastDNS=yes and rebootet the machine. But mdns still not enabled for this network. # networkctl status eno1 ● 3: eno1 Link File: /run/systemd/network/10-netplan-eno1.link Network File: /run/systemd/network/10-netplan-eno1.network Type: ether ... and /run/systemd/network/10-netplan-eno1.network [Match] Name=eno1 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 [DHCP] RouteMetric=100 UseMTU=true So no, the MulticastDNS setting doesn't make its way into the config from this way of setting. -- 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/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 2003892] [NEW] libcap2 seems to not work correctly when linked with -Bsymbolic-functions
Public bug reported: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 ** Affects: libcap2 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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 1996552] Re: The liborc-0.4-dev package contains binarys
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: orc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to orc in Ubuntu. https://bugs.launchpad.net/bugs/1996552 Title: The liborc-0.4-dev package contains binarys Status in orc package in Ubuntu: Confirmed Bug description: -dev is for header files only and this strews with multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1996552/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Thanks. Please attach the PPD and error_log from that 18.04 computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 2003025] Re: systemd/resolved can't enable mdns permanently
You can use a drop-in configuration to achieve this: $ cat /etc/systemd/network/10-netplan-eth0.network.d/mdns.conf [Match] Name=eth0 [Network] MulticastDNS=yes This will basically append the MulticastDNS option to the existing netplan-generated network configuration. Does that solve your problem? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2003025 Title: systemd/resolved can't enable mdns permanently Status in systemd package in Ubuntu: Incomplete Bug description: I currently ran into the problem, that systemd (i.e. its resolved) cannot properly configured to run with mdns. I'm currently setting up some machines in a network with a poor router which routes and offers DHCP, but does not put the DHCP clients into a DNS domain, so the machines need to use mdns to find each other. In order to have systemd/resolved use mdns, two steps are necessary: 1. MulticastDNS=yes must be put into /etc/systemd/resolved.conf and resolved restarted to enable it in general. 2. It must be enabled per interface. On the command line this can be done with resolvectl mdns eth0 yes result: # resolvectl mdns Global: yes Link 63 (eth0): yes and it works. Problem: It cannot be done automatically in a server/LXD image. Im having this problem inside the LXD 22.04 image. a) man pages suggest that /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] MulticastDNS=yes would do the job, but it doesn't. It seems to be completely ignored. The reason seems to be that networkctl status eth0 shows Network File: /run/systemd/network/10-netplan- eth0.network so it seems to be overridden by netplan. b) netplan itself does not seem to support the MulticastDNS settings. c) On Desktop Machines I found a workaround with NetworkManager, but on server and LXD images, Network Manager does not exist. So I do not see a way to have this configured permanently (other than writing a systemd unit). But: I need to configure the machines / LXD machines using cloud-init, in order to have the installation pull packages from a server to be found with mdns. I tried to run resolvectl mdns eth0 yes as a bootcmd in Cloud-init, but this has no effect, because it is too early. I tried to run it as a runcmd, and it works but it is too late, because package installation has already failed. So where in this scrub between systemd and netplan could mdns be enabled in a way, that the automatic installation would work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003025/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian
** Patch added: "resulting debdiff between debian and ubuntu" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+attachment/5643439/+files/10-10--10-10ubuntu1.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Pleae merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian
** Patch added: "resulting debdiff between current and proposed ubuntu" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+attachment/5643440/+files/10-9ubuntu1--10-10ubuntu1.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Pleae merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2003889] [NEW] Pleae merge wpa 2.10-10 from Debian
Public bug reported: I built it successfully in Lunar. ** Affects: wpa (Ubuntu) Importance: Wishlist Assignee: Nathan Teodosio (nteodosio) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Pleae merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Confirmed Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Also I just tried printing the test document on another computer which still has Ubuntu 18.04 installed. The output rectangle was undersized by less than 1mm, which seems okay. I can attach the ppd file and error log from there if it would help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 2003548] Re: Merge Debian unstable's p11-kit 0.24.1-2
** Summary changed: - Merge Debian unstable's 0.24.1-2 + Merge Debian unstable's p11-kit 0.24.1-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/2003548 Title: Merge Debian unstable's p11-kit 0.24.1-2 Status in p11-kit package in Ubuntu: New Bug description: This is a merge of Debian unstable's 0.24.1-2 as 0.24.1-2ubuntu1. A PPA is available at https://launchpad.net/~adrien-n/+archive/ubuntu/p11-kit-merge-0.24.1-2 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/2003548/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl
### VERIFICATION DONE JAMMY ### sudo apt-get update sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils -y sudo systemctl enable libvirtd sudo systemctl status libvirtd wget https://releases.ubuntu.com/jammy/ubuntu-22.04.1-live-server- amd64.iso sudo chown ubuntu:ubuntu ubuntu-22.04.1-live-server-amd64.iso sudo chmod +rwx ubuntu-22.04.1-live-server-amd64.iso *you will get a permission denied if you don't do this part* virsh list sudo virt-install --location='./ubuntu-22.04.1-live-server-amd64.iso', --name=setfont-repo01 --vcpus=2 --memory=2048 --disk size=10 --console pty,target_type=virtio --serial pty --graphics none --boot=uefi,kernel='/boot/vmlinuz',initrd='/boot/initrd.img',kernel_args='console=/dev/ttyS0' --extra-args='console=ttyS0,115200n8 serial' --debug select Tab-> Help -> Enter Shell sudo apt-cache policy kbd # Check version installed Installed: 2.3.0-3ubuntu4 #Error message thrown in logs root@ubuntu-server:/# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device ### ENABLE PROPOSED ### # create new VM for kinetic sudo virt-install --location='./ubuntu-22.04.1-live-server-amd64.iso', --name=setfont-repo03 --vcpus=2 --memory=2048 --disk size=10 --console pty,target_type=virtio --serial pty --graphics none --boot=uefi,kernel='/boot/vmlinuz',initrd='/boot/initrd.img',kernel_args='console=/dev/ttyS0' --extra-args='console=ttyS0,115200n8 serial' --debug select Enter -> Tab-> Help -> Enter Shell # update /etc/apt/sources.list deb http://archive.ubuntu.com/ubuntu jammy-proposed universe multiverse restricted main sudo apt --only-upgrade install kbd Check version installed sudo apt-cache policy kbd Installed: 2.3.0-3ubuntu4.22.04 # execute command setfont $SNAP/subiquity.psf bash: # no error messages thrown # we don't have any error messages being thrown in the logs - /var/log/installer/subiquity-client-debug.log # if you need to log back into the vm virsh list virsh console setfont-repo03 # notes ctl+5 = exit rich console command or CTRL+] ### VERIFICATION DONE KINETIC ### ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1996619 Title: Setfont error due to deprecated PIO_FONTX ioctl Status in subiquity: Invalid Status in kbd package in Ubuntu: Fix Released Status in kbd source package in Jammy: Fix Committed Status in kbd source package in Kinetic: Fix Committed Bug description: [Impact] There is an error message that get thrown in in syslog. There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ (upstream) has a fix. It is caused by this line in subiquity https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11 It's due to PIO_FONTX ioctl removed from kernel since 5.12 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d In 2.4.5 of kbd which provide setfont in user space, they already switched over to use KDFONTOP only. [ Test Plan ] ### REPRODUCER STEPS ### # install libvirt sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils sudo systemctl enable libvirtd sudo systemctl start libvirtd # check libvirtd process is running virsh virsh list # get iso wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso # install vm sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso' --name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty --graphics none --boot=uefi --debug # you can either do the full install, the error will be in the /var/log/installer.log file # or on the first page of the installer press Tab-> go to Help, -> Shell and cd /var/log/ grep setfont* syslog # to show error message cd to /snap/subiquity/3698 #execute setfont $SNAP/subiquity.psf # error root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device # grep grep setfont* syslog Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device [ Where problems could occur ] There could be a failure to correctly parse fonts. https://man7.org/linux/man-pages/man8/setfont.8.html
[Touch-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
Note that both of the print commands failed to print anything at all, but the testipp printer does know that my printer is low on toner. Also I tried deleting the testipp printer and recreating it but still nothing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
ppd file ** Attachment added: "testipp.ppd" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643436/+files/testipp.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
error log ** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643437/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
I've tested 0.99.9.10 on 20.04, activating ubuntu pro through the magic workflow, detachig and activating again using the manual token one, it works as expected, marked as verified on F -- 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/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released 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 Jammy: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
I've tested 0.99.22.5 on 22.04, activating ubuntu pro through the magic workflow, detachig and activating again using the manual token one, it works as expected, marked as verified on J ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released 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 Jammy: Fix Committed Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl
### VERIFICATION DONE KINETIC ### sudo apt-get update sudo apt install qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils -y sudo systemctl enable libvirtd sudo systemctl status libvirtd wget https://releases.ubuntu.com/kinetic/ubuntu-22.10-live-server- amd64.iso virsh list sudo chown -R ubuntu:ubuntu ubuntu-22.10-live-server-amd64.iso * you will get a permission denied if you don't do this part* sudo virt-install --location='./ubuntu-22.10-live-server-amd64.iso', --name=setfont-repo --vcpus=2 --memory=2048 --disk size=10 --console pty,target_type=virtio --serial pty --graphics none --boot=uefi,kernel='/boot/vmlinuz',initrd='/boot/initrd.img',kernel_args='console=/dev/ttyS0' --extra-args='console=ttyS0,115200n8 serial' --debug virsh console setfont-repo select Tab-> Help -> Enter Shell sudo apt-cache policy kbd kbd package version previous 2.3.0-3ubuntu4 #Error message thrown in logs root@ubuntu-server:/# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device ### ENABLE PROPOSED ### # create new VM for kinetic sudo virt-install --location='./ubuntu-22.10-live-server-amd64.iso', --name=setfont-repo03 --vcpus=2 --memory=2048 --disk size=10 --console pty,target_type=virtio --serial pty --graphics none --boot=uefi,kernel='/boot/vmlinuz',initrd='/boot/initrd.img',kernel_args='console=/dev/ttyS0' --extra-args='console=ttyS0,115200n8 serial' --debug select Tab-> Help -> Enter Shell # edit sources.list deb http://archive.ubuntu.com/ubuntu kinetic-proposed universe multiverse restricted main sudo apt-get upgrade kbd Check version installed sudo apt-cache policy kbd Candidate: 2.3.0-3ubuntu4.22.10 sudo apt --only-upgrade install kbd # execute command $SNAP/subiquity.psf bash: /snap/subiquity/4003/subiquity.psf: Permission denied # we get a permission denied, not an ioctl error # we don't have any error messages being thrown in the logs - /var/log/installer/subiquity-client-debug.log # if you need to log back into the vm virsh list virsh console setfont-repo03 # notes ctl+5 = exit rich console command or CTRL+] ### VERIFICATION DONE KINETIC ### -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1996619 Title: Setfont error due to deprecated PIO_FONTX ioctl Status in subiquity: Invalid Status in kbd package in Ubuntu: Fix Released Status in kbd source package in Jammy: Fix Committed Status in kbd source package in Kinetic: Fix Committed Bug description: [Impact] There is an error message that get thrown in in syslog. There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ (upstream) has a fix. It is caused by this line in subiquity https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11 It's due to PIO_FONTX ioctl removed from kernel since 5.12 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d In 2.4.5 of kbd which provide setfont in user space, they already switched over to use KDFONTOP only. [ Test Plan ] ### REPRODUCER STEPS ### # install libvirt sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst bridge-utils sudo systemctl enable libvirtd sudo systemctl start libvirtd # check libvirtd process is running virsh virsh list # get iso wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso # install vm sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso' --name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty --graphics none --boot=uefi --debug # you can either do the full install, the error will be in the /var/log/installer.log file # or on the first page of the installer press Tab-> go to Help, -> Shell and cd /var/log/ grep setfont* syslog # to show error message cd to /snap/subiquity/3698 #execute setfont $SNAP/subiquity.psf # error root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device # grep grep setfont* syslog Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: Inappropriate ioctl for device [ Where problems could occur ] There could be a failure to correctly parse fonts. https://man7.org/linux/man-pages/man8/setfont.8.html [Other Notes] # github link to upstream repo & commit https://github.com/legionus/kbd
[Touch-packages] [Bug 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race
I think the "Failed to connect system bus: No such file or directory" stderr output rather comes from networkctl [1] than from "netplan-dbus" (Netplan's output would be "... connect TO system bus..."). netplan-dbus is not involved at all AFAICS, as cloud-init is calling into the "netplan apply" CLI and not calling its "io.netplan.Netplan Apply()" DBus method; which would fail due to missing DBus communication, too. So the root-cause IMO is networkctl trying to talk to systemd-networkd via DBus, which is not yet ready. Porting this communication to using varlink instead of dbus could solve this (but is probably a big task). Are we sure that systemd-networkd.service is already up-and-running at this stage and dbus.service/.socket being the bottleneck? We're sorting `After=systemd-networkd-wait-online.service`, so I assume: Yes. Netplan's "apply" CLI could probably implement a "systemctl is-active ..." check for dbus.service/.socket and/or systemd-networkd.service/NetworkManager.service (depending on which backend is about to be (re-)configured. But generally "netplan apply" is designed to be a userspace tool and only Netplan's generator is designed to be executed during early boot. So if it's possible to postpone the execution of "netplan apply" until after systemd's initial boot transaction finished (i.e. into cloud-config.service) this would IMO be the cleaner solution and could avoid similar, future issues related to early boot. [1] https://github.com/systemd/systemd/blob/main/src/network/networkctl.c#L2992 ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Wishlist -- 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/1997124 Title: Netplan/Systemd/Cloud-init/Dbus Race Status in cloud-init: In Progress Status in netplan: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: Cloud-init is seeing intermittent failures while running `netplan apply`, which appears to be caused by a missing resource at the time of call. The symptom in cloud-init logs looks like: Running ['netplan', 'apply'] resulted in stderr output: Failed to connect system bus: No such file or directory I think that this error[1] is likely caused by cloud-init running netplan apply too early in boot process (before dbus is active). Today I stumbled upon this error which was hit in MAAS[2]. We have also hit it intermittently during tests (we didn't have a reproducer). Realizing that this may not be a cloud-init error, but possibly a dependency bug between dbus/systemd we decided to file this bug for broader visibility to other projects. I will follow up this initial report with some comments from our discussion earlier. [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801 [2] https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1997124/+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 1971323] Re: Merge six from Debian unstable for kinetic
** Changed in: six (Ubuntu) Milestone: later => ubuntu-22.11 ** Changed in: six (Ubuntu) Milestone: ubuntu-22.11 => kinetic-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1971323 Title: Merge six from Debian unstable for kinetic Status in six package in Ubuntu: Fix Released Bug description: Upstream: tbd Debian: 1.16.0-3 Ubuntu: 1.16.0-3ubuntu1 Debian typically updates six every 2 months on average, but it was last updated 21.12 and looks overdue. Check back in on this monthly. ### New Debian Changes ### six (1.16.0-3) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Colin Watson ] * Link directly to upstream in Homepage and debian/copyright. -- Colin Watson Sun, 26 Dec 2021 02:24:26 + six (1.16.0-2) unstable; urgency=medium * Team upload. [ Andreas Beckmann ] * python-six/python3-six: Copy Breaks: python (<< 2.7.18), python-minimal (<< 2.7.18), libpython-stdlib (<< 2.7.18), python-iso8601 (<< 0.1.12-2~), python-pbr (<< 5.4.5) from python2.7 to ensure removal of the unversioned python packages (and some persisting obsolete Python 2 module packages) on upgrades from buster. In some upgrade scenarios (mostly involving openstack packages) these Breaks in python2.7 were ineffective because the unversioned python packages got higher scores than python2.7. python-six/python3-six are usually very high scoring Python module packages in these cases, making them ideal candidates for such copies of the Breaks. (Closes: #991433) -- Stefano Rivera Tue, 27 Jul 2021 11:44:18 -0400 six (1.16.0-1) unstable; urgency=medium * New upstream release. -- Colin Watson Sun, 09 May 2021 11:40:54 +0100 six (1.15.0-2) unstable; urgency=medium [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Colin Watson ] * Remove Barry Warsaw from Uploaders, with thanks for their previous contributions (closes: #970181). -- Colin Watson Tue, 10 Nov 2020 00:16:45 + six (1.15.0-1) unstable; urgency=medium [ Debian Janitor ] * Update standards version to 4.5.0, no changes needed. [ Colin Watson ] * New upstream release. -- Colin Watson Sun, 24 May 2020 10:23:22 +0100 six (1.14.0-3) unstable; urgency=medium * Dont run unittests for python2 binary, to reduce pytest rdeps -- Sandro Tosi Mon, 13 Apr 2020 20:16:04 -0400 six (1.14.0-2) unstable; urgency=medium * Build-depend on python2 rather than python. -- Colin Watson Tue, 21 Jan 2020 09:44:26 + six (1.14.0-1) unstable; urgency=medium [ Debian Janitor ] * Remove unnecessary team-upload line in changelog. * Set upstream metadata fields: Bug-Database, Repository. * Set upstream metadata fields: Bug-Submit, Repository-Browse. [ Colin Watson ] * New upstream release. -- Colin Watson Mon, 20 Jan 2020 21:39:42 + six (1.13.0-1) unstable; urgency=medium [ Emmanuel Arias ] * New upstream version 1.13.0 * d/control: Bump Standard-Version to 4.4.1 * d/control: Bump debhelper-compat to 12 (from 9) [ Colin Watson ] * Replace manually-written basic autopkgtests with 'Testsuite: autopkgtest-pkg-python'. * Remove build-dependencies on python-py and python3-py, no longer used upstream. * Fix HTML paths in doc-base control file. -- Colin Watson Tue, 12 Nov 2019 08:10:54 + six (1.12.0-2) unstable; urgency=medium ### Old Ubuntu Delta ### six (1.16.0-3ubuntu1) jammy; urgency=medium * Drop Breaks on python to allow python-is-python2 to remain when upgrading from Focal (LP: #1958720) -- Robie Basak Wed, 13 Apr 2022 21:08:40 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1971323/+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 1993387] Re: Merge bridge-utils from Debian unstable for lunar
A new Debian version for bridge-utils is available. There is also a new upstream release but it's not yet packaged by Debian. bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 There is an upstream 1.7.1 release, with just a couple cleanups: From https://kernel.googlesource.com/pub/scm/network/bridge/bridge-utils/+log/refs/tags/v1.7.1: 75d949b Chnage version to 1.7 by Stephen Hemminger · 1 year, 11 months ago v1.7.1 a1f2022 fix string overflow warnings by Stephen Hemminger · 1 year, 11 months ago 4691bf3 brctl: fix spelling on man page by Stephen Hemminger · 2 years ago ab8a2cc README: mark bridge-utils as deprecated by Stephen Hemminger · 2 years, 7 months ago v1.7 ** Changed in: bridge-utils (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1993387 Title: Merge bridge-utils from Debian unstable for lunar Status in bridge-utils package in Ubuntu: New Bug description: Scheduled-For: ubuntu-22.12 Upstream: 1.7.1 Debian: 1.7-2 Ubuntu: 1.7-1ubuntu3 ### New Debian Changes ### bridge-utils (1.7-2) unstable; urgency=medium * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils to stop disabling IPv6 on physical interfaces of vlan ports if set to no. Closes: #989162. * Update interfaces man page, IPv6 works with STP on after DAD was fixed. Closes: #980507. * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. * Update NEWS file to fix us blaming the kernel for the MAC address selection that is really overridden by systemd. -- Santiago García Mantiñán Mon, 03 Oct 2022 23:11:46 +0200 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu3) jammy; urgency=medium * No-change rebuild for ppc64el baseline bump. -- Łukasz 'sil2100' Zemczak Wed, 23 Mar 2022 10:44:35 +0100 bridge-utils (1.7-1ubuntu2) impish; urgency=medium * No-change rebuild to build packages with zstd compression. -- Matthias Klose Thu, 07 Oct 2021 12:09:41 +0200 bridge-utils (1.7-1ubuntu1) impish; urgency=low * Merge from Debian unstable. Remaining changes: - Don't call ifup from bridge-network-interface, instead just call brctl and let udev/upstart bring the interface up. - debian/ifupdown.sh: Handle bridge params which use port and value - debian/bridge-utils-interface.5: + Update max, default value for path cost + Update unsettable gcint value for newer kernels -- Steve Langasek Wed, 17 Mar 2021 12:32:22 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1993387/+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 2003778] Re: systemd-resolved uses malformed link-local IPv6 forwarder
Right, I understand why it would be needed in a ping. But since the DNS server config in systemd-resolved applies to a specific link, the scope ID is implied. As far as your desktop vs server systems, maybe it's the difference between the interfaces available on each system? If you only have one non-lo interface on the server, the scope ID shouldn't be necessary. But if your desktop has e.g. both wlan0 and eth0, then I would expect you need to specify the scope ID in a ping. My system is working with systemd-resolved in stub mode, using my DNS server's IPv6 link-local address. So maybe there is something else on your system causing the problem. Is there anything else odd about your network configuration? Can you share the output of `systemd-analyze cat-config systemd/resolved.conf`? Also when you are in stub mode, what does `SYSTEMD_LOG_LEVEL=debug resolvectl query google.com` show? It may be a good idea to run `resolvectl flush-caches` after switching back to stub mode. -- 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/2003778 Title: systemd-resolved uses malformed link-local IPv6 forwarder Status in systemd package in Ubuntu: Incomplete Bug description: In a network with a local nameserver that has IPv4-address 10.1.0.1 and link-local IPv6-address fe80::2a0:57ff:fe24:b041%2 'resolvectl' returns: Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: uplink Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: fe80::2a0:57ff:fe24:b041 DNS Servers: 10.1.0.1 fe80::2a0:57ff:fe24:b041%21905 DNS Domain: < edited > Name resolution fails because the indicated 'Current DNS Server' IPv6-address is an incomplete link-local address. Also the link-local IPv6-address indicated in the second position of the 'DNS Servers' line is malformed. Issuing consecutive 'resolvectl' calls have the last 4 digits in this line changing, i.e. they all show 'fe80::2a0:57ff:fe24:b041%2', which would be the correct link-local IPv6-address including the interface specification, but then 4 digits that are not constant. Workaround: Take systemd-resoved out of stub-mode with: (cd /etc && sudo rm -f resolv.conf && sudo ln -s /run/systemd/resolve/resolv.conf resolv.conf) The auto generate file '/run/systemd/resolve/resolv.conf' has the proper specification of the name servers link-local IPv6-address: nameserver 10.1.0.1 nameserver fe80::2a0:57ff:fe24:b041%2 search < edited > The broken stub mode is configured with: (cd /etc && rm -f resolv.conf && ln -s /run/systemd/resolve/stub- resolv.conf resolv.conf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003778/+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 1993387] Re: Merge bridge-utils from Debian unstable for lunar
** Description changed: Scheduled-For: ubuntu-22.12 - Upstream: tbd - Debian: 1.7-1 + Upstream: 1.7.1 + Debian: 1.7-2 Ubuntu: 1.7-1ubuntu3 - - ### New Debian Changes ### - bridge-utils (1.7-1) unstable; urgency=medium + bridge-utils (1.7-2) unstable; urgency=medium - * New upstream version. - Only messages related changes and compilation fixes. - * Remove preserve_gcc_flags patch (in upstream now). - * Bump standards, no change needed. - * Clarify portprio and fix example. - * Update upstream url. - * Fix NEWS versioning of last entry :-? + * Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils + to stop disabling IPv6 on physical interfaces of vlan ports if set to no. + Closes: #989162. + * Update interfaces man page, IPv6 works with STP on after DAD was fixed. + Closes: #980507. + * Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627. + * Update NEWS file to fix us blaming the kernel for the MAC address + selection that is really overridden by systemd. - -- Santiago Garcia Mantinan Wed, 24 Feb 2021 - 12:34:03 +0100 - - bridge-utils (1.6-6) unstable; urgency=medium - - * Fix IPv6 address getting assigned on hotplug devices. - Closes: #980752. - * Fix waiting so that DAD works again. Closes: #982943. - * Move mac setting before brctl addif to ensure mac setting. - Closes: #980856. - * Update documentation and add examples. Closes: #765098. - * Update manpages. Closes: #981253. - * Add a note on MTU settings. Closes: #292088. - * Hook also on down to recreate the bridge so that multiple - stanzas work Ok on ifdown. Closes: #319832. - - -- Santiago Garcia Mantinan Tue, 16 Feb 2021 - 13:29:04 +0100 - - bridge-utils (1.6-5) unstable; urgency=low - - * Overload bridge_hw to allow do specify an interface as well as the - MAC address. Closes: #966244. - * Change man page for bridge-utils-interfaces and news fileto document - this overloading. - - -- Santiago Garcia Mantinan Fri, 22 Jan 2021 - 11:08:47 +0100 - - bridge-utils (1.6-4) unstable; urgency=low - - * Add en* to the device regex so that all catches them. Closes: #966319. - * Document MAC address changes on news. Closes: #980505. - - -- Santiago Garcia Mantinan Thu, 21 Jan 2021 - 10:51:31 +0100 - - bridge-utils (1.6-3) unstable; urgency=medium - - * Support VLAN aware setups where we need vlan filtering. - Thanks Benedikt Spranger for the patch. Closes: #950879. - * Clarify on manual page that stp will get IPv6 lost. Closes: #736336. - * Add a 1 second sleep if hw address needs to be changed. Closes: #945466. - - -- Santiago Garcia Mantinan Thu, 30 Apr 2020 - 10:06:38 +0200 - - bridge-utils (1.6-2) unstable; urgency=medium - - * Bump Standards-Version. - * Preserve gcc flags set when building the lib. - - -- Santiago Garcia Mantinan Mon, 28 Jan 2019 - 00:25:14 +0100 - - bridge-utils (1.6-1) unstable; urgency=low - - * New upstream version. - * Change default back to not hotplug. Closes: #892277. - * Allow mtu to be set on the bridge by propagating it to the bridged - interfaces. Closes: #661711. - * Remove kernel headers from the package. - - -- Santiago Garcia Mantinan Tue, 15 Jan 2019 - 13:18:33 +0100 - - bridge-utils (1.5-16) unstable; urgency=medium - - * Don't set dev globally at bridge-utils.sh. Closes: #873086. - - -- Santiago Garcia Mantinan Sun, 08 Apr 2018 - 23:06:30 +0200 - - bridge-utils (1.5-15) unstable; urgency=medium - - * Fix substrings on interfaces. Closes: #873087. - * Make it lintian clean sticking to 1.0 source format for now. - No time to properly comment all the patches right now. - - -- Santiago Garcia Mantinan Fri, 02 Mar 2018 - 22:08:20 +0100 - - bridge-utils (1.5-14) unstable; urgency=low - - * Fix a problem with some vlan interfaces not being created. - - -- Santiago Garcia Mantinan Mon, 26 Jun 2017 - 17:48:37 +0200 - - bridge-utils (1.5-13) unstable; urgency=low - - * Fix a hardcoded interface name on bridge-utils.sh. Closes: #854841. - - -- Santiago Garcia Mantinan Sat, 11 Feb 2017 - 00:16:45 +0100 - - bridge-utils (1.5-12) unstable; urgency=medium - - * Add vlan support so that old setups using vlans as ports don't - break. - - -- Santiago Garcia Mantinan Sun, 22 Jan 2017 - 00:23:50 +0100 + -- Santiago García Mantiñán Mon, 03 Oct 2022 + 23:11:46 +0200 ### Old Ubuntu Delta ### bridge-utils (1.7-1ubuntu3) jammy; urgency=medium - * No-change rebuild for ppc64el baseline bump. + * No-change rebuild for ppc64el baseline bump. - -- Łukasz 'sil2100' Zemczak Wed, 23 Mar + -- Łukasz 'sil2100' Zemczak Wed, 23 Mar 2022 10:44:35 +0100 bridge-utils (1.7-1ubuntu2) impish; urgency=medium - * No-change rebuild to build packages with zstd compression. + * No-change rebuild to build packages with zstd compression. - -- Matthias
[Touch-packages] [Bug 2003845] Re: updating NSS on 18.04
** Package changed: ubuntu => nss (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/2003845 Title: updating NSS on 18.04 Status in nss package in Ubuntu: New Bug description: Ubuntu 18.04 uses older version of NSS (version 3.35) by which the latest root certificates distributed by NSS are not trusted in Ubuntu 18.04. Hence, please update it to latest version of NSS. For example, Mozilla Firefox uses version 3.86 of NSS in Ubuntu 18.04. This issue is impacting a set of users using their TLS certificates from latest root CAs, where website connections are failing due to untrusted certificate authorities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/2003845/+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 2003845] [NEW] updating NSS on 18.04
You have been subscribed to a public bug: Ubuntu 18.04 uses older version of NSS (version 3.35) by which the latest root certificates distributed by NSS are not trusted in Ubuntu 18.04. Hence, please update it to latest version of NSS. For example, Mozilla Firefox uses version 3.86 of NSS in Ubuntu 18.04. This issue is impacting a set of users using their TLS certificates from latest root CAs, where website connections are failing due to untrusted certificate authorities. ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- updating NSS on 18.04 https://bugs.launchpad.net/bugs/2003845 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
We are suspecting issues in the ppc64el toolchain. The problem is only reproducible on Ubuntu ppc, and not on other distributions. The backtrace show some borken pointers that can't be explained. The upstream issue has all the details. None of us speak ppc assembly so we can't really check the binaries. -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
** Tags added: ppc64el reverse-proxy-bugzilla ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Assignee: (unassigned) => bugproxy (bugproxy) -- 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/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 1992178] Re: autopkgtest: upstream tests that run in qemu hang on ppc64el
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1992178 Title: autopkgtest: upstream tests that run in qemu hang on ppc64el Status in systemd: Unknown Status in The Ubuntu-power-systems project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: New Bug description: I believe this started early in the kinetic cycle, cf. https://autopkgtest.ubuntu.com/packages/systemd/kinetic/ppc64el vs https://autopkgtest.ubuntu.com/packages/systemd/jammy/ppc64el. Timeouts in the upstream tests have been an issue for a while, but kinetic on ppc64el consistently times out with upstream tests that run in QEMU. Skipping individual tests does not help, because *which* tests time out appears to change with each build. For example, in 251.4-1ubuntu4 the TEST-36-NUMAPOLICY test was consistently the culprit, but now in 251.4-1ubuntu6 the TEST-14-MACHINE-ID often times out. I have not been able to identify a root cause for this, but it seems that running tests in QEMU is very fragile on ppc64el, where as the tests that run in nspawn are more consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1992178/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
This annoying bug rears its ugly head since I upgraded my own and my wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop or 20.04 workbox. When using the Save As dialog, focus switches to the filter/search field in the dialog when we start typing a name for the file. The focus change happens after each character, so it's practically unusable. Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2003759] Re: apt phasing should be documented in apt.conf(5) rather than apt_preferences(5)
I think it's better to ship slightly wrong documentation in the wrong place than to ship the right documentation in a language users don't understand, so that's why they don#t get updated in stable releases. I do not think the apt.conf manual page is a good idea in the first place. These options belong to upgrade commands now, so they should be documented in apt-upgrade once that is written (which houses apt upgrade, apt-get upgrade, apt dist-upgrade, apt full-upgrade, apt-get dist-upgrade docs). Because the problem is that apt.conf(5) doesn't really have a clear place. Any commandline option can be specified in the config files too, but they're only relevant to their individual commands, so they should be documented alongside their commands. So like apt.conf serves to describe the file format and common options not exposed via command-line flags. So like if we add a -4 argument corresponding to Acquire::ForceIPv4, it should not be listed in apt.conf anymore as it's in all manual pages that involve downloading, if that makes sense. And phasing is in apt_preferences because it was implemented using preferences. It no longer is, it's now part of the upgrade code. It certainly does not belong in apt.conf, that's a last resort for stuff we just can't seem to fit in anywhere else. The whole documentation is horrible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2003759 Title: apt phasing should be documented in apt.conf(5) rather than apt_preferences(5) Status in apt package in Ubuntu: Confirmed Bug description: Hello, the apt documentation on controlling apt phasing is in apt_preferences(5). However, putting the records into a file in /etc/apt/preferences.d leads to an error: $ rg -l APT::Machine-ID -g '*.xml' apt_2.2.2ubuntu1/doc/apt_preferences.5.xml apt_2.3.10/doc/apt_preferences.5.xml apt_2.3.7/doc/apt_preferences.5.xml apt_2.1.17/doc/apt_preferences.5.xml apt_2.3.3/doc/apt_preferences.5.xml apt_2.3.9/doc/apt_preferences.5.xml apt_2.4.8/doc/apt_preferences.5.xml apt_2.2.3/doc/apt_preferences.5.xml apt_2.5.0/doc/apt_preferences.5.xml apt_2.4.5/doc/apt_preferences.5.xml apt_2.3.13/doc/apt_preferences.5.xml apt_2.2.1/doc/apt_preferences.5.xml apt_2.3.11/doc/apt_preferences.5.xml apt_2.3.6/doc/apt_preferences.5.xml apt_2.1.16/doc/apt_preferences.5.xml apt_2.3.9ubuntu0.1/doc/apt_preferences.5.xml apt_2.5.3/doc/apt_preferences.5.xml apt_2.4.0/doc/apt_preferences.5.xml apt_2.3.5/doc/apt_preferences.5.xml apt_2.2.2/doc/apt_preferences.5.xml apt_2.3.15build1/doc/apt_preferences.5.xml apt_2.3.15/doc/apt_preferences.5.xml apt_2.3.8/doc/apt_preferences.5.xml apt_2.2.4ubuntu0.1/doc/apt_preferences.5.xml apt_2.4.3/doc/apt_preferences.5.xml apt_2.1.18/doc/apt_preferences.5.xml ⏚ [sarnold:/etc/apt] $ sudo vim /etc/apt/preferences.d/phased-updates [sudo] password for sarnold: ⏚ [sarnold:/etc/apt] 11s $ apt list E: Invalid record in the preferences file /etc/apt/preferences.d/phased-updates, no Package header ⏚ [sarnold:/etc/apt] $ cat /etc/apt/preferences.d/phased-updates // To have all your machines phase the same, set the same string in this field // If commented out, apt will use /etc/machine-id to seed the random number generator APT::Machine-ID ""; // Always include phased updates APT::Get::Always-Include-Phased-Updates "1"; // Never include phased updates # APT::Get::Never-Include-Phased-Updates "1"; Considering how difficult it is to tell which of preferences vs conf should be used for which settings, mentioning phasing in both manpages would be very kind. However, both manpages should be clear about which one is actually correct. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003759/+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 2003785] Re: apt source exact-source-package doesn't download the requested source package
As David wrote, the behavior here is correct. linux-lowlatency is a binary package provided by linux-meta-lowlatency, for which you are requesting the source code. ** Changed in: apt (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2003785 Title: apt source exact-source-package doesn't download the requested source package Status in apt package in Ubuntu: Opinion Bug description: apt source exact-source-package doesn't download the right source package when specifying source package, i expect the exact source package to be downloaded. example: $ apt source linux-lowlatency => incorrectly downloads linux-meta-lowlatency $ apt source --only-source linux-lowlatency => is very counter intuitive but downloads linux-lowlatency source package Please default to downloading exact source package by default first, and offer binary->source resolution separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003785/+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 1775325] Re: package python3 3.5.1-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1775325 Title: package python3 3.5.1-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in python3-defaults package in Ubuntu: Confirmed Bug description: When my PC starts, it occurs this error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 6 06:42:44 2018 DpkgHistoryLog: Start-Date: 2018-06-06 06:41:46 Commandline: /usr/bin/unattended-upgrade Upgrade: git-man:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), liblouis9:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), libelf1:amd64 (0.165-3ubuntu1, 0.165-3ubuntu1.1), libelf1:i386 (0.165-3ubuntu1, 0.165-3ubuntu1.1), git:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), python3-louis:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), libexempi3:amd64 (2.2.2-2, 2.2.2-2ubuntu0.1), apport:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18), python3-apport:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18), apport-gtk:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18), liblouis-data:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), python3-problem-report:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18) DuplicateSignature: package:python3:3.5.1-3 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package python3 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-07-06 (1065 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150705) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2018-05-26 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1775325/+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 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Thanks for the reply. Julian.
Let's assume that the problem is indeed latency/dropped packets/whatever
on our side. IMO, an (occasionally) broken network should not cause apt-
get to hang indefinitely. Do you think it should?
Also, it doesn't address that the behaviour seems recent. We have not
observed anything like this with Focal or Bionic.
In the mean time, I've added notification code so at least we can we
track when this occurs. I'll fill you in if I get more details (like
versions that are (not) affected).
Additional debug info:
I called recv(3..) on the http socket with a recv-q. It returns 0 (no error,
EOF).
```
(gdb) call (ssize_t)recv(3, "abcdef", 1, 0)
$1 = 0
```
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp1 0 10.91.52.91:60868 217.21.205.139:80 CLOSE_WAIT
154030/http
tcp1 0 10.91.52.91:40756 178.128.6.101:80CLOSE_WAIT
154029/http
tcp0 0 10.91.52.91:56818 185.37.124.14:80CLOSE_WAIT
154031/http
```
Next, I called close(0) on the stdin socket on one of the processes, and this
awoke the whole list of tasks:
```
(gdb) call (int)close(0)
$1 = 0
```
This yielded the following error message:
```
E: Method http has died unexpectedly!
```
And the apt-get process got unstuck / was reaped succesfully.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
New
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe
154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe
154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe
154026,apt-get,6r
http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe
154026,apt-get,12w
http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe
154026,apt-get,7r
gpgv
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Patches are welcome but unfortunately there isn't much we can do
otherwise, this highly depends on network specifics like latency and
mtus and is never reliably reproducible.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
New
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe
154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe
154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe
154026,apt-get,6r
http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe
154026,apt-get,12w
http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe
154026,apt-get,7r
gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe
154026,apt-get,14w
gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe
154026,apt-get,9r
```
So:
- apt-get is waiting for any data written by any of its four children (at fd
5/6/7/9)
- http and gpgv are waiting for any data written by their parent (at their
respective fd 0)
Parent backtrace:
```
#0 0x7f420116a74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f420153fb5d in pkgAcquire::Run(int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int)
()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4 0x7f42016d127b in DoUpdate (CmdL=...)
at ./apt-private/private-update.cc:73
#5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch
const*, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#6 0x7f420169fa97 in DispatchCommandLine (CmdL=...,
Cmds=std::vector of length 27, capacity 32 = {...})
at
[Touch-packages] [Bug 2003851] [NEW] occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Public bug reported:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ] &&
/etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [], NULL,
{tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe 154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe 154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe 154026,apt-get,6r
http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe
154026,apt-get,12w
http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe 154026,apt-get,7r
gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe
154026,apt-get,14w
gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe 154026,apt-get,9r
```
So:
- apt-get is waiting for any data written by any of its four children (at fd
5/6/7/9)
- http and gpgv are waiting for any data written by their parent (at their
respective fd 0)
Parent backtrace:
```
#0 0x7f420116a74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f420153fb5d in pkgAcquire::Run(int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4 0x7f42016d127b in DoUpdate (CmdL=...)
at ./apt-private/private-update.cc:73
#5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch
const*, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#6 0x7f420169fa97 in DispatchCommandLine (CmdL=...,
Cmds=std::vector of length 27, capacity 32 = {...})
at ./apt-private/private-cmndline.cc:588
#7 0x561fc06bafbd in main (argc=2, argv=0x7ffc0e14aa38)
at ./cmdline/apt-get.cc:447
```
Child backtrace:
```
#0 0x7f58b1c9b74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f58b237cb43 in WaitFd(int, bool, unsigned long) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x5643e37bc7b3 in BaseHttpMethod::Loop (
this=0x7ffdeaed56c0) at ./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
```
Where this is:
```
(gdb) print *this
$1 = { = { = { = {}, = {
methodNames = std::vector of length 2, capacity 2 = {
"http",
[Touch-packages] [Bug 2003797] Re: Pre-1970 timestamps are knowingly wrong
** Description changed: tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users that care about pre-1970 timestamps will be satisfied and users not caring will probably not care about the additional timezones. - The install size will increase by around 20% and the amount of - distincted (i.e. not symlinked) timezones will increase by 33%: + The install size will increase by around 20% and the amount of distinct + (i.e. not symlinked) timezones will increase by 33%: ``` $ grep ^Zone africa antarctica asia australasia etcetera europe factory northamerica southamerica | wc -l 352 $ grep ^Zone backzone | wc -l 119 ``` -- 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/2003797 Title: Pre-1970 timestamps are knowingly wrong Status in tzdata package in Ubuntu: Triaged Bug description: tzdata 2021b says in NEWS: "Merge more location-based Zones whose timestamps agree since 1970, as pre-1970 timestamps are out of scope. This is part of a process that has been ongoing since 2013. This does not affect post-1970 timestamps, and timezone historians who build with 'make PACKRATDATA=backzone' should see no changes to pre-1970 timestamps." tzdata 2022b finished that process: "Finish moving to 'backzone' the location-based zones whose timestamps since 1970 are duplicates; adjust links accordingly. This change ordinarily affects only pre-1970 timestamps, and with the new PACKRATLIST option it does not affect any timestamps. In this round the affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake and Pacific/Wallis, and the affected links are Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap." The Debian/Ubuntu package builds tzdata with the default settings (PACKRATDATA unset) which merges zones whose timestamps agree since 1970. This leads to timestamps before 1970 being knowingly wrong. Example: Europe/Oslo is a link to Europe/Berlin since they are identical since 1970, but they differed before 1965. Berlin observed no summertime between 1950 and 1980, but Oslo did in 1959 to 1965. So summer 1960 in Oslo should be UTC+2 compared to UTC+1 in Berlin: ``` $ TZ=Europe/Oslo date -d "1960-07-01 10:00 Z" Fri Jul 1 12:00:00 CEST 1960 $ TZ=Europe/Berlin date -d "1960-07-01 10:00 Z" Fri Jul 1 11:00:00 CET 1960 ``` There was a big debate upstream (see https://lwn.net/Articles/870478/ or https://mm.icann.org/pipermail/tz/2021-May/030137.html). The Debian/Ubuntu package should ship timezones from backzone. Users
[Touch-packages] [Bug 1908073] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 package pre-removal script subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1908073 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 package pre-removal script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: Confirmed Bug description: dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: python3:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 18:15:13 2020 ErrorMessage: new python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-03 (10 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: new python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1908073/+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 2003778] Re: systemd-resolved uses malformed link-local IPv6 forwarder
I'm on Ubuntu 22.04 LTS. I always need to provide the interface specification when using link-local IPv6-addresses, e.g. a simple 'ping fe80::2a0:57ff:fe24' doesn't work but 'ping fe80::2a0:57ff:fe24%2' does the trick. I couldn't figure out why this is required on my desktop Ubuntu system. In contrary on a Debian bullseye server the IPv6-addresss without the interface specifier is sufficient. Any idea? However, since it is required on my Ubuntu system the systemd-resolved stub doesn't work and I have to employ the workaround mentioned in my initial post. The '/run/systemd/resolve/resolv.conf' file contains the proper link-local IPv6-address of my name server including the interface specifier. -- 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/2003778 Title: systemd-resolved uses malformed link-local IPv6 forwarder Status in systemd package in Ubuntu: Incomplete Bug description: In a network with a local nameserver that has IPv4-address 10.1.0.1 and link-local IPv6-address fe80::2a0:57ff:fe24:b041%2 'resolvectl' returns: Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: uplink Link 2 (ens33) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: fe80::2a0:57ff:fe24:b041 DNS Servers: 10.1.0.1 fe80::2a0:57ff:fe24:b041%21905 DNS Domain: < edited > Name resolution fails because the indicated 'Current DNS Server' IPv6-address is an incomplete link-local address. Also the link-local IPv6-address indicated in the second position of the 'DNS Servers' line is malformed. Issuing consecutive 'resolvectl' calls have the last 4 digits in this line changing, i.e. they all show 'fe80::2a0:57ff:fe24:b041%2', which would be the correct link-local IPv6-address including the interface specification, but then 4 digits that are not constant. Workaround: Take systemd-resoved out of stub-mode with: (cd /etc && sudo rm -f resolv.conf && sudo ln -s /run/systemd/resolve/resolv.conf resolv.conf) The auto generate file '/run/systemd/resolve/resolv.conf' has the proper specification of the name servers link-local IPv6-address: nameserver 10.1.0.1 nameserver fe80::2a0:57ff:fe24:b041%2 search < edited > The broken stub mode is configured with: (cd /etc && rm -f resolv.conf && ln -s /run/systemd/resolve/stub- resolv.conf resolv.conf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003778/+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
