[Bug 2012430] Re: attribute breaks dashes

[Kevin Wilke]

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 Ubuntu and derivatives. I'm glad it's fixed,
though.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012430

Title:
   attribute breaks dashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2012430/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066902] Re: Night Light occasionally gets stuck

[Kevin Keijzer]

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: verification-needed-noble
** Tags added: verification-failed-noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066902

Title:
  Night Light occasionally gets stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2066902/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072602] [NEW] partclone.ext4 twirls forever when working on an unmounted RAID partition

[Kevin O'Gorman]

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 
└─md1p1 259:00  32.8T  0 part  
  sdb 8:16   0  16.4T  0 disk  
  └─md1   9:10  32.8T  0 raid5 
└─md1p1 259:00  32.8T  0 part  
  sdc 8:32   0  16.4T  0 disk  
  └─md1   9:10  32.8T  0 raid5 
└─md1p1 259:00  32.8T  0 part

This has resulted in partclone.ext4 running for what I expect to be forever
because not a single byte has been written to 'testout', and it has been 
running for about 3 hours.
I tried it overnight once before, with the same result.

There was a little bit of output on stdout:
  root@plato-f:/mnt/18tc# time partclone.ext4 --clone  --source=/dev/md1p1 
--output=testout
  Partclone v0.3.13 http://partclone.org
  Starting to clone device (/dev/md1p1) to image (testout)
  Reading Super Block
  Calculating bitmap... Please wait... 
  Elapsed: 00:02:11, Remaining: 00:00:00, Completed: 100.00%
  
  Total Time: 00:02:11, 100.00% completed!
and not a bit more.

Top(1) shows partclone.ext4 using 1.0 CPUs (of the available 32); this
machine uses two Xeon chips.

There does not seem to be anything wrong with the RAID.  I just now stopped 
partclone and remounted
the raid as usual, and I can see the usual files and directories in it.  
Moreover, I have been able to
use tar(1) and dar(1) on it previously, but I was really hoping for a better 
compression result.

The relevant line in /etc/fstab is
  UUID=625c7324-0102-43f8-9120-680ad6ad82c3   /raidp xt4
nofail,discard,noatime,acl 0  2

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: partclone 0.3.13+dfsg-4
Uname: Linux 6.0.12-76060012-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul  9 16:24:53 2024
SourcePackage: partclone
UpgradeStatus: Upgraded to focal on 2022-05-13 (788 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000

** Affects: partclone (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072602

Title:
  partclone.ext4 twirls forever when working on an unmounted RAID
  partition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partclone/+bug/2072602/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066388] Re: decimal point gnored with LC_NUMERIC=it_IT.UTF-8

[Kevin Keijzer]

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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066388

Title:
  decimal point gnored with LC_NUMERIC=it_IT.UTF-8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2066388/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066388] Re: decimal point gnored with LC_NUMERIC=it_IT.UTF-8

[Kevin Keijzer]

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.launchpad.net/bugs/2066388

Title:
  decimal point gnored with LC_NUMERIC=it_IT.UTF-8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2066388/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072435] [NEW] New upstream release (1.5.0)

[Kevin Williams]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072435

Title:
  New upstream release (1.5.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bucklespring/+bug/2072435/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64

[Kevin Becker]

It was reported that this is happening on noble arm64. It turns out that
CONFIG_KEXEC_IMAGE_VERIFY_SIG was not enabled there. I'm working on
getting that enabled on noble arm64.

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu 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

Title:
  kdump doesn't work with UEFI secure boot and kernel lockdown enabled
  on ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066902] Re: Night Light occasionally gets stuck

[Kevin Keijzer]

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 colour temperature
is stuck again when I unlock my computer in the morning. I haven't
discovered any pattern or causality.

So I guess the only way to test this is to just wait and see if it
doesn't happen any more.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066902

Title:
  Night Light occasionally gets stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2066902/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2072370] Re: URL for home page and privacy policy point to a dead site

[Kevin Cole]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alpine/+bug/2072370/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067080] Re: [SRU] Please bump firmware revision to 8 from jammy

[Kevin Yeh]

@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.net/bugs/2067080

Title:
  [SRU] Please bump firmware revision to 8 from jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067080] Re: [SRU] Please bump firmware revision to 8 from jammy

[Kevin Yeh]

@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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067080

Title:
  [SRU] Please bump firmware revision to 8 from jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/2067080/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070319] Re: Xorg crash after installing the nvidia-driver-470.256.02

[Kevin Yeh]

** 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:
  Xorg crash after installing the nvidia-driver-470.256.02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2070319/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070319] [NEW] Xorg crash after installing the nvidia-driver-470.256.02

[Kevin Yeh]

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. Install nvidia-driver-470
5. reboot

[Fail rate]
5/5

[additional information]
This test is conducting on 
https://certification.canonical.com/hardware/202205-30322/

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-107.117~20.04.1-generic 5.15.149
Uname: Linux 5.15.0-107-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.256.02  Thu May  2 
14:37:44 UTC 2024
 GCC version:  gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
Date: Mon Jun 24 21:01:25 2024
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 20.03.00, 5.15.0-107-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
 fwts-efi-runtime-dkms, 20.03.00, 5.8.0-43-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 nvidia, 470.256.02, 5.15.0-107-generic, x86_64: installed
 tp_smapi, 0.43, 5.15.0-107-generic, x86_64: installed
 tp_smapi, 0.43, 5.8.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:4626] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0bc1]
   Subsystem: Dell Device [1028:0bc1]
InstallationDate: Installed on 2021-02-09 (1231 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Dell Inc. Precision 3470
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-107-generic 
root=UUID=d8111630-716f-480c-84fe-0805951492c5 ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2022
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: RAID
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1:
dmi.product.family: Precision
dmi.product.name: Precision 3470
dmi.product.sku: 0BC1
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.17
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug crash focal ubuntu uec-images

-- 
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:
  Xorg crash after installing the nvidia-driver-470.256.02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2070319/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069550] Re: DUTs displayed a black screen after installing the kernel in proposed on Focal

[Kevin Yeh]

** 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:
  DUTs displayed a black screen after installing the kernel in proposed
  on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069550/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069550] [NEW] DUTs displayed a black screen after installing the kernel in proposed on Focal

[Kevin Yeh]

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 me know.

** Affects: linux (Ubuntu)
 Importance: Critical
 Status: New


** Tags: cert-sru regression-proposed

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/bugs/2069550/+attachment/5790120/+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/2069550

Title:
  DUTs displayed a black screen after installing the kernel in proposed
  on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069550/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069400] Re: Some DUTs can't boot up after installing the hwe kernel in the proposed on Focal

[Kevin Yeh]

** 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
  proposed on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069400/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2069400] [NEW] Some DUTs can't boot up after installing the hwe kernel in the proposed on Focal

[Kevin Yeh]

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://bugs.launchpad.net/ubuntu/mantic/+source/linux/+bug/2061940 

Here is the list of the impacted machines that I found so far
https://certification.canonical.com/hardware/202107-29332
https://certification.canonical.com/hardware/202107-29331
https://certification.canonical.com/hardware/202105-29007
https://certification.canonical.com/hardware/202104-28970
https://certification.canonical.com/hardware/202104-28965
https://certification.canonical.com/hardware/202104-28966
https://certification.canonical.com/hardware/202104-28968
https://certification.canonical.com/hardware/202104-28969
https://certification.canonical.com/hardware/202104-28970

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cert-sru regression-proposed

** Attachment added: "DSC_1856.JPG"
   
https://bugs.launchpad.net/bugs/2069400/+attachment/5789474/+files/DSC_1856.JPG

-- 
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
  proposed on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069400/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068749] Re: modprobe of speakup modules on ARM RT kernel ends up in a lockup of module loading

