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
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
**
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.
@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
*** 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
** 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:
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`
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
** 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
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
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
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
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,
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
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:
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.
> 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
> 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
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
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
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
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
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.
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 /
*** 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
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
@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
** 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
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,
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,
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
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
** 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
** 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.
** 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
** 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
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
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
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
** 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
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
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
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
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
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
** 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
*** 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
** 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 Ubu
** 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
** 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
@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.
** 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
** 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
** 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
> 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
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
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
Настраивается пакет 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:
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
@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
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
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.
@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
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
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
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
** 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:
"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
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
@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.
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
** 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:
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
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
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
** 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.ne
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
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
** 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
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
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
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-
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.
** 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
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:
** 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.
** 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:
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
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
** 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
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:
** 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
** 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
** 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:
** 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
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
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
** 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
** 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
** 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.
901 - 1000 of 9162 matches
Mail list logo
