The issue persists also with the 5.8 and 5.15 kernels that are
installable on Focal.
It actually looks like the machine wakes up, but Xorg does not. I was
able to shut down the machine gracefully by pressing the power button.
Looking at the log files after rebooting, it looks like there is a
prob
Same issues here:
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb v: 0.9
bus-ID: 3-4:2 chip-ID: 0489:e0e4 class-ID: e001 serial:
Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: no
address
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.
https://b
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 directly
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023650
Title:
Add microphone support of the front
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 directly
Actually it sounds like that log message is benign:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1106
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2025460
Title:
night ligh
Please uninstall the extension 'toggle-night-li...@cansozbir.github.io'
because it seems to be broken, then see if night light works using the
normal controls in Settings.
If it still doesn't work after that then it sounds like the problem is:
gnome-shell[1269]: Failed to set CRTC gamma: drmModeC
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => In
** Tags added: kern-7321
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2025675
Title:
Realtek Bluetooth Radio ID 6655:8771 cannot connect after update
Status in linux-firmware
Please run 'apport-collect 2025675' on this system.
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2025675
This issue can be found on J-azure-6.2 AMD64 as well.
** Tags added: 6.2
** Tags added: sru-20230515
** Summary changed:
- test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 AMD64
+ test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
Does the issue still present on mainline kernel?
--
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/1956177
Title:
battery not detected by ACPI
Status in linux package in Ubuntu:
Confirme
Should be fixed by next OEM kernel 6.1 release.
--
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 change screen brightness in ubuntu desktop
Status
@superm1, do you have the symptoms, reproducing steps? We'll need them
to justify the need to SRU firmware changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427
Title:
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New
Removing packages from mantic:
linux-signed-kvm 6.2.0-1003.3 in mantic
linux-image-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
Comment: kvm flavor merged into virtual; LP: #2025686
1 package successfully removed.
** Changed in: linux-signed-kvm (Ubuntu Mantic)
Statu
Removing packages from mantic:
linux-kvm 6.2.0-1003.3 in mantic
linux-buildinfo-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
linux-headers-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
linux-image-unsigned-6.2.0-1003-kvm 6.2.0-1003.3 in mantic am
Removing packages from mantic:
linux-meta-kvm 6.2.0.1003.4 in mantic
Comment: Obsolete source package subsumed by linux-meta; LP: #2025686
1 package successfully removed.
** Changed in: linux-meta-kvm (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notifi
Removing packages from mantic:
linux-allwinner 5.19.0-1009.9 in mantic
linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic
amd64
linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic
arm64
linux-allwinner-headers-5.19.0-1009 5.
Removing packages from mantic:
linux-meta-allwinner 5.19.0.1009.9 in mantic
Comment: Obsolete source package subsumed by linux-riscv; LP: #2025398
1 package successfully removed.
** Changed in: linux-meta-allwinner (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received t
My problems only occur when running a KDE Wayland session, not with KDE
X11 sessions.
--
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/1959525
Title:
Occasional no display output on 6900XT
** Also affects: linux-allwinner (Ubuntu Mantic)
Importance: Undecided
Status: Triaged
** Also affects: linux-meta-allwinner (Ubuntu Mantic)
Importance: Undecided
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Public bug reported:
RM superseded by generic
generic kernel now supports initrd-less boot on VIRTIO SCSI devices.
all other features were also ported to the generic kernel and/or livecd-rootfs.
please remove kvm kernel from mantic.
transitional packages will remain in linux-meta until after next
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wireless-regdb (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.la
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wireless-regdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpa
I did an check and can confirm that the chromium-browser as installed by
the usual 22.04 package is *NOT* affected.
But Google chrome well as google-chrome-beta installed by the PPA
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
do show the bug.
--
You received this bug not
Got a similar issue with Asus K513.
It happens every time I suspend with a type-C dock connected (the laptop
does not support the HDMI out on type-C, so I'm only using it as a USB
3.0 hub). The power indicator starts blinking with a strange pattern:
0.1 sec of light every two seconds. And I have t
Today apt want's to update my nvidia driver from
510.108.03-0ubuntu0.22.04.1 to 525.125.06-0ubuntu0.22.04.1
Based on the bad experience of the unwanted kernel update I'm not sure
whether I should take the risk.
Hopefully one of the maintainers reacts to this bug soon and gives more
advice about h
For the record, I personally ran into this specific issue with some
moderate use of a ZFS pool:
[Mon Jul 3 10:07:56 2023] RIP: 0010:__list_del_entry_valid+0x0/0x70
[Mon Jul 3 10:07:56 2023] Code: 39 c0 0f 85 89 cf 4b 00 48 39 d7 0f 84 69 cf
4b 00 4c 39 c7 0f 84 60 cf 4b 00 b8 01 00 00 00 c3 cc
** Package changed: ubuntu => linux-nvidia (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2025616
Title:
kernel Firmware Bug: TSC ADJUST differs failures during suspend
Canonical has provided a signature for an exact set of bytes in the .ko
file. The packaging needs to relink the object files into that exact set
of bytes on the target system for the signature to match. The relinking
is required for license compliance AIUI. binutils does the linking. If
you use a d
Public bug reported:
After updating my system this morning, about six hours ago, my Bluetooth
radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001 Device 002: ID
6655:8771 Realtek Bluetooth Radio) stopped working entirely.
ubuntu-version:
Ubuntu 22.04.2 LTS
linux-firmware:
Installed: 202203
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
https://
Still figuring out potential upstream bluetooth firmware regression in
https://lore.kernel.org/linux-firmware/20230703134824.7795b277@smeagol/
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: oem-priority originate-from-2024125 somerville
--
You received this bug no
Public bug reported:
WIFI Driver:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/drivers/net/wireless/realtek/rtw89
BT Driver:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=8b1d66b50437b65ef109f3227
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.laun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.laun
Public bug reported:
Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571
This is specifically when a system advertises support for PMF, but
doesn't support static power slider for any reason.
Upstream fix in
https://github.com/torvalds/linux/commit/146b6f6855e7656e83299106065952
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2025538
Title:
Unrequested k
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2017980
Title:
FATAL:credentia
The problem seems to come from a wrong suggestion of Nvidia proprietary
driver packages, where Ubuntu logic (likely from the “ubuntu-drivers-
common” package) hints towards drivers that depend on a kernel stack
that’s not installed, which triggers those kernel installations as well,
because depende
*** This bug is a duplicate of bug 1959525 ***
https://bugs.launchpad.net/bugs/1959525
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
Public bug reported:
Hello,
OpenZFS 2.2.0-RC1 has been released a couple of days ago.
Could you update the Mantic package to this version?
I'm personally asking because I'm running into a bug which has been
fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c, which is
the version current
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Jammy)
** No longer affects: nvidia-graphi
1. You are not supposed to confirm your own bug reports
2. You are not running Ubuntu, but Linux Mint.
Support for Linux Mint can be found at https://www.linuxmint.com/contactus.php
and https://forums.linuxmint.com/
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Confirmed => I
Same Here, impossible to update using APt or ubuntu update:
sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libnvidia-cfg
Public bug reported:
https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of-
updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588
https://forums.linuxmint.com/viewtopic.php?p=2344294
timeline 10:36 - 10:39
switch to TTY not helped, SSH not tested
After emergency
Kerjes thanks a lot for the info
Worked for me as well!
--
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/2025560
Title:
lubuntu does not boot after upgrade
Status in linux package in Ubu
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+attachment/5683537/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.laun
It's now working again without (known) action (update?). I attach the
files anyway in case the problem is back in the future.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+attachment/5683536/+files/lspci.txt
--
You received this bug n
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.14
---
linux-firmware (20220329.git681281e4-0ubuntu3.14) jammy; urgency=medium
* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
(LP: #1968604)
- rtl_bt: Update RTL8761B BT
This bug was fixed in the package linux-firmware -
20220923.gitf09bebf3-0ubuntu1.7
---
linux-firmware (20220923.gitf09bebf3-0ubuntu1.7) kinetic; urgency=medium
* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
(LP: #1968604)
- rtl_bt: Update RTL8761B BT
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
This bug was fixed in the package linux-firmware -
20230323.gitbcdcfbcf-0ubuntu1.2
---
linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium
* rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
(LP: #1968604)
- rtl_bt: Update RTL8761B BT U
That sucks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1921536
Title:
"modprobe: ERROR: could not insert 'nvidia': Key was rejected by
service" due to binutils m
In oem-6.1 6.1.0-1016.16 through stable updates bug 2021945.
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.l
And we're back to the original problem. I'm out of ideas sorry, and
would just be googling at this stage.
Jul 03 16:45:29 khteh-p17-2i gdm3[3111]: modprobe: ERROR: could not insert
'nvidia': Key was rejected by service
Jul 03 16:45:29 khteh-p17-2i kernel: Loading of module with unavailable key is
This just happened to me on Ubuntu 22.04.2 LTS. After installing updates
in the last weeks, and a reboot today, I'm suddenly running kernel
linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency. I guess I'm
lucky that the machine still booted!
When trying to remove the kernel, it tries to install
/var/lib/dkms/nvidia/535.54.03/6.2.0-24-generic/x86_64/log/make.log
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683512/+files/make.log
--
You received this bug notification because you are a member of Kernel
Pac
journalctl -b0
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683511/+files/journal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-
After rebooting, if it still doesn't work then please run:
journalctl -b0 > journal.txt
find /var/lib/dkms/nvidia -name make.log
and attach both files here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in
Done but still doesn't work.
$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver.
Make sure that the latest NVIDIA driver is installed and running.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
@guiverc, added output from "apport-collect 2025560".
The question is why "aptdaemon role='role-upgrade-system'
sender=':1.69'" picks up unsupported kernels as "22.04.2 LTS (Jammy
Jellyfish)" only supports kernel v.5.19-x according to
https://launchpad.net/ubuntu/+source/linux, why?
I managed to
@Raof,
your understandings are correct.
Then, "motion=1" isn't supported currently.
For apct, the motion variant may not exist in each entries.
so extra policy rules maybe hit.
if these cause the problem,
1. the apct have the incorrect rules and table needs correction.
2. need fully support in
** Summary changed:
- Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission
denied (13)
+ FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-met
** Description changed:
[Summary]
in-Motion condition doesn't work with adaptive performance policy
[Fix]
This patch fix the issue,
cc0890a59725) Always match motion = 0
[Test cases]
1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X
2. run the thermald applied the fix.
Or more generally install whichever one is listed as "tested".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1921536
Title:
"modprobe: ERROR: could not insert 'nvidia
YES: nvidia-driver-535
NO: nvidia-driver-535-open
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1921536
Title:
"modprobe: ERROR: could not insert 'nvidia': Key was re
No, there are 2 535 drivers listed in the "Additional Drivers" gnome
app. Which one should I install?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1921536
Title:
"mo
Public bug reported:
BlueZ release 5.68 is now available:
https://mirrors.edge.kernel.org/pub/linux/bluetooth/
** Affects: bluez (Ubuntu)
Importance: Wishlist
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: mantic udeng-894
** Tags added: udeng-894
** Changed
Sounds like:
> Xwayland does not provide a suitable mechanism for our driver to synchronize
> application
> rendering with presentation, which can cause visual corruption in some
> circumstances.
from
http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/wayland-
issues.html
** A
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Fix Released
** Changed in: nvidia-graphics-drivers-530 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this
I also had this bug. The workaround posted in November helped fix it for
me.
--
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/1859592
Title:
Bluetooth unavailable after updates - Reading I
Thanks for the bug report. Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Package changed: gnome-shell (Ubuntu) => linux-hwe-5.15 (Ubuntu)
--
You received this
Removing chromium-browser as affected package because this wasn't
actually verified on Chromium. If it is verified on Chromium, please
revert that.
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
> Amd why are ALL the options disabled for me?
It thinks you installed a driver manually from nvidia.com, which Ubuntu
doesn't support. Try this:
/usr/bin/nvidia-installer --uninstall
# From
http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/installdriver.html
Also uninstal
nvidia-driver-535 should be best.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1921536
Title:
"modprobe: ERROR: could not insert 'nvidia': Key was rejected by
serv
Which one of the two should I install?
** Attachment added: "Screenshot from 2023-07-03 14-52-48.png"
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683488/+files/Screenshot%20from%202023-07-03%2014-52-48.png
--
You received this bug notification
81 matches
Mail list logo
