Ubuntu
linux package

Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

Bug #2038567 reported by Philip Roche
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
New
Undecided
Unassigned
apparmor (Ubuntu)
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Critical
Unassigned
Ubuntu ubuntu-23.10
lxd (Ubuntu)
Triaged
High
Unassigned
snapd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following:

```
lxd init --auto --storage-backend dir
lxc launch ubuntu-daily:mantic mantic
lxc info mantic
lxc exec mantic -- cloud-init status --wait
```

The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result.

I have been able to replicate in a local VM

```
wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img
wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
chmod +x launch-qcow2-image-qemu.sh

./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img
cat <<EOF > "./reproducer.sh"
#!/bin/bash -eux
lxd init --auto --storage-backend dir
lxc launch ubuntu-daily:mantic mantic
lxc info mantic
lxc exec mantic -- cloud-init status --wait
EOF
chmod +x ./reproducer.sh
sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P 2222 ./reproducer.sh ubuntu@127.0.0.1:~/
sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p 2222 ubuntu@127.0.0.1 sudo apt-get update
sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p 2222 ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes
sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p 2222 ubuntu@127.0.0.1 ./reproducer.sh
```

The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this.

From my test VM

```
ubuntu@cloudimg:~$ uname --all
Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@cloudimg:~$ uname --kernel-release
6.5.0-7-generic
```

This is a regression in our test that will block 23.10 cloud image release next week.

Dimitri John Ledkov (xnox)
Changed in linux (Ubuntu):
milestone: none → ubuntu-23.10
importance: Undecided → Critical
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2038567

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Dimitri John Ledkov (xnox) wrote : Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage

Current suspects are out of date apparmor features in livecd-rootfs pending https://launchpad.net/ubuntu/+source/livecd-rootfs/23.10.55

kernel, apparmor, snapd, lxd, snapd again having fits about all of them because of:

......................................................................
Make snap "snapd" (20092) available to the system

2023-10-05T19:04:57Z INFO Requested daemon restart (snapd snap).

......................................................................
Copy snap "lxd" data

2023-10-05T19:04:56Z ERROR unlinkat /var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo: function not implemented

......................................................................
Run install hook of "lxd" snap if present

2023-10-05T19:04:55Z ERROR run hook "install": cannot read mount namespace identifier of pid 1: Permission denied

and also because of:

Oct 05 19:21:39 mantic-con-priv systemd[1]: snapd.service: Got notification message from PID 2560, but reception only permitted for main PID 2338
Oct 05 19:21:39 mantic-con-priv snapd[2338]: taskrunner.go:299: [change 7 "Setup snap \"snapd\" (20092) security profiles" task] failed: cannot reload udev rules: exit status 1
Oct 05 19:21:39 mantic-con-priv snapd[2338]: udev output:
Oct 05 19:21:39 mantic-con-priv snapd[2338]: Failed to send reload request: No such file or directory
Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Deactivated successfully.
Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Unit process 2559 (snapfuse) remains running after unit stopped.
Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading requested from client PID 2565 (unit snapd.service)...
Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading...
Oct 05 19:21:39 mantic-con-priv (sd-gens)[2568]: Read-only bind remount failed, ignoring: Permission denied

and because of:

Oct 05 19:20:58 cloudimg kernel: audit: type=1400 audit(1696533658.780:276): apparmor="DENIED" operation="mount" class="mount" info="failed type match" error=-13 profile="lxd-dominant-goldfish_</var/snap/lxd/common/lxd>" name="/snap/" pid=1940 comm="(sd-gens)" flags="ro, remount, bind"

but could be util-linux too

Revision history for this message
John Johansen (jjohansen) wrote :

apparmor side there are 2 immediate suspects.

1. kernel
0191e8433f76 UBUNTU: SAUCE: apparmor4.0.0: apparmor: Fix regression in mount mediation

2. userspace mount work to fix the mount CVE https://bugs.launchpad.net/apparmor/+bug/1597017

https://gitlab.com/apparmor/apparmor/-/merge_requests/1054

https://gitlab.com/apparmor/apparmor/-/merge_requests/333

I doubt #2 as this has been in the apparmor userspace in mantic since before FF.

Revision history for this message
John Chittum (jchittum) wrote :
Download full text (20.2 KiB)

livecd-rootfs 23.10.55 for mantic is currently migrating, and has apparmor changes as well (mounting different features in the build chroot). To help rule out some issues, I built a a qcow2 image and a squashfs for mantic using livecd-rootfs 23.10.55

Running the mantic host, and launching a released jammy container

# On the mantic host VM
journalctl -f -b -k

Oct 05 21:25:26 novel-ram kernel: kauditd_printk_skb: 220 callbacks suppressed
Oct 05 21:25:26 novel-ram kernel: audit: type=1400 audit(1696541126.968:6178): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=11660 comm="systemd" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.036:6179): apparmor="DENIED" operation="signal" class="signal" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=12656 comm="snapd" requested_mask="send" denied_mask="send" signal=urg peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.044:6180): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=11722 comm="systemd-journal" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.044:6181): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=11722 comm="systemd-journal" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.168:6182): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=12699 comm="systemctl" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.228:6183): apparmor="DENIED" operation="signal" class="signal" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=11660 comm="systemd" requested_mask="send" denied_mask="send" signal=exists peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.236:6184): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=12701 comm="systemctl" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.240:6185): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=12702 comm="systemctl" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"
Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.244:6186): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_...

