That kernel change doesn't fix the issue:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-
loop/noble/amd64/l/livecd-rootfs/20240125_203808_8b5c9@/log.gz
Which actually didn't surprise me after thinking about it. systemd-udevd
is going to ask for a partition reread when it gets the
Public bug reported:
This log shows initramfs-tools' qemu-net test failing on arm64. Here's
the relevant portion:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/arm64/i/initramfs-tools/20240119_214255_431f3@/log.gz
[...]
5482s no valid interfaces found
5482s exiting due to one
I hit this in mantic on 2024-01-19, so seems to still be an issue:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/armhf/i/initramfs-tools/20240119_180724_10d3d@/log.gz
** Changed in: cryptsetup (Ubuntu)
Status: Invalid => New
** Changed in: initramfs-tools (Ubuntu)
I was bothered by the fact that we only sometimes see the double
partition rescan in dmesg. If udev always rescans the partitions of a
full block devices, shouldn't we always see those messages twice?
It turns out that udev doesn't rescan partitions just because a new
block device appears. When it
I updated my livecd-rootfs PPA test package that runs this section of
code in a loop to use this pattern, and it survived until the
autopkgtest timeout - 304 iterations:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-
loop/noble/amd64/l/livecd-rootfs/20240128_061640_5c909@/log.gz
Comparing the artifacts between a failed and successful log, the
relevant difference appears to be that cryptsetup-initramfs is only
installed in the failed log. These errors also appear during the setup
phase when package installation causes the initramfs for the host to be
updated:
3870s Process
** Changed in: initramfs-tools (Ubuntu)
Status: New => Triaged
** Changed in: cryptsetup (Ubuntu)
Status: New => Invalid
--
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.la
** Also affects: cryptsetup (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: cryptsetup (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: initram
On Tue, Jan 30, 2024 at 6:21 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Oh wait, we've been through something very like this before
> https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
> a judicious application of flock may be the most correct solution
> a
The test passed w/ flock as well:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-loop/noble/amd64/l/livecd-rootfs/20240131_104633_df869@/log.gz
274 successful iterations before the timeout killed it.
I've updated the MP:
https://code.launchpad.net/~dannf/livecd-rootfs/+git/l
I've examined all of the test failures, and all have root causes
unrelated to this fix. I've cleared all from the excuses page except:
mantic/initramfs-tools/armhf: bug 2043579
jammy/linux-azure-5.19/arm64: the kernel build test timed out. retries keep
hitting slow builders :(
jammy/linux-lowlate
** Also affects: util-linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: livecd-rootfs (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubunt
While the above MP is now merged, I still see additional potential races
in the code. For example, anything calling mount_partition() for the
first partition, and also maybe bug 2030771. I don't see a good way to
solve that w/o `udevadm lock` because these functions don't currently
know what the fu
The remaining autopkgtest failures are due to the following unrelated
bugs:
cmake-extras/armhf: bug 2052360
livecd-rootfs/amd64: bug 2045586
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.l
> I'm retrying these failing autopkgtests with migration-reference/0
since if they fail anyway they shouldn't hold things up.
Oh, is that something I should do in cases like this? Would that
automatically cause SRUs with failing tests to be unblocked?
> In the meantime, could you please also veri
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1991553
Title:
c
Yeah - maybe its just the mantic builder image that has the bad
cryptsetup config (/etc/crypttab)?
--
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/2043579
Title:
in
I'm glad to hear you are seeing an improvement! The current
implementation is still racy as mentioned in Comment #22. I did a search
of the logs I downloaded, and I believe this one shows that the
mount_partition() race isn't just theoretical:
https://autopkgtest.ubuntu.com/results/autopkgtest-
ma
** Summary changed:
- Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable
(main)
+ [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
It seems like this bug should now be a FFe (see
https://wiki.ubuntu.com/FreezeExceptionProcess) - so converting...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2051672
Ti
** Attachment added: "Upstream 6.2 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763784/+files/6.2-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.4 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763786/+files/6.4-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.3 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763785/+files/6.3-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.5 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763787/+files/6.5-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.6 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763788/+files/6.6-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.8 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763790/+files/6.8-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
** Attachment added: "Upstream 6.7 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763789/+files/6.7-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
h
Thanks Matthieu. I spoke to the kernel team and I think they will handle
the update. I'm just trying to help unblock them by getting this
reviewed/agreed by our release team ahead of time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Description changed:
- A few versions have been released and Ubuntu Noble still has the 6.1
- version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
- import the latest version from Debian unstable fixing a bunch of issues
- and supporting features from more recent kernels?
+ iprou
** Description changed:
iproute2 upstream produces releases coinciding with upstream kernel
releases to support the latest kernel features. Noble's iproute2 is
still back at v6.1 even though it will use the v6.8 kernel. This means
we provide no userspace interface for newer features - some
Thank Utkarsh. Yeah, we just dropped the ball on not getting this done
sooner. I'd like to see if we can make the case for SRU'ing 6.8 in, so
let's convert the bug to that.
I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.
We'll need to make a convincing
On Mon, Apr 22, 2024 at 11:07:54AM -, Matthieu Baerts wrote:
> > I don't think we can justify dropping FAN support in an SRU, so let's
> add that port back in.
>
> Even if it will not be used in Ubuntu 24.04,
I'm happy to drop it if the stable release team would accept it.
Here's the policy:
ded
Status: Fix Released
** Affects: libjsoncpp (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: libjsoncpp (Ubuntu Mantic)
Importance: Undecided
Status: Fix Released
** Affects: libjsoncpp (Ubuntu Noble)
** Description changed:
[Impact]
- Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp. This can be reproduced by building a a new version of
cmake itself (reproduced w/
** Description changed:
[Impact]
Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp because libjsoncpp's cmake config does not protect against
duplicate imports. This
** Description changed:
[Impact]
Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp because libjsoncpp's cmake config does not protect against
duplicate imports. This
I was not able to make the .link approach work, even in an installed
environment. I fought with it for a while during spurts of machine
access. Without that, I was not able to move on to the next step of
trying to insert it into a commissioning script.
--
You received this bug notification becaus
** Summary changed:
- [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)
+ Backport iproute2 6.8.0 to noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://b
** Description changed:
- iproute2 upstream produces releases coinciding with upstream kernel
- releases to support the latest kernel features. Noble's iproute2 is
- still back at v6.1 even though it will use the v6.8 kernel. This means
- we provide no userspace interface for newer features - some
Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:
1) Edit this bug to use the SRU Template
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you
have any conc
Public bug reported:
I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
included a change that dropped a number of transitional packages:
mesa (23.1.4-1) unstable; urgency=medium
[ Diederik de Haas ]
* Drop transitional libegl1-mesa package (Closes: #1032712)
* Drop transiti
Apologies for the delay - I took a few months off over the summer. I
agree that we should close this ticket if IPRoute2 is not to be
upgraded, but I do not see that this decision has been reached. It is
clear from #25 that we need to maintain `ubuntu-fan` support - so that
patchset would need to be
Public bug reported:
[Impact]
Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 (optional
-64k flavors). When booted on 64K kernels, tail emits no output when tailing a
sysfs file. The difference in behavior can be a source for bugs in scripts that
use tail, and general user
** Changed in: coreutils (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: coreutils (Ubuntu Noble)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: New
** Also affects: coreutils (Ubuntu Jammy)
Importance: Undecided
Status:
cided
Assignee: dann frazier (dannf)
Status: In Progress
** Tags: block-proposed-jammy
** Also affects: util-linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu)
Status: New => Fix Released
** Tags added: block-proposed-jammy
** Ch
** Also affects: util-linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Also affects: util-linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: util-linux
@ahasenack - thanks for asking these questions.
I do know of a user rebuilding jammy's util-linux. The build recipe I've
seen installs these binaries. I don't know the risk that they might
become setuid. This CVE I noticed as being fixed in a later version of
util-linux, but not in jammy. I then l
** Changed in: coreutils (Ubuntu Mantic)
Status: Confirmed => In Progress
** Changed in: coreutils (Ubuntu Lunar)
Status: Confirmed => In Progress
** Changed in: coreutils (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are
= mantic verification =
ubuntu@hinyari:~$ getconf PAGESIZE
65536
ubuntu@hinyari:~$ tail /sys/kernel/profiling
0
ubuntu@hinyari:~$ dpkg -l | grep coreutils
ii coreutils9.1-1ubuntu2.23.10.1
arm64GNU core utilities
** Tags removed: verificati
= jammy verification =
ubuntu@hinyari:~$ getconf PAGESIZE
65536
ubuntu@hinyari:~$ tail /sys/kernel/profiling
ubuntu@hinyari:~$ sudo apt install coreutils -t jammy-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will b
I ran into this on jammy/amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/l/livecd-rootfs/20240121_173406_e4f9a@/log.gz
I downloaded all of the amd64 failures and searched for this failure
pattern. These were the kernels that were running at the time:
"Linux 5.15.0-91-
I ran the above test:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240123_035147_6470b@/log.gz
It does appear that systemd-udevd is trying to scan partitions at the
same time as losetup:
1599s ++ losetup --show -f -P -v binary/boot/disk-uefi
** Summary changed:
- livecd-rootfs uses losetup -P for theoretically reliable/synchronous
partition setup but it's not reliable in noble
+ livecd-rootfs uses losetup -P for theoretically reliable/synchronous
partition setup but it's not reliable
--
You received this bug notification because y
On Tue, Jan 23, 2024 at 8:55 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Amazing debugging Dann. Until we can get a kernel fix, what's the way
> forward here? Run losetup without -P, run udevadm settle, run partprobe
> on the device (then maybe run udevadm settle again??)
That
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1914469
Title:
network screen fails to show IP
** Summary changed:
- network screen fails to show IP on crb2s system
+ network screen fails to show IP when netbooted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1914469
Verified - I do now get the prompt! Thanks laney & didrocks!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Also affects: systemd (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1933402
Title:
net card set VF and altname di
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Reproducibility]
- 100%
-
- [Additional information]
- (Firmware version, kernel version, affected hardware, etc. if required):
-
- [Resolution]
+ [What Could Go Wrong]
+ TBD
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Assignee: (un
** Description changed:
[Impact]
- When running with the HWE kernel (5.4 didn't support altnames), altnames
containing garbage (uninitialized memory) may get assigned to a NIC. This is
100% reproducible on arm64.
+ When running with the HWE kernel (5.4 didn't support altnames), altnames
conta
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1933402
Title:
net card set VF and altnam
On Mon, Jun 28, 2021 at 10:28:00PM -, Dan Streetman wrote:
> systemd doesn't use iproute2 tooling to set the altnames, it sets them
> directly with netlink.
You're right. The problem is that it does so w/ possibly uninitialized
memory. I added the following patch to demonstrate:
--- systemd-2
** Changed in: kunpeng920
Status: New => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: New => Fix Committed
** Changed in: kunpeng920/ubuntu-20.04-hwe
Milestone: None => ubuntu-20.04.3
--
You received this bug notification because you are a member of Ubuntu
Thanks for checking in @ddstreet. I haven't found an alternate way yet -
but I also haven't exhausted alternatives. I've got an open request w/
the MAAS team for which I'm awaiting a response.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It would be interesting to know if the issue is due to the differences in the
toolchain used to build elfutils 0.183-6 and 0.183-8. The build logs show they
were 10.2.1-23ubuntu2
and 11.2.0-1ubuntu2, respectively. If we built 2 copies of 0.183-8 in the same
environment, but just varied the diff
Understood, thanks for considering the issue. Perhaps this just needs to
be release noted, warning users it may happen and how to avoid it (i.e.
implement their own set-name config)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Public bug reported:
[Impact]
udev can produce unpredictable network interface names by default when multiple
devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2
system, I see the following when booting a system with udev 245.4-4ubuntu3.13:
ubuntu@akis:~$ ls /sys/class
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Description changed:
[Impact]
ude
** Changed in: systemd (Ubuntu Impish)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned
And here's some proposed text. I assume this would be applicable to the
release notes from 20.04->22.04
= Known Issues =
== Network Interface Names ==
Ubuntu generates [predictable interface
names](https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/)
by default. T
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1940860
Title:
Mellanox NIC interface name
On Wed, Oct 13, 2021 at 05:10:05PM -, Dan Streetman wrote:
> > udev can produce unpredictable network interface names by default when
> multiple devices map to the same slot due to an intermediate bridge.
>
> so, if I understand it right, the MR won't actually fix this for anyone
> without add
OK, I'll reach out to the MAAS team to see if they have a good
recommendation. To be clear of my goals here - I'm confident that I
could come up with a workaround that would work for my environment. My
goal here is to come up with an easy-to-apply workaround for other users
of such systems. I like
Public bug reported:
When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attempt to "switch to" a n
** Attachment added: "_usr_bin_gnome-shell.1002.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015386/+attachment/5661328/+files/_usr_bin_gnome-shell.1002.crash
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificatio
I could not reproduce with kinetic (see my steps in bug 2016193). I went
back to a clean jammy install, reproduced, then upgraded just the gdm3
packages to kinetic's versions, and the problem went away, so it seems
gdm3 in isolation is the relevant difference. I took a look at the
differences betwe
Upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/808
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #808
https://gitlab.gnome.org/GNOME/gdm/-/issues/808
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/-/issues/808
Importance: Unknown
Status: Unknown
Public bug reported:
apt/jammy
apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server
is installed *and* out of date. I can reproduce this by disabling all but the
jammy release pocket, installing the old n-d-450-s from there, and then
enabling updates and trying to in
Verification:
Before:
ubuntu@akis:~$ ls /sys/class/net
enp134s0f0 enp230s0 enp93s0 ens103 eth0 eth7
enp134s0f1 enp6s0ens102 ens107 eth2 lo
After upgrade to systemd 245.4-4ubuntu3.19 (w/ net.naming-scheme=v247):
ubuntu@akis:~$ ls /sys/class/net
enp134s0f0 enp184s0 enp225s0 enp53s
** Changed in: kbd (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kbd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
@hypothetical-lemon - thanks for preparing theses! Some quick feedback:
- The jammy and kinetic packages need to have different versions. See the
following for a versioning scheme:
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
- Just a nit, but when you respin
** Changed in: apt (Ubuntu Bionic)
Status: Fix Released => In Progress
--
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/1871268
Title:
Installation fails due to useless i
** Changed in: ubuntu-cdimage
Assignee: kevindorseymacka...@gmail.com (kevindorseymackall1) =>
(unassigned)
--
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/1871268
Title:
** Changed in: ubuntu-cdimage
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu)
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu Bionic)
Assignee: enes (ekko52) => (unassigned)
** Changed in: apt (Ubuntu Focal)
Assignee: enes (ekko52) => (u
** Changed in: apt (Ubuntu Focal)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Groovy)
Status: Fix Released => Triaged
** Changed in: apt (Ubuntu Bionic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: ubuntu-cdimage
Assignee: jason mercer (jasdace) => (unassigned)
--
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/1871268
Title:
Installation fails due to use
** Changed in: apt (Ubuntu Focal)
Status: Fix Released => Fix Committed
** Changed in: apt (Ubuntu)
Assignee: islam elalani (i.s.l.a.m) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu
** Changed in: ubuntu-cdimage
Assignee: Andrius KL (andrewdaman) => (unassigned)
--
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/1871268
Title:
Installation fails due to u
Yes, it still exists as of systemd 248.3-1ubuntu1:
ubuntu@howzit:~$ sudo dpkg --add-architecture armhf
ubuntu@howzit:~$ sudo apt update > /dev/null 2>&1
ubuntu@howzit:~$ sudo apt install systemd:armhf systemd-container:arm64
[...]
Setting up systemd:armhf (248.3-1ubuntu1) ...
Setting up systemd-co
** Bug watch added: Debian Bug tracker #990547
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990547
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990547
Importance: Unknown
Status: Unknown
--
You received this bug notification because
= Verification =
Before:
14: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8:f1:ae:10 brd ff:ff:ff:ff:ff:ff
altname `�lժ�
altname ��lժ�
After:
15: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
I noticed on a couple of systems that my network interface names change
when upgrading from the focal LTS (5.4) kernel to the focal HWE (both
5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs.
dannf@bizzy:~$ uname -a
Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP
@ddstreet I agree that systemd is behaving as designed. But I'm not sure
what the proper fix for this is, and therefore where changes would be
required.
My initial thought is that perhaps subiquity installs should do what
MAAS installs do and configure netplan to always use the install-time
names.
Public bug reported:
While trying to track down a behavior difference between focal and
impish, I installed focal's kernel in an impish userspace and attempted
to boot it. The boot failed, unable to find root. While GRUB reported
that it had loaded the initramfs, no initramfs messages were emitted
The rebuild of protobuf no longer has lto information according to
objdump, but the reported version certainly does. The "bad" version was
built during hirsute devel, so I took a current hirsute system and
systematically downgraded build-deps to the versions in the log of the
"bad" build. Turns out
Maybe it is only on ARM?
dannf@xps13:/tmp$ dpkg -c
linux-modules-4.15.0-64-generic_4.15.0-64.73~16.04.1_arm64.deb | grep
ehci-platform
-rw-r--r-- root/root 17238 2019-09-13 06:10
./lib/modules/4.15.0-64-generic/kernel/drivers/usb/host/ehci-platform.ko
** Changed in: initramfs-tools (Ubunt
** Also affects: gdb (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Also affects: gdb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gdb (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: gdb (Ubuntu Disco)
Importance:
I have a test fix building here, could one of you verify it?
https://launchpad.net/~dannf/+archive/ubuntu/lp1848200
** Changed in: gdb (Ubuntu Bionic)
Status: New => In Progress
** Changed in: gdb (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
--
You receive
1 - 100 of 247 matches
Mail list logo