[Kevin Becker]

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:

[  303.168453] input: Speakup as /devices/virtual/input/input1
[  303.174246] initialized device: /dev/synth, node (MAJOR 10, MINOR 122)
[  303.176539] speakup 3.1.6: initialized
[  303.176600] synth name on entry is: (null)
[  303.187469] synth probe
[  492.396049] INFO: task modprobe:1042 blocked for more than 122 seconds.
[  492.397557]   Not tainted 6.8.0-35-generic #35-Ubuntu
[  492.398493] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  492.399616] task:modprobestate:D stack:0 pid:1042  tgid:1042  
ppid:1041   flags:0x0004
[  492.401357] Call trace:
[  492.401789]  __switch_to+0xbc/0xf0
[  492.403196]  __schedule+0x2a8/0x7b0
[  492.403312]  schedule+0x40/0x168
[  492.403363]  schedule_preempt_disabled+0x30/0x68
[  492.403408]  __mutex_lock.constprop.0+0x31c/0x5d0
[  492.403454]  __mutex_lock_slowpath+0x20/0x48
[  492.403502]  mutex_lock+0x8c/0xc0
[  492.403541]  synth_add+0x3c/0x110 [speakup]
[  492.404115]  synth_apollo_init+0x24/0xff8 [speakup_apollo]
[  492.404213]  do_one_initcall+0x64/0x3b8
[  492.404260]  do_init_module+0xa4/0x280
[  492.404316]  load_module+0x7b8/0x8f0
[  492.404364]  init_module_from_file+0x98/0x118
[  492.404412]  idempotent_init_module+0x1a4/0x2c8
[  492.404459]  __arm64_sys_finit_module+0x70/0xf8
[  492.404511]  invoke_syscall+0x7c/0x128
[  492.404563]  el0_svc_common.constprop.0+0x4c/0x140
[  492.404763]  do_el0_svc+0x28/0x58
[  492.404823]  el0_svc+0x44/0x1a0
[  492.404874]  el0t_64_sync_handler+0x148/0x158
[  492.404926]  el0t_64_sync+0x1b0/0x1b8


We'll continue investigating this.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   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/2068749

Title:
  modprobe of speakup modules on ARM RT kernel ends up in a lockup of
  module loading

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-realtime/+bug/2068749/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel

[Kevin Becker]

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:

- QEMU arm64, linux-realtime 6.8.1-1002-realtime
- QEMU arm64, linux (generic) 6.8.0-35-generic

I haven't been able to get these combinations to fail:

- bare metal amd64, linux-realtime 6.8.1-1002-realtime
- LXD VM (multipass) amd64, linux-realtime 6.8.1-1002-realtime

-- 
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 oops in aafs_create in 6.8.1-1002-realtime kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068602] Re: kernel oops in aafs_create in 6.8.1-1002-realtime kernel

[Kevin Becker]

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 on realtime, at least on amd64. I was able to
reliably reproduce it in QEMU on amd64 without realtime. I'll add that
to this bug ticket and let the relevant people know. We'll continue
investigating this.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   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/2068602

Title:
  kernel oops in aafs_create in 6.8.1-1002-realtime kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-realtime/+bug/2068602/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059259] Re: ubuntu_ltp sched:starvation fails with ARM64 on bos2 region

[Kevin Becker]

** 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:starvation fails with ARM64 on bos2 region

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2059259/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068615] Re: kernel oops in pick_next_task_fair in 6.8.1-1002-realtime kernel

[Kevin Becker]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-realtime/+bug/2068615/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067108] Re: Dell XR5610 does not boot

[Kevin Becker]

Hi Jesse,

Have you used the realtime kernel on this system in the past? Are there
any issues with the generic kernel? See if you can try the latest linux-
realtime update, 5.15.0.1063.71 and please report if there's any
difference.

Could you describe how you enabled the real-time kernel? Are you using
Ubuntu Pro?

Also, could you like to collect some additional information about your
system? I realize you might not be able to if it doesn't fully boot, but
anything would be helpful. From a terminal, please run the following:

apport-collect BUG_ID
or to a file:
apport-bug --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

** Changed in: linux-realtime (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux-realtime (Ubuntu)
 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/2067108

Title:
  Dell XR5610 does not boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-realtime/+bug/2067108/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067004] [NEW] GIMP seg fault.

[Kevin Remisoski]

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_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 325907 - Thread 325907 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 326570]
[New LWP 326023]
[New LWP 325943]
[New LWP 325939]
[New LWP 325937]
[New LWP 325935]
[New LWP 325934]
[New LWP 325933]
[New LWP 325932]
[New LWP 325931]
[New LWP 325930]
[New LWP 325929]
[New LWP 325928]
[New LWP 325927]
[New LWP 325926]
[New LWP 325925]
[New LWP 325924]
[New LWP 325923]
[New LWP 325922]
[New LWP 325921]
[New LWP 325920]
[New LWP 325919]
[New LWP 325918]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7dbd9fea9c00 in malloc_consolidate (av=av@entry=0x7dbda0003ac0 
) at ./malloc/malloc.c:4878
  Id   Target Id   Frame 
* 1Thread 0x7dbd9f681640 (LWP 325907) "gimp-2.10"  0x7dbd9fea9c00 
in malloc_consolidate (av=av@entry=0x7dbda0003ac0 ) at 
./malloc/malloc.c:4878
  2Thread 0x7dbd654006c0 (LWP 326570) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7dbd716006c0 (LWP 326023) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7dbd670006c0 (LWP 325943) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7dbd70c006c0 (LWP 325939) "gimp-2.10"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7dbd720006c0 (LWP 325937) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7dbd82a006c0 (LWP 325935) "gdbus"  0x7dbd9ff1b4cd 
in __GI___poll (fds=0x7dbd30009bf0, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7dbd834006c0 (LWP 325934) "gmain"  0x7dbd9ff1b4cd 
in __GI___poll (fds=0x562a927fc7a0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7dbd83e006c0 (LWP 325933) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7dbd8d6006c0 (LWP 325932) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7dbd8e0006c0 (LWP 325931) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7dbd8ea006c0 (LWP 325930) "worker" syscall () at 

[Bug 2066972] [NEW] ubuntu-bug ubuntu-release-upgrader-core

[Kevin George Meads]

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-release-upgrader-core 1:23.10.14
ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 02:55:28 2024
InstallationDate: Installed on 2024-05-10 (14 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2024-05-23 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade mantic third-party-packages 
wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066972

Title:
  ubuntu-bug ubuntu-release-upgrader-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066972/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066902] [NEW] Night Light occasionally gets stuck

[Kevin Keijzer]

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 menu does
nothing.

The only ways to restore the screen to normal are disabling and enabling
the colour profile or running `gdbus call -e -o
/org/gnome/SettingsDaemon/Color -d org.gnome.SettingsDaemon.Color -m
org.gnome.SettingsDaemon.Color.NightLightPreview 1`

I have never been able to find anything remotely relevant in any system
logs regarding this issue. It also does not happen every day, but
probably once every seven to ten days or so.

My PC has an AMD RX550 GPU using the amdgpu driver. I'm not sure if it
makes a difference, but so far I've not seen this problem on my other
machines with Intel IGPs.

The upstream bug report can be found here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3439

** Affects: mutter (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/2066902

Title:
  Night Light occasionally gets stuck

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2066902/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066388] Re: decimal point gnored with LC_NUMERIC=it_IT.UTF-8

[Kevin Keijzer]

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-calculator/-/issues #403
   https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/403

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066388

Title:
  decimal point gnored with LC_NUMERIC=it_IT.UTF-8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/2066388/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061914] Re: libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04)

