Public bug reported:
$ sudo capable-bpfcc
[sudo] password for ryan-lee:
In file included from /virtual/main.c:14:
In file included from include/uapi/linux/ptrace.h:183:
In file included from arch/x86/include/asm/ptrace.h:175:
In file included from arch/x86/include/asm/paravirt_types.h:12:
In
compilation error
Status in bpfcc package in Ubuntu:
New
Status in linux-hwe-6.11 package in Ubuntu:
New
Bug description:
$ sudo capable-bpfcc
[sudo] password for ryan-lee:
In file included from /virtual/main.c:14:
In file included from include/uapi/linux/ptrace.h:183:
In file included from
to
extract the following BUG trace from /var/log/kern.log after the fact:
2025-05-01T17:46:22.726963-07:00 ryan-lee-laptop-13-amd kernel: watchdog: BUG:
soft lockup - CPU#3 stuck for 336s! [Renderer:5725]
2025-05-01T17:46:22.726974-07:00 ryan-lee-laptop-13-amd kernel: Modules linked
in: vhost_net
The profile fix will be added as a patch to the version packaged in
Plucky, and should be uploaded into the queue by my EOD tomorrow.
** Tags added: sec-6054
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Summary changed:
- not able to deploy Plucky Puffin
+ unable to deploy Plucky Puffin due to AppArmor lsblk denials
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2092232
Title:
unabl
AIL
==
FAIL: test_sock_dgram (__main__.ApparmorUnixDomainConnect.test_sock_dgram)
Test mediation of file based SOCK_DGRAM connect
--
Traceback (most recent call last):
File "/home/ryan-lee/qrt-test-apparmo
Can confirm that the bugs targeted by the patches do not affect the
Linux 6.8.0-53 kernel in noble-proposed.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Summary changed:
- Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble
+ Backport some AppArmor complain-mode profile bugfixes from Oracular
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Description changed:
+ SRU Justification:
+
[Impact]
Backporting two AppArmor bugfixes (2de989ae726b "apparmor: allocate
xmatch for nullpdf inside aa_alloc_null" and 62bd5d5f2149 "apparmor:
properly handle cx/px lookup failure for complain") from the Ubuntu
Oracular kernel will fi
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2086210
Title:
Backport some AppArmor complain-mode profile bugfixes from Oracu
Public bug reported:
[Impact]
Backporting two AppArmor bugfixes (2de989ae726b "apparmor: allocate
xmatch for nullpdf inside aa_alloc_null" and 62bd5d5f2149 "apparmor:
properly handle cx/px lookup failure for complain") from the Ubuntu
Oracular kernel will fix incorrect behavior that occurs with t
This affects me as well. Seemingly with each type of bluetooth device
I've connected. Sony SRS-X11 bluetooth speaker, my JBL Bluetooth speaker
(not sure on the model), and my SkullCandy Hesh 2 Wireless Headphones.
Restarting the devices multiple times appears to randomly fix it. Then I
just make s
12 matches
Mail list logo
