** Changed in: linux-aws-6.8 (Ubuntu)
Status: New => Fix Committed
** Tags removed: verification-needed-jammy-linux-aws-6.8
** Tags added: verification-done-jammy-linux-aws-6.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
<2081...@bugs.launchpad.net>
wrote:
> Thank you for making this bug report Kevin!
>
> This install failed because the maintscript could not restart dovecot.
> Are you able to restart it manually?
>
> side note for maintainer: I see invoke-rc.d is being used in the
> maintscript,
** Changed in: cups (Ubuntu Noble)
Assignee: (unassigned) => Kevin bush (akjk32002)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082335
Title:
Sept 2024 security issue tracking bug
; Status in libppd source package in Oracular:
> New
>
> Bug description:
> This bug is to track the vulnerabilities in the cups and associated
> packages.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/20
Fixed in jammy/linux-aws-6.8 6.8.0-1016.17~22.04.2 by compiling with
gcc12. The fix has been committed but still needs to undergo testing.
** Changed in: linux-aws-6.8 (Ubuntu)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
--
You received this bug notification because you ar
** Changed in: linux-realtime (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: ubuntu-realtime
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/208
** Also affects: linux-realtime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Rerun the cert-testing on the impacted systems that mentioned in the
description, both of them complete the test.
https://certification.canonical.com/hardware/202306-31696/submission/392825/packages/?term=linux-firmware
https://certification.canonical.com/hardware/202306-31695/submission/396179/pa
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077490
Title:
Error: out of memory while booting after installing the
@Atlas, thanks for pointing out that, after checking that HP platform
has 4 configs in the cert lab, which are sku2, sku4, sku6 and sku10,
only sku2 has this issue. So it indeed looks like a single hardware
issue.
@Acelan, I think we still need to figure out why only this single
hardware won't wor
Public bug reported:
error during do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: dovecot-core 1:2.3.21+dfsg1-2ubuntu6
ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: a
TRYING TO UPDATE TO 24.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081681
Title:
Could not calculate the upgrade An unresolvable problem occurred
while calculating the upgrade. This
Public bug reported:
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.
Unable to access ppa-purge. I tried sudo apt ppa-purge. I am new
Public bug reported:
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.
Unable to access ppa-purge. I tried sudo apt ppa-purge. I am new
Public bug reported:
trying to install nvidia-driver-545
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidi
I have been testing those packages (described in bug 2025006) from
noble-proposed for a week now, and so far I haven't seen the issue any
more.
Usually it happened at least once a week, so I am carefully optimistic.
I'd have to not see the issue for a bit longer to be completely
convinced it's fix
@Aaron
I just checked that it also happened on -40 kernel which is already in the
update.
I only can confirm 6.5.0-1013-oem which is the GM kernel is good, since we
always do restoring the system then dist-upgrade while testing.
Full dmesg log is attached.
** Attachment added: "dmesg"
https
Public bug reported:
[Summary]
During the SRU testing, I found a Lenovo workstation has multiple NICs
installed that failed to wake up from cold-reboot by rtc event. After
some investigations, I found that it's because too many kernel message
appear and slow down the power off.
We don't have any
Public bug reported:
[Summary]
During the SRU testing, I found a hp laptop always timeout after suspend
test, after checking I found that the NIC didn't link up.
Part of journal log as follows:
Sep 12 11:13:01 ubuntu kernel: PM: suspend entry (s2idle)
...
...
Sep 12 11:13:10 ubuntu kernel: PM: s
** Tags removed: verification-needed-jammy-linux-realtime-6.8
verification-needed-noble-linux
** Tags added: verification-done-jammy-linux-realtime-6.8
verification-done-noble-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I saw this with jammy:linux-realtime 5.15.0-1071.79 on scobee-kernel. I
think this was the first time this test used scobee-kernel in a while,
so that's probably why we didn't see it before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
[Summary]
During the SRU testing, I found at least 2 DUTs always timeout after
suspend test, after checking I found that both of them only detect 10
Mbps speed on their NIC and can't get IP from DHCP.
Part of journal log as follows:
Sep 02 10:55:00 ubuntu kernel: PM: suspend
** Summary changed:
- kernel oops in aafs_create in 6.8.1-1002-realtime kernel
+ kernel oops in aafs_create in noble/oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068602
Title:
kernel oop
Public bug reported:
We have 12 rpi4b4g set up in the certification lab now.
2 older rpi4b4g with hw rev 1.1 can boot with ubuntu-core-18-arm64+raspi3
image, but newer rpi4b4g with hw rev 1.5 can't.
I think that should be the firmware issue.
Output from newer RPI4B4G
ubuntu@ubuntu:~$ cat /proc
: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kevin 1172 F pulseaudio
BuildID: 20240819150008
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Wed Aug 28 07
Just tested the linux-firmeware in proposed, it fixed the problem.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077490
Title:
Error: out of memory while boo
Public bug reported:
During the kerenl SRU testing, I found that the DGX A100 station kept
showing error messages from nouveau in dmesg as follows. These numerous
kernel error messages crippled the system and made it unresponsive.
[ 2265.721452] nouveau :07:00.0: disp: ctrl 0080
[ 2265.72
Public bug reported:
I found that there are some machines in cert lab can't boot after
installing the linux-frimware in proposed with 6.8.0-40 kernel.
After selecting booting with the 6.8.0-40 kernel, it shows error: out of
memory on the screen then freeze.
There aren't any journal logs availabl
Testing complete on jammy:linux-realtime 5.15.0-1070.78
** Tags removed: verification-needed-jammy-linux-realtime
** Tags added: verification-done-jammy-linux-realtime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Perhaps related to this issue, I have also noticed that sometimes when I
(re)boot my computer in the evening when Night Light is in an early
stage, it remains stuck in that initial level of orange set after boot,
and it doesn't gradually increase like it should do. Disabling and
enabling Night Ligh
** Also affects: linux-realtime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ubuntu-realtime
Status: New => Fix Committed
** Changed in: linux-realtime (Ubuntu)
Status:
This was fixed in 6.8.1-1006.6 realtime on Noble and 5.15.0-1068.76
realtime on Jammy.
** Changed in: ubuntu-realtime
Status: Fix Committed => Fix Released
** Changed in: linux-realtime (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-realtime (Ubuntu Jammy)
Testing passes for jammy:linux-realtime/5.15.0-1068.76 and noble:linux-
realtime/6.8.1-1006.6.
** Tags removed: verification-needed-jammy-linux-realtime
verification-needed-noble-linux-realtime
** Tags added: verification-done-jammy-linux-realtime
verification-done-noble-linux-realtime
--
You
With realtime access enabled via Ubuntu Pro (either via `sudo pro enable
realtime-kernel` or `sudo pro enable realtime-kernel --access-only`),
you can run the following command to download the source:
sudo apt-get source --only-source linux-realtime
--
You received this bug notification because
** Changed in: linux-realtime (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-realtime (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux-realtime (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-realtime
Does this mean the uninstall-upgrade-reinstall dance has to be done
anyway on any major upgrade of virtualbox (e.g. when upgrading Ubuntu
past jammy)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073
** Changed in: linux-realtime (Ubuntu)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
** Changed in: linux-realtime (Ubuntu Jammy)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
** Changed in: linux-realtime (Ubuntu Noble)
Assignee: (unassigned) => Kev
** Also affects: linux-realtime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-realtime
Upgrading to virtualbox 7 let the vm start booting, but windows crashes
on boot with a message about an issue with the driver vboxwddm.sys , I'm
guessing because guest additions installed from ubuntu package conflict
with those from the ppa? So that workaround doesn't solve all cases
either.
--
Y
Cert team has already fixed the test procedure to prevent this issue
happen, so I think this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069400
Title:
Some DUTs can't boot up a
Thanks for your response. I can confirm that the problem does not happen
with Ubuntu 24.04. It does happen with 23.10.1 and below.
I'm not sure about filing a bug report with Mozilla. I think they'll
blame it on the Ubuntu modifications because the bug doesn't happen on
any version of Debian, only
I've been testing all these packages since last Monday, and this morning
night light was stuck again when I unlocked my screen. So I'm afraid
this doesn't fix the issue.
I also haven't seen any activity in the upstream ticket of people
actually confirming the issue was fixed.
** Tags removed: ver
Public bug reported:
I'm trying to clone an EXT4 partition on a Linux software RAID
I'm using the command line
partclone.ext4 --clone --source=/dev/md1p1 --output=testout
when the relevant part of 'lsblk' output is
sda 8:00 16.4T 0 disk
└─md1 9:10 32.8T 0 raid5
The oracular archives already contain gnome-calculator 46.1 as a .deb
package. I've installed that on noble without issues, and I can confirm
that also fixes this issue.
So if that package is copied to the noble archives, this bug will be
fixed.
--
You received this bug notification because you
Upstream says this is fixed in gnome-calculator 46.1. I've just tested
the Flatpak of that version, and can confirm that it indeed is fixed in
the next point release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
A new upstream version (1.5.0) was released on 2021-10-28:
https://github.com/zevv/bucklespring/releases
** Affects: bucklespring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033007
Tit
I have installed the mutter package from noble-proposed and rebooted, so
I'll be testing it from now on.
kevin@arcadia:~$ mutter --version
mutter 46.2
Sadly I don't know of any way to manually trigger this bug. Sometimes it
doesn't happen for days, and then all of a sudden the col
** 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/2072370
Title:
URL for home page and privacy policy point to a dead site
To manage
@Dave, I didn't see anything displayed on the monitor with core20.
Only see there is a fixed pattern on ACT LED, 4 long flashes first, followed by
7 short flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
@Dave, the current focal server image originally can boot on the rev 1.4
rpi3b+, but core20(https://cdimage.ubuntu.com/ubuntu-
core/20/stable/current/) can't, so how do I verify the new firmware
works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "journal log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2070319/+attachment/5792126/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070319
Title:
Public bug reported:
I'm conducting the nvidia driver SRU testing, during test this version
on Focal, I found one of laptop can't perform auto-login after
installing this driver.
[Reproduce]
1. Install ubuntu 20.04
2. Run dist-upgrade to update all the packages.
3. Enable proposed pocket
4. Insta
** Attachment added: "lspci.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069550/+attachment/5790121/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069550
Title:
DU
Public bug reported:
During the SRU testing for 5.15.0-112 kernel on Focal, I found 2 AMD laptops
displayed a black screen.
After some investigation, the impacted laptops both with Picasso/Raven
2(1002:15d8) GPU.
Output for lscpi and journalctl are attached.
If you need more detail, please let m
** Changed in: linux (Ubuntu)
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/2069400
Title:
Some DUTs can't boot up after installing the hwe kernel in the
propo
Public bug reported:
During the SRU testing for 5.15.0-112 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
Loading Linux 5.15.0-112-generic...
Loading initial ramdisk...
It looks like it's very similar to this bug.
https
Hi Colin, I've consistently reproduced this issue in QEMU VMs on arm64
realtime (6.8.1.1002-realtime). However, it also occurs with the generic
kernel (6.8.0-35-generic) on arm64. I couldn't get it to happen with
amd64.
Here's the dmesg output on 6.8.0-35-generic after the modprobe gets
stuck:
[
To be clear, so far I've only been able to get the following hardware
configurations to fail reliably:
- QEMU VM amd64, linux-realtime 6.8.1-1002-realtime
- QEMU VM amd64, linux (generic) 6.8.0-35-generic
I once got each of the following to fail, but haven't been able to
reproduce it consistently
Hi Colin, I've been able to reproduce this issue in QEMU VMs on amd64
consistently and I got it to happen once in arm64, however, I haven't
been able to reproduce the kernel oops again. I can't get it to happen
on bare metal or in an LXD VM (multipass). I've also found that this
doesn't just happen
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059259
Title:
ubuntu_ltp sched:starva
** Package changed: linux (Ubuntu) => ubuntu-realtime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068615
Title:
kernel oops in pick_next_task_fair in 6.8.1-1002-realtime kernel
To manage notif
-save /tmp/report.BUG_ID linux
If apport can't be run:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
Thanks,
Kevin
** Changed in: linux-realtime (Ubuntu)
Status: New => Triaged
** Chan
Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TAR
Public bug reported:
Unable to calculate upgrade use ppa-purge - removed ppa file from other
software then tried to upgrade again ans till get unable to calculate
upgrade and to report the bug in the summary - have submitted bug report
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-
Public bug reported:
Since installing Ubuntu 24.04, every now and then Night Light gets stuck
when my screen is locked at night and I unlock it in the morning. The
screen is then very orange (more so than normally is the case with Night
Light), and disabling it with the button in in the top bar me
This happens with nl_NL.UTF-8 for me as well. The period is no longer
converted to a comma, as it used to be in older gnome-calculator
releases.
This seems to be the upstream bug: https://gitlab.gnome.org/GNOME/gnome-
calculator/-/issues/403
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calcul
Further research indicates that `webkit2gtk-4.0` is legacy and removed
on purpose, which I fully understand, and bringing it back might not be
a practical operation.
My project (GlobalProtect-openconnect) uses Tauri 1.x, which depends on
`webkit2gtk-4.0`. Tauri started to use `webkit2gtk-4.1` in 2
I'm experiencing the same issue. Will we be adding these packages back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061914
Title:
libjavascriptcoregtk-4.0-18 seems to be missing on the latest bui
** Description changed:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
- The last messages displayed on the screen are:
+ The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID
Public bug reported:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
The
That did the trick, thank you! I can confirm that after updating via apt
on noble beta, VisualVM now launches successfully with the default JRE
(21)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206024
You're experiencing LDAP authentication issues while migrating from
Ubuntu 10.04 with Apache 2.2 to Ubuntu 14.04 with Apache 2.4 and
Subversion 1.8. The problem stems from changes in Apache versions. To
address this, apply the patch provided in the Apache bug report
(https://www.dg-customerfirst.co
Public bug reported:
Installing VisualVM via the apt on noble beta automatically installs
java 21, but the packaged version of VisualVM (2.1.6) only supports Java
20 and below. When you try to launch it, you get a pop up message
stating:
"You are running VisualVM using an unsupported Java version
** Changed in: linux-aws (Ubuntu Jammy)
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/2043811
Title:
AWS: arm64: pauth: don't sign leaf functions
To manag
Confirmed as working by Amazon.
** Tags removed: verification-needed-jammy-linux-aws
** Tags added: verification-done-jammy-linux-aws
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043811
Title:
AW
** Also affects: linux-intel-iotg-5.15 (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/2056383
Title:
Audio turned to dummy output from 5.15.0-1049
@Francis
I've confirmed that the DUT has already used the latest ubuntu-drivers from
proposed.
Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ...
But it doesn't seem to solve the issue. Please check following messages.
+ _run sudo ubuntu-drivers devices
+ ssh -t -o StrictHostKeyChecking=n
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197761
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller /1
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope o
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
To manage notifications about this bug go to:
h
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
- ip6.privacy=
@seb128 I have created a new bug report with links to the upstream
commits. The core of the issue is that IPv6 addresses are now being
added in the wrong order, so the kernel prefers SLAAC addresses over
DHCPv6 addresses, which should be the other way around.
As this is a breaking change in source
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
** Tags added: jammy
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being a
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft 43193
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428
Title:
Update to the current 1.36 stable version
To manage notifications
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=
Public bug reported:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the conne
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
1 - 100 of 9160 matches
Mail list logo