[Kevin Yue]

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.0, but it
has not been released yet. Since few breaking changes exist between
`webkit2gtk-4.1` and `webkit2gtk-4.0`, I plan to port the Tauri 1.x to
use `webkit2gtk-4.1`. I have managed to make this work but with one
error. And I'm currently working on it.

-- 
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 build
  (24.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2061914/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061914] Re: libjavascriptcoregtk-4.0-18 seems to be missing on the latest build (24.04)

[Kevin Yue]

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 build
  (24.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2061914/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Kevin Yeh]

** 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 device path
  EFI stub: Measured initrd data into PCR 9
  
- There are not journal logs existed when I boot with previous kernel.
+ There are no journal logs existed when I boot with the 6.5.0-33 kernel.
  
  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

** 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:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9
  
- There are no journal logs existed when I boot with the 6.5.0-33 kernel.
+ There are no journal logs existed when it boot with the 6.5.0-33 kernel.
  
  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061940] [NEW] Some DUTs can't boot up after installing the proposed kernel on Mantic

[Kevin Yeh]

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

There are not journal logs existed when I boot with previous kernel.

Here is the list of the impacted machines that I found so far
https://certification.canonical.com/hardware/202106-29206/
https://certification.canonical.com/hardware/202106-29207/
https://certification.canonical.com/hardware/201912-27623/
https://certification.canonical.com/hardware/202007-28059/
https://certification.canonical.com/hardware/202103-28762/
https://certification.canonical.com/hardware/202012-28510/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cert-sru regression-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060246] Re: [FFe] Packaged VisualVM version (2.1.6) in Noble beta is incompatible with default java version (21)

[Kevin Milner]

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/2060246

Title:
  [FFe] Packaged VisualVM version (2.1.6) in Noble beta is incompatible
  with default java version (21)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/2060246/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313848] Re: AuthnProviderAlias does not work w/ authnz_ldap

[kevin vasquez]

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.com) which targets LDAP authentication
problems in Apache 2.4. Follow the steps to apply the patch, rebuild
Apache, and then test LDAP authentication to ensure it's functioning
correctly. Monitor server stability post-patch to ensure reliable LDAP
authentication. Double-check any Apache 2.4 configuration adjustments
made during the migration to Ubuntu 14.04. If you encounter
difficulties, seek specific guidance on patch application and Apache
configuration.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313848

Title:
  AuthnProviderAlias does not work w/ authnz_ldap

To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1313848/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060246] [NEW] Packaged VisualVM version (2.1.6) in Noble beta is incompatible with default java version (21)

[Kevin Milner]

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: 21.

Please use JDK 8 to JDK20 to run VisualVM. For more information about
requirements and setup visit https://visualvm.github.io.;

From that website, I see that version 2.1.7 is required for Java 21
support (and a newer 2.1.8 release adds Java 22 support).

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: visualvm 2.1.6-1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 15:30:22 2024
InstallationDate: Installed on 2024-03-26 (10 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: visualvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: visualvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble third-party-packages wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060246

Title:
  Packaged VisualVM version (2.1.6) in Noble beta is incompatible with
  default java version (21)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/2060246/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

** 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Kevin Becker]

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:
  AWS: arm64: pauth: don't sign leaf functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056383] Re: Audio turned to dummy output from 5.15.0-1049-intel-iotg to 5.15.0-1050

[Kevin Yeh]

** 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-intel-iotg to
  5.15.0-1050

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg-5.15/+bug/2056383/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines

[Kevin Yeh]

@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=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.153.239 sudo ubuntu-drivers devices
WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid Support 
PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-535: package has invalid Support 
PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-535-open: package has invalid 
Support PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-525-server: package has invalid 
Support PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-535-server-open: package has 
invalid Support PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-525-open: package has invalid 
Support PBheader, cannot determine support level
WARNING:root:_pkg_get_support nvidia-driver-535-server: package has invalid 
Support PBheader, cannot determine support level
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd2191sv1028sd0949bc03sc00i00
vendor   : NVIDIA Corporation
model: TU116M [GeForce GTX 1660 Ti Mobile]
driver   : nvidia-driver-450-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free recommended
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-modules-nvidia-535-server-open-generic : Depends: 
linux-modules-nvidia-535-server-open-5.4.0-173-generic (= 5.4.0-173.191) but it 
is not going to be installed
E: Unable to correct problems, you have held broken packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044973

Title:
  ubuntu-drivers install the wrong version of Nvidia driver on some
  machines

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

[Kevin Keijzer]

** 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/1977619

Title:
  NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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 SLAAC addresses when
  available. And according to RFC 6724, the smaller /128 scope of the
  DHCPv6 address should be chosen over the larger /64 scope of the SLAAC
  address.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection (in nm-connection-editor *not*
  selecting "Prefer temporary address" for IPv6 privacy extensions). Then
  it would use the DHCPv6 address as the source for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Regression:
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection.
  
  Constantly removing the SLAAC addresses with `ip addr del` or disabling
  SLAAC RA's on the router are now the only ways to stop NetworkManager
  from preferring SLAAC over DHCPv6. None of the local options in
  NetworkManager 1.36.6 are able to restore the previous, desired and
  correct way of working: the SLAAC address should never be used as the
  preferred address if a DHCPv6 lease is given.
  
  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed in
  that release:
  
  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  Steps to reproduce:
  
  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).
  
  2. When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
  the case. (The Linux kernel uses the address highest in the list as
  preferred.)
  
  3. When running something like `curl ifconfig.co`, the SLAAC address is
  being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)
  
  Desired behaviour:
  
  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
- those should take first priority, with DHCPv6 second and SLAAC last.
+ those should take first priority, with DHCPv6 second and SLAAC/autoconf
+ last.
  
  Implications:
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on and cannot centrally configure), I
  am being locked out of the servers in question unless I forcefully
  remove the addresses or disable SLAAC on my router, so my outgoing
  traffic is being routed through the DHCPv6 address again.
  
  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover, it
  would break IPv6 connectivity entirely for devices that don't support
  DHCPv6 (read: Android).
  
  Conclusion:
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should. As that version is also used in Ubuntu kinetic, most likely this
  bug is not present there.
  
  Looking at the changelog of 1.38.0:
  
  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
  
  It looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
  Please either backport the fix from 1.38.0 or revert to 1.36.4, which
  was working fine.
  
  System information:
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS 

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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 /128 scope of the
  DHCPv6 address should be chosen over the larger /64 scope of the SLAAC
  address.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection (in nm-connection-editor *not*
  selecting "Prefer temporary address" for IPv6 privacy extensions). Then
  it would use the DHCPv6 address as the source for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
- 
  
  Regression:
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  on the router is the only way to stop NetworkManager from preferring
  SLAAC over DHCPv6 now. None of the local options in NetworkManager
  1.36.6 are able to restore the previous, desired and correct way of
  working.
  
  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed in
  that release:
  
  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
- 
  Steps to reproduce:
  
  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).
  
  2. When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
  the case. (The Linux kernel uses the address highest in the list as
  preferred.)
  
  3. When running something like `curl ifconfig.co`, the SLAAC address is
  being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)
  
- 
  Desired behaviour:
  
  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and SLAAC last.
- 
  
  Implications:
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on and cannot centrally configure), I
  am being locked out of the servers in question unless I forcefully
  remove the addresses or disable SLAAC on my router, so my outgoing
  traffic is being routed through the DHCPv6 address again.
  
+ Note that "just disabling SLAAC RA's on the router" is not something
+ everybody can do, as it requires root access to the device. Moreover, it
+ would break IPv6 connectivity entirely for devices that don't support
+ DHCPv6 (read: Android).
  
  Conclusion:
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should. As that version is also used in Ubuntu kinetic, most likely this
  bug is not present there.
  
  Looking at the changelog of 1.38.0:
  
  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.
  
  
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 the fix from 1.38.0 or revert to 1.36.4, which
  was working fine.
