[Bug 2077563] Re: [BPO] obs-studio/30.2.3+dfsg-1 from oracular
** Changed in: obs-studio (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077563 Title: [BPO] obs-studio/30.2.3+dfsg-1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2077563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077563] Re: [BPO] obs-studio/30.2.3+dfsg-1 from oracular
approved, thanks! ** Changed in: obs-studio (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077563 Title: [BPO] obs-studio/30.2.3+dfsg-1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2077563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072793] Re: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular
setting as fix-released since it looks like it's built and published for amd64 and s390x, though the arm64/armhf builds haven't started yet...presumably they'll build sometime soon ** Changed in: obs-studio (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072793 Title: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2072793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072793] Re: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular
setting as fix-released in oracular and fix-committed in noble, since the target here is noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072793 Title: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2072793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072793] Re: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular
> obs-studio dependency waits on ppc64el and riscv64 due to missing the proper version of lua libraries on those architectures I feel like this isn't ideal and would be nice if it could be fixed for those archs, but not a blocker for this backport since, as you pointed out, it's also missing its dep(s) in the release/updates pockets. Otherwise LGTM, thanks! ** Changed in: obs-studio (Ubuntu Noble) Status: Invalid => Fix Committed ** Changed in: obs-studio (Ubuntu Oracular) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072793 Title: [BPO] obs-studio/30.1.2+dfsg-1build1 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/2072793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073502] Re: [BPO] package-notes/15 from oracular
** Changed in: package-notes (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073502 Title: [BPO] package-notes/15 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/package-notes/+bug/2073502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073502] Re: [BPO] package-notes/15 from oracular
** Changed in: package-notes (Ubuntu) Status: New => Fix Released ** Changed in: package-notes (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073502 Title: [BPO] package-notes/15 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/package-notes/+bug/2073502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069775] Re: [BPO] lsp-plugins/1.2.16-1 from oracular to noble
** Changed in: lsp-plugins (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069775 Title: [BPO] lsp-plugins/1.2.16-1 from oracular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2069775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069775] Re: [BPO] lsp-plugins/1.2.16-1 from oracular to noble
** Changed in: lsp-plugins (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069775 Title: [BPO] lsp-plugins/1.2.16-1 from oracular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2069775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071361] Re: [BPO] xca 2.6.0-1 to noble, jammy
** Changed in: xca (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: xca (Ubuntu Noble) Status: New => Fix Committed ** Changed in: xca (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071361 Title: [BPO] xca 2.6.0-1 to noble, jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xca/+bug/2071361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067544] Re: [BPO] package-notes/13 from oracular
** Changed in: package-notes (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067544 Title: [BPO] package-notes/13 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/package-notes/+bug/2067544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067544] Re: [BPO] package-notes/13 from oracular
accepted, thanks! ** Changed in: package-notes (Ubuntu) Status: New => Fix Released ** Changed in: package-notes (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067544 Title: [BPO] package-notes/13 from oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/package-notes/+bug/2067544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056201] Re: [BPO] rpki-client/9.0-1 from noble
** Changed in: rpki-client (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056201 Title: [BPO] rpki-client/9.0-1 from noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056732] Re: [BPO] libreoffice 7.6.5 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056732 Title: [BPO] libreoffice 7.6.5 for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2056732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056201] Re: [BPO] rpki-client/9.0-1 from noble
** Also affects: rpki-client (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: rpki-client (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: rpki-client (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056201 Title: [BPO] rpki-client/9.0-1 from noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056732] Re: [BPO] libreoffice 7.6.5 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056732 Title: [BPO] libreoffice 7.6.5 for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2056732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056201] Re: [BPO] rpki-client/9.0-1 from noble
** Changed in: rpki-client (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056201 Title: [BPO] rpki-client/9.0-1 from noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
thanks, I reviewed and uploaded to the focal-backports queue. ** Changed in: memtest86+ (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
@kilobyte have you been able to find a sponsor to upload for you, and also can you clarify that you tested the backport and verified it works correctly (as mentioned in comment 3)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
** Also affects: memtest86+ (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: memtest86+ (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
uploaded to -backports queues for bionic and focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency)
uploaded to -backports queues for bionic and focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
as impish is a non-LTS release and will EOL next month, marking as wontfix. ** Changed in: debhelper (Ubuntu Impish) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency)
The backporters team decided in a previous mtg to take the approach of reverting the use of debugedit. ** Summary changed: - debhelper in focal-backports not usable for i386 package building (missing dependency) + [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency) ** Also affects: debhelper (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: debugedit (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: debugedit (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: debhelper (Ubuntu) Status: New => Invalid ** Changed in: debugedit (Ubuntu) Status: New => Invalid ** Changed in: debugedit (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963829] Re: [BPO] primecount/7.2+ds-6 from jammy
As this still requires a sponsor, I'm unsubscribing ubuntu-backporters team, and subscribing the ubuntu-sponsors team, however it's up to you (Preetham Gujjula) to follow through with preparing the backported package and finding a sponsor to upload it for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963829 Title: [BPO] primecount/7.2+ds-6 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/primecount/+bug/1963829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967003] Re: [BPO] obfs4proxy/0.0.13-1 from jammy
As this still requires a sponsor, I'm unsubscribing ubuntu-backporters team, and subscribing the ubuntu-sponsors team, however it's up to you (wurstsemmel) to follow through with preparing the backported package and finding a sponsor to upload it for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967003 Title: [BPO] obfs4proxy/0.0.13-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obfs4proxy/+bug/1967003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
** Changed in: opencpn (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
** Changed in: opencpn (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974167] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal
** Also affects: opencpn (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: opencpn (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974167 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1974167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
** Description changed: - A customer reported network disconnections on their storage + [impact] + + manual disabling of ipv4 DAD (IACD) for static link-local address does + not work in jammy + + [test case] + + see 'Reproducer' in original description below + + [regression potential] + + failure to disable DAD, or incorrect disabling of DAD, or networkd + issues around parsing of DAD config parsing + + [scope] + + this is needed for j and k + + introduced upstream by commit 1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e, + first included in v249, so this bug does not affect impish or earlier + + fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53 + + [original description] + + A customer reported network disconnections on their storage servers when running 'netplan apply'. The culprit was that - they have link-local addresses configured and the Duplicate - Address Detection (DAD) mechanism was delaying the interfaces - from coming back up. + they have link-local addresses configured and the Duplicate + Address Detection (DAD) mechanism was delaying the interfaces + from coming back up. - As a workaround we tried to disable DAD for the interfaces + As a workaround we tried to disable DAD for the interfaces but that's not working in Ubuntu 22.04: I've noticed that setting DuplicateAddressDetection=none for an - interface with a link-local address (e.g., 169.254.*) via a - .network file added to /etc/systemd/network/ doesn't really + interface with a link-local address (e.g., 169.254.*) via a + .network file added to /etc/systemd/network/ doesn't really disable Duplicate Address Detection. OS and package versions: - - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 - - systemd 249.5-2ubuntu4 + - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 + - systemd 249.5-2ubuntu4 Reproducer: --- 1- Set up Ubuntu 22.04 VM 2- Increase systemlog level: - mkdir -p /etc/systemd/system/systemd-networkd.service.d/ - cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf < /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Bug 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512
** Description changed: [impact] when talking to upstream nameservers, systemd-resolved limits its advertised max packet size as 512 in its edns0 opt. However, one of the primary benefits of edns0 is to allow using packet sizes larger than 512, which is the pre-edns0 max packet size. this results in systemd-resolved failing to handle responses larger than 512 with udp/edns0, and having to fall back to tcp. This is not optimal (since tcp dns imposes significantly higher overhead) and may even cause failures, if a firewall allows udp dns but blocks tcp dns traffic. [test case] enable debug logging in systemd-resolved, with 'sudo systemctl edit systemd-resolved' and then add: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then save that file and restart systemd-resolved (or reboot). Make sure to flush the cache and reset server features before reproducing: $ sudo resolvectl flush-caches $ sudo resolvectl reset-server-features Lookup 'toomany.ddstreet.org' and check systemd-resolved logs to see if it used TCP fallback or not: ... Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Reply truncated, retrying via TCP. ... Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Verified we get a response at feature level TCP from DNS server 10.202.51.1. Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Added positive unauthenticated cache entry for toomany.ddstreet.org IN A 1799s on eth0/INET/10.202.51.1 A correct lookup using larger EDNS0 response size looks like: ... Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using feature level UDP+EDNS0 for transaction 43808. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using DNS server 10.202.51.1 for transaction 43808. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Announcing packet size 1472 in egress EDNS(0) packet. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Emitting UDP, link MTU is 1500, socket MTU is 0, minimal MTU is 40 Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Sending query packet with id 43808 of size 49. Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing query... Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Received dns UDP packet of size 689, ifindex=131, ttl=0, fragsize=0 Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing incoming packet of size 689 on transaction 43808 (rcode=SUCCESS). Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Added positive unauthenticated non-confidential cache entry for toomany.ddstreet.org IN A 1175s on eth0/INET/10.202.51.1 ... [regression potential] failure to correctly look up dns records, or other problems while performing dns lookups with systemd-resolved [scope] - this is needed for all releases + this is needed in impish and earlier - this still needs fixing upstream: + this is fixed in jammy at commit + 22545a74c3a24395bc6e894fe6a681deb66d434c + + this is fixed upstream by commit + 526fce97afe130f71dba3bd4646196bbb1188b82 which in included in v250, so + this is fixed in kinetic and later + + the upstream PR is: https://github.com/systemd/systemd/pull/20528 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940715 Title: systemd-resolved restricts edns0 advertised max size to 512 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1940715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512
** Changed in: systemd (Ubuntu Hirsute) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940715 Title: systemd-resolved restricts edns0 advertised max size to 512 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1940715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly
** Changed in: systemd (Ubuntu)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Groovy)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Hirsute)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Impish)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881207
Title:
systemd-networkd brings eno1 up and down repeatedly
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881207/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal
This is released now for focal-backports, except for arm64/armhf, which appear to be having quite a hard time keeping up with builds, as they currently haven't even started: https://launchpad.net/ubuntu/+source/libreoffice/1:7.2.7-0ubuntu0.21.10.1~bpo20.04.1 I'm marking this fix released for focal, but if you notice the arm builds fail, please add a comment and I'll take a look at them. ** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973594 Title: [BPO] libreoffice 7.2.7 for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
uploaded to k, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962743] Re: [BPO] freeipmi/1.6.9-2 from Jammy to Focal
** Changed in: freeipmi (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962743 Title: [BPO] freeipmi/1.6.9-2 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1962743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
Ok that sounds good to me, thanks! One note for future changes, in this upload the bug reference was 'LP: 1971109', however the launchpad tooling requires that to be 'LP: #1971109' (with the '#'); it's not important enough to require a new upload but do try to remember for next upload. ** Also affects: opencpn (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: opencpn (Ubuntu) Status: New => Fix Released ** Changed in: opencpn (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973594] Re: [BPO] libreoffice 7.2.7 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973594 Title: [BPO] libreoffice 7.2.7 for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962743] Re: [BPO] freeipmi/1.6.9-2 from Jammy to Focal
Hi, sorry for the delay, accepted into focal-backports. ** Changed in: freeipmi (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962743 Title: [BPO] freeipmi/1.6.9-2 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1962743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971109] Re: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy
Looks mostly ok, couple of questions though: 1) the description says 5.6.2 has several important bugfixes; if that means the 5.6.0 version in jammy is affected by those bugs, the correct approach is to patch that version to fix the bugs. The backports pocket shouldn't be used *instead* of the SRU process. Can you clarify if there are bugs in 5.6.0 in jammy that should be fixed? 2) I'm confused about 0004-Build-Use-20.04-plugins-on-22.04.patch; I see it's setting the plugin target version to 20.04, but how does that get the plugins from 20.04? It doesn't expect to get plugins from 20.04, right? Are the plugins included in the source, but expecting a '20.04' build? Or does the application download plugins from some external source at runtime? Or something else? I think it would be good to add some clarification either to the patch header, and/or here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971109 Title: [BPO] Backport opencpn 5.6.2 from Kinetic to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1971109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961833] Re: openssh 8.8 breaks login to Canonical servers
interestingly, paramiko is also broken when connecting to older servers, but not for the same reason as this bug. See bug 1973241 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961833 Title: openssh 8.8 breaks login to Canonical servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973241] Re: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh-rsa and not supporting server-sig-algs
Note that for servers showing this problem, using openssh to connect is also broken, but for a different reason (because the ssh-rsa alg is disallowed by default), see bug 1961833 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973241 Title: Paramiko 2.9.0 breaks compatibility with devices only supporting ssh- rsa and not supporting server-sig-algs To manage notifications about this bug go to: https://bugs.launchpad.net/paramiko/+bug/1973241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973241] [NEW] Paramiko 2.9.0 breaks compatibility with devices only supporting ssh-rsa and not supporting server-sig-algs
Public bug reported:
[impact]
paramiko fails to connect to some servers.
[test case]
attempt to connect to a server that does not support server-sig-algs and
also only supports ssh-rsa (specifically, does not support rsa-
sha2-512). the connection will fail:
DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa'
DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512',
'rsa-sha2-256', 'ssh-rsa']
DEBUG:paramiko.transport:Server did not send a server-sig-algs list; defaulting
to our first preferred algo ('rsa-sha2-512')
DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms'
SSHClient/Transport init kwarg to disable that or other algorithms if your
server does not support them!
INFO:paramiko.transport:Authentication (publickey) failed.
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in connect
self._auth(
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth
raise saved_exception
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 736, in _auth
key = self._key_from_filepath(
File "/usr/lib/python3/dist-packages/paramiko/client.py", line 588, in
_key_from_filepath
key = klass.from_private_key_file(key_path, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 249, in
from_private_key_file
key = cls(filename=filename, password=password)
File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 64, in __init__
self._from_private_key_file(filename, password)
File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 190, in
_from_private_key_file
data = self._read_private_key_file("RSA", filename, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 322, in
_read_private_key_file
data = self._read_private_key(tag, f, password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 351, in
_read_private_key
data = self._read_private_key_openssh(lines[start:end], password)
File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 452, in
_read_private_key_openssh
raise PasswordRequiredException(
paramiko.ssh_exception.PasswordRequiredException: private key file is encrypted
[regression potential]
any regression would likely prevent paramiko from connecting to a remote
server.
[scope]
this needs to be fixed in jammy and later.
this problem was introduced in paramiko 2.9.0 so does not exist in
impish or earlier.
[other info]
this doesn't appear to be fixed upstream yet.
https://github.com/paramiko/paramiko/issues/2012
Note this can be worked around if direct access to the paramiko code is
possible, by using the 'disabled_algorithms' parameter to the client
connect() method, e.g.:
client.connect("", disabled_algorithms={'pubkeys': ['rsa-
sha2-256', 'rsa-sha2-512']})
Note this can break connections to other systems however, that do
support (only) those algs, so is not a very good workaround.
Additionally, this workaround isn't even possible if paramiko is being
used internally by some other python application.
** Affects: paramiko
Importance: Unknown
Status: Unknown
** Affects: paramiko (Ubuntu)
Importance: Undecided
Status: New
** Affects: paramiko (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: paramiko (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: paramiko (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: paramiko (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Bug watch added: github.com/paramiko/paramiko/issues #2012
https://github.com/paramiko/paramiko/issues/2012
** Also affects: paramiko via
https://github.com/paramiko/paramiko/issues/2012
Importance: Unknown
Status: Unknown
** Description changed:
[impact]
paramiko fails to connect to some servers.
[test case]
attempt to connect to a server that does not support server-sig-algs and
also only supports ssh-rsa (specifically, does not support rsa-
sha2-512). the connection will fail:
DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa'
DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512',
'rsa-sha2-256', 'ssh-rsa']
DEBUG:paramiko.transport:Server did not send a server-sig-algs list;
defaulting to our first preferred algo ('rsa-sha2-512')
DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms'
SSHClient/Transport init kwarg to disable that or other algorithms if your
server does not support them!
INFO:paramiko.transport:Authentication (publickey) failed.
Traceback (most recent call last):
- File "", line 1, in
- File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in
connect
- self._auth(
- File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth
- raise saved_exception
-
[Bug 1961833] Re: openssh 8.8 breaks login to Canonical servers
For reference to anyone coming here with this problem, when connecting to a remote sshd server you can find what host key algorithms the remote host uses by using -vv and check the debug output; look first for the *peer* server KEXINIT proposal (not the earlier *local client* KEXINIT proposal): debug2: peer server KEXINIT proposal a line or two after that, you should see the list of host key algorithms the remote host is offering; if it contains *only* ssh-rsa then this bug is relevant. debug2: host key algorithms: ssh-rsa Note that by default many systems support multiple algorithms, e.g. you may see: debug2: host key algorithms: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh- ed25519 in this case, even though the remote host does offer ssh-rsa, it also supports other algorithms that jammy does support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961833 Title: openssh 8.8 breaks login to Canonical servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1961833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Changed in: openssl (Ubuntu) Assignee: Nicolas Bock (nicolasbock) => (unassigned) ** Changed in: openssl (Ubuntu Bionic) Assignee: Nicolas Bock (nicolasbock) => Bruce Elrick (virtuous-sloth) ** Changed in: openssl (Ubuntu Bionic) Status: Fix Committed => In Progress ** Tags removed: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933363] Re: Backport reprepro fixes to focal..hirsute
** Also affects: reprepro (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933363 Title: Backport reprepro fixes to focal..hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/reprepro/+bug/1933363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965325] Re: upstream patch from opendev - double encoding-decoding
uploaded to kinetic, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965325 Title: upstream patch from opendev - double encoding-decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-etcd3gw/+bug/1965325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969808 Title: [BPO] libreoffice 7.2.6 for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969808] Re: [BPO] libreoffice 7.2.6 for focal
** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969808 Title: [BPO] libreoffice 7.2.6 for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
** Changed in: systemd (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Hirsute) Assignee: Dan Streetman (ddstreet) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
per comment 6, this should be fixed in jammy, so marking fixed released there. ** Changed in: systemd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928733 Title: Starting systemd Network Service fails with "Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1928733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967920] Re: sysconfig installation scheme change breaks stuff
> You sure nothing else needs to be done for this in Debian?
To be specific: are you sure that it's better to leave {base} set to
/usr and prefix the various paths with 'local'? Any package build that
chooses a different {base} will then still have things put into their
custom {base}/local/... which might not be what they expect (certainly
wasn't what meson expected)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967920
Title:
sysconfig installation scheme change breaks stuff
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1967920/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967920] Re: sysconfig installation scheme change breaks stuff
> This is by design. See: https://lists.debian.org/debian- python/2022/03/msg00039.html I get that, my point is it doesn't seem to be done correctly. > There was a Debian bug tracking the effect on Meson, apparently the issue was > fixed upstream. > See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009097#32 I think it's more likely this failing test was fixed upstream by: https://github.com/mesonbuild/meson/commit/54808cd39b765f5553c3c6ae49e5ef14b5290b08 However, that test isn't the real problem; see how upstream meson 'fixed' this: https://github.com/mesonbuild/meson/commit/a2079939de2d1d271e5ea7f23c3656a73e325728 You sure nothing else needs to be done for this in Debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967920 Title: sysconfig installation scheme change breaks stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1967920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once
> It seems this issue may occur not only when receiving addresses on multiple interfaces, but also when dhcp requests on multiple interfaces times out and the hook script was called with 'reason' == FAIL. yep, the try-reload-or-restart is done for those as well and this should be fixed for those $reason cases; since this bug is already resolved, I suggest you open a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939255 Title: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968805] Re: Hibernation fails when an additional swapfile is added due to priority mismatch
I have no comment on working around this by changing ec2-hibinit-agent, but is this a dup of bug 1910252 (i.e. maybe fixing that bug would solve this as well?) I never found time to fix that bug with upstream systemd (and sru the fix) but it's probably worth doing at some point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968805 Title: Hibernation fails when an additional swapfile is added due to priority mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1968805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967920] [NEW] sysconfig installation scheme change breaks stuff
Public bug reported: the 3.10 version of python in debian and ubuntu appears to have changed its installation scheme from 'posix_prefix' to the debian-specific 'posix_local', which breaks things, for example meson is no longer buildable: https://launchpadlibrarian.net/595057055/buildlog_ubuntu-jammy-amd64.meson_0.61.2-1_BUILDING.txt.gz I suspect the problem is an incomplete patching of python to correctly use the 'local' path, as (for example) distutils/setuptools doesn't appear to be using the new 'local' path (in the above build output, search for 'test_meson_installed' to see the failure of meson getting installed to the sysconfig 'scripts' path, which is now '/usr/local/bin' instead of '/usr/bin'). ** Affects: python3.10 (Ubuntu) Importance: Undecided Status: New ** Affects: python3.10 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python3.10 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967920 Title: sysconfig installation scheme change breaks stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1967920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967920] Re: sysconfig installation scheme change breaks stuff
I suspect this might be a rather critical problem to fix before jammy releases? Just guessing though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967920 Title: sysconfig installation scheme change breaks stuff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1967920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
> I think you have a problem there too. oh I'm certainly not claiming a 1g default swap is appropriate, that does seem far, far too small to me and will likely cause widespread issues beyond just this, I was only saying that tweaking the systemd- oomd swap % full setting would IMHO not be likely to fix this very well - and as you point out increasing the swap size to a more reasonable size almost certainly will help (and might be why upstream hadn't noticed this before), regardless of the systemd-oomd swap % used default setting, because it would be far less likely to fill swap up to the oomd swap % full default. > Maybe running with such a starved swapspace triggers systemd-oom to do weird things? From my quick read of the code, it doesn't seem to be doing anything weird at all, I think it's doing exactly what it's programmed to do. I just don't think the code is correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
> it's going to be hard to get around the core issue of oomd counting pagecache as memory pressure assuming my quick 10-minute assessment of this bug is correct, of course...maybe i'm totally wrong about what the problem is ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
> So, maybe the default SwapUsedLimit is not appropriate for Ubuntu I don't think tweaking that will help much if at all, it's going to be hard to get around the core issue of oomd counting pagecache as memory pressure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04
wow, looking at the systemd code (even upstream), oomd is counting pagecache as 'used' memory which is massively unfair as the kernel is responsible for pagecache use, not userspace, and it's not even accurate (from a OOM perspective) since the kernel will drop pagecache as memory pressure increases. Definitely some discussion and patching needs to happen upstream in systemd I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964632] Re: [BPO] gramps/5.1.5-1 from jammy
** Changed in: gramps (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: gramps (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964632 Title: [BPO] gramps/5.1.5-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1964632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964632] Re: [BPO] gramps/5.1.5-1 from jammy
> Sorry for not making clear my intentions in the bug description. No problem, it was my misunderstanding, and sorry for the confusion. ** Changed in: gramps (Ubuntu) Status: New => Fix Released ** Changed in: gramps (Ubuntu Impish) Status: New => Fix Committed ** Changed in: gramps (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964632 Title: [BPO] gramps/5.1.5-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1964632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows
** Merge proposal linked: https://code.launchpad.net/~ddstreet/software-properties/+git/software-properties/+merge/417981 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965180 Title: apt-add-repository requires --login for private repos, breaking automated workflows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: debhelper in focal-backports not usable for i386 package building (missing dependency)
> also backporting debugedit sounds like the correct thing to do I don't think we can backport debugedit for i386 currently, since debugedit's i386 build depends on debhelper which depends on debugedit's i386 build. Maybe we can do a build without the backports pocket in a PPA, then binary-copy debugedit over to -backports, or some other magic to work around the circular dep. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
> *If* want to fix this in bionic and focal, a full SRU will be required agreed, and that would require its own [SRU] bug separate from this [BPO] bug > I'll take this on, I have some spare cycles today this afternoon. @teward did you get a chance to prepare this? I didn't see it in the upload queues yet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962743] Re: [BPO] freeipmi/1.6.9-2 from Jammy to Focal
Just a note that this needs a sponsor to review and upload it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962743 Title: [BPO] freeipmi/1.6.9-2 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1962743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal
** Changed in: simplestreams (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964632] Re: [BPO] gramps/5.1.5-1 from jammy
I just realized I probably misunderstood, as this is fixing bugs in the *previous* backport for this, which (if that's the case) is totally fine to backport as-is. Can you just clarify if that's correct, and also if any of this backport, or the last backport, fixes bugs in the official focal version, that should be SRUed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964632 Title: [BPO] gramps/5.1.5-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1964632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964632] Re: [BPO] gramps/5.1.5-1 from jammy
It's slightly concerning that -backports may be getting used here just for fixes? The concern is that bug fixes should be done as SRU so that everyone gets the bug fixes. The backports pocket generally should be limited to mainly pulling new features/functionality back; stuff that would be inappropriate for SRU. I do understand that the SRU process is more involved and more difficult, but that's by design as SRUs need to be handled more carefully than BPOs, for obvious reasons. Can you clarify if you plan to SRU the bug fixes listed, or can you clarify which of them aren't appropriate for SRU (and why)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964632 Title: [BPO] gramps/5.1.5-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1964632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal
** Changed in: simplestreams (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
uploaded to bionic queue, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
If you'd rather remove the opt-in part, that's fine with me; I can sponsor the debdiff then with the opt-in parts left out, if that works for you Bruce and Nicolas. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
@ubuntu-security since this is openssl, could you give the debdiff a review? I can sponsor it as a normal SRU if you have no objections (and the changes look ok to you), as it doesn't really seem like it would specifically need to go to the -security pocket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
> It's not needed for actual functionality of the backport but that assumes that any future backports or fixes don't break this backport yes i get that, my comment is about whether or not the patch changes any code *outside* of the self-tests, e.g. the TLSProxy perl code changes. If that's *only* used for self-tests then including in the backport shouldn't cause any regression. Remember that people reviewing/sponsoring patches may not have deep experience with the code so it's good to more clearly explain things that aren't necessarily obvious, such as the 2nd patch only affecting test code (if that is indeed the case), since at first glance that isn't what it looks like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
The 2nd upstream patch appears to add new functionality, for actually parsing a certificate request; is that actually needed (outside of the self-tests)? If not, it shouldn't be included in the backport. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964486] Re: crash when in FIPS mode
> Default to SHA256 for key fingerprints. Typically changes should go upstream first, and it doesn't seem this was patched upstream yet or even an issue opened? And not patched in Debian yet either? > MD5 is long deprecated, OpenSSH has switched to SHA256. is this accurate even for key fingerprints used only in log messages? i didn't think that the hash function really mattered from a security perspective if used only for key fingerprints (this is a hash of the *public* key, right?), and md5 fingerprints seem fairly common still? Shouldn't this change at least be proposed upstream before making this change in ubuntu? Making this change only for FIPS would be one thing, but unilaterally changing this for all users might not be appropriate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964486 Title: crash when in FIPS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
> I have update ongoing on esm-infa-staging for it just to clarify, if the systemd patch isn't added to the actual main (currently closed) xenial-updates repo, it won't be very much help to anyone wanting to create new xenial containers on jammy. So, just patching systemd in the esm repo likely is not enough - especially if the prebuilt LXD container images don't pick up the ESM version of systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
> I think this commit [1] may be related (landed in systemd v249) yeah, that commit seems to be intentionally forcing ACD on for statically configured ipv4, i'm not sure quite why, it seems like a user-configured setting should be honored; but possibly Yu was trying to default it to on instead of overriding user config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964494 Title: Setting DuplicateAddressDetection=none doesn't disable DAD for link- local IPs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1964494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964486] Re: crash when in FIPS mode
@ubuntu-security team, as this only affects FIPS, could you take a look at this and determine if you should create a FIPS-specific version of this package? ** Also affects: pam-ssh-agent-auth (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: pam-ssh-agent-auth (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: pam-ssh-agent-auth (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: pam-ssh-agent-auth (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964486 Title: crash when in FIPS mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964486] [NEW] crash when in FIPS mode
Public bug reported:
[impact]
when in FIPS mode, MD5 is not allowed; however in
pamsshagentauth_check_authkeys_file(), if a key match is found for a key
is found, its MD5 fingerprint is generated in order to log the
fingerprint. Unfortunately that calls into
pamsshagentauth_key_fingerprint_raw() which uses openssl EVP_* functions
for the fingerprint creation, but without any kind of error checking.
The call to EVP_DigestInit() fails because openssl is in FIPS mode and
disallows MD5, but the result isn't checked, and the following call to
EVP_DigestUpdate() results in openssl attempting to call ctx->update(),
although ctx->update is null.
[test case]
set up a system in FIPS mode with FIPS openssl, install pam-ssh-agent-auth and
configure per:
https://blog.heinzl.dev/use-public-key-to-prevent-sudo-passwor
Then ssh to the system, making sure to use -A to pass the local ssh-
agent along, and also ssh to an account that does not have NOPASSWD sudo
enabled. Then run 'sudo -i', which will segfault.
[regression potential]
TBD
[scope]
the use of MD5 fingerprint is still in upstream code, so this may need
to be fixed there and in all releases. alternately, a FIPS-compliant
package could be created.
[other info]
the openssl FIPS addition that causes this is:
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
so pam-ssh-agent-auth could set either flag to force openssl to allow
this use of MD5; however the pam-ssh-agent-auth code that calls into
openssl doesn't know what the md5 is going to be used for, so it may be
more complex, and probably is much simpler just to stop using MD5 for
the logged fingerprint.
** Affects: pam-ssh-agent-auth (Ubuntu)
Importance: Undecided
Status: New
** Affects: pam-ssh-agent-auth (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: pam-ssh-agent-auth (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: pam-ssh-agent-auth (Ubuntu Impish)
Importance: Undecided
Status: New
** Affects: pam-ssh-agent-auth (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964486
Title:
crash when in FIPS mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal
** Changed in: simplestreams (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal
** Changed in: simplestreams (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal
Everything looks good to me, just one question - I see uvtool-libvirt depends on python3-simplestreams, have you looked at and/or tested uvtool on focal with the backported python3-simplestreams? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
> systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. at some point it would be a better idea to drop the procps files and adjust the systemd defaults where/if needed. The sysctl configuration hasn't been applied by procps since upstart; with systemd, the systemd- sysctl service is what applies all the sysctl settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
> 5.31b+dfsg-4 is now in Jammy, can be considered this "bug" as solved? since it's still 'broken' in focal, i added a focal target, but changed the main bug to 'resolved'. the focal target could be changed to 'wontfix' if you don't think you will fix it there, or you could SRU the entire newer version back to focal if you get a SRU exception: https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases you could alternatively move the latest version back to the focal- backports pocket if you don't want to mess with SRUing it, but considering that the version in focal seems to be 100% broken, it would be better to just SRU the latest version, I think. ** Also affects: memtest86+ (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: memtest86+ (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
> "so this is fixed already in f and later" - think you mean "b and later" here? yes sorry, fixed in b and later ** Description changed: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, - so this is fixed already in f and later. + so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962286] Re: [FFE] sshuttle merged to 1.1.0-1ubuntu1 fails autopkgtests
For the xenial container under jammy problem, I opened bug 1962332 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962286 Title: [FFE] sshuttle merged to 1.1.0-1ubuntu1 fails autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1962286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962332] [NEW] xenial systemd fails to start if cgroup2 is mounted
Public bug reported: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in f and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962332 Title: xenial systemd fails to start if cgroup2 is mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962286] Re: [FFE] sshuttle merged to 1.1.0-1ubuntu1 fails autopkgtests
I looked a bit more into the trusty failure and it seems like that isn't a cgroups issue, since it doesn't use systemd and instead uses upstart, which doesn't seem to care about what cgroup is mounted. On trusty, the problem appears to be that it's simply too old to run with the python from jammy. By default, trusty sshuttle attempts to use 'python' on the remote system, which no longer exists in jammy. If --python is manually specified using jammy's python3, it fails: root@test-t:~# sshuttle --python python3 -r ubuntu@10.46.117.1 1.1.1.1/24 ubuntu@10.46.117.1's password: File "", line 1 import sys; skip_imports=1; verbosity=0; exec compile(sys.stdin.read(764), "assembler.py", "exec") ^ SyntaxError: invalid syntax client: fatal: server died with error code 1 If --python is manually specified using jammy's python2 (which isn't installed by default), that still fails: root@test-t:~# sshuttle --python python2 -r ubuntu@10.46.117.1 1.1.1.1/24 ubuntu@10.46.117.1's password: Traceback (most recent call last): File "", line 1, in File "assembler.py", line 26, in File "server.py", line 170, in main File "server.py", line 71, in list_routes File "server.py", line 51, in _list_routes File "ssubprocess.py", line 606, in __init__ File "ssubprocess.py", line 1117, in _execute_child OSError: [Errno 2] No such file or directory client: fatal: server died with error code 1 So it may not be possible to use sshuttle from trusty->jammy at all, unfortunately, and the jammy autopkgtests might need to just stop running the trusty->jammy tests completely. Note that the jammy->trusty connection does appear to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962286 Title: [FFE] sshuttle merged to 1.1.0-1ubuntu1 fails autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1962286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
** Changed in: gramps (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
** Changed in: gramps (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
** Changed in: gramps (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
** Changed in: gramps (Ubuntu) Status: New => Fix Released ** Changed in: gramps (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
> https://launchpad.net/~rosco2/+archive/ubuntu/backports/+packages ... > If you are building in a PPA, there is an extra flag to check in the PPA settings. the specific url, using the PPA linked earlier, would be: https://launchpad.net/~rosco2/+archive/ubuntu/backports/+edit- dependencies -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
> With your ACK I'm then going to accept my own upload yep fine with me, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
It looks like the build does have checks to set WITH_GSPELL off if the lib isn't available so the d/control could maybe just have [!i386] added to the libgtkspell3-3-dev depends? It looks like it already has that restriction for the ragel dep. Or, the Architecture could be changed to avoid i386; or as you said we can just ignore the i386 build failures. Any option is fine with me, as I agree it seems really unlikely anyone will want to use inkscape on a 32-bit system. Feel free to reupload with arch adjustment, or also feel free to accept the current upload (or let me know and I can accept it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
It looks like the i386 arch fails to build due to missing dep on 'libgtkspell3-3-dev': https://launchpad.net/~ddstreet/+archive/ubuntu/backport/+build/23139572 I'm not sure why i386 is missing in focal for that package; it seems like it's available both before and after focal, but the specific version in focal doesn't have it: https://launchpad.net/ubuntu/+source/gtkspell3/3.0.10-1 can you look into that before we approve the backport? Possibly there should be a no-change rebuild of gtkspell3 in focal to pick up that i386 build? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959541] Re: pull-lp-source crashed with AttributeError in __new__(): module 'collections' has no attribute 'Callable'
looks like this was fixed in git already, and should be fixed once 0.188 is released; @mapreri you planning to release that in debian soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959541 Title: pull-lp-source crashed with AttributeError in __new__(): module 'collections' has no attribute 'Callable' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945324] Re: systemtap 4.4 not compatible with linux kernel 5.11
@chfast @mukherjee-indraneel i think it's *extremely* unlikely - at least in the short term - that systemtap will become/remain usable in stable releases, especially when using HWE kernels; can I suggest that you try to use the backports process to provide a later (and hopefully working) version of systemtap to existing LTS release(s)? https://wiki.ubuntu.com/UbuntuBackports -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945324 Title: systemtap 4.4 not compatible with linux kernel 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1945324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
