You have an unsupported DKMS modules installed. Remove it and retry the
upgrade:
$ dkms remove nvidia/520.61.05 --all
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
You have an unsupported DKMS module installed. Remove it and retry the
upgrade:
# dkms remove anbox-binder/1 --all
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Building module:
Cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1
'make' -j4 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.0-20-generic
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/6.2.0-20-generic/build LD=/usr/bin/ld.bfd
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-restricted-modules-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
I plugged in external monitor and set the settings to external display.
But even after removing HDMI cable, it not showing content in laptop
screen (black screen). I have restarted system twice.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package:
** Tags removed: need-duplicate-check
--
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/2024346
Title:
package linux-image-6.2.0-23-generic 6.2.0-23.23 failed to
install/upgrade:
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.2.0-23-generic all
KERNEL_SRC=/lib/modules/6.2.0-23-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for anbox-binder: 1 not found
Error! Bad return status for module build on kernel: 6.2.0-23-generic
@BlindB0 (blindb0)
HI ,
I Installed fresh Ubuntu and again camera not working I followed#67
your steps as previous but this time showing me
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1)
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002968
Title:
Fix flicker display problem on some panels
My experience so far lines up with the above: 148 good, 150 bad, 152
good.
--
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/2018960
Title:
linux-image-5.4.0-149-generic
** Description changed:
[Impact]
- eDP power on flow enhancement to speed up kernel boot time
+ eDP power on flow enhancement to speed up kernel boot time.
+ This commit is recommended by Intel.
[Fix]
- The commit from 6.2-rc1 is recommended by Intel
+ The commit below is from 6.2-rc1
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Also affects: linux-oem-6.1 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee:
--- Comment From boris.m...@de.ibm.com 2023-06-19 06:27 EDT---
Big thank you to everybody who has contributed and helped to make this
important feature available for s390x.
With this being released to Jammy, we can close the bug / LP entry.
Changing the status to CLOSED.
--
You
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
@andrianovigor
Hi Igor !
the
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/uvc_driver.c
at line 2687 has ALREADY supported the 0408:4033 Quanta model.
Which uvc_drriver.c did you download ?
Did you launch the bash file ? It directly download all
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
** Changed in: ubuntu-kernel-tests
Status: In Progress => 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/2015440
Title:
fib_tests.sh in ubuntu_kernel_selftests was
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
I've verified a Jammy guest as follows:
1. Reproduced the problem with kernel 5.15.0-75-generic:
https://pastebin.ubuntu.com/p/844W5SzjR8/
2. As a workaround removed:
0x0003
3. Installed kernel from -proposed:
root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
Verified a Focal guest as follows:
1. Reproduced the problem with kernel 5.4.0-152-generic:
https://pastebin.ubuntu.com/p/Cgj6j4Prbc/
2. As a workaround removed:
0x0003
3. Installed kernel from -proposed:
root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1015.15
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux/5.15.0-77.84 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-25.25 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.4.0-154.171 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-focal' to 'verification-done-focal'. If the problem
still exists, change
Can you please boot with kernel parameter
"intel_pmc_core.warn_on_s0ix_failures=1", suspend overnight, resume the
system and attach dmesg here? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Adding acpi_backlight=nvidia_wmi_ec worked for me, on 23.04 using
proprietary nvidia drivers.
--
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/1976473
Title:
[Dell G15 5515] Unable to
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2015956
Title:
selftest: fib_tests: Always
** Tags removed: need-duplicate-check
--
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/2024395
Title:
BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
Status in linux package in
This change was made by a bot.
** 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/2024395
Title:
BUG: Bad rss-counter state
Public bug reported:
all i know is what is in the summary above
BUG: Bad rss-counter state mm:f4f57600 idx:1 val:1
ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
Remote Debian server on 5.10.0-23-amd64 x86_64 kernel after running
memory-hungry job.
Swap enabled, 16GB of ram, Intel Xeon W3550.
System hangs without any warning.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This doesn't seem to have been mentioned yet, but so far it's got sound
working for me (the SSDT patch answer):
https://askubuntu.com/questions/1467417/no-sound-from-speakers-on-asus-
zenbook-ux3402za-q409za
Direct link to patch:
https://github.com/thor2002ro/asus_zenbook_ux3402za/tree/main/Sound
** Description changed:
[Impact]
During the S3 stress test, the system sometimes hangs when resuming. This is
due to the SCSI rescan task being unable to acquire the mutex lock during the
resumption from S3. The mutex lock has already been acquired by EH and is
waiting for the device to be
71 matches
Mail list logo
