** Description changed:
needrestart MIR has been completed.
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1907422
We are post FF, thus I am asking FFe to include needrestart as
recommends in the ubuntu-server package.
This change will results in needrestart being
Public bug reported:
needrestart MIR has been completed.
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1907422
We are post FF, thus I am asking FFe to include needrestart as
recommends in the ubuntu-server package.
This change will results in needrestart being installed by default
"America" does not maintain neither tzdata nor ISO 3166-2 database, both
of which are delegated to international community of Internet Standards
via RFC & to a committee headquartered in Genera with delegates from all
around the world. All of which has lots of experience with classifying
and
** Changed in: ubuntu-keyring (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: ubuntu-keyring (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ubuntu-keyring (Ubuntu Groovy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1920640
Title:
EXPKEYSIG
** Description changed:
+ [Impact]
+
+ * Cannot update apt metadata from ddebs.ubuntu.com whilst using ubuntu-
+ dbgsym-keyring package
+
+ [Test Plan]
+
+ * Install ubuntu-dbgsym-keyring package
+ * Add ddebs.ubuntu.com repository for your release
+ * sudo apt update must be successful
+
To be fair, Sevastopol has always had a special status of a federal city
- across all times. Closes analogy being Vatican City. It was federal
city separate from Crimea during whichever government defacto government
ruling be it USSR, Ukranian SSR, Ukrain or Russian Federation.
--
You received
In the iso-codes package there is a related issue, ISO 3166-2:RU
contains no codes for the Russian-administered Republic of Crimea and
Federal City of Sevastopol. Instead the UA codes are still specified,
i.e. UA-43 for Crimea.
** Also affects: iso-codes (Ubuntu)
Importance: Undecided
** Description changed:
- initramfs-tools does not include fsck in initrd if MNT_PASS equals zero
- in the fstab entries.
+ [Impact]
+
+ * initramfs-tools does not include fsck in initrd if MNT_PASS equals
+ zero in the fstab entries.
This has lead to the following situation :
when
The upstream IANA tzdata file format is very restrictive and cannot
change and reflect country codes correctly, across correct historical
dates.
>From "europe" file:
Zone Europe/Simferopol 2:16:24 - LMT 1880
2:16 - SMT 1924 May 2 # Simferopol Mean
Setting the status of the bug report to Opinion, as it doesn't fit the
scope of Ubuntu project. It has to be fixed by IANA in upstream releases
of tzdata. Once they come up with a better solution in the file format,
the bug can change to confirmed to be integrated in Ubuntu.
--
You received this
Is there anything in particular about all the other packages that you
marked them as affected? I suspect that they all use Ubuntu's provided
tzdata as the source of information, and hence they will all be
reflecting simply whatever tzdata tells them. Hence any changes will be
automatically
Also note https://bugs.launchpad.net/subiquity/+bug/1905932
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1920933
Title:
live desktop system booted with ip=dhcp has the
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
As per private conversation, it's not a bug but a feature to only
consider candidates by default.
** Changed in: apt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
never mind `apt build-dep` also fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1920804
Title:
Apt does not seem to automatically consider non-candidates when
Btw.
$external_commands = {
'build-deps-failed-commands' => ['%s'],
};
Is useful when debugging build-deps not installable, as that exposes the
dummy build-depends package ; archive; and one can redo commands that
sbuild tries to run to install them.
** Description changed:
Public bug reported:
# apt show sbuild-build-depends-main-dummy
Package: sbuild-build-depends-main-dummy
Version: 0.invalid.0
Maintainer: Debian buildd-tools Developers
Installed-Size: unknown
Depends: debhelper (>= 9), debhelper-compat (= 12), dpkg-dev (>= 1.17.14),
python3, cargo (>=
@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:
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
Touch seeded packages, which is subscribed to openssl
> 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
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1917780
Title:
** Changed in: wireshark (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include
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
Touch
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
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
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: 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
Touch seeded packages, which is subscribed to apport in Ubuntu.
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
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
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
Title:
OpenSSL TLS 1.1
*** 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
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1915966
Title:
Please merge
> 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
Touch seeded packages, which is
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 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
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
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1917920
Title:
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1917920
Title:
magic-proxy broke with iptables 1.8.7-1ubuntu2
Status in Launchpad itself:
New
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
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
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
Touch seeded packages, which is subscribed to ifupdown in
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:
** Changed in: ubuntu-core-initramfs
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1878969
Title:
time-epoch never changes in SRUs
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
** Changed in: findutils (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1915005
Title:
Please merge findutils
https://github.com/systemd/systemd/pull/18829
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914740
Title:
IPs are not assigned for Hipersockets in DHCP mode
Status in
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
Touch seeded packages, which is
** 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
Touch seeded packages, which is subscribed to
I've started drafting this patch.
I want to prepare a PPA for you to try, can you please let me know which
Ubuntu release is best / easiest for you to test? Hirsute? Focal?
Bionic?
** Patch added: "dhcp_broadcast_qeth_l3.patch"
My preference would be to fix networkd, if that fails netplan, and isc-
dhcp only if there is syntax to online the device in the right l2/l3
state via kernel cmdline and that one needs to complete install over it.
For example, does automatic chzdev device enablement provides
autoconfiguration for
Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3
interfaces be good enough in networkd?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1914740
Title:
IPs
@kernel team
please check which dkms packages in -updates fix FTBFS, and if they need
to be rebuilt in -security pocket and released in -security pocket.
** Changed in: linux-meta (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You
doko merged above pull request already.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1916117
Title:
Public bug reported:
pkgbinarymangler slows down all builds, unnecessarily.
pkgbinarymangler prevents running the io intensive dpkg-builddeb in
parrallel which is the default.
instead of making the builds use dpkg-builddeb in parallel, it makes all
packages getting processed serially for the
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1915307
Title:
Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
Status in sudo
** Tags removed: block-proposed
** Changed in: sudo (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1915789
Title:
sudo:
fakeroot with glibc broke dpkg-deb for packages that do not use "Rules-
Requires-Root: no" was broken.
binutils stopped preserving permissions from objcopy & strip, leading to
incorrect permissions of files after stripping.
fakeroot is now patched with better glibc 2.33 support. TODO upstream
** Changed in: glibc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: debhelper (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
** Changed in: fakeroot (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1915250
Title:
buildd file owner/group for shared
letting just the dep update of ubuntu-meta through.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1906671
Title:
[MIR] usrmerge
@mvo we know, we are tracing them all.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1915250
Title:
buildd file owner/group for shared libraries
Status in binutils
Ok, need to patch debootstrap to switch to usrmerge by default + make it
list usrmerge package; then update script in ubuntu-meta adds it to
minimal. Will upload all that to bileto ppa and test upgrades since non-
usrmerged systems.
** Also affects: debootstrap (Ubuntu)
Importance: Undecided
oh the binary is in main, it's the source that is in the universe never
mind.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1906671
Title:
[MIR] usrmerge
Status in
seems it has gone back to universe, preparing upload of ubuntu-meta and
will block it proposed to ensure we can test any fallouts.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Tags added: block-proposed
--
You received this bug notification because you
Sorry, this bug is not fixed.
After getting better wifi driver, it gains a different kernel name. And
hence NetworkManager "disconnects" and doesn't reconnect.
When this happens, you need to setup Wifi connection again.
I do not know how to fix this, and/or anticipate the new wifi card name.
We should probably ignore failure to start NetworkManager-wait-
online.service in the autopkgtests for now.
** Changed in: systemd (Ubuntu)
Importance: High => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
> So one solution to this would be to run "vgck --updatemetadata" on
each vg in postinst... would there be downside to that?
how slow is it on very very large LVMs? Is it distructive? Maybe
something to check with devops-y people, like I.S. / bootstack?
--
You received this bug notification
libffi7 (3.3-5ubuntu1) hirsute; urgency=medium
* Provide libffi7 runtime library for the 3rd party app
compatiblity. LP: #1903890
-- Dimitri John Ledkov Fri, 05 Feb 2021 13:34:22
+
I have now shipped libffi7 in hirsute. Such that if one installs third-party
binaries, on hirsute
** Changed in: libffi (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1892915
Title:
gnome-shell crashing (libffi8ubuntu1
** Description changed:
+ Ubuntu groovy and up upgraded to libffi8ubuntu1, thus making Ubuntu
+ incompatible with 3rd-party binaries that desire to use libffi7.
+
+ Let's backport and provide libffi7 runtime library only, for those.
+
+ Not sure how that would work with ctypes though.
+
+
+
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
New
adding breaks on linux-meta in -security, on dkms package versions that
are in -updates only, would result in the kernel being held back and not
get autoinstalled.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
@seth-arnold @mdeslaur
Mostly the dkms packages ship source code only, without strict binary
deps on packages/libraries from updates. It should be safe to publish
them into -security pocket.
It is correct that there were a few bugs with dkms modules, which are
now resolved in -updates. But one
Request for truely flicker free boot is in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1914409
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1880250
Title:
Installed focal Ubuntu desktop .2 media with LUKS full disk encryption.
On boot the fsck messages briefly flicker, and then are cleared, then
there is smooth transition to gdm.
It's a lot better than before, where fsck message would linger forever.
It would be ideal to make it flickerfree. Aka
Public bug reported:
Install Ubuntu desktop, with full disk LUKS encryption, on an UEFI
system.
On boot, ESP & rootfs will have fsck started.
This flickers briefly that fsck are in progress, although most of the
time both the ESP and rootfs fsck finish/exit instantly.
It would be nice delaying
Apparently lots of things still ship stuff in /updates/
And because kernel says so, distributions are forced to follow.
** Changed in: initramfs-tools (Ubuntu)
Status: Won't Fix => Triaged
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
**
*** This bug is a security vulnerability ***
Public security bug reported:
Whilst discussing
https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
ubuntu-desktop-installation-media/20606
We have noticed a reference to somebody not having working backport-
iwlwifi-dkms, whilst
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1914075
Title:
subiquity 20.04.2 fails to
Public bug reported:
subiquity 20.04.2 fails to install hwe kernel offline
as hwe kernel is missing from the pool
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => ubuntu-20.04.2
--
You
Also release team posted this update https://discourse.ubuntu.com/t
/improvements-for-hardware-support-in-ubuntu-desktop-installation-
media/20606 about this issue, which they were forced to do before the
weekend instead of during normal working hours this week. They were
hoping to collect more
@michel.ekimia
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1901904 has
full support for the v5.8 kernel in focal, released on 18th of January
2021.
What package versions are you referring to? for which release? and which
archive origin? And which combinations of the
https://wiki.ubuntu.com/Kernel/LTSEnablementStack was updated with
expanded instructions around 20.04 LTS, and make it more obvious that
one is most likely tracking HWE kernel on Desktop; unless one is on the
OEM kernel. Note that on certified hardware downgrades to GA stack may
cause loss of
@laney i would agree to patch cron with our default path, with snap/bin
included.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH does not
** Changed in: gzip (Ubuntu)
Status: New => In Progress
** Changed in: gzip (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1913423
Title:
getgrouplist is not thread safe with libnss_systemd
Status in systemd
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nographic -no-reboot
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for a list
Verifying v5.8 build
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for
1) checking that reproducer still fails
sudo qemu-system-x86_64 -kernel ./vmlinuz-5.4.0-64-generic -initrd
./initrd-pad4-5.4.0-64-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
[3.581106] Initramfs unpacking failed: Decoding failed
Spawning shell within the initramfs
@vmc
this bugfix is not yet available on any .iso for any series yet. It can
only be tested from installed systems and enabling proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
301 - 400 of 2744 matches
Mail list logo