Revision history for this message
John Johansen (jjohansen) wrote :

Oct 05 21:25:27 novel-ram kernel: audit: type=1400 audit(1696541127.240:6185): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-current-iguana_</var/snap/lxd/common/lxd>" pid=12702 comm="systemctl" requested_mask="read" denied_mask="read" peer="lxd-current-iguana_</var/snap/lxd/common/lxd>//&unconfined"

indicates 1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns - allow restricting unprivileged change_profile

Revision history for this message
John Johansen (jjohansen) wrote :

To test if 1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns - allow restricting unprivileged change_profile is the cause of the ptrace denials. You can disable it using

sudo bash -c "echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"

Revision history for this message
John Chittum (jchittum) wrote :
Download full text (4.6 KiB)

Did the following:

1. launched a new VM from the custom build

lxc launch mantic-20231005 --vm --device root,size=20GiB mantic-cust-vm

2. pushed squashfs and lxc metadata from same custom build

lxc file push build.output/livecd.ubuntu-cpc.squashfs mantic-cust-vm/root/
lxc file push vm/mantic-server-cloudimg-amd64-lxd.tar.xz mantic-cust-vm/root/

3. initialized lxd

lxd init --auto

3. imported into lxc

lxc image import ./mantic-server-cloudimg-amd64-lxd.tar.xz ./livecd.ubuntu-cpc.squashfs --alias mantic-cust-con

4. launched the container

lxc launch mantic-cust-con m-c-c

5. observed the DENIED ptrace

Oct 06 12:27:01 mantic-cust-vm kernel: audit: type=1400 audit(1696595221.386:113): apparmor="DENIED" operation="ptrace" class="ptrace" profile="lxd-m-c-c_</var/snap/lxd/common/lxd>" pid=2420 comm="systemd" requested_mask="read" denied_mask="read" peer="lxd-m-c-c_</var/snap/lxd/common/lxd>//&unconfined"

6. deleted the container

lxc stop m-c-c
lxc delete m-c-c

6. disabled apparmor_restrict_unprivileged_unconfined

sudo bash -c "echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"

7. launched container

lxc launch mantic-cust-con m-c-c

8. see different apparmor denied messages:

Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.722:905): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=4055 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"
Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.766:906): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=4048 comm="(polkitd)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"
Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.818:907): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-m-c-c_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=4071 comm="(ostnamed)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"
Oct 06 12:29:58 mantic-cust-vm kernel: audit: type=1400 audit(1696595398.874:908): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_</var/snap/lxd/common/lxd>//&:lxd-m-c-c_<var-snap-lxd-common-lxd>:unconfined" name="rsyslogd" pid=4062 comm="apparmor_parser"
Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.106:909): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_</var/snap/lxd/common/lxd>//&:lxd-m-c-c_<var-snap-lxd-common-lxd>:unconfined" name="/usr/lib/snapd/snap-confine" pid=4130 comm="apparmor_parser"
Oct 06 12:29:59 mantic-cust-vm kernel: audit: type=1400 audit(1696595399.106:910): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" label="lxd-m-c-c_</var/snap/lxd/common/lxd>//&:lxd-m-c-c_<var-snap-lxd-common-lxd>:unconfined" name="/usr/lib/snapd/snap-confine//mount-name...

Read more...

Revision history for this message
John Chittum (jchittum) wrote :
Download full text (3.1 KiB)

Repeating a bit with a Jammy container (hence new comment)

### PRE CONDITION

this is using the custom Mantic VM _and_ has apparmor_restrict_unprivileged_unconfined disabled

sudo bash -c "echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined"

1. start a jammy container

lxc launch ubuntu:jammy
Creating the instance
Instance name is: alive-bee
Starting alive-bee

2. see some apparmor denies in journal

Oct 06 12:32:57 mantic-cust-vm kernel: audit: type=1400 audit(1696595577.647:954): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-alive-bee_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=5421 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"
Oct 06 12:33:01 mantic-cust-vm kernel: kauditd_printk_skb: 20 callbacks suppressed
Oct 06 12:33:01 mantic-cust-vm kernel: audit: type=1400 audit(1696595581.539:975): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_<var-snap-lxd-common-lxd>" profile="snap.lxd.hook.install" name="/apparmor/.null" pid=5538 comm="snap-exec" requested_mask="wr" denied_mask="wr" fsuid=1000000 ouid=0
Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.771:976): apparmor="DENIED" operation="file_inherit" class="net" namespace="root//lxd-alive-bee_<var-snap-lxd-common-lxd>" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=5784 comm="snap-confine" family="netlink" sock_type="raw" protocol=15 requested_mask="send receive" denied_mask="send receive"
Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.779:977): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_<var-snap-lxd-common-lxd>" profile="snap.lxd.hook.configure" name="/apparmor/.null" pid=5784 comm="snap-exec" requested_mask="wr" denied_mask="wr" fsuid=1000000 ouid=0
Oct 06 12:33:03 mantic-cust-vm kernel: audit: type=1400 audit(1696595583.791:978): apparmor="DENIED" operation="file_inherit" class="file" namespace="root//lxd-alive-bee_<var-snap-lxd-common-lxd>" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" name="/apparmor/.null" pid=5784 comm="aa-exec" requested_mask="wr" denied_mask="wr" fsuid=1000000 ouid=0
Oct 06 12:33:04 mantic-cust-vm kernel: audit: type=1400 audit(1696595584.007:979): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-alive-bee_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=5933 comm="(imedated)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"

