** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1942133
Title:
Nvidia driver packages prevent suspend due
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
I have the same issue with an AMD EPYC 9334 32-core processor.
The Problem appears with an upgrade to Ubuntu 22.04.4., already with live
ubuntu from a bootstick. Ubuntu 22.04.3 works fine.
A fresh install (without updates on OS install) of 22.04.3 runs without
problems. After the 1st apt
This looks a lot like you have the no longer maintained anbox-modules
(https://github.com/anbox/anbox-modules) installed, at least according
to the dpkg output:
dkms autoinstall on 6.5.0-15-generic/x86_64 succeeded for anbox-ashmem
dkms autoinstall on 6.5.0-15-generic/x86_64 failed for
I might be missing something, but I don't think that's related to the
kernel?
** Also affects: ghc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I gave this another spin today with 6.5.0-17-generic #17~22.04.1 and the
LRM modules of the 535 driver (6.5.0-17.17~22.04.1+1 of linux-modules-
nvidia-535-server-generic-hwe-22.04) on our Altra system with 2x L4 GPUs
and the same problem exists as with the DKMS modules:
[ 39.437849] watchdog:
Verified that with linux-aws-edge 6.5.0.1012.12~22.04.1 the DKMS
installation via
$ sudo apt install -y nvidia-driver-535-server
on an AWS g5g.xlarge goes through the driver comes up fine.
Trying the same with linux-generic-hwe-22.04-edge 6.5.0-17-generic
#17~22.04.1 on an Ampere Altra with 2x
Trying the same with the linux-nvidia-hwe-22.04-edge kernel from
proposed linux-image-6.5.0-1011-nvidia wit the same NVIDIA driver
(535.154.05-0ubuntu0.22.04.1 of nvidia-utils-535-server) and loading
kernel driver and running nvidia-smi works fine without problems.
--
You received this bug
Verified that the issue does not exist with 535.154.05-0ubuntu0.22.04.1
of nvidia-utils-535-server on 6.2.0-1017-aws or 6.2.0-1018-aws of linux-
aws.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
I can reproduce the the same with the latest 535.154.05-0ubuntu0.22.04.1
on jammy with the 6.5 HWE kernel on an arm64 machine. The same happens
with the -server driver 535.154.05-0ubuntu0.22.04.1.
Reproducing is pretty simple:
1. Boot plain Ubuntu 24.04 with either HWE already installed or
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049352
Title:
Package BlueZ 5.72 for Noble
Status in bluez
This was missing a build dependency on python3-pygments (which is in
Main), I added it.
Testing well with my Beats Flex, YouTube Music with the Firefox Nightly
snap. I can adjust the latency offset with no issue, and blueman DTRT
with connecting and disconnecting. Popped open journalctl and
It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)
After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.
--
You received this bug notification because you are a member of
> Simon, ell already has a recent approved MIR LP: #1971738
Er, the binary packages in question don't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
Force pushing my local commits over, sorry not sorry. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.
I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.
Something's up with my
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:
```
$ check-mir
Checking support status of build dependencies...
* debhelper-compat does not exist (pure virtual?)
*
** Changed in: bluez (Ubuntu)
Status: Fix Released => In Progress
** Summary changed:
- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)
--
You received this bug notifi
Daniel, I don't want you to feel burned over this. That wiki page does
seem quite rational, and I appreciate that you linked it. I'm reading
some mixed feelings, so let me be clear: thank you for the work you
*are* able to put into this.
Both Gianfranco and I are Ubuntu Core Developers but are
> In other words, asking an Archive Admin to build binfmt-support on
i386.
I have stopped short of this so far because I'm entirely unsure if we
still need that build dependency in the first place. Debian doesn't have
it, and I'm not sure I see rationale on our end for it.
There is probably
Following the dependency chain through to the cause for the i386 builds,
binfmt-support should be added to the i386 allowlist. This may be a bug
in evolution-data-server in the case libebook-contacts-1.2-4 can build
without libphonenumber8-protobuf32 - for now, blanket-disabling that
dependency in
This is now blocking a Lubuntu feature goal. I tested this locally with
my bluetooth earbuds, and have been streaming audio with no problems.
Uploaded Gianfranco's packaging with some minor tweaks.
Please, we *need* to merge this from Debian *this* cycle. The Security
Team will NOT be happy when
Rik mentioned a common mistake that I've been trying harder to catch
(but didn't in this case, to my great frustration)...
If we're doing a merge and an orig tarball already exists in Debian,
always always ALWAYS grab that one instead of using uscan or finding the
tarball yourself. It breaks
The reason I essentially blindsponsored this was out of faith and
courtesy for the Desktop Team.
Lubuntu does similar things, but we have a merge party from Debian once
a cycle. If your response would be "we don't follow Debian," *I get it*,
but once or twice a cycle a merge should really be
Daniel, if you'd like to iterate on this (a debdiff for an ubuntu2
upload), it would be appreciated.
If you don't have the time, say the word, this looks like a simple fix.
...on everything but i386. What's up with that?
--
You received this bug notification because you are a member of Kernel
> 34174 lines in this case is not plausibly reviewable.
I typically use filterdiff to get the packaging changes, and review
specific source files as necessary (including copyright changes in the
diff, which can be important, even if you're just using a script for
it).
Thanks for your help here.
I very much dislike reviewing packages this way. For a package to be in
the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz.
I understand that it's a new upstream release, but that does not excuse
the need for a debdiff, even if you *also* include these files.
I'm uploading
@Lucas, you mentioned GitHub Actions but those use the Azure flavor
(https://github.com/actions/runner-
images/blob/ubuntu22/20231126.1/images/ubuntu/Ubuntu2204-Readme.md#ubuntu-2204).
That flavor also lacks the CONFIG_DMI_SYSFS however.
The Azure flavor seems to also be lacking the config on
** Changed in: linux-kvm (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2045561
Title:
linux-kvm: please enable CONFIG_DMI_SYSFS for
This shouldn't be an issue in Mantic and Noble as the linux-kvm flavor
was replaced by linux-virtual which has the normal config set.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
I have the same problem, this bug has been around for quite some time as
it seems. Is there no fix available?
I have this problem with multiple machines, but I don't even find any
useful information about the copymods package aside from this bugreport
and the related posts.
--
You received this
Laptop is a ASUS TUF A15 (2023) model nr:FA507XI
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036258
Title:
Bluetooth is active but not detecting any devices
Status
Public bug reported:
Fastboot is disable
bluetooth is actve and no devices are detected. Just "searching for devices"
What I'm expecting: the bluetooth to detect devices and connect to them
What I got: no devices are detected and just searching for devices
Description:Ubuntu 22.04.3 LTS
In the above tests from Christian, it's interesting to note the MemTotal
shrink by ~22MiB. Is this due to the higher NR_CPUS alone?
--
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/2032933
Sorry, there were some potential regressions that needed investigating,
and we're still waiting on a few benchmark results for bug 1999551.
Other than that the overall autopkgtest results are in good shape, so
assuming the benchmarks show what we want them to, this shouldn't be
long.
--
You
Nowadays, btrfs snapshots can only be taken by the owner of the source
subvol. https://btrfs.readthedocs.io/en/latest/ch-mount-
options.html#btrfs-specific-mount-options:
> Historically, any user could create a snapshot even if he was not
owner of the source subvolume, the subvolume deletion has
** Changed in: glibc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2011421
Title:
TDX azure instances crash during boot because of
Hi,
This seems reasonable to me, especially since it also seems like it
would be needed to address xnox's review in bug 2012412. Uploaded, and
unsubscribed ubuntu-sponsors.
I also took the liberty to modify a bit the testplan to make it obvious
to bystanders (e.g. me) how to reproduce the issue.
** Description changed:
[SRU Justification]
Impact:
Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG
which prevent it from building if a specific configuration is enabled/disabled.
This feature was released for kinetic but not for jammy.
This backports the
** Changed in: dkms (Ubuntu)
Status: New => Fix Released
** Also affects: dkms (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: dkms (Ubuntu Kinetic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Marking this as affecting the kernel, with glibc as Invalid, as it
doesn't seem like something we can do much about on our end.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu Focal)
Status: New => Invalid
** Changed in: glibc
** Changed in: glibc (Ubuntu Jammy)
Status: Incomplete => In Progress
** Also affects: glibc (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu Lunar)
Sorry, my bad for the status, we discussed this offline with joalif.
I'm not planning on fixing this in Kinetic as the affected platform is
more of an LTS user, as I understand, and the kinetic EOL is
approaching. Given the time it can take for a glibc SRU to go through
-proposed even when
Public bug reported:
updating using apt
HW is an HP Elitebook 840
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion:
The issue doesn't show when using the 525 driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2012908
Title:
nvidia driver 515 fails to boot on kernel 6.2
Status in
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657759/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657756/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657758/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657757/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657755/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657754/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657753/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657752/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657749/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657751/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657750/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657747/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657743/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657745/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657746/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657748/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2012908/+attachment/5657744/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Public bug reported:
I just updated my Lunar install, which brought me the 6.2 kernel, and it
failed to start, stalling after enumerating my USB devices, until
something times out with a message saying that the udev event queue
failed to be drained.
When attempting to move on to the normal
@Matthew, that's a good question. Since you are using 22.04 with the
5.15 kernel, you'll need to wait for the 5.15.0-68.75 kernel to land in
-updates as it is still in -proposed ATM.
The zfs-linux user space tools, shouldn't need an update for this bug
but even if it did, the LXD snap bundles
R9 290 here, HDMI audio output disappeared after updating to 5.19.0-35,
loaded 5.19.0-32 and it's working again.
--
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
** Changed in: thermald (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: thermald (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
I'm seeing the exact same error on 450-server, 470-server, 510-server
and 515-server in the glibc autopkgtests
https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lunar/amd64/n/nvidia-graphics-
drivers-450-server/20230217_153300_3ba46@/log.gz
There's also other failures on 470, 510 and 515
A user on #ubuntu-server reported being affected by this bug as well but
on Focal with the HWE kernel 5.15. I'm not sure how to do verification
in such case? Should they manually pull the .deb from jammy-proposed or
will there be a HWE kernel built for focal-proposed?
--
You received this bug
Also seeing on Jammy 5.15.0.58.56 with a similar setup (xen, lacp bond,
bridges using openvswitch). Initially tried downgrading vswitch to
2.17.0 from 2.17.3 which didn't make any difference. Both versions of
vswitch are working on the original kernel 5.15.0-25 as well as
5.15.0-33.
--
You
Public bug reported:
hello, i use DellLatitude E5400 which has in-built bluetooth but cant turn on
and i cant search devices .
when i open bluetooth manager it tells me the "connection to bluez failed"
i have tried all commands but has failed .
when i check bluetooth status it show
I can confirm the issue on an *old* GCP instance:
$ mount | grep devtmp
devtmpfs on /dev type devtmpfs
(rw,relatime,size=490260k,nr_inodes=122565,mode=755,inode64)
$ cat /etc/cloud/build.info
build_name: server
serial: 20200902
$ uname -a
Linux mx1 5.15.0-1018-gcp #24~20.04.1-Ubuntu SMP Mon
Looking at the attached journal logs, there's a lot of Yubikey service
activity between the lid closed and lid opened lines. Do you use a
third-party package to handle your Yubikey, by any chance?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
Anbox Cloud is affected by this too. We used shiftfs by default until
our 1.14 release in May 2022. According to the metrics we have there are
still a few users around with the 1.13 release which enables shiftfs on
ZFS.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
This package blocks the glibc 2.36 transition due to breakage of
libsanitizer that isn't observed on later versions of LLVM. Plus, it has
already been removed from Debian testing due to this bug:
https://bugs.debian.org/1012193
❯ reverse-depends src:llvm-toolchain-12
@saltf1sh, thanks for reporting this, however, the 5.13 kernel is no
longer supported (since July 2022). Are you able to reproduce the
problem on a kernel version that's still supported (like 5.4 or 5.15)?
--
You received this bug notification because you are a member of Kernel
Packages, which
I just started noticing this same error/bug when using
5.15.0-41-generic.
I am able still to boot using this kernel, however it is very slow and
when it does boot the screen resolution is stuck at 800x600 and the
Nvidia drivers do not work (according to nvidia-smi).
On the other hand if i boot
Marking as "invalid" as it's not a bug in nvidia-graphics-drivers-510
but an external NVIDIA component.
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
See https://github.com/rust-lang/llvm-project/pull/121
This is required for rustc 1.59, which in turn is required for Firefox
100 and related tunderbird.
** Affects: llvm-toolchain-13 (Ubuntu)
Importance: Undecided
Status: New
** Affects: llvm-toolchain-13
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1010150:
Source: llvm-toolchain-13
Version: 1:13.0.1-3
Severity: normal
Tags: patch upstream
Control: affects + rustc
Dear Maintainer,
Please backport upstream https://reviews.llvm.org/D115098
It is needed for rust 1.59,
And the *release* version of Jammy has a 5.15 kernel that boots on the
machine in question, so I've managed a successful upgrade, and this
doesn't seem to be a problem for me any more.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
On a fresh arm64 system I failed to start LXD containers with NVIDIA
GPUs attached. The error message LXD / nvidia-container-cli fails with
is:
lxc t0 20220506112123.475 DEBUGconf - conf.c:run_buffer:310 - Script exec
/snap/lxd/current/lxc/hooks/nvidia produced output:
Update: linux-image-5.14.0-1034-oem appeared in my normal apt upgrade
today and has booted successfully, so perhaps whatever the problem was
has been fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu.
Looks like the missing bits were re-added in Bionic HWE kernel version
5.4.0-108.122~18.04.1. This allowed confirming with the recently
released -109 version:
root@bionic-vm:~# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@bionic-vm:~# uname -a
Linux bionic-vm
Identified this issue in Focal starting with the update to 105 kernel.
Constant soft lockups then freezing when kauditd/auditd exceeded backlog
limit. Due to DoD requirements, all systems set to audit=1 in kernel
boot options and have stringent list of syscalls/binaries/files that are
audited.
** Description changed:
# Overview
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
Public bug reported:
After leaving the system for a while and it turning the screen off the
kernel crashes in the NVIDIA driver with the following:
Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address:
0070
Apr 06 17:24:56 kore kernel: #PF: supervisor read
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
Attaching logs fails when `apport-collect 1968027` wants to authorized
with my LP with an "Not allowed error".
** Description changed:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000
Public bug reported:
When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps
within a container:
root@anbox0:~# cat /proc/self/maps
55930e60-55930e608000 r-xp 00:51 14509
This also happens with the kernel in xubuntu-22.04-beta-desktop-
amd64.iso, so it will block me upgrading that machine to Jammy when it's
released.
Is there anything I can do to help? I'm not familiar with debugging
kernel drivers, but I'm a competent general developer, and I'm prepared
to put in
Same problem on the same machine on ubuntu-derived Pop!_OS 21.10. Also
persists in Windows after reboot. Problem is temporarily fixable by
switching the trackpad off in bios, saving, and switching it on again.
--
You received this bug notification because you are a member of Kernel
Packages,
I don't really know what information I should be reporting about my
hardware. My first guess is that the output of 'lspci -v' relating to
the video device might be useful, so here it is:
00:02.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) (prog-
if 00 [VGA controller])
** Attachment added: "dmesg.success.5.11.0-46-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574752/+files/dmesg.success.5.11.0-46-generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "dmesg.nomodeset.5.14.0-1031-oem.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574751/+files/dmesg.nomodeset.5.14.0-1031-oem.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
been working fine for me (and supported the network device on my
reasonably recent PC, which 20.04's default kernel didn't). But the 5.13
and 5.14 kernels all hang on boot.
If I edit the GRUB boot commands
It turns out the Bionic verification failed because the required changes
went into 5.4.0-106.120~18.04.1 but were dropped from
5.4.0-107.121~18.04.1. Presumably because the later address multiple
CVEs.
--
You received this bug notification because you are a member of Kernel
Packages, which is
5.13.0-38.43 has the fix but 5.13.0-39.44 doesn't, presumably because
-39 includes urgent security fixes.
--
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/1966499
Title:
Recent 5.13
Bionic (HWE) verification *failure*:
root@bionic-vm:~# uname -a
Linux bionic-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
root@bionic-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.4.0-105-generic 5.4.0-105.119~18.04.1
** Summary changed:
- Tourchpad not working
+ Touchpad not working
--
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/1966107
Title:
Touchpad not working
Status in linux package in
This seems to be fixed upstream by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5a6248c0a22352f09ea041665d3bd3e18f6f872c
which is marked `Cc: stable `.
I'd expect this commit to eventually percolate to Ubuntu kernels, right?
If so, should this bug be kept open until
1 - 100 of 1063 matches
Mail list logo
