[Bug 1920774] Re: v5.11 kernel seems to sometimes hang on unmatched board
For debugging i think it is best to use something like: console=ttySIF0,115200 earlycon=sbi note that by default kernel/systemd seem to enable sbi0 hvc0 (via sbi) ttySIF0 consoles all of which seem to be the same thing. It is quite confusing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920774 Title: v5.11 kernel seems to sometimes hang on unmatched board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920774] [NEW] v5.11 kernel seems to sometimes hang on unmatched board
Public bug reported: v5.11 kernel seems to sometimes hang on unmatched board ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Summary changed: - v5.11 kernel seems to hang on unmatched board + v5.11 kernel seems to sometimes hang on unmatched board ** Description changed: - v5.11 kernel seems to hang on unmatched board + v5.11 kernel seems to sometimes hang on unmatched board -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920774 Title: v5.11 kernel seems to sometimes hang on unmatched board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920723] Re: upgrade fwupd/focal to 1.4.x
Where problems could occur -> is incomplete. There are a lot less users on groovy, and a lot less people applying fwupd updates in groovy. What has changed/fixed? Which plugins/machines/skus are affected? Also note that this fwupd will not work with the next shim, due to lack of sbat sections. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920723 Title: upgrade fwupd/focal to 1.4.x To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
@Fred eldmannen+launchpad This issue is only fixed in the Ubuntu patchset for the Linux Kernel. Although I have submitted this fix upstream, it has not been picked up yet by kernel.org vanilla kernels. See https://lkml.org/lkml/2021/1/14/1091 The mainline builds you point to, do not contain Ubuntu patchset, and thus are as vanilla as possible. Meaning that yes, those builds are affected by this issue. There should be point release updates for Hirsute soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
*** This bug is a duplicate of bug 1920640 *** https://bugs.launchpad.net/bugs/1920640 ** This bug has been marked a duplicate of bug 1920640 EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
** Also affects: ubuntu-keyring (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-keyring (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: ubuntu-keyring (Ubuntu Hirsute) Importance: High Status: Confirmed ** Also affects: ubuntu-keyring (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-keyring (Ubuntu Hirsute) Importance: High => Critical ** Changed in: ubuntu-keyring (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: ubuntu-keyring (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: ubuntu-keyring (Ubuntu Groovy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2
It would be interesting to know: - if Secureboot is on or off (if at all supported) - the shim version installed - increase grub debugging and capture more detailed debug messages from grub - vmlinuz and/or initrd are corrupted, or the disk itself is in need of fsck - if using `linux-azure` yields better results, instead of `linux- generic` We could also escalate this to Azure / Microsoft as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918265 Title: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920055] [NEW] debootstrap
Public bug reported: usrmerge needs to be seeded, but not in the debootstrap set, somehow. ** Affects: debootstrap (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Affects: debootstrap (Ubuntu Hirsute) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: debootstrap (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: debootstrap (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: debootstrap (Ubuntu Hirsute) Status: New => Triaged ** Changed in: debootstrap (Ubuntu Hirsute) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920055 Title: debootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1920055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918120] Re: dpkg/debhelper building with noudebs by default broken linitian
** Changed in: lintian (Ubuntu) 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/1918120 Title: dpkg/debhelper building with noudebs by default broken linitian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1918120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919563] Re: updated sssd with smart cards now brick systems without full cert chain
re conversion / upgrades => we should really find the full chain if we can to inject it into openssl. I'm not sure if there are any ways to force openssl to be happy with trusted issuer without a full chain. I would have thought there is a way to make openssl do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919563 Title: updated sssd with smart cards now brick systems without full cert chain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1919563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919563] Re: updated sssd with smart cards now brick systems without full cert chain
Re: certs. Ideally we should be shipping a bundle of certificates, which are well known roots of trust for smarcards. Aka the DOD, National ID cards/passports, etc. In a new path locations. Because the smartcard roots of trusts are not the same as for https:// connections. But that's not immediately fixable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919563 Title: updated sssd with smart cards now brick systems without full cert chain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1919563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919563] Re: updated sssd with smart cards now brick systems without full cert chain
I think that is a long standing openssl bug that it demands full chains, and more so it trips up not only when the chain is incomplete, but also where there are extra chains, which are redundant; and if any of them have untrusted certs, or certs of small sizes / old hashes (aka legacy chains) it also refuses to establish connections. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919563 Title: updated sssd with smart cards now brick systems without full cert chain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1919563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904271] Re: Python 3.9 package is missing dependency on tzdata
Installing -full package will pull in all the things and make all the things work. We absolutely have a wrath of people complaining about the size of tzdata and that it must not be in their containers / systems, even though they otherwise use python. so would you rather not ship zoneinfo module, such that the import fails? and then move it to like python3-zoneinfo package and make regular std recommend it, but not depend on it. That way classic server / desktop installs have it, but specifically docker containers will not, because they are required to ship without tzdata. if i recall correctly, we only ship minimal docker containers with just the UTC timezone. Such that lookups of UTC should work. At the moment, the way we ship python is a compromise between the wrath of people who deploy these things in production and demand to shrink the size of python and its deps. And the polar oposite of the typical desire to have all the things enabled / ship all the things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904271 Title: Python 3.9 package is missing dependency on tzdata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1904271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842047] Re: Flavors should use their slideshows in oem-config
we should install matching slideshow when install oem-config into target not sure how we can ensure that only the right slideshow is in the /pool/ and in-target for oem-config installs. ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Wishlist ** No longer affects: oem-config (Ubuntu) ** Tags removed: rls-hh-incoming ** Tags added: rls-hh-notfixing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842047 Title: Flavors should use their slideshows in oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919395] Re: Must not provide ifupdown on Ubuntu
we do not have time to commit to integrating this package into Ubuntu, thus it should be removed & blocklisted until it is integrated with ubuntu properly. ** Summary changed: - Must not provide ifupdown on Ubuntu + RM: ifupdown2 & blocklist (Must not provide ifupdown on Ubuntu) ** Changed in: ifupdown2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919395 Title: RM: ifupdown2 & blocklist (Must not provide ifupdown on Ubuntu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown2/+bug/1919395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
Opened https://github.com/openssl/openssl/issues/14607 ** Bug watch added: github.com/openssl/openssl/issues #14607 https://github.com/openssl/openssl/issues/14607 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
> to change the security level. Here Ubuntu deviates from standard OpenSSL 1.1.1 policies. So I ask again: Should we detect and special case the deviation and document it? I am reluctant to say yes here. But also want to ask how would you detect that it's an Ubuntu, or ubuntu derived openssl. I don't think we export anything in openssl APIs to be definitive about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
> Could you hook up the check to SSL_CTX_set_min_proto_version() and return an error code when level and security policy don't match? It's a modern setter, so it can return 0 on error. That is interesting proposal. However, need to be careful as to potentially not break configs, i.e. if they specify min_protocol_level first, then lower the security level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
so looking into that hook, it should ignore passno & always include fscks. Will try to upload that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918733] Re: file integrity check provides no feedback to the user
loopy thing is just booting slowly. The media check is performed in the background, but should not be blocking boot per se. Will double check things again, when doing iso testing in a bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918733 Title: file integrity check provides no feedback to the user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1918733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Kind of wish for a config option that would do add_to_platform_keyring a built-in set of keys, until we have something like the other platforms have (ipl on s390x, uefi db on EFI platforms). Similar to how the built-in trusted keys are initialized. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
this is all very annoying! But I see what you mean now. We probably should not add opal keys to the trusted_keyring then. I would rather avoid introducing a new CA key whilst we cannot travel to assemble and distribute CA shards offline. I'd rather somehow enable platform_keyring or IMA keyring, and make kernel have ability to specifies keys listed there at build time and ship the OPAL key there. Cause the keys we use to sign kernel image & grub-image, are not the keys that are used to signed kernel modules, hence shouldn't be in the trusted kerying. Or we can end up with a userspace .service that exports trusted_keyrings and imports them into ima keyring on everyboot. But that would be sad as well. Let me find power machines to play around with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920008] [NEW] grub2-signed depends on grub2-common
Public bug reported: [Impact] * one-grub has loosed the dependencies between src:grub2-signed and src:grub2, specifically grub2-common. However the modules in grub modules built by src:grbu2-unsigned require a high enough version of grub2-common with support for R_X86_64_PLT32 relocations. Generate depends that are high enough, for older releases. Otherwise users that have grub-efi-amd64-signed installed may get errors upon trying to configure the package from `grub-install` unable to handle unknown relocation. [Test Plan] * Disable -proposed * Install grub-efi-amd64-signed * Enable -proposed * Install grub-efi-amd64-signed (again) * Observe that not only grub-efi-amd64-signed is upgraded, but also that new version of grub2-common are upgraded too, on bionic and earlier series. [Where problems could occur] * As one-grub evolves, similar dep updates may be required in the future again. Thus every one-grub update should be tested across all releases prior to upload into -proposed. [Other Info] * This bug also reported at https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917509 ** Affects: grub2-signed (Ubuntu) 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/1920008 Title: grub2-signed depends on grub2-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1920008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919395] [NEW] Must not provide ifupdown on Ubuntu
Public bug reported: I am concerned about shipping ifupdown2 package in Ubuntu, with declaration that it can provide ifupdown. It is not a direct replaced of ifupdown in Ubuntu, as features present in Ubuntu's ifupdown are not implemented in ifupdown2 package. * allow-hotplug / auto / udev-rules for hotplug are not present * does not use dhclient -1 option * does not ship resolved integration Installing ifupdown2 thus will break system expectations, reintroduce previously fixed bugs, potentially leave people without networking if they are currently using ifupdown. Imho ifupdown2 package should be removed from the archive, or for at least Provides ifupdown should be dropped, until it gains bug fixes and features to be a viable ifupdown provider on Ubuntu. ** Affects: ifupdown2 (Ubuntu) Importance: High Status: New ** Tags: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919395 Title: Must not provide ifupdown on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown2/+bug/1919395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919339] [NEW] streams should be gpg signed & gpg verified
*** This bug is a security vulnerability *** Public security bug reported: streams should be gpg signed & gpg verified Over at https://cloud-images.ubuntu.com/releases/streams/v1/ https://cloud-images.ubuntu.com/releases/streams/v1/index.sjson is GPG signed stream, with key available from src:ubuntu-keyring package. Similarly https://images.maas.io/streams/v1/ should also be probably GPG signed And ditto https://cdimage.ubuntu.com/ubuntu-core/appliances/streams/v1/ and any other streams that I might now. Also multipass & maas should have access to the gpg keyrings (i.e. vendor various debs produced by src:ubuntu-keyring) and fetch streams with gpg verification. Otherwise we cannot detect if streams get mirrored and tampered with. ** Affects: cloud-images Importance: Undecided Status: New ** Affects: maas Importance: Undecided Status: Incomplete ** Affects: ubuntu-cdimage Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Also affects: maas Importance: Undecided Status: New ** Also affects: cloud-images Importance: Undecided Status: New ** Information type changed from Public to Public Security ** Also affects: ubuntu 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/1919339 Title: streams should be gpg signed & gpg verified To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1919339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
191691 has not been mirrored to launchpad, thus Ubuntu developers cannot see any of that details. Note that Ubuntu does not have access to the LTC bugzilla, instead bugproxy mirrors reports to Launchpad as needed. Please check with hws if 191691 should be mirrored across, or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892023] Re: RM: obsolete android tooling, FTBFS, python2, no longer needed
@jbicha but both adb and fastboot that we ship, are no longer compatible with what are now considered quite old releases of Android. If we still want them, we should ship versions that can authenticate with android firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892023 Title: RM: obsolete android tooling, FTBFS, python2, no longer needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-build/+bug/1892023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
** Changed in: wireshark (Ubuntu) Status: Confirmed => 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/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
On SSLcontext, security callback has prototype /* Security callback */ int (*sec_cb) (const SSL *s, const SSL_CTX *ctx, int op, int bits, int nid, void *other, void *ex); if one calls that function, with context passed in, "op" set to SSL_SECOP_VERSION, "bits" set to zero, "nid" set to protocol version, other set to NULL, and ex set to null => then the security callback will tell us if at the current configuration a given protocol version is acceptable. This should work on OpenSSL 1.1.0+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
Oooh, can we add bindings for: s->cert->sec_cb() and then call it with SSL_SECOP_VERSION operation with nbits set to TLS1.1 version? then it will return and tell us if it is acceptable or not, by the security level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
ideally it would be nice if we could access sec_cb and call it with the protocol versions to check the versions there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
I feel that openssl upstream needs to add: server_context.verify_consistent() Because in the above example, even before trying to establish the connection between the two context, the server context is already internally inconsistent. And upstream has changed the meaning of security levels in the past, and will do so again in the future. Ditto distro customization which brought the preview of such change earlier. It does feel that until such API arrives upstream, one needs to do something to the effect of: 1) if openssl version 3.x, and security level is greater than 0, assume no TLS1.1 is available 2) if openssl version 1.1.1+, and security level is greater than 1, assume no TLS1.1 is available 3) if ctx.get_min_proto_level returns TLS1.2 assume no TLS1.1 is available 4) else try setting min_proto_level and run tests 5) if min_proto_lvel is not available the build is against openssl 1.0.2x series, TLS1.1 is probably available. Above logic should cover the next upstream openssl version; the current deployments of ubuntu derivatives; the debian derivatives; and fedora/rhel derivatives. 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/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844761] Re: Casper doesn't properly support NFSOPTS
** Changed in: casper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844761 Title: Casper doesn't properly support NFSOPTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1844761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use
** Changed in: casper (Ubuntu) Status: In Progress => Fix Committed ** Changed in: casper (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/1870408 Title: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1870408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877618] Re: 20.04 fails to boot via PXE (amd64) - "hidden .disk not found, and hard to discover"
** Changed in: casper (Ubuntu) Status: Confirmed => Incomplete ** Description changed: The problem: The following PXE cmdline fails to boot the 20.04 Desktop iso served via NFS but works flawlessly for 19.10 and earlier: "imgargs vmlinuz initrd=initrd root=/dev/nfs boot=casper netboot=nfs nfsroot=: ip=dhcp splash quiet --" During early boot, the only error message printed is: "Unable to find a live file system on the network" with no further help on why the failure occoured or how to resolve it. During debugging it was also found that the above message is printed for multiple failures during boot, which does not help to differientiate what's actually failing for what reason. How to reproduce: 1. Download the official ubuntu desktop iso 2. Mount iso as loop on /mnt/iso 3. Copy (cp -r /mnt/iso/*) iso files to nfsroot location + + No, do not use '*' use '.' as in cp -r /mnt/iso/. => as per + documentation at https://wiki.ubuntu.com/LiveCDNetboot + 4. Copy vmlinuz and initrd from iso to tftp location 5. Boot client PC 6. Watch boot fail - The solution (case specific): In my case the underlying problem was caused by the .disk folder not being copied by cp to the nfsroot location. Once that was resolved, the above cmd line started working again. Suggested fixes: 1. instead of .disk, use a folder which is not hidden by default and will hence be captured by normal copy operations 2. (significantly) improve error messages when currently the "no live file systems found" message would be triggered to better guide users to possible error causes and solutions 3. update documentation to point out importance of the .disk directory for PXE (and other) ways of booting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877618 Title: 20.04 fails to boot via PXE (amd64) - "hidden .disk not found, and hard to discover" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1877618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883274] Re: Please use blake2b blake2s for CRC checking
** Description changed: - Please use blake2b-256 blake2s-256 for CRC checking, instead of md5sums + Please use blake3 for CRC checking, instead of md5sums they are faster than md5sum and more secure ** Summary changed: - Please use blake2b blake2s for CRC checking + Please use blake3 for CRC checking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883274 Title: Please use blake3 for CRC checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1883274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905383] Re: Xubuntu hirsute live system, on shutdown no "Please remove the installation medium, then press ENTER:" message appeared
Does pressing any key on keyboard make the message render better? What are the exact words of the message seen? There are two wordings one for graphical splash and another for serial text. One is "and press enter" the other one is "and reboot" or some such. Does changing TTYs make the message appear? cycle with ALT-[arrow key right] repeatedly. ** Changed in: casper (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905383 Title: Xubuntu hirsute live system, on shutdown no "Please remove the installation medium, then press ENTER:" message appeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1905383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915515] Re: "toram" loads the entire media, not just filesystem.squashfs
toram is meant to be the option for single disk devices. I.e. when iso is blasted on the drive. machine is booted off that drive. installer is transfered to ram. and then installation is done on the same drive. Unless we transfer all of ISO to ram, this will not be possible to complete correctly, or at all if there is no network connectivity. ** Changed in: casper (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915515 Title: "toram" loads the entire media, not just filesystem.squashfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1915515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897930] Re: use something better than md5sum to verify image contents
this is not meant to be cryptographic authenticity check. it's meant to be a quick check against media corruption. for authenticity checks we do publish sha256sum of the .iso, gpg sign the package pool, and gpg sign filesystem.squashfs for when booting over the network. md5sum is fastest CRC like function. If there is anything faster we would use that. I.e. we might use blake3 instead. But not sha256 it's very slow. ** Changed in: casper (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897930 Title: use something better than md5sum to verify image contents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1897930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917590] Re: File integrity check at boot of install media no longer functional
** Changed in: casper (Ubuntu Hirsute) 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/1917590 Title: File integrity check at boot of install media no longer functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918733] Re: file integrity check provides no feedback to the user
installers should parse and present the status information as generated in /run. apport & subiquity use it. And ubiquity will store it in /var/log/installer with the next ubiquity upload. even when it did show error, it didn't block boot and just delayed it a bit. So in practice everyone was still running off bad media. ** Changed in: casper (Ubuntu) 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/1918733 Title: file integrity check provides no feedback to the user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1918733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck in initrd if mount pass is 0
wait what?! =/ fsck binaries should totally be there! that sounds very broken if they are not there. ** Changed in: initramfs-tools (Ubuntu) Importance: Medium => Critical ** Summary changed: - initramfs-tools does not include fsck in initrd if mount pass is 0 + initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887638] Re: Failure to build snap that runs pull-lp-source
I have made improvements to pull-lp-source in hirsute which make things better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887638 Title: Failure to build snap that runs pull-lp-source To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1887638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
Please note that: OpenSSL upstream security level 3 only allows TLS v1.1 and above OpenSSL upstream security level 4 only allows TLS v1.2 and above, DTLS v1.2 and above On Ubuntu, these restrictions are brought in earlier at security level 2. Thus, if one builds upstream OpenSSL with security level set to 4 all of the above testsuite should be failing as well. I feel there is lack of API documentation about this in OpenSSL. Also, Python tests are incomplete and are not testing for, or setting appropriate security levels for the protocols they are attempting to use. Thus are not using the OpenSSL api correctly and making assumptions about the openssl library that are out of date with current standards and requirements. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
I need to verify a few things, but I believe it is to do with chiphersuites, seclevel callback, and protocol versions. When setting chiphersuite string ; or changing security level; or changing the security level callback; or setting min/mas protocol versions. All of those things are not checked against each other to ensure that as whole they are compatible with each. Then at connection establishment time things are verified and security callback is called and things go "you request max version y, but security hook rejects things at y, no connection for you". This does brings the existential/API question similar to the previous bug report. It is not known over the API that security level is 2 and that it rejects protocol versions. I wonder, if setting min_version / max_version, that would be rejected by the current security level, if security level should be adjusted appropriately automatically. I.e. when trying to set min protocol version to TLS1.1 and the security level is at 2, if security level should be updated to 1 automatically. Or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error
** Also affects: openssl (Ubuntu Hirsute) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917625 Title: OpenSSL TLS 1.1 handshake fails internal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917780] Re: initramfs-tools does not include fsck in initrd if mount pass is 0
*** This bug is a duplicate of bug 1902103 *** https://bugs.launchpad.net/bugs/1902103 We must honor MNT_PASS. The actual bug is that many things do not set it to 1 by default as they should have. I.e. bits in curtin, maas, subiquity, cloud-images. It is correctly set to 1 on ubiquity desktop images and d-i based installs. So this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source /livecd-rootfs/+bug/1902103 ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Won't Fix ** This bug has been marked a duplicate of bug 1902103 Ensure default fstab options are sane and consistent across all images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck in initrd if mount pass is 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917590] Re: File integrity check at boot of install media no longer functional
** Also affects: casper (Ubuntu Hirsute) Importance: High Status: Confirmed ** Changed in: casper (Ubuntu Hirsute) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917590 Title: File integrity check at boot of install media no longer functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1917590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916034] Re: Please merge flash-kernel 3.104 from Debian unstable
** Changed in: flash-kernel (Ubuntu) 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/1916034 Title: Please merge flash-kernel 3.104 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1916034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916898] Re: Please merge u-boot 2021.01+dfsg-2 from Debian unstable
** Changed in: u-boot (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/1916898 Title: Please merge u-boot 2021.01+dfsg-2 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1916898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917509] Re: Call for testing: grub2 security updates
@kleber that is known, and being worked on. It seems that one has upgraded grub2-signed without upgrading grub2. We are adding more strict dependencies to mitigate that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917509 Title: Call for testing: grub2 security updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916898] Re: Please merge u-boot 2021.01+dfsg-2 from Debian unstable
** Changed in: u-boot (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/1916898 Title: Please merge u-boot 2021.01+dfsg-2 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1916898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916034] Re: Please merge flash-kernel 3.104 from Debian unstable
** Changed in: flash-kernel (Ubuntu) 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/1916034 Title: Please merge flash-kernel 3.104 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1916034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable
** Changed in: initramfs-tools (Ubuntu) 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/1915966 Title: Please merge initramfs-tools 0.139 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable
> git range-diff old/debian..logical/0.137ubuntu12 new/debian..merge/0.139ubuntu1 i see this and i have no clue what i am looking at! i guess i need to go and learn how to read range-diffs! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915966 Title: Please merge initramfs-tools 0.139 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
The nat fiddles are not visible inside the container network namespace. Thus I am wondering if there is an odd interaction between namespace, nftables based iptables vs legacy iptables. I.e. whilst the host is configured using legacy iptables, maybe the lxd guests must be using legacy iptables too. I'll experiment to see if forcing to simply only use iptables-legacy inside the lxd guest is good enough for now. Despite the hosts getting upgraded to bionic. Cause it's only groovy that started to use nftables based iptables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872050] Re: package gcc 4:9.2.1-3.1ubuntu1 failed to install/upgrade: installed gcc package post-installation script subprocess returned error exit status 2
I think /usr/bin/gcc-9 is a recursive symlink to **nowhere** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872050 Title: package gcc 4:9.2.1-3.1ubuntu1 failed to install/upgrade: installed gcc package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1872050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872050] Re: package gcc 4:9.2.1-3.1ubuntu1 failed to install/upgrade: installed gcc package post-installation script subprocess returned error exit status 2
Настраивается пакет gcc (4:9.2.1-3.1ubuntu1) … update-alternatives: ошибка: не удалось выполнить stat для файла «/usr/bin/gcc-9»: Слишком много уровней символьных ссылок dpkg: ошибка при обработке пакета gcc (--configure): Setting up package gcc (4:9.2.1-3.1ubuntu) update-alternatives: error: could not perform stat on file : Too many levels of symbolic links dpkg: error while processing package gcc (--configure): I think /usr/bin/gcc-9 is a recursive symlink to anywhere? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872050 Title: package gcc 4:9.2.1-3.1ubuntu1 failed to install/upgrade: installed gcc package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1872050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
i think either -L or -S "made everything work". Note that there is no iptables installs in the lxd container, and we install iptables on the fly. nftables are not installed either, because that's not in main. So when lxd container started, nothing did "restore" of any default chains I don't think. But also have no idea if any are needed, or if I can tune any debugging in the kernel to notice if iptables are poked in some odd ways inside the network namespace that we are in. Also note all the extra setup that launchpad-buildd does: https://git.launchpad.net/launchpad-buildd/tree/lpbuildd/target/lxd.py in terms of creating lxd profile, and doing stuff to the bridge with iptables. I wonder if I must always use legacy iptables, if that's what used on the host to configure the bridge of the lxd container one is in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
@Daniel "In either case, however, the CA that signs the kernel signing key needs to be built in to the kernel's .builtin_trusted_keys keyring." On Ubuntu, for OPAL singing, on PowerPC, we do not use CA at all. It is our understanding that firmware doesn't support verifying signature chains to a CA. Thus instead we use self-signed certificates for the kernel which have not been signed by a CA. Thus we should simply include them all in trusted keyring, and there is no need to ship anything on disk or load anything from the userspace. We have UEFI CA which is used for UEFI booting and embedded in the UEFI shim, but I do not believe it is appropriate to use that CA here, as the revocations are controlled by a KEK key which has no relationship with POWER firmware vendors. @sforshee Subject: CN = Canonical Ltd. Live Patch Signing Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., OU = Secure Boot, CN = "Canonical Ltd. Secure Boot Signing (POWER, 2017)" Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing This is all that's needed for now. However, we should start also shipping the next/future OPAL signing certificate that we have generated in 2019. Please add the 2019 opal signing certificate as debian/opal-2019-ppc64el.pem Key ID: 6B:E5:A1:25:FC:48:97:91:02:2C:2B:FB:54:91:16:F6:07:16:EA:81 There are no CA to add, and no keys to load from userspace. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907422] Re: [MIR] needrestart + dependencies
checkrestart only checks packaged things, whereas needrestart also monitors and offers to restart unpackaged end-user created daemons, user-session processes, runtime ephemeral scopes and things that might be unsupervised at all. overall checkrestart is insufficient to identify and restart things that may still be using vulnerable libssl for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907422 Title: [MIR] needrestart + dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libintl-perl/+bug/1907422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
However I do not think that google.com is a good test, as it will try to redirect to https, no? and magic proxy only does things with http. We are failing to reach http ftpmaster.internal. I am now trying to rewrite bits of magic-proxy to use more of urllib and surface more HTTP and IO errors. Maybe it will tell us something more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
@alex Thanks for trying this. And yes, we have been unable to reproduce this outside of launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
otherwise cross-compile bootstrap is an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915722] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
you can republish last working on in a ppa, and then have strict build- depends on version guarded one in the next ppa (with build-dep on the first ppa) to rebuild fixed one with last fixed toolchain. if there is one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918120] [NEW] dpkg/debhelper building with noudebs by default broken linitian
Public bug reported: dpkg/debhelper building with noudebs by default broken linitian New dpkg/debhelper in ubunty imply "DEB_BUILD_OPTIONS=noudeb" build profile, which makes lintian FTBFS and fail its autopkgtest, as somehow when building udebs as part of the testsuite doesn't produce them, and everything is sad. This is now holding up migrations. Please mark linitian as badtest, i will try to fix the next upload of lintian to work correctly with now implied `noudeb` build profile. Please badtest current lintian in hirsute-release & hirsute-proposed. ** Affects: lintian (Ubuntu) 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/1918120 Title: dpkg/debhelper building with noudebs by default broken linitian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1918120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917810] Re: Setup for raspberry image is broken
"1." maybe a gnome-shell / Xorg / graphics driver issue. "2." after you completed setup and logged in, did you receive a popup saying that language support is incomplete, with an offer to install the missing language packs? "3." is what I call "the-keyboard-bug" every page of our setup/installer dialogs have a keyboard layout bug. Either inability to switch layout, or wrong layout set. "4." - "5." i don't know. "6." is related to "2." although the full language pack for all of desktop to be available in a given language are not there, the base strings of the installer setup app should have been there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917810 Title: Setup for raspberry image is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1917810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917920] [NEW] magic-proxy broke with iptables 1.8.7-1ubuntu2
Public bug reported: when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. ** Affects: launchpad Importance: Undecided Status: New ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: launchpad Importance: Undecided Status: New ** Summary changed: - magic-proxy broke with 1.8.7-1ubuntu2 + magic-proxy broke with iptables 1.8.7-1ubuntu2 ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu) 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/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1917920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765933] Re: Allow building livefses against a view of the archive at a fixed point in time
@colin watson After fighting with magicproxy & iptables issues. again. I am interested in getting magic proxy doing more-or-less things that might one day make things "nice". I.e. make magic proxy, talk to launchpad proxy to access authenticated archives without explicit username/password. drop iptables nat rules, and instead try to simply export proxy for apt to use. try to drop proxy, and instead make magic-proxy write out in-release- path stanzas for apt to use based on the passed in timestamp, and make livebuild / debootstrap use all that. eventually "just" accept the mapping of archive/suites = hash as collected via launchpad api before dispatching the build. Hopefully above things will make certain things easier as we go along. Alternatively, maybe we could merge magic-proxy into the proxy that launchpad exports for the builds? I guess probably not, cause all of that is quite hackish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765933 Title: Allow building livefses against a view of the archive at a fixed point in time To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1765933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1916165 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Tags removed: block-proposed block-proposed-hirsute patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
ubuntu-core-initramfs v40 has support for main & server features, which on x86 are enabled by default. The next snap build of pc-kernel in 20/ tracks should contain the required modules. ** Changed in: ubuntu-core-initramfs 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878969] Re: time-epoch never changes in SRUs
with core-initrd v40, each new initrd build increases time epoch. This still means that for brand new account keys, one needs to wait or build a new kernel to be able to boot in UC20. ** Changed in: ubuntu-core-initramfs 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/1878969 Title: time-epoch never changes in SRUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Can you please provide the output of: $ sudo ubuntu-drivers list In the live session? There are two ways to get the nvidia kernel driver. One option is to compile it from scratch on the users machine with dkms. THe other option is to install a metapackage linux-modules-nvidia for the appropriate kernel flavour and the appropriate nvidia revsision which provides a prebuild, not linked, and secureboot signed nvidia module. So as to why the dkms one will not work or load on secureboot machines, unless one goes through cryptic MOK key enrollment procedure during boot. The secureboot signed nvidia module works on secureboot machines without any additional steps by the user. But the caveat is that the secureboot signed ones must be kept in correct tandem with the kernel flavour & nvidia revisions. Anything you install from the PPA will not be secureboot signed, and thus need MOK signing. ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu) 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/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916898] Re: Please merge u-boot 2021.01+dfsg-2 from Debian unstable
** Changed in: u-boot (Ubuntu) Status: New => In Progress ** Changed in: u-boot (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916898 Title: Please merge u-boot 2021.01+dfsg-2 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1916898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887187] Re: [MIR] nftables
In trello, there is no asignee to perform the security review. Thus removing assignee. @ Security Team, when and who can do security review of nftables? we are overdue to seed nftables by default. ** Changed in: nftables (Ubuntu) Importance: Undecided => Critical ** Changed in: nftables (Ubuntu) Status: Incomplete => New ** Changed in: nftables (Ubuntu) Assignee: Seth Arnold (seth-arnold) => (unassigned) ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887187 Title: [MIR] nftables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1887187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872098] Re: Installing nftables empties the current ruleset
Automatically added by dh_installsystemd/11.1.3ubuntu1 was present in postinst in bionic, despite debian/rules saying --no-start In focal there is no attempt made to start/restart nftables upon package configuration. ** Also affects: nftables (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nftables (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/1872098 Title: Installing nftables empties the current ruleset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1872098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Changed in: grub2 (Ubuntu Hirsute) Status: Fix Released => In Progress ** Changed in: grub2-signed (Ubuntu Hirsute) Status: Fix Released => In Progress ** Also affects: grub2-unsigned (Ubuntu) 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/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917665] Re: PXE booting exits into grub command-line
MAAS does not use grub from the archive directly. It uses streams. First stop is to debug it with MAAS team. For example, which image streams are you using? which bootloaders revision are you on? is this with UEFI or Bios boot? The bootloader version from the stream is needed to figure out if you are on the latest bootloader level or not. ** Also affects: maas Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Status: New => Incomplete ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917665 Title: PXE booting exits into grub command-line To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1917665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905472] Re: Something starts dhcclient for every intrface on boot
aoetools is effectively unchanged, and their initramfs_hook is the same since xenial. in the initramfs-tools the changes between 18.04 LTS and 20.04 LTS are that for automatic IP bring up, more methods are now supported with more robust IPv4 DHCP and IPv6 DHCP. Was your 18.04 LTS installation customized to prevent DCHP in the initrd? Or was DHCP attempted in 18.04 LTS and simply was failing, keeping things working? Is this something you can rectify with preup ifupdown hooks, such that dhcp leases that are not needed are removed in the running system? Or is booting with ip=none parameter sufficient for you? Please indicate what has changed, to cause failures. Because the behaviour of aoetools in stock configuration between 18.04 LTS and 20.04 LTS is expected to be the same, with dhcp being performed from the initrd by default. ** Changed in: aoetools (Ubuntu) Status: New => Incomplete ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete ** Summary changed: - Something starts dhcclient for every intrface on boot + aoetools initramfs hooks starts dhcclient for every intrface on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: aoetools initramfs hooks starts dhcclient for every intrface on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aoetools/+bug/1905472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905472] Re: Something starts dhcclient for every intrface on boot
aoe hook is provided by https://packages.ubuntu.com/source/hirsute/aoetools If you need this package, but you do not want aoe hook to fire in the initramfs, you can as a local override dissable it with: dpkg-statoverride --add --update root root 0644 /usr/share/initramfs- tools/scripts/local-top/aoe Or if you have recommendations to improve it, please share your thoughts. Your remarks in your comments are not polite. Please check out https://ubuntu.com/community/code-of-conduct ** Changed in: ifupdown (Ubuntu) Status: Incomplete => Invalid ** Changed in: netplan.io (Ubuntu) Status: Incomplete => Invalid ** Also affects: aoetools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aoetools/+bug/1905472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905472] Re: Something starts dhcclient for every intrface on boot
I marked the bug incomplete, when asking for additional information. Which is a normal bug processing procedure. This happened _before_ your comment #4 and #5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aoetools/+bug/1905472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878969] Re: time-epoch never changes in SRUs
** Changed in: ubuntu-core-initramfs 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/1878969 Title: time-epoch never changes in SRUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905472] Re: Something starts dhcclient for every intrface on boot
ubuntu-core-initramfs project is not used on Ubuntu 20.04 LTS servers and desktops. However I also don't think this is caused by initramfs. It would help for you to check your NetworkManager configuration, netplan configuration and ifupdwon configurations. ** Project changed: ubuntu-core-initramfs => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete ** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Changed in: ifupdown (Ubuntu) Status: New => Incomplete ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1905472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New ** Changed in: ubuntu-core-initramfs 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/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Tags added: block-proposed block-proposed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
But Debian & Fedora implementation are buggy, because they break 1.0.2x users & they do not prohibit DTLSv1.1 whilst enforcing TLSv1.2+. So although Debian & Fedora look "nice" they are security vulnerable configurations. I can set min_version to TLSv1.2, in addition to security level 2 but that will not make current stable test_ssl test suite pass, as it will require not only changing min_level but also setting security level to 1. I do not see a way to make things secure, for both TLS and DTLS, and discoverable and not pain to use. Because when default context is created it is not known if TLS or DTLS will be used, and the enums for TLS & DTLS are not compatible with each other. Ultimately it is deficiency in the OpenSSL APIs because it is impossible to know what is or isn't allowed by a given client OpenSSL context, against which server context, and vice versa. Even when enums are available, and one sets them as appropriate min/max. There are no inspection APIs available into the security levels. For example, it impossible to query if ones client certificate is suitable for a given security level, apart from trying to establish the connection. Re Kurt => i have spoken to Kurt about this, he is aware that Debian's implementation is buggy and he does prefer Ubuntu's one, however Ubuntu's one is not without drawbacks either. I.e. at the moment in Debian people simply choose to not install openssl package and thus end up operating without public certificates and with TLS v1.1/v1.0 enabled, meaning the system is insecure by accident against the intentions. Especially if one tries to be secure, and use private CA certificates only. """ 2) With some configuration, OpenSSL's SSL_do_handshake() function fails with an "internal error" message (SSL_AD_INTERNAL_ERROR / TLS1_AD_INTERNAL_ERROR) somewhere in its internal state machine. """ I'm not sure how this is related to anything of the above, can you please open a new bug report with details? crashes in handshake are typically specific to the connection type, context on both client & server, and well bugs. The one thing that I know failing badly, is when server has redundant tls certificates in its chain that are considered insecured (i.e. old CA cross-signed new CA). And OpenSSL client currently rejects establishing the connection, despite the server chain having alternative paths of certs that are secure throughout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
Fedora & Debian & Ubuntu implement openssl differently. In Ubuntu, as an Ubuntu-specific patch, we set default security level to 2, and prohibit protocols lower than TLSv1.2 / DTLSv1.2. This is documented in the Ubuntu manpages for OpenSSL http://manpages.ubuntu.com/manpages/hirsute/en/man3/SSL_CTX_set_security_level.3ssl.html """ The default security level can be configured when OpenSSL is compiled by setting -DOPENSSL_TLS_SECURITY_LEVEL=level. On Ubuntu, 2 is used. Level 2 Security level set to 112 bits of security. As a result RSA, DSA and DH keys shorter than 2048 bits and ECC keys shorter than 224 bits are prohibited. In addition to the level 1 exclusions any cipher suite using RC4 is also prohibited. On Ubuntu, TLS versions below 1.2 are not permitted. Compression is disabled. """ This is the only way that we have able to configure minimum key sizes, protocol versions for both TLS and DTLS without making any openssl cnf changes, whilst remaining compatible with both openssl cnf from 1.0.2x, 1.1.0x and 1.1.1x series. As min/max API calls are not available across all openssl series and software that allows to configure openssl cipherstrings but not min/max versions. If you need access to (D)TLS below 1.2 or weak cryptography you can use openssl 1.1.1 API to set_security level to 1. Or you can set CipherString to DEFAULT@SECLEVEL=1. Without modifying the software at all, libssl can be configured via envrionment variables too. I.e. exporting export OPENSSL_CONF=`pwd`/openssl.cnf cat openssl.cnf openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] CipherString = DEFAULT@SECLEVEL=1 Note that this openssl.cnf is compatible with _any_ openssl series. In debian, they set min versions of TLS communication only, which breaks with openssl 1.0.2x series as it fails to parse those settings. That was unacceptable for Ubuntu. I don't know how Fedora implements this, I guess I should take a look. It would be nice for OpenSSL upstream to provide a standard configure time option to set these things in a consistent manner, as at the moment each distribution has to invent their own way of doing this. My proposals to bump minimum protocol versions to TLSv1.2 in OpenSSL 3.0.0 for the time being got rejected, as it is deemed too soon. In Ubuntu, we also configure GnuTLS with similar parameters, the override mechanism there is different see https://discourse.ubuntu.com/t /default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8 for both OpenSSL and GnuTLS details. I'm not sure what is expected from this bug report. Ubuntu changes are documented and publicized and are trivial to find. Were you expecting to find this documentation somewhere else? Where did you look? I am happy to add more documentation in more places, or change the implementation. What does Fedora do? And is it portable to distributions that do not use the crypto-policies package to maintain configs? ** Changed in: openssl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881006] Re: Incorrect ESP mount options
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881006 Title: Incorrect ESP mount options To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1881006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917555] [NEW] UC20 Online Key signing request for grub2-signed 1.164
Private bug reported: This is the UC20 Online Signing Key Request for grub2-signed Package versions: grub2-unsigned 2.04-1ubuntu42 grub2-signed 1.164 grub2 build PPA to copy from: https://launchpad.net/~canonical- foundations/+archive/ubuntu/uc20-build-ppa signing PPA to use: ~canonical-signing UC20 signed binaries staging ppa: https://launchpad.net/~canonical- foundations/+archive/ubuntu/uc20-staging-ppa Steps Todo: 1) ~canonical-signing to copy with binaries grub2-unsigned 2) await signing NB! do not copy grub2-signed at the same time, as build-depends will be satisfied from the archive, instead of PPA, as the package version of grub2 is unchanged, and will result in a miss-built. 3) source-only copy grub2-signed 4) canonical-signing to copy with binaries grub2 & grub2-signed to the staging ppa ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Description changed: This is the UC20 Online Signing Key Request for grub2-signed Package versions: grub2-unsigned 2.04-1ubuntu42 - grub2-signed 1.142.8+uc20.1 + grub2-signed 1.164 grub2 build PPA to copy from: https://launchpad.net/~canonical- foundations/+archive/ubuntu/uc20-build-ppa signing PPA to use: ~canonical-signing UC20 signed binaries staging ppa: https://launchpad.net/~canonical- foundations/+archive/ubuntu/uc20-staging-ppa Steps Todo: 1) ~canonical-signing to copy with binaries grub2-unsigned 2) await signing NB! do not copy grub2-signed at the same time, as build-depends will be satisfied from the archive, instead of PPA, as the package version of grub2 is unchanged, and will result in a miss-built. 3) source-only copy grub2-signed 4) canonical-signing to copy with binaries grub2 & grub2-signed to the staging ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917555 Title: UC20 Online Key signing request for grub2-signed 1.164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1917555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Merge proposal unlinked: https://code.launchpad.net/~xnox/grub/+git/grub/+merge/398407 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Also affects: grub2 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: grub2 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: grub2 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: grub2 (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: grub2 (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: grub2-signed (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: grub2-signed (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: grub2-signed (Ubuntu Focal) Status: New => Fix Committed ** Changed in: grub2-signed (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: grub2-signed (Ubuntu Hirsute) 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/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915536] Re: one grub
** Changed in: grub2-signed (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915536 Title: one grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915005] Re: Please merge findutils 4.8.0 from Debian unstable
** Changed in: findutils (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/1915005 Title: Please merge findutils 4.8.0 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1915005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
https://github.com/systemd/systemd/pull/18829 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
I have made this PPA https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4477 It has packages for focal versioned above current focal-updates version, but lower than the next SRU. sudo add-apt-repository ppa:ci-train-ppa-service/4477 sudo apt install systemd Should be enough to upgrade networkd. After that if you have installed network.d snippets you should remove them, and then reboot and things should just work. If reboot is too much doing chzdev -d / -e on the hipersocket interfaces that are in l3 should do the trick as well. After testing you can downgrade / remove those packages with ppa-purge, or just leave them until next SRU update arrives. If you can't use add-apt-repository (needs http(s) access to api.launchpad.net and ppa.launchpad.net) you can also download the .deb files from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4477/+build/21099271 and install them with $ sudo apt ./*.deb => do not it has to "absolute path names, or paths prefixed with ./" for apt to recognise them to install from local files instead of trying to fetch things from the mirror. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Patch added: "focal_qeth_l3_request_broadcast.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914740/+attachment/5471480/+files/focal_qeth_l3_request_broadcast.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Patch added: "0001-s390x-For-qeth_l3-set-dhcp_broadcast-to-true-by-defa.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914740/+attachment/5471481/+files/0001-s390x-For-qeth_l3-set-dhcp_broadcast-to-true-by-defa.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode
** Patch removed: "dhcp_broadcast_qeth_l3.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914740/+attachment/5467722/+files/dhcp_broadcast_qeth_l3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914740 Title: IPs are not assigned for Hipersockets in DHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
