[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Exact same behavior, and exact same fix. On 5.64-0ubuntu1.1, the
connection attempt results in a PIN prompt ( doesn't work). It
*does* still work over USB.
Per OP, I tried downgrading to 5.64-0ubuntu1 *immediately* corrected the
problem.
--
You received this bug notification because you
I just got prompted to update to 23.04 / Lunar - is that safe to attempt
while suffering the effects of this bug? Alternatively, can I try an
update to 23.10 / Mantic?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Public bug reported:
I have MangoPi Pro, which is a single board computer with a D1 RISC-V
cpu. I am using the Nezha image from here:
https://cdimage.ubuntu.com/releases/23.10/release/ubuntu-23.10-preinstalled-
server-riscv64+nezha.img.xz
This works very well (albeit slow considering the
Forgive my ignorance on this, but how can I help move this forward?
--
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/2016040
Title:
Creating bcache backing device using a Dell Ent NVMe
Public bug reported:
[Impact]
Intel Trust Domain Extensions (TDX) protects guest VMs from malicious host and
certain physical attacks.
Linux 6.7 introduced the TDX support for the host to run confidential VMs (TDX
guests).
[Test case]
We should probably define with Intel a proper test case
I'm having this bug as well. It is a bug cause with current version
Dualshock 3 just doesn't connect, even if you do enter the PIN
code.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Oh. To the question of whether there was a systemd change in this
window: yes absolutely, because this is the point at which the riscv64
builders moved from lgw manually-operated qemu with a 20.04 guest image,
to bos03 openstack-operated qemu with a 22.04 guest image.
Which is also why we've
On Sat, Dec 09, 2023 at 05:13:28PM -, Andy Whitcroft wrote:
> Was there any systemd/udev change in this timeframe? As the device
> files are very much connected to those.
My understanding is that these devices are supposed to be created directly
by the kernel on devtmpfs and NOT via udev,
Was there any systemd/udev change in this timeframe? As the device
files are very much connected to those.
--
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/2045586
Title:
livecd-rootfs
My original post said it was a kernel issue, so no idea why it was
logged against konsole.
I've changed it.
** Package changed: konsole (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in
Are there plans for a patch for kernel 6.2?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2041495
Title:
Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
You have been subscribed to a public bug:
Having upgraded from Jammy to Kinetic I now find that fstrim no longer
works on SSD drives in some external USB enclosures.
The issue is caused by the provisioning_mode status for these now being
set to disabled, whereas previously they were set to
The "scsi: core: ata: Do no try to probe for CDL on old drives" commit included
in this update should fix this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=217914
** Bug watch added: Linux Kernel Bug Tracker #217914
https://bugzilla.kernel.org/show_bug.cgi?id=217914
--
You received
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
Interestingly, the information about nomodeset cannot be found in the
[Ubuntu Wiki about kernel
debugging](https://wiki.ubuntu.com/Kernel/Debugging).
I had to resort to
[AskUbuntu](https://askubuntu.com/questions/207175/what-does-nomodeset-
do), which refers to an [Ubuntu Forum
With kernel 5.15.0-84-generic and previous, setting nomodeset was not
necessary.
--
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/2043203
Title:
Kernel 5.15.0-86 causes LightDM to
Yes! I tried with kernel 5.15.0-91-generic now, and the system boots
with LigthDM remaining on screen. Thanks!
--
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/2043203
Title:
Kernel
19 matches
Mail list logo
