This is occurring on the Kubuntu Focus NX Gen 2 as well.
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launch
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: Ubuntu Noble
Importance: Undecided
Status: New
** No longer affects: ubuntu
** No longer affects: Ubuntu Noble
** Tags added: kinetic
--
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/1971933
Title:
Unable to wake laptop using trackpad input
Status in linux package in Ubuntu:
Confirmed
Bug descr
Successfully replicated this bug on an HP Elitebook 8570p, 16 GB RAM,
Intel i5-3210M (if dmidecode is not deceiving me). I also cannot get the
touchpad to cause the system to wake from suspend even trying to enable
the wakeup files for all three of the USB controllers in my system. OS
is the latest
@chromastone I have experience with building software from source, and
have a laptop that replicates the problem. I'll give it a shot.
--
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/1971933
Sadly, I have to correct myself - I thought I had replicated the issue,
but it turns out my particular laptop doesn't use USB to attach the
mousepad. I tried plugging a USB mouse into my system while running a
"bad" kernel, and it was able to wake from suspend when I moved the
mouse. Also, it appea
I installed the same kernel that is in 20.04 onto a Lubuntu Kinetic
(22.10 alpha) installation, and the touchpad wake didn't work on my
laptop. I then tried USB wake on the kernel that's part of Kinetic, and
USB wake did work.
--
You received this bug notification because you are a member of Kern
I don't believe that my system ever was able to wake from the touchpad -
I seem to remember having to use the power button or open the lid in the
past. I thought maybe I just had something misconfigured back then, but
maybe not.
--
You received this bug notification because you are a member of Ke
You may be able to determine why the system is freezing by manually
editing the kernel command line in GRUB and removing the "quiet splash"
part of the command line. Then boot with this modified command line.
This will make the Linux kernel print debugging information to your
screen - this will tel
Thanks for taking the time to report this bug. However, Ubuntu only
supports kernels that are included in Ubuntu. Linux 5.19 is not
available in Ubuntu yet through any official channel, and the bug report
info itself states "The running kernel is not an Ubuntu kernel". Only
Ubuntu kernels are handl
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
Can you boot into an older kernel and see if it works right there? Also,
it might be interesting if you could plug in your hub into a USB 3 port,
try to use it, unplug it, then run "sudo dmesg > dmesg.txt" in a
terminal and attach the dmesg.txt file generated by doing this. That
will give us info a
Public bug reported:
Notice: I have not reproduced this bug myself, nor do I have the needed
setup to reproduce this bug. This is a bug report based on info provided
to me over IRC.
In order for CUDA compute to work, a kernel module "nvidia-uvm" is
necessary. This module *should* exist in the hea
strace of "clinfo -l" from the machine of the affected user.
** Attachment added: "clinfo_strace.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+attachment/5645158/+files/clinfo_strace.log
--
You received this bug notification because you are a member
** Description changed:
Notice: I have not reproduced this bug myself, nor do I have the needed
setup to reproduce this bug. This is a bug report based on info provided
to me over IRC.
- In order for CUDA compute to work, a kernel module "nvidia-uvm" is
- necessary. This module *should* e
I can verify that the latest version of Ubiquity from -proposed fixes
this problem - I booted Ubuntu Desktop 22.04.1, enabled -proposed on the
ISO, installed Ubiquity from -proposed, then did a ZFS+encryption
installation. Rebooted, logged in, "sudo apt update" behaves normally,
Firefox launches an
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1991936
When reporting bugs in the future please use apport by using 'ubuntu-
b
** Description changed:
This is *probably* the wrong package, but it's the best I can figure for
this, so here goes.
Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5,
- UEFI, no secure boot. Testing done in VirtualBox, BIOS, 4 GB RAM, 50 GB
- SSD. OS is Ubuntu Deskt
Installing the Kinetic Final image on a Secure Boot enabled laptop with
Broadcom WiFi resulted in the WiFi adapter not being able to be turned
on in the newly installed system. Doing "sudo modprobe wl" tells me "Key
was rejected by service".
--
You received this bug notification because you are a
Also, I was able to manually sign the Broadcom kernel module with
kmodsign and now it's accepted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725
Title:
fails to sign kernel module
Worthy of note, to get the driver to build so I could sign it, I had to
do "sudo dpkg-reconfigure bcmwl-kernel-source", then sign the resulting
wl.ko file. So it looks like the driver isn't even building in the first
place.
--
You received this bug notification because you are a member of Kernel
To workaround the issue by rebuilding and signing the driver manually:
1: Run "sudo dpkg-reconfigure bcmwl-kernel-source" to rebuild the driver.
2: Run "sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv
/var/lib/shim-signed/mok/MOK.der
/lib/modules/5.19.0-21-generic/updated/dkms/wl.ko" to s
At the time of this writing, this fix is still stuck in -proposed. This
makes the Lubuntu release notes wrong, as it makes it so that updating
the system prior to installing WiFi drivers is not enough, even though
it is documented as being enough. Considering that this fix very nearly
was hotfixed
** Description changed:
+ [Impact]
+
+ With the current state of the DKMS package, if a user attempts to
+ install any package that includes a third-party driver (Broadcom WiFi,
+ VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
+ driver with a MOK key will fail silently. T
** Description changed:
[Impact]
With the current state of the DKMS package, if a user attempts to
install any package that includes a third-party driver (Broadcom WiFi,
VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
driver with a MOK key will fail silently. T
** Description changed:
[Impact]
With the current state of the DKMS package, if a user attempts to
install any package that includes a third-party driver (Broadcom WiFi,
VirtualBox, v4l2loobpack, etc.), the process of signing the newly built
driver with a MOK key will fail silently. T
Tested on my HP Elitebook 8570p, with Secure Boot and Broadcom WiFi,
following the current test plan. All operations went as expected, WiFi
is working properly.
** Tags removed: verification-needed verification-needed-kinetic
** Tags added: verification-done verification-done-kinetic
--
You rece
Loading initial ramdisk... you don't happen to see an "Out of memory"
error when that happens, do you?
--
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/1990068
Title:
Kernel 5.19.0.15.15 c
Could you attach the output of the commands "lspci" and "lsusb" to your
report? This is almost without question a hardware-specific problem, so
knowing the hardware involved would be helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1981727
When reporting bugs in the future please use apport by using 'ubuntu-
b
Did you tweak /etc/default/grub by any chance?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1981907
Title:
Errors were encountered while processing: linux-
image-5.1
31 matches
Mail list logo
