(In reply to Luiz Von Dentz from comment #16)
> Can you guys try with the following change:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-
> 1-luiz.de...@gmail.com/
I have the same issue and applied this patch to my kernel, but it seems
to have broken the
Public bug reported:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
Still reproducible with 6.5.0-26-generic
kdump won't generate any dump or send anything over ssh.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
Kernel Oops -
The issue is likely somewhere in
https://salsa.debian.org/ci-
team/autopkgtest/-/blob/933bd29bb628bad8a66b877298ebcfaeb4aa41a6/runner/autopkgtest#L348
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => 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/2058477
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761623/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
mounting with
-o cache=loose
seems to circumvent the issue for me.
This is probably not safe if multiple machines are accessing the same files.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
It looks like installation of this update may have resolved the issue on
our systems:
ethtool/jammy-updates 1:5.16-1ubuntu0.1
I believe that release was put together as a result of this bug report,
which may or may not be a duplicate:
I just went back to another machine that doesn't have "ethtool/jammy-
updates 1:5.16-1ubuntu0.1" installed yet. It also produces correct
output when I run "sudo ethtool --module-info eno3" now.
I think it's likely that this issue was fixed by some previous release
and I just didn't notice it
Public bug reported:
NVIDIA patches Mar 22 - April 5, 2024.
NVIDIA tracking details
soc/tegra: fuse: Remove security_mode fuse from keepout list
https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228
soc/tegra: fuse: Update Tegra234 nvmem keepout list
** Description changed:
We want to enable tracks for different versions of the out-of-tree
modules. For now we only have R36.3, so create the meta packages for
that version.
These meta packages include:
- * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and
Public bug reported:
There are a number of configuration options that were set in the 5.15.
and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was
created those config options were not brought forward. This patch set
brings them into the 6.8 kernel.
** Affects: linux-nvidia (Ubuntu)
This bug is still present in Ubuntu 22.04.4 LTS with current patches.
I'm glad to have found the workaround mentioned above.
--
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/1981141
Title:
Public bug reported:
I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since
about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D
controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)).
Yesterday, I had an ubuntu update, so I use driver 535 now, the
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 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-bluefield' to
This bug was fixed in the package mutter - 46.0-1ubuntu6
---
mutter (46.0-1ubuntu6) noble; urgency=medium
* Rebuild for CVE-2024-3094
-- Jeremy Bícha Sun, 31 Mar 2024 10:24:22 -0400
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
** CVE added:
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 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-bluefield' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 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-bluefield' to
I have a suspicion the root cause of the white screen could be fixed in
BIOS 3.05.
https://community.frame.work/t/framework-
laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276
Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS
upgrade?
--
You received this
Public bug reported:
The problem only exist with (all conditions must be true)
- Ubuntu 22.04.4 LTS
- kernel >= 6.5.0-14 (6.5.0-14 ist the oldes 6.5 I found in the repos)
- mounted share from a Fritz-Box (works on mount from another linux PC)
If I use kernel 6.2.0-39 (that's the newest Kernel
Public bug reported:
no bluetooth detected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
Probably nvidia.ko is missing a call to
drm_aperture_remove_conflicting_pci_framebuffers()
--
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/2060268
Title:
Phantom 46" monitor (simpledrm)
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761624/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fantastic, thanks for re-testing and confirming!
Closing this ticket as Fix Released.
** Changed in: ubuntu-power-systems
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761626/+files/acpidump.txt
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Phantom 46" monitor after
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 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-bluefield' to
Public bug reported:
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still controlled
by simpledrm, while Nvidia uses /dev/dri/card1.
---
ProblemType:
I was able to successfully install and boot PowerVM partitions - Power9
and Power10 with the latest kernel `6.8.0-20.20` (today's image -
20240405) :
POWER10 LPAR:
```
patricia@noble-a5:~$ cat /var/log/installer/media-info
Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el
This bug was fixed in the package gcc-12 - 12.3.0-17ubuntu1
---
gcc-12 (12.3.0-17ubuntu1) noble; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-12 (12.3.0-17) unstable; urgency=medium
* Fix typo in distro_defaults spec.
gcc-12
** Description changed:
+ [Impact]
+
+ Commit: "smb: move client and server files to common directory fs/smb" moved
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was
not updated, it still contains the old path. This means that the cifs.ko module
cannot be loaded
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
32 matches
Mail list logo