3. snap changes is Done

root@alive-bee:~# snap changes
ID Status Spawn Ready Summary
1 Done 9 days ago, at 02:11 UTC today at 12:33 UTC Initialize system state
2 Done today at 12:32 UTC today at 12:33 UTC Initialize device

4. cloud-init is done

root@alive-bee:~# cloud-init status
status: done

So using the latest released jammy container is also now launching "successfully." Unsure how the other apparmor things denies affect container performance. Running a quick spot check of my machine (Jammy) launch...

Read more...

Revision history for this message
John Chittum (jchittum) wrote :

on my machine (specs at the end) running Jammy as the host, and launching a Jammy container:

1. lxc launch ubuntu:jammy test-jammy-on-jammy

from journal

Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.223:51559): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=723735 comm="(d-logind)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"
Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.227:51560): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/tmp/" pid=723724 comm="(crub_all)" flags="rw, nosuid, remount, bind"
Oct 06 07:36:47 j5awry-sys76 kernel: audit: type=1400 audit(1696595807.239:51561): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="lxd-test-jammy-on-jammy_</var/snap/lxd/common/lxd>" name="/run/systemd/unit-root/proc/" pid=723750 comm="(ostnamed)" fstype="proc" srcname="proc" flags="rw, nosuid, nodev, noexec"

so i get the same `mount - failed flags match` that i see above, but not the `file-inherit` denies.

Revision history for this message
John Johansen (jjohansen) wrote :

Thanks John,

it has been confirmed that

1ea37b26d720 UBUNTU: SAUCE: apparmor4.0.0 [73/76]: userns - allow restricting unprivileged change_profile

is causing the issue. It has a sysctl to disable its behavior, but the sysctl can't be defaulted to off in the kernel. So to disable the sysctl, either
1. lxd needs to do it dynamically like it is doing for some other sysctls
2. we need the disable it at the system level
3. we revert the patch

For the time frame we are looking at, I recommend reverting the patch. Doing so will not materially affect the userns mediation feature. This patch is about closing off a confinement escape.

Dimitri John Ledkov (xnox)
summary: - Mantic 6.5.0-7 kernel causes regression in LXD container usage
+ Disable restricting unprivileged change_profile by default, due to LXD
+ latest/snap not yet compatible with this new apparmor feature
Changed in lxd (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in linux (Ubuntu):
status: Incomplete → Triaged
summary: Disable restricting unprivileged change_profile by default, due to LXD
- latest/snap not yet compatible with this new apparmor feature
+ latest/stable not yet compatible with this new apparmor feature
Revision history for this message
John Johansen (jjohansen) wrote :

Fix for the ptrace issue

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Fix under review https://lists.ubuntu.com/archives/kernel-team/2023-October/146015.html

Revision history for this message
Steve Langasek (vorlon) wrote :

marking this fix committed for linux, version 6.5.0-9.9 in mantic-proposed should contain the fix.

Changed in linux (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Philip Roche (philroche) wrote :

cloud minimized and non minimized images have now been tested with 6.5.0-9 kernel from -proposed and pass our lxd-start-stop test suite which was failing and which is the test suite which prompted this whole thread. +1

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.5.0-9.9

---------------
linux (6.5.0-9.9) mantic; urgency=medium

  * mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687)

  * update apparmor and LSM stacking patch set (LP: #2028253)
    - re-apply apparmor 4.0.0

  * Disable restricting unprivileged change_profile by default, due to LXD
    latest/stable not yet compatible with this new apparmor feature
    (LP: #2038567)
    - SAUCE: apparmor: Make apparmor_restrict_unprivileged_unconfined opt-in

 -- Andrea Righi <email address hidden> Fri, 06 Oct 2023 21:03:52 +0200

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0001-UBUNTU-SAUCE-no-up-apparmor-disable-1ea37b26d720-UBU.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apparmor (Ubuntu):
status: New → Confirmed
Changed in snapd (Ubuntu):
status: New → Confirmed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done-jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-linux-oem-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-jammy-linux-oem-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-jammy-linux-nvidia-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-6.5-v2 verification-needed-jammy-linux-nvidia-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency-hwe-6.5/6.5.0-14.14.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-done-jammy-linux-lowlatency-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-lowlatency-hwe-6.5' to 'verification-failed-jammy-linux-lowlatency-hwe-6.5'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-lowlatency-hwe-6.5-v2 verification-needed-jammy-linux-lowlatency-hwe-6.5
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.