- 
  
  System information:
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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 over the
- larger /64 scope of the SLAAC address.
+ 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 /128 scope of the
+ DHCPv6 address should be chosen over the larger /64 scope of the SLAAC
+ address.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection (in nm-connection-editor *not*
  selecting "Prefer temporary address" for IPv6 privacy extensions). Then
  it would use the DHCPv6 address as the source for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
+ 
+ Regression:
+ 
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
- altogether is the only way to stop NetworkManager from preferring SLAAC
- over DHCPv6 now.
+ on the router is the only way to stop NetworkManager from preferring
+ SLAAC over DHCPv6 now. None of the local options in NetworkManager
+ 1.36.6 are able to restore the previous, desired and correct way of
+ working.
  
- Looking at the changelog of NetworkManager 1.36.6, things regarding IP
- address order and temporary addresses have been changed in that release:
+ Looking at the changelog of NetworkManager 1.36.6, multiple things
+ regarding IP address order and temporary addresses have been changed in
+ that release:
  
  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.
  
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
- When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
- addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
- kernel uses the address highest in the list as preferred.)
+ 
+ Steps to reproduce:
+ 
+ 1. Connect to a network where the router sends "A" and "M" bits in the
+ RA's and has a DHCPv6 server running (e.g. any OpenWrt router).
+ 
+ 2. When running `ip -6 a`, the list now sorts SLAAC addresses above
+ DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not
+ the case. (The Linux kernel uses the address highest in the list as
+ preferred.)
+ 
+ 3. When running something like `curl ifconfig.co`, the SLAAC address is
+ being returned, which makes sense as that is now preferred by the
+ kernel. (But it shouldn't be.)
+ 
+ 
+ Desired behaviour:
+ 
+ NetworkManager should always sort DHCPv6 addresses above SLAAC
+ addresses, as is the case for all versions prior to 1.36.6 and also
+ corrected again in 1.38.0. In case static addresses are manually set,
+ those should take first priority, with DHCPv6 second and SLAAC last.
+ 
+ 
+ Implications:
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
- address that I have no influence on), I am being locked out of the
- servers in question unless I forcefully remove the addresses or disable
- SLAAC on my router, so my outgoing traffic is being routed through the
- DHCPv6 address again.
+ address that I have no influence on and cannot centrally configure), I
+ am being locked out of the servers in question unless I forcefully
+ remove the addresses or disable SLAAC on my router, so my outgoing
+ traffic is being routed through the DHCPv6 address again.
+ 
+ 
+ Conclusion:
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
- should.
+ should. As that version is also used in Ubuntu kinetic, most likely this
+ bug is not present there.
+ 
+ Looking at the changelog of 1.38.0:
+ 
+ * Fix bug setting priority for IP addresses.
+ * 

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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 over the
  larger /64 scope of the SLAAC address.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection (in nm-connection-editor *not*
  selecting "Prefer temporary address" for IPv6 privacy extensions). Then
  it would use the DHCPv6 address as the source for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
+ 
+ * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
+ * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
+ * Ensure temporary IPv6 addresses are removed on disconnect and reapply.
+ 
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6
  
  Looking at the changelog of 1.38.0:
  
  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.
  
  
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 the fix from 1.38.0 or revert to 1.36.4, which
  was working fine.
  
  More background here: https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1974428/comments/11

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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 of the DHCPv6 address should be chosen over the
+ larger /64 scope of the SLAAC address.
  
  NetworkManager has always been able to adhere to that by simply setting
- ip6.privacy=0 for the connection. Then it would not generate temporary
- addresses and use the DHCPv6 address as the source for outgoing traffic.
+ ip6.privacy=0 for the connection (in nm-connection-editor called "Prefer
+ temporary address"). Then it would use the DHCPv6 address as the source
+ for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6
  
  Looking at the changelog of 1.38.0:
  
  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.
  
  
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 the fix from 1.38.0 or revert to 1.36.4, which
  was working fine.
  
  More background here: https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1974428/comments/11

** 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 over the
  larger /64 scope of the SLAAC address.
  
  NetworkManager has always been able to adhere to that by simply setting
- ip6.privacy=0 for the connection (in nm-connection-editor called "Prefer
- temporary address"). Then it would use the DHCPv6 address as the source
- for all outgoing traffic.
+ ip6.privacy=0 for the connection (in nm-connection-editor *not*
+ selecting "Prefer temporary address" for IPv6 privacy extensions). Then
+ it would use the DHCPv6 address as the source for all outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC 

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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=0 for the connection. Then it would not generate temporary
  addresses and use the DHCPv6 address as the source for outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6
+ 
+ Looking at the changelog of 1.38.0:
+ 
+ * Fix bug setting priority for IP addresses.
+ * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from autoconf. This 
affects IPv6 source address selection, if the rules from RFC 6724, section 5 
don't give a exhaustive match.
+ 
+ 
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 the fix from 1.38.0 or revert to 1.36.4, which
+ was working fine.

** 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=0 for the connection. Then it would not generate temporary
  addresses and use the DHCPv6 address as the source for outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world and be echoed
  back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For 

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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=0 for the connection.
+ ip6.privacy=0 for the connection. Then it would not generate temporary
+ addresses and use the DHCPv6 address as the source for outgoing traffic.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
- address would be used to connect to the outside world.
+ address would be used to connect to the outside world and be echoed
+ back.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
  So this update introduces a very breaking change in IPv6 source address
  selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

[Kevin Keijzer]

@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-based IPv6 routing in an LTS
release, I think the impact is severe. In my opinion, this update should
never have reached stable, especially because this bug is known upstream
and fixed in a later version.

I'm already quite stressed how this will turn out at work after the
weekend. We use source-based ACL's on all of our firewalls, giving
static DHCPv6 leases to our client devices. Now all of a sudden those
addresses are no longer being used for outgoing traffic, but instead the
non-controllable SLAAC-addresses are. This will lock everyone out of all
servers.

The only way to get the proper addresses to be preferred again seems to
be to disable SLAAC on the router, because any local setting in
NetworkManager no longer works. I can disable SLAAC without issues at
home, because everything is 100% Ubuntu and Debian there. But in
environments with other OS'es that don't support DHCPv6 (like Android),
disabling SLAAC will break IPv6 on all such devices. Moreover, not
everybody controls their own routers, so this really isn't much of a
solution.

Other options would be to downgrade and apt-mark hold network-manager on
all Ubuntu 22.04 devices, or to completely change server firewall
infrastructure by whitelisting prefixes. As you can see, none of these
options sound appealing.

So regarding the regression potential: it has severely regressed IPv6
handling, and definitely *not* fixed things.

-- 
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
- So this update introduces a very breaking change to an LTS release,
- while LTS releases should be stable.
+ So this update introduces a very breaking change in IPv6 source address
+ selection to an LTS release, while LTS releases should be stable.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
  any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
+ So this update introduces a very breaking change to an LTS release,
+ while LTS releases should be stable.
+ 
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

[Kevin Keijzer]

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
- net.ipv6.conf.all.use_tempaddr = 0 and
- net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
- has any effect.
+ net.ipv6.conf.all.use_tempaddr=0 and
+ net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has
+ any effect.
  
- Removing the SLAAC addresses with `ip addr del` or disabling RA's
+ Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in all
  kinds of firewalls to allow me to access servers for my work. Now that
  the "wrong" address is being preferred for outgoing traffic (a SLAAC
  address that I have no influence on), I am being locked out of the
  servers in question unless I forcefully remove the addresses or disable
  SLAAC on my router, so my outgoing traffic is being routed through the
  DHCPv6 address again.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
  
  /etc/os-release:
  
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy
  
  nmcli -v:
  
  nmcli tool, version 1.36.6

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

** 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 setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
- addresses. With NetworkManager 1.36.4 this was not the case.
- 
- Unfortunately, this introduced this bug, which is really breaking a lot
- of my use cases.
+ addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
+ kernel uses the top address as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
- kernel uses the top address as preferred.)
+ kernel uses the address highest in the list as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
+ 
+ /etc/os-release:
+ 
+ PRETTY_NAME="Ubuntu 22.04 LTS"
+ NAME="Ubuntu"
+ VERSION_ID="22.04"
+ VERSION="22.04 LTS (Jammy Jellyfish)"
+ VERSION_CODENAME=jammy
+ ID=ubuntu
+ ID_LIKE=debian
+ 

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

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 added in the wrong order, which is
known and fixed upstream for 1.38.x, but never fixed for 1.36.x.

-- 
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:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

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 43193sec preferred_lft 43194sec
inet6 fd10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43194sec
inet6 fd10:3781::0:9875:4dec:b9f9:e768/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781::0:f802:2428:9af1:dcb3/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::36e2:ec4c:fddb:3c89/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

After (network-manager 1.36.6):

2: eno0:  mtu 1500 state UP qlen 1000
inet6 fd10:3781::0:9875:4dec:b9f9:e768/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781::0:f802:2428:9af1:dcb3/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43194sec preferred_lft 43194sec
inet6 fd10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43194sec preferred_lft 43194sec
inet6 fe80::36e2:ec4c:fddb:3c89/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

On another machine with Debian sid and network-manager 1.38.0, it looks
like the way it should be again (dynamic addresses at the top of the
list, preferred to autoconfigured / temporary addresses):

2: wlan0:  mtu 1500 state UP qlen 1000
inet6 fd10:3781:::5bf/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43193sec
inet6 2a10:3781:::5bf/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43193sec
inet6 2a10:3781::0:42cd:4f1b:89b8:77fd/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fd10:3781::0:8a59:df52:9ea1:e7c8/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::a738:71dc:f10e:924e/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

So this bug was not present in NetworkManager 1.36.4, introduced in
1.36.6, and then fixed in 1.38.0.

-- 
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:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
- altogether is the only way to stop NetworkManager from prefering SLAAC
+ altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case.
  
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
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:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

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.

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
- Physically removing the SLAAC addresses or disabling RA's altogether is
- the only way to stop NetworkManager from prefering SLAAC over DHCPv6
- now.
+ Removing the SLAAC addresses with `ip addr del` or disabling RA's
+ altogether is the only way to stop NetworkManager from prefering SLAAC
+ over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case.
  
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
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:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

[Kevin Keijzer]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

** 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=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Physically removing the SLAAC addresses or disabling RA's altogether is
  the only way to stop NetworkManager from prefering SLAAC over DHCPv6
  now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
+ When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
+ addresses. With NetworkManager 1.36.4 this was not the case.
+ 
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
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:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] [NEW] DHCPv6 addresses are no longer preferred over SLAAC addresses

