Public bug reported:
During ISO testing of the plucky server image, with the 6.14 kernel, the
image failed to boot on the Pi Zero 2W, the 3A+, the 3B+, and the 2B
(all from SD card). Boot fails at the initramfs attempting to find the
rootfs (by label). Listing /dev there are no /dev/mmcblk* nodes
Okay, this looks fixed to me, many thanks!
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2103738
Title:
mes
Public bug reported:
I've been testing the 6.14 kernel on an Ubuntu installation upgraded
from oracular to plucky. The system *appears* to be running very nicely,
but I've just noticed there's a very large number of oops reports in
dmesg. Looking at the systemd journal they all seem to be paired w
Any update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2100340
Title:
PCI/ACS: Fix 'pci=config_acs=' parameter
Status in linux-nvidia package in Ubuntu:
Incomplete
Bug de
This is a request to backport a fix from upstream commit that is
accepted by maintainer
here is the patchwork link:
https://patchwork.kernel.org/project/linux-pci/patch/20250207030338.456887-1-td...@nvidia.com/
Here is the repo where this patch is queued:
https://kernel.googlesource.com/pub/sc
Moving to linux-raspi as the affected kernel flavour
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
--
You received this bug
Public bug reported:
Linux kernel upstream Commit 47c8846a49ba ("PCI: Extend ACS
configurability") introduced bugs that fail to configure ACS ctrl to
the value specified by the kernel parameter. Essentially there are two
bugs:
1) When ACS is configured for multiple PCI devices using 'config_acs
do reboot
* systemctl status
* Verify status is "running" and not "degraded"
For Dave (not including full instructions for the sake of brevity, but
if anyone else wants to try this I can provide instructions on
request):
* Build 24.04.2 image locally with propose
systemctl status
* Verify status is "running" and not "degraded"
For Dave (not including full instructions for the sake of brevity, but
if anyone else wants to try this I can provide instructions on
request):
* Build 24.04.2 image locally with proposed pocket
* Check
stall -t noble-proposed ubuntu-desktop-minimal
+ * sudo apt autoremove
+ * Check that protection-domain-mapper is removed as no longer required
+ * sudo reboot
+ * systemctl status
+ * Verify status is "running" and not "degraded"
+
+ For Dave (not including full instructions for the
Doh! Knew I'd forgotten something in the whirlwind of meetings today.
Just a mo...
** Summary changed:
- Fails on (and should be removed from) raspi desktop
+ [SRU] Fails on (and should be removed from) raspi desktop
--
You received this bug notification because you are a member of Kernel
Packa
** Changed in: ubuntu-meta (Ubuntu Noble)
Milestone: None => ubuntu-24.04.2
** Changed in: ubuntu-meta (Ubuntu Noble)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-meta (Ubuntu Noble)
Importance: Undecided => High
--
You received this bug not
Bah, keep forgetting I need to go update ubuntu-meta. Also qrtr and
protection-domain-mapper aren't really the targets of these fixes;
marking those invalid.
** Changed in: qrtr (Ubuntu)
Status: Confirmed => Invalid
** Changed in: protection-domain-mapper (Ubuntu)
Status: Confirmed
These changes are now merged for both oracular and noble. I'll wait for
a rebuild on the noble images tomorrow, re-check those, and then mark
this fix released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.l
Moving to Fix Released as it that seems to be the state of this.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/17086
Public bug reported:
When attempting to boot the Ubuntu 24.04 image on an eMMC variant of the
CM5, attached to a CM4 I/O carrier board, the boot hangs fairly early
on, just presumably at the point it attempts to mount the "real" root.
The following error message is repeated on the console:
[ 14
Oh, I actually did this back in ... erm ... mantic maybe (the git blame
isn't here because ubuntu-raspi-settings got split out as a separate
source package in noble, but this change was definitely before then):
https://git.launchpad.net/ubuntu/+source/ubuntu-raspi-
settings/tree/10-raspi-eth0.link
I'm going to add linux-raspi as affected here given this is (at least
partially) down to a linux-raspi configuration difference. Kernel team:
is there a reason landlock is disabled in the Pi kernel? Seems to work
happily on a Pi 5, but perhaps there was some incompatibility with
earlier models?
**
That's a different issue, LP: #2063365, which only started occurring
after the recent wifi firmware bump
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861338
Title:
RPI4 wifi un
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be removed from) raspi
Public bug reported:
While attempting to play music as part of the ISO tests for the release,
while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321
player used by the tests (which has never worked *well* on the older
models, but at least worked) failed with:
[0.029s] ubuntu@mis
Public bug reported:
The protection-domain-mapper package (and qrtr-tools) are both installed
by default on the Ubuntu Desktop for Raspberry Pi images, thanks to
their inclusion in the desktop-minimal seed for arm64. However, there's
no hardware that they target on these platforms, and the result
** Changed in: linux-raspi (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2038924
Title:
No alsa sound cards on Pi 5
Status i
I haven't managed to reproduce this on several systems (pi4 booting from
USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can
come up with a firm reproduction case.
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
Public bug reported:
The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the
kernel starts booting under noble (I hope this is only on noble; I only
just noticed this during ISO testing and it's quite possible I missed it
on earlier revisions...).
Specifically, on the 2W (which only
This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.
** Changed in: linux-firmware-raspi (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-f
Public bug reported:
When shutting down Ubuntu noble desktop on my Pi 5, I consistently see
the following kernel errors briefly flash by before the machine shuts
down:
kernel: spl: loading out-of-tree module taints kernel.
kernel: zfs: module license 'CDDL' taints kernel.
kernel: Disabling
I believe this is also "fixed" (or rather wasn't an issue) with the
noble kernel; at least testing the current noble desktop beta image from
an SD card shows an NVMe drive attached to a pimoroni base. I'll mark
this as Fix Released; please feel free to re-open if this re-appears on
the noble images
Public bug reported:
Came across something bizarre when investigating the audio situation
with server on the Pi 5 (LP: #2038924). Moving the server images to use
the KMS overlay solves the situation, and would be preferable as it
would eliminate another difference between server and desktop images
Public bug reported:
First reported on the Raspberry Pi forums
(https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since
confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT,
which is basically the same board) works happily under RaspiOS on the Pi
5, but not Ubuntu 23
Indeed -- the Pi isn't compatible with our generic arm64 kernel, so
we'll be sticking with the flavour limit for the time being, and this
does actually reduce our delta with Debian. I've got a couple of other
patches to incorporate into f-k this week, so I'm going to sponsor this
as part of a large
Any updates here?
--
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/2033348
Title:
Wireless: Update RTL8852BE wifi driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
rpi-imager currently has no facility to encrypt the image it flashes to
the storage on the Pi (and making such a facility generic enough that it
would fit all potentially interested distros is a daunting task to say
the least), so this isn't valid for rpi-imager.
I *did* add some initial steps tow
Ah, I remember this old one. We discussed this with upstream and found
the issue was that for that specific firmware, the clm-blob was included
in the firmware blob itself, but the code that loaded firmware blobs
still warned that it couldn't find the external file. That code was
eventually cleaned
At this point, we've had all the necessary firmware blobs for numerous
releases and I'm reasonably convinced that the remaining AC wifi issues
are largely related to incorrect regulatory domain, because we don't
provide a friendly way of setting this on desktop (see LP: #1951586 for
more on this).
** Changed in: linux-raspi (Ubuntu)
Importance: Undecided => High
** Also affects: linux-raspi (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Mantic)
Status: New => Confirmed
** Changed in: linux-raspi (Ubuntu Mantic)
Importance: Undec
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
Stat
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037059
Title:
array index out of bounds in brcmfmac driver
S
Public bug reported:
During ISO testing of the final mantic images on the Pi 5, no ALSA cards
are listed under /proc/asound/cards and (predictably) none of the ALSA
utilities are able to output audio. Is this a DT related issue again?
(reminiscent of LP: #1991254)
** Affects: linux-raspi (Ubuntu)
The following changes since commit
294374341c622e5c2ffd15712cadabe0dd9865f1:
UBUNTU: Ubuntu-5.15.0-83.92 (2023-08-14 11:05:34 +0200)
are available in the Git repository at:
https://github.com/tdavenvidia/ubuntu_kernel_jammy/pull/3
for you to fetch changes up to 11ef7073533e332ce5ec96ef9aa3f
Public bug reported:
DAMBUF is backported using the two series of patches:
First, we need the series of 3 patches at:
https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/
- dma-buf: Fix pin callback comment
- RDMA/umem: Allow pinned dmabuf umem usage
- RDMA/efa: Add support
The rpiboot package can be skipped for now; according to upstream the
updated package won't be ready at release. The separate bug LP: #2032178
will track updates if/when I can get the uploaded.
** No longer affects: rpiboot (Ubuntu)
--
You received this bug notification because you are a member
Public bug reported:
Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B
with 4GB or 8GB of RAM (the only two I've tested thus far) causes the
following to show up in dmesg:
[ 10.384021]
[ 10
Public bug reported:
I formatted a new Flash Drive and the process hung. So I unplugged the
drive. Disks App crashed when I did.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.
Public bug reported:
Would it be possible to move the "nbd" kernel module from linux-modules-
extra-raspi into linux-modules-extra? This would enable NBD-based
network boot (which has certain advantages over the NFS-based network
boot more traditional in the Pi world, such as permitting services t
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/2033348
Title:
Wireless: Update RTL8852BE wifi driver
Status in linux
@kobako The full thread of the problem can be seen in
https://lore.kernel.org/linux-
wireless/20230421015357.13940-1-pks...@realtek.com/T/#u
This bug report is mainly a preemptive request to get the latest stable
driver on.
A few error logs below.
* Note: these were not gathered in an Ubuntu im
Submitted request to update driver/firmware to latest v0.29 in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2002601
Public bug reported:
Firmware 0.27 was added in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there
has been an update submitted by Realtek which resolves crash issues of
the driver related to DMA.
New firmware file is up in kernel:
https://git.kernel.org/pub/scm/linux/kernel/g
** Tags removed: rls-ll-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027847
Title:
Bump minimum /boot size in ubuntu-release-upgrader
Thanks. I see the same behavior (i.e. no warning) with the patch.
I will add the patch 'commit f5451547b8310868f5b5acff7cd4aa7c0267edb3' to
linux-nvidia-6.2 then..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubunt
Can you try the below commit from linus's "linux" tree and see if the
warning goes away?
commit f5451547b8310868f5b5acff7cd4aa7c0267edb3
Author: Thomas Gleixner
Date: Tue Feb 7 15:16:53 2023 +0100
mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early
--
You received this bug
yeah I suspect that.. there are couple of irq patches in the 6.2.0-1004-nvidia
could be the cause..
I will update here shortly!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/20
** Changed in: linux-nvidia-6.2 (Ubuntu)
Assignee: (unassigned) => Tushar Dave (tdavenvidia)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2026891
Title:
linux-nvi
As stated above, Ubuntu on ZFS failed to boot after an earlier version
upgrade.
The Jonathon F PPA
(https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) resolved this
problem.
If Ubuntu patches zfs to be compatible, why does this PPA exist?
--
You received this bug notification because you are
Public bug reported:
In the lunar release of linux-raspi, despite the boot configuration
enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0
and /dev/i2c-1 devices are missing (they are present in jammy and
kinetic). These are the I2C interfaces present on the GPIO header (and
Was able to purge the non-working 6.2 kernels with --
sudo dpkg --purge
and then list the 6.2 kernels listed
after finding all the 6.2 linux kernels with
sudo dpkg -l | grep "Linux kernel"
Have not yet tried installing anything beyond 5.19 yet.
--
You received this bug notification because y
Same issue here though I don't have any displaylink drivers installed.
Seemed that my upgrade install was interrupted perhaps and no amount of
installing a new kernel either by download and with dpkg -i or using
Ubuntu's mainline yield any success. 6.2 Kernel still shows up when I
reboot and is th
Under lunar's 6.2 kernel the situation is the same as kinetic's 5.19
kernel: display output works, but rotation is ignored and touchscreen
input doesn't work.
** Also affects: linux-raspi (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification becau
As a workaround until the fix lands (and is subsequently back-ported to
the jammy HWE kernel), Koba's test-kernel in comment 36 works nicely.
However, please note that the test kernel is not signed and will require
that you disable secure boot to try it (if it's enabled on your
machine), which may
@Koba I can confirm the 5.19.9000-37-generic kernel from comment 36
fixes the issue for me as well, congratulations!
I agree the 60Hz audio issue ought to be a separate report, but until
that appears a quick side note to this one: my refresh rate is 60Hz and
I have no issues with my audio but I wo
** Description changed:
CLARIFICATION: Just to avoid any confusion for those coming to this bug
report; the "Jammy: invalid" status above does *not* mean that this bug
doesn't affect jammy -- it does, and the kernel team is aware of this.
All it reflects is that the fix has to go into the
@duxeu To fill in a bit of background here, the AMD folks were emailed
in the background and are of the same opinion.
Personally, I'm not sure the bisect *did* identify that as the commit,
but unfortunately bisection isn't an entirely straight-forward process
when dealing with packages that have a
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
>From lspci.txt it appears your GPU is a Radeon RX 550, so this is almost
certainly a duplicate of LP: #2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 & -37
@koba I've tried each of the kernels in comment 25 and I'm afraid it
rather refutes the theory that fdcc4c22b is the culprit:
The latest vanilla kernel (#1) is "good"; HDMI audio works happily. That
suggests (although not conclusively) that fdcc4c22b isn't the culprit as
it presumably includes tha
** Description changed:
+ CLARIFICATION: Just to avoid any confusion for those coming to this bug
+ report; the "Jammy: invalid" status above does *not* mean that this bug
+ doesn't affect jammy -- it does, and the kernel team is aware of this.
+ All it reflects is that the fix has to go into the
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 & -37 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
I'm *reasonably* certain this is a duplicate of LP: #2009136 as that
covers kernel 5.19.0-35. I don't think there *is* a 5.15.0-35, and the
"reversion to 5.15.0-67" (which is the current 5.15 release) also
s
@Timo ah I see, sorry for the noise!
--
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/2009136
Title:
No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Status in linux package in U
@bpl indeed -- I asked Timo if the targeting should be adjusted in
comment 9 as I wasn't sure if the kernel team wanted to track this
separately over in the hwe package, but given this bug was moved from
that package this one I may as well just add jammy to the affected set.
** Also affects: linux
Errr, let me try that again from root so it's actually got the caps
output!
** Attachment added: "lspci.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653114/+files/lspci.out
--
You received this bug notification because you are a member of Kernel
Packages, wh
@kobako the 5.15.9003-68-generic kernel in comment 16 is "good"; HDMI
audio detected and working happily. I'm attaching the requested lspci
output.
** Attachment added: "lspci.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653113/+files/lspci.out
--
You receiv
@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad"
--
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/2009136
Title:
No HDMI audio under 5.19.0-35 (regression from -32)
Sta
@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also
"bad" (same symptoms, same dmesg lines as seen in the -35 kernel)
--
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/20091
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
My apologies; I'm going to mark this as a duplicate of LP: #2009136 even
though that bug was reported later as it's very likely the same issue
(AMD-based card with HDMI audio output), and that seems to be wh
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad"
(no HDMI audio present, same dmesg lines as seen in the -35 kernel)
--
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/20
Hi Timo, this also affects jammy -- should I add that to the targeting,
or is that to be handled separately?
--
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/2009136
Title:
No HDMI audio u
Looking through the growing list of duplicates, everyone has an AMD GPU
so this is almost certainly an issue in that driver. The list of cards
affected so far:
* RX570 (mine)
* RX6700 XT (from LP: #2009275)
* RX580 (from LP: #2009276)
* RX6600 (from LP: #2009542)
I'm happy to post any additional
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Attachment added: "pactl-list-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5
** Attachment added: "pactl-list-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5
** Attachment added: "dmesg-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubu
** Attachment added: "dmesg-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubu
Public bug reported:
After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
the kernel, I found my HDMI audio output device had disappeared.
Reverting to the -32 release caused it to appear again (hence why I'm
filing the bug against the kernel rather than pulseaudio). I'm attaching
.
===
Date: Tue, 24 Mar 2015 10:54:37 -0700
From: Dave Taht
To: Joseph Salisbury
Cc: Kernel Team
command ran
** Package changed: linux (Ubuntu) => spectacle (Ubuntu)
--
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/170
Title:
Plasma notification setting not honoured
Status in s
apport information
** Tags added: apport-collected jammy
** Description changed:
My notification pop-up timeout is set for 1second.
Taking a screenshot with spectacle I expect the pop up to be removed after 1
second.
The pop up stays for 5 seconds which is the default for the notification
Public bug reported:
My notification pop-up timeout is set for 1second.
Taking a screenshot with spectacle I expect the pop up to be removed after 1
second.
The pop up stays for 5 seconds which is the default for the notification.
reboot/restart of KDE/Plasma makes no difference
System Informati
@vorlon, I just found this ticket, and would like to report that my Intel AX211
wifi card no longer connects via 6ghz with the linux-oem-22.04b. It was
working fine with the 5.15 kernel. I suspect regulatory compliance to be the
issue as all of the 6ghz channels show disabled when running
$ su
Is there actually an issue in gcc-12 here? Looking at the patch Juerg
linked to, it appears to be a kernel issue only?
--
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/1993120
Title:
armhf
ce: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu Lunar)
Assignee: (unassigned) => Dave Jones
So where are we on this folks?
--
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/1991975
Title:
dev file system is mounted without nosuid or noexec
Status in linux package in Ubuntu:
Con
Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality. I do
think the nosuid flag does still provide some benefit even if we decide
not to inclu
In case anyone is curious conversation is on-going on the kernel-team mailing
list
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
@juliank, is this an aws system? If not there's a good chance that you
are using an initramfs to mount the filesystems. That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.
--
You received this bug notification because you are a member of Kernel
P
Here is a workaround for this issue in case anyone finds this in the
future.
Copy remount_dev.service to /etc/systemd/system
sudo chown root:root /etc/systemd/system/remount_dev.service
sudo systemctl daemon-reload
sudo systemctl enable remount_dev.service
Still I think the kernel patch should be
** Information type changed from Private Security to Public Security
** Summary changed:
- dev file system is mounted without nosuid
+ dev file system is mounted without nosuid or noexec
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Description changed:
+ [ SRU TEMPLATE ]
+ [ Impact ]
+
+ * nosuid, and noexec bits are not set on /dev
+ * This has the potential for nefarious actors to use this as an avenue for
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more
discussion around this.
+ *
1 - 100 of 916 matches
Mail list logo