[Kevin Keijzer]

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 connection.

So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
address would be used to connect to the outside world.

Since the update to 1.36.6, this is no longer the case. NetworkManager
now routes outgoing traffic through the SLAAC address, even if
ip6.privacy=0 is set for the connection. Setting
net.ipv6.conf.all.use_tempaddr = 0 and
net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
has any effect.

Physically removing the SLAAC addresses or disabling RA's altogether is
the only way to stop NetworkManager from prefering SLAAC over DHCPv6
now.

Looking at the changelog of NetworkManager 1.36.6, things regarding IP
address order and temporary addresses have been changed in that release:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

Unfortunately, this introduced this bug, which is really breaking a lot
of my use cases.

I should note that the bug is not present in NetworkManager 1.38.0 on
Debian sid. That just prefers DHCPv6 addresses when available, like it
should.

** Affects: network-manager (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/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

[Kevin Keijzer]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Output of dmesg attached.

** Attachment added: "output dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593690/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code

[Kevin]

This is greatly exasperated because systemd until v251 is using MemFree
and not MemAvailable to decide how much memory is remaining. Since Linux
aggressively uses MemFree for caching, this will result in systemd-oomd
excessively killing applications.

There's a fix in upstream 030bc91cb98385904b28a839d1e04bb4160a52d2,
which was released as v251 about a week ago.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972159

Title:
  systemd-oomd frequently kills firefox and visual studio code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Please find output of cat /proc/iomem attached.

** Attachment added: "output cat /proc/iomem"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593426/+files/iomem.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATL
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATL returned object 09af25b3, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATH
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATH returned object 3c0aee1f, 
external buffer length 18
 [Integer] = 

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Yes - Disabling Secureboot worked in order to get acpidbg working
(killed my touchpad mouse however that is another topic).

Output from both commands here:

$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATD
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATD returned object a3ce38e0, 
external buffer length 18
 [Integer] = 

$ sudo acpidbg -b 'ex \_SB_.BAT1._STA'
Evaluating \_SB_.BAT1._STA
Evaluation of \_SB_.BAT1._STA returned object cb8c88ff, external buffer 
length 18
 [Integer] = 000F

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Unfortunately I get an "Operation not permitted" error when running sudo
acpidbg -b 'ex \_SB_.BAT1._STA' as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Hi,
I left the PC at the office. Will try the new command on Friday when I will be 
there again. Thanks!
Br. Kevin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Unfortunately I get an "Operation not permitted" error when I try to run
acpidbg here. Is above command exactly as it should be entered? Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956177] Re: battery not detected by ACPI

[Kevin Peter Gade]

Hello.
I have tried to follow above instructions carefully, recompiling my own file. 
However for me its not working, unfortunately battery is still not recognized. 

I followed these steps:

1) install acpica-tools
sudo apt-get install acpica-tools

2) Grab the DSDT of your device
sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat

3) Decompile the dsdt.dat
sudo iasl -d dsdt.dat

4) Open the dsdt.dsl with whatever editor tickles your fancy
sudo xed dsdt.dsl

5) Delete everything with a * in front, first line should be "DefinitionBlock"
(For me that include Firmware Error (ACPI) in line 1 and 2 - if that could 
matter:
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload-388)
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload2-369)

6) Raise the last number in Definition Block by one
e.g.:
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C)
   ↓
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C0001)

7) Search for the string "OperationRegion (ERAM"
for me it was at line 18751; your mileage may vary

8) Replace the entire line with this one:
OperationRegion (ERAM, EmbeddedControl, Zero, 0x0100)

(I had OperationRegion (ERAM, SystemMemory, 0xFE508300, 0x0100) to begin
with)

9) Save and Exit

10) Recompile the dsdt.dsl (Note: This WILL show loads of warnings and 
optimizations
This will give you a dsdt.aml that should work.

I did that with: sudo iasl -ta dsdt.dsl and got the aml file just with
warnings.

11) Proceed as above

sudo cp dsdt.aml /boot/
sudo cp 01_acpi /etc/grub.d/
chmod 755 01_acpi
sudo update-grub
reboot

Still just the same :/
Can anyone point me in the right direction?

PS. BIOS v. 1.12 (freshly update through Windows, Fujitsu DeskUpdate).

Br. Kevin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177

Title:
  battery not detected by ACPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750

[Kevin]

This bug is back in ubuntu 22.04, somehow. In the previous ubuntu version I was 
using it was possible to add workarounds via xinput rules, but the clickpad 
parameter seems to be absent from libinput quirks, instead it uses this kernel 
parameter?
all three mouse buttons misbehave in various ways, although the right button is 
most obvious, being completely disabled

root@usb128:~# dpkg -l \*libinput\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---==>
ii  libinput-bin1.20.0-1 amd64input device 
management and event handling library>
ii  libinput-tools  1.20.0-1 amd64input device 
management and event handling library>
ii  libinput10:amd641.20.0-1 amd64input device 
management and event handling library>
ii  xserver-xorg-input-libinput 1.2.1-1  amd64X.Org X server -- 
libinput input driver
root@usb128:~# udevadm info /sys/class/input/input14
P: 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DELL09C3:00/0018:0488:120A.0001/input/input14
L: 0
E: 
DEVPATH=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DELL09C3:00/0018:0488:120A.0001/input/input14
E: PRODUCT=18/488/120a/100
E: NAME="DELL09C3:00 0488:120A Touchpad"
E: PHYS="i2c-DELL09C3:00"
E: UNIQ=""
E: PROP=5
E: EV=1b
E: KEY=e520 1 0 0 0 0
E: ABS=2e08003
E: MSC=20
E: 
MODALIAS=input:b0018v0488p120Ae0100-e0,1,3,4,k110,145,148,14A,14D,14E,14F,ra0,1,2F,35,36,37,39,m5,lsfw
E: SUBSYSTEM=input
E: USEC_INITIALIZED=15474954
E: ID_INPUT=1
E: ID_INPUT_TOUCHPAD=1
E: ID_SERIAL=noserial
E: ID_PATH=pci-:00:15.1-platform-i2c_designware.1
E: ID_PATH_TAG=pci-_00_15_1-platform-i2c_designware_1
E: ID_FOR_SEAT=input-pci-_00_15_1-platform-i2c_designware_1
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

root@usb128:~#

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906341

Title:
  Touchpad button doesn't work on Dell Precision 7550/7750

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1906341/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971901] Re: dlltool uses non-unique temp filenames

[Kevin Puetz]

** Also affects: wine via
   https://bugs.winehq.org/show_bug.cgi?id=52770
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971901] Re: dlltool uses non-unique temp filenames

[Kevin Puetz]

Linking binutils package and subscribing Mattias Klose since
https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 mentions
"Update from the binutils 2.38 branch: Fix PR 28885" and so a rebuild
based on binutils-source_2.38-4ubuntu1 would fix this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971901] Re: dlltool uses non-unique temp filenames

[Kevin Puetz]

** Bug watch added: Sourceware.org Bugzilla #28885
   https://sourceware.org/bugzilla/show_bug.cgi?id=28885

** Also affects: binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=28885
   Importance: Unknown
   Status: Unknown

** Also affects: binutils (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/1971901

Title:
  dlltool uses non-unique temp filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1971901/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973226] Re: UI doesn't allow setting Left Ctrl as Compose

[Kevin Bullock]

Thanks for the reply! Reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860

And patch submitted here: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1328

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1860
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973226

Title:
  UI doesn't allow setting Left Ctrl as Compose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973226/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973226] [NEW] UI doesn't allow setting Left Ctrl as Compose

[Kevin Bullock]

Public bug reported:

In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
have been removed from gnome-tweaks and moved into control-center, but
Left Ctrl is not in the list of options for Compose.

I was able to restore Left Ctrl as my Compose key using:

$ gsettings set org.gnome.desktop.input-sources xkb-options ...

adding 'compose:lctrl' to that list, but it would be nice to expose it
in the GUI.

For context, my modifier settings are:

* Caps Lock is Ctrl ('ctrl:nocaps')
* Left Ctrl is Compose ('compose:lctrl')
* Both Shift keys enable/disable Caps Lock ('shift:both_capslock')

which gives me both a Ctrl key on both sides of the keyboard and an
easily-accessible Compose key.

** Affects: gnome-control-center (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/1973226

Title:
  UI doesn't allow setting Left Ctrl as Compose

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1973226/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973054] Re: containerd regression for CVE-2022-23648 in latest version 1.5.9-0ubuntu1~20.04.1

[Kevin R]

** Description changed:

  Hi,
  
  CVE-2022-23648 allows leaking files on the host inside containers given
  an attacker crafted image if you use containerd's CRI implementation
  (e.g. Kubernetes). Ubuntu fixed this in `1.5.5-0ubuntu3~20.04.2` on
  focal, as noted in [this security
  advisory](https://ubuntu.com/security/CVE-2022-23648) on March 2nd.
  However, the latest package version for focal is
  `1.5.9-0ubuntu1~20.04.1`, published on [April
  
27th](https://www.ubuntuupdates.org/package/core/focal/main/updates/containerd),
  and I just reproduced the vulnerability on this version. Upstream
  containerd fixed this issue in 1.5.10.
  
  This also exists on the latest official Ubuntu EKS AMI (us-west-2 is
  `ami-05146f3491fd02c4b` for EKS 1.21). I think most folks on EKS might
  not be vulnerable unless they specify kubelet to use containerd's CRI
  rather than the default dockershim, but the package itself is still
  vulnerable given the right kubelet configuration.
  
  I reproduced the bug with the following steps:
  1. Build the POC docker image with the following `Dockerfile`:
  ```
  FROM debian:latest
  VOLUME /../../../../../../../../var/lib/kubelet/pki```
  then tag it as `cve-2022-23648-test:1` and push to a registry of your choice
  2. Launch the AMI we're testing (`ami-05146f3491fd02c4b` from May 6th), then 
ssh into node
  3. To trick containerd into running, give it a dummy CNI (this is because I'm 
too lazy to spin up a full EKS cluster)
  ```cat </cve-2022-23648-test:1
    command: ["/bin/bash", "-c", "--"]
    args: [ "while true; do sleep 30; done" ]
  EOF```
  5. Ask kubelet to pick up the static pod, and also ask it to use containerd's 
CRI and not dockershim
  ```sudo snap set kubelet-eks pod-manifest-path=/etc/kubernetes/manifests/ 
container-runtime=remote 
container-runtime-endpoint=unix:///var/run/containerd/containerd.sock
  sudo snap restart kubelet-eks```
  6. Wait for the container to come up. `sudo ctr -n [k8s.io](http://k8s.io) c 
ls` should show two containers:
  ```ubuntu@ip-10-4-32-200:~$ sudo ctr -n k8s.io c ls
  CONTAINER   IMAGE 
   RUNTIME
  209d6f3ddf858df5bf7653dd54bf1f6f88210d6d99ccd3a6272666a553efb48b
k8s.gcr.io/pause:3.5 io.containerd.runc.v2
- 319c6e9c5c053aac13fca3bd78f0016aac1b3507597b4c414c86c1686e33db53
infra.docker.zooxlabs.com/krong-cve-2022-23648-test:2
io.containerd.runc.v2```
+ 319c6e9c5c053aac13fca3bd78f0016aac1b3507597b4c414c86c1686e33db53
/cve-2022-23648-test:1io.containerd.runc.v2```
  7. Verify if /var/lib/kubelet/pki is empty by using runc to exec into the 
container (containerd does not have this functionality)
  ```ubuntu@ip-10-4-32-200:~$ sudo runc --root /run/containerd/runc/k8s.io exec 
319c6e9c5c053aac13fca3bd78f0016aac1b3507597b4c414c86c1686e33db53 ls -la 
/var/lib/kubelet/pki
  total 16
  drwxr-xr-x 2 root root 4096 May 11 05:09 .
  drwxr-xr-x 3 root root 4096 May 11 05:09 ..
  -rw-r--r-- 1 root root 2291 May 11 05:02 kubelet.crt
  -rw--- 1 root root 1675 May 11 05:02 kubelet.key```
  If the files are there, then it's vulnerable.
  
  Thanks,
  Kevin R

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973054

Title:
  containerd regression for CVE-2022-23648 in latest version
  1.5.9-0ubuntu1~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1973054/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972913] [NEW] man pages are out of date

[Kevin Turner]

Public bug reported:

`man java` shows a man page for some build of JDK 8 in 2015, not the
`java` included in this package with documentation appropriate for the
included JVM.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: openjdk-11-jre-headless 11.0.15+10-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 10 16:20:13 2022
InstallationDate: Installed on 2020-12-25 (501 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-kitty
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openjdk-lts
UpgradeStatus: Upgraded to impish on 2022-01-02 (128 days ago)

** Affects: openjdk-lts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972913

Title:
  man pages are out of date

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1972913/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971901] Re: dlltool uses non-unique temp filenames

[Kevin Puetz]

Missed a link, https://bugs.winehq.org/show_bug.cgi?id=52770 shows
others on jammy hitting the same (and confirms this upstream patch fixes
it)

** Bug watch added: Wine Bugzilla #52770
   https://bugs.winehq.org/show_bug.cgi?id=52770

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils-mingw-w64/+bug/1971901/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971907] [NEW] QGIS 3.22.4 from the Jammy won't install

[Kevin Havener]

Public bug reported:

Installation of qgis 3.22.4 fails in post install configure on jammy.
The qgis-providers package seems to be the problem.  The only meaningful
info I got was an error from synaptic claiming a name was missing from a
package file.  apt only gave a generic 127 error.

Don't be misled by the 3rd party app.  The initial install attempt was
from a jammy repository that was not disabled on upgrade.

I have also tried the 3.24 package from qgis.org.  It fails in exactly
the same manner.  QGIS 3.22.4 installed and worked just fine on impish.
Actually, so did 3.24.1 from qgis.org.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: qgis 3.22.4+dfsg-3build1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Thu May  5 21:31:35 2022
InstallationDate: Installed on 2017-06-01 (1799 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: qgis
UpgradeStatus: Upgraded to jammy on 2022-05-02 (3 days ago)
modified.conffile..etc.default.qgis: [deleted]

** Affects: qgis (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971907

Title:
  QGIS 3.22.4 from the Jammy won't install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qgis/+bug/1971907/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971901] [NEW] dlltool uses non-unique temp filenames

[Kevin Puetz]

Public bug reported:

Description:Ubuntu 22.04 LTS
Release:22.04

binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

/usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
  ../wine-6.0.4/dlls/winmm/winmm.spec
Assembler messages:
Error: can't open winmm_dll_t.s for reading: No such file or directory
/usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited with 
status 1
/usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
make: *** Waiting for unfinished jobs
tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
  ../wine-6.0.4/dlls/winmm/winmm.spec

Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for it's
temp file - these are not unique when building libwinmm.delay.a and
libwinmm.cross.a in parallel. (This can of course affect any dll wine is
building import libs for, winmm is just the one I happaned to get caught
on).

This is regression newly introduced in binutils 2.38 vs older versions
which used getpid() as the basis of their temp name. We just encountered
it as part of updating our CI for a winelib application from focal to
jammy, but it seems to have been discovered by others already: see
https://sourceware.org/bugzilla/show_bug.cgi?id=28885

There is an upstream fix on master (2.39) which is already backported to
the binutils-2_38 branch:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just be
a matter of cherry-picking. Hopefully the fact it's a regression from
impish->jammy and that upstream already backported it to 2.38 might make
this a candidate for jammy-updates?

** Affects: binutils-mingw-w64 (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/1971901

Title:
  dlltool uses non-unique temp filenames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils-mingw-w64/+bug/1971901/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Kevin Keijzer]

Isn't this a release blocker? It most definitely should be in my
opinion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Kevin Keijzer]

You can just remove 61-gdm.rules yes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969197] Re: 42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card

[Kevin Keijzer]

42.0-1ubuntu4 seems to block Wayland on *every* GPU, so it's not really
a good way to test NVIDIA support I would say.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969197

Title:
  42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969197/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969250] Re: gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4

[Kevin Keijzer]

*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243

** This bug has been marked a duplicate of bug 1969243
   gdm 42.0-1ubuntu4 no longer shows Wayland option

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969250

Title:
  gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969250/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969249] Re: all wayland options missing after apt update/upgrade

[Kevin Keijzer]

*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243

** This bug has been marked a duplicate of bug 1969243
   gdm 42.0-1ubuntu4 no longer shows Wayland option

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969249

Title:
  all wayland options missing after apt update/upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969249/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Kevin Keijzer]

When I outright delete /lib/udev/rules.d/61-gdm.rules it also works
normally again with 42.0-1ubuntu4, so the problem is with one of the
udev rules.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

[Kevin Keijzer]

For me, gdm3 42.0-1ubuntu4 breaks Wayland entirely. There is no option
to select a session left when logging in, and when I enter my password
and press enter I'm left in an X11 session.

I only have machines with Intel graphics.

Reverting to 42.0-1ubuntu2 makes it work normally again (defaults to
Wayland, with an option to select "Ubuntu on Xorg").

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968809

Title:
  Verify that the gdm cherry-picks are wanted for jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

[Kevin Keijzer]

For me 42.0-1ubuntu4 breaks Wayland as well on all my (Intel-only)
machines.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  No Wayland support on my NVIDA laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Kevin Keijzer]

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] [NEW] gdm 42.0-1ubuntu4 no longer shows Wayland option

[Kevin Keijzer]

Public bug reported:

After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no
longer shows any sessions in the bottom-right corner. When I log in, I
am dropped into an X11 session, with no way to switch to Wayland.

Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to
42.0-1ubuntu2 or 42.0-1ubuntu3 restores the option to select sessions
and defaults to Wayland again.

Looking at the changelog:

gdm3 (42.0-1ubuntu4) jammy; urgency=medium

  * Drop patch disabling Wayland on hybrid laptops using Nvidia's drivers.
It's not needed for Ubuntu 22.04 LTS (LP: #1968809)

 -- Jeremy Bicha   Thu, 14 Apr 2022 14:29:35 -0400


However, all my machines are i915-only.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968938] [NEW] Integrated webcam no longer working after latest system update (April 13, 2022).

[Kevin Scobey]

Public bug reported:

The 'Cheese' application states "no device found". This problem has
happened before. It seems like sometimes system updates fix the issue;
however, the most recent update seems to have re-broken the webcam.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: webcam (not installed)
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 13 19:39:41 2022
InstallationDate: Installed on 2022-02-16 (56 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xawtv
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968938

Title:
  Integrated webcam no longer working after latest system update (April
  13, 2022).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1968938/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968477] [NEW] Online accounts screen for Google, Microsoft and Flickr empty

[Kevin]

*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418

Public bug reported:

When I navigate to Settings / Online accounts and try to add a Google,
Microsoft or Flickr-account the pop-up screens remains blank. Other
accounts are fine.

I'm using IUbuntu 22.04 beta on Wayland.

I resolved the bug by swhitching to Xorg to add the accounts.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968477

Title:
  Online accounts screen for Google, Microsoft and Flickr empty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1968477/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location

[Kevin Dong]

For someone who is still struggling with this,
https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509 may help.

It seems that
sudo snap set system experimental.hidden-snap-folder=true
works and puts data in ~/.snap/data, but snap still creates an empty ~/snap on 
app startups.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575053

Title:
  Please move the "$HOME/snap" directory to a less obtrusive location

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966093] Re: Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in Bionic, Focal, and Impish

[Kevin Yeh]

Test results for 510 are available at 
https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing
Test results for 390 are available at 
https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing

No regression found for both.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966093

Title:
  Update to the 510.60.02 and the 390.147UDA NVIDIA driver series in
  Bionic, Focal, and Impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1966093/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1967947] Re: WiFi will not connect to open WiFi with complicated re-direct

[Kevin English]

You don't consider a lack of documentation of how to connect to a basic
hotel WiFi that every other operating system can connect to a short-coming
in your documentation or product?  I have been programming for fun and
profit since 1979.  I built BSD Unix systems from source in the 1980's.  I
am not new to this and I could not figure it out.  Clearly there is a
problem with your product and no workaround documented.  Please fix this
and do not so readily close this issue.

On Tue, Apr 5, 2022 at 3:30 PM Gunnar Hjalmarsson <
1967...@bugs.launchpad.net> wrote:

> Hi,
>
> It looks to me as if you are seeking support, not reporting a docs bug,
> so closing.
>
> Please use some support resource to seek support:
>
> https://ubuntu.com/support/community-support
>
> ** Changed in: ubuntu-docs (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1967947
>
> Title:
>   WiFi will not connect to open WiFi with complicated re-direct
>
> Status in ubuntu-docs package in Ubuntu:
>   Invalid
>
> Bug description:
>   I am at a Marriott Hotel and cannot connect to the open WiFi on
>   Ubuntu20.  The re-direct url they are using is complicated and the
>   usual tricks (which one does not have to use to connect using Windows,
>   Macs or Android) including http://, etc. do not work.
>
>   The redirect looks like (note the use of JavaScript to accomplish the
>   redirect also note the fact that I have typed this into a computer
>   that does have an internet connection):
>
>   
>   Redirecting...
>   
>   
>   
>   
>   
>   
>   document.location.href="
> https://bwiam.cust.blueprintrf.com:8001/index.php?zone=guest&redirurl=https%3A%2F%2F52.1.100.109%2F
> ;
>   
>   
>   
>
>   Even when I paste this curl-obtained content into "connect-
>   marriott.html" and then open in Chrome or FireFox, I do not get an
>   internet connection.  Chrome seems to make it a little farther than
>   FireFox as the title bar changes to:
>   "
> https://bwiam.cust.blueprintrf.com:8001/index.php?zone=guest=https%3A%2F%2F52.1.100.109%2F
> "
>
>   Ubuntu 20.04.04 LTS
>
>   network-manager 1.22.10-1ubuntu2.3
>
>   Expected to happen: seamlessly taken to network usage agreement page
>   on open Wi-Fi network.
>
>   What happened instead:  Wi-Fi connected, but cannot reach the
>   internet.  IPv4, IPv6 and DNS properly assigned via DCHP, just no
>   passage through gateway.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1967947/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967947

Title:
  WiFi will not connect to open WiFi with complicated re-direct

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1967947/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland

[Kevin Keijzer]

Copy/paste works for me, but drag/drop does not. I can't even rearrange
tabs or bookmarks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947210

Title:
  Firefox Snap can't copy or drag in Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967977] Re: Can't boot up after installing nvidia-driver-510 on Jammy beta

[Kevin Yeh]

** Description changed:

  [Reproduce step]
  1. install ubuntu-22.04 beta.
  2. run "apt update" and "ubuntu-driver install"
  3. reboot the system.
  
  [Expected result]
  
  system should boot into desktop.
  
  [Actual result]
  
  system stuck in boot stage and monitor keeps blinking.
  please see the attachment.
  
  [Info]
  
  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: Dell Precision 5760
  CID: 202103-28844
  kernel version: 5.15.0-25
+ 
+ [Additional info]
+ 
+ SWE helped me to do some test, and obverse that after installing jammy,
+ kernel version is 5.15.0-25, but when I use ubuntu-driver install the
+ nvidia-driver will also install 5.15.0.25 and won't install linux-
+ modules-extra.
+ 
+ This machine's output is using intel GPU, so without i915 there is no
+ GUI display.

** Description changed:

  [Reproduce step]
  1. install ubuntu-22.04 beta.
  2. run "apt update" and "ubuntu-driver install"
- 3. reboot the system.
+ 3. reboot the system. 
  
  [Expected result]
  
  system should boot into desktop.
  
  [Actual result]
  
  system stuck in boot stage and monitor keeps blinking.
  please see the attachment.
  
  [Info]
  
  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: Dell Precision 5760
  CID: 202103-28844
  kernel version: 5.15.0-25
  
  [Additional info]
  
  SWE helped me to do some test, and obverse that after installing jammy,
  kernel version is 5.15.0-25, but when I use ubuntu-driver install the
  nvidia-driver will also install 5.15.0.25 and won't install linux-
  modules-extra.
  
  This machine's output is using intel GPU, so without i915 there is no
  GUI display.

** Tags removed: jaiyi
** Tags added: jiayi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967977

Title:
  Can't boot up after installing nvidia-driver-510 on Jammy beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1967977/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967977] Re: Can't boot up after installing nvidia-driver-510 on Jammy beta

[Kevin Yeh]

** Description changed:

  [Reproduce step]
  1. install ubuntu-22.04 beta.
  2. run "apt update" and "ubuntu-driver install"
  3. reboot the system.
  
  [Expected result]
  
  system should boot into desktop.
  
  [Actual result]
  
  system stuck in boot stage and monitor keeps blinking.
  please see the attachment.
  
  [Info]
  
  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: Dell Precision 5760
  CID: 202103-28844
+ kernel version: 5.15.0-25

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967977

Title:
  Can't boot up after installing nvidia-driver-510 on Jammy beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1967977/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967977] [NEW] Can't boot up after installing nvidia-driver-510 on Jammy beta

[Kevin Yeh]

Public bug reported:

[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.

[Expected result]

system should boot into desktop.

[Actual result]

system stuck in boot stage and monitor keeps blinking.
please see the attachment.

[Info]

OS version: Ubuntu Jammy Jellyfish (development branch)
Device: Dell Precision 5760
CID: 202103-28844

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jaiyi jammy nvidia-driver-510 oem-priority

** Attachment added: "IMG_6022.mp4"
   
https://bugs.launchpad.net/bugs/1967977/+attachment/5577445/+files/IMG_6022.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967977

Title:
  Can't boot up after installing nvidia-driver-510 on Jammy beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1967977/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967947] [NEW] WiFi will not connect to open WiFi with complicated re-direct

[Kevin English]

Public bug reported:

I am at a Marriott Hotel and cannot connect to the open WiFi on
Ubuntu20.  The re-direct url they are using is complicated and the usual
tricks (which one does not have to use to connect using Windows, Macs or
Android) including http://, etc. do not work.

The redirect looks like (note the use of JavaScript to accomplish the
redirect also note the fact that I have typed this into a computer that
does have an internet connection):


Redirecting...






document.location.href="https://bwiam.cust.blueprintrf.com:8001/index.php?zone=guest&redirurl=https%3A%2F%2F52.1.100.109%2F;




Even when I paste this curl-obtained content into "connect-
marriott.html" and then open in Chrome or FireFox, I do not get an
internet connection.  Chrome seems to make it a little farther than
FireFox as the title bar changes to:
"https://bwiam.cust.blueprintrf.com:8001/index.php?zone=guest=https%3A%2F%2F52.1.100.109%2F;

Ubuntu 20.04.04 LTS

network-manager 1.22.10-1ubuntu2.3

Expected to happen: seamlessly taken to network usage agreement page on
open Wi-Fi network.

What happened instead:  Wi-Fi connected, but cannot reach the internet.
IPv4, IPv6 and DNS properly assigned via DCHP, just no passage through
gateway.

** Affects: ubuntu-docs (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/1967947

Title:
  WiFi will not connect to open WiFi with complicated re-direct

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1967947/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs