I just checked the chromium bug tracker: the link is valid, but it is
flagged as "Only users with EditIssue permission or issue reporter may
view.".
I guess it's caused by being created from an uploaded crash report. Probably
due to privacy considerations as the crash dump might contain private
Coming back to this report here: as expected but now confirmed: when I
boot the old kernel everything is working normally.
So the cause is *confirmed* to be the different/upgraded kernel that was
installed without my request (as described in
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
Public bug reported:
lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
This morning upgrade installed a bunch of new kernels which made my computer
unbootable.
Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work.
>From /var/log/apt/history.log:
St
Public bug reported:
nvidia manager seems to not recognize my GT660
resolution is like xorg driver 1024 x 768
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-470 470.199.02-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.19.0-1028.29~22.04.1-lowlatency 5.19.17
Uname: Linux 5.
Same issue here - after an upgrade to my Ubuntu 22.04.2 LTS installation
(not lubuntu), the system either does not boot anymore, or it can load
older kernels but without the proprietary nvidia driver loaded.
--
You received this bug notification because you are a member of Kernel
Packages, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-nvidia-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-nvidia-5.19 in Ubuntu.
htt
i also have/had this problem. ThinkPad P14s 3rd gen (21J6) with AMD
Ryzen 7 pro 6850u with Radeon Graphics. Ubuntu 22.04. Kernel was
5.19.0-46-generic.
Those solutions did not work:
- no "Sleep Mode" option in my BIOS
- did not manage to successfully access the Lenovo advanced BIOS menu to switch
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 2025560
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Public bug reported:
Notebook with "Network controller: MEDIATEK Corp. MT7921 802.11ax PCI
Express Wireless Network Adapter" have no WiFi after upgrading firmware
package
# journalctl --since "2 days ago" | grep mt7921e
Before Update:
Jul 02 16:27:57 hogwarts kernel: mt7921e :01:00.0: enabli
--
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:
Chrome crashes with FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Status in chromiu
I'm seeing the same thing running Slack.
---
[** ~]$ /bin/slack
[64844:0702/180844.731816:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)
---
This started after the latest 'apt update/upgrade'
The 2nd monitor connected to the laptop this
Is Windows installed on this computer?
--
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/2025568
Title:
After update to 20230629.gitee91452d-0ubuntu1 no WiFi/WLAN with MT7921
Stat
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
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/2025568
Title:
After update to 20230629.gitee91452d-0ubuntu1
No, this is a Linux only system, but something else clashed. More
details:
System was tested with kernel mainline 6.3.7 and 6.4.0
Reverting the patch files => Didn't helped (rmmod/modprobe and reboot)
Tried original Ubuntu 6.2.0 kernel and this worked again.
Removed mainline kernels and reinstall
Public bug reported:
When installing Broadcom Wireless driver (bcmwl-kernel-source) the
package does not properly force the updating of the kernel module
blacklist, and as a result the system still loads a conflicting driver
(bcma). Users need to manually call the command:
sudo update-initram
the same. The second monitor does not work, chrome does not start. what
do you advise to do? wait or reinstall the system?
--
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/20
When booting just select an older kernel - and hope that the maintainers
are quickly cleaning the mess
--
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:
Chro
yes i tried that. but even with the old kernel, the second monitor did
not work. but chrome was running.
--
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:
Ch
** Attachment added: "IMG_20230703_003916.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683463/+files/IMG_20230703_003916.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Same problem here with lubuntu 22.04.
Last night I did the updates
Unfortunately, as of today I cannot boot either in the new 5.19
lowlatency nvidia or 5.15.0.76 generic or anywhere else
I can enter safe mode, but do not know what to do there
When trying to boot in 5.19 the attached img appears
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/2025560
More than "occasionally". It's now "usually" :(
** Summary changed:
- Crash in ucsi_acpi_async_write [ucsi_acpi] occasionally prevents booting
+ Crash in ucsi_acpi_async_write [ucsi_acpi] prevents booting
** Summary changed:
- Crash in ucsi_acpi_async_write [ucsi_acpi] prevents booting
+ Crash
https://bugs.launchpad.net/ubuntu/+bug/2025585
--
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/2023946
Title:
Nvidia 530 kernel driver is not installed/built
Status in dkms package in Ubu
Verified on both Pink Sardine and RPL DMIC devices for jammy and lunar,
the mic-mute LED works correctly now.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-lunar
** Tags added: verification-done verification-done-jammy verification-done-lunar
** Changed in: o
Was away for a week and today things break again after `apt update &&
apt upgrade` !
$ dpkg -l | grep -i nvidia
ii libaccinj64-11.8:amd64 11.8.87~11.8.0-3
amd64NVIDIA ACCINJ Library (64-bit)
ii libcu++-dev
Thanks for the bug report. It sounds like the HDMI connection isn't
getting the full display info (sometimes). Next time it happens, please
run:
journalctl -b0 > journal.txt
and attach the resulting text file here. It might be helpful to do the
same also when the bug is NOT happening.
** Packa
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
--
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/2023946
Title:
Nvidia 530 kernel driver is
That's unfortunate, but useful for debugging this. Please try to find
the relevant log file from when it tried to build the kernel graphics
driver:
find /var/lib/dkms/nvidia -name \*.log
Please also attach the system update logs:
/var/log/apt/history.log
/var/log/dpkg.log
--
You received
/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/nvidia-graphics-drivers-530/+bug/2023946/+attachment/5683479/+files/make.log
--
You received this bug notification because you are a member of Kernel
/var/log/apt/history.log
/var/log/dpkg.log
** Attachment added: "nvidia.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2023946/+attachment/5683480/+files/nvidia.log
--
You received this bug notification because you are a member of Kernel
Packages, which is su
It looks like the nvidia kernel has been reverted. However, I am still
seeing the same error with Slack, and the second monitor is still not
working
--
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://
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2021949
Title:
Fix Monitor lost after replu
That's odd. Those logs suggest the nvidia kernel driver built and
installed successfully. But your log from bug 2025585 explains the
issue:
Jul 03 11:40:12 khteh-p17-2i gdm3[3370]: modprobe: ERROR: could not insert
'nvidia': Key was rejected by service
Jul 03 11:40:12 khteh-p17-2i kernel: Loadin
options snd-hda-intel model=alc295-hp-x360
didn't help either.
--
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/1982483
Title:
No sound from built-in speakers HP Pavilion All-in-One Deskt
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
*** This bug is a duplicate of bug 1921536 ***
https://bugs.launchpad.net/bugs/1921536
Bug 2014983 has a suggestion for how to fix it.
** No longer affects: dkms (Ubuntu)
** This bug has been marked a duplicate of bug 1921536
"modprobe: ERROR: could not insert 'nvidia': Key was rejected b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-restricted-modules (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
htt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
>From bug 2014983:
> Fixed by purging everything nvidia, libnvidia, or cuda, and reinstalling
> through
> the "additional drivers" interface. I also reinstalled linux-headers-$(uname
> -r).
** Tags added: nvidia
** Tags added: lunar
** Also affects: linux (Ubuntu)
Importance: Undecided
Please provide complete reinstallation commands.
--
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 rej
** Tags added: verification-done-jammy
--
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/2023638
Title:
Various backlight issues with the 6.0/6.1 kernel
Status in HWE Next:
New
S
At a guess:
1. sudo apt remove nvidia-driver-535 nvidia-dkms-535
2. sudo apt purge
3. Reboot.
4. Open the 'Additional Drivers' app in GNOME and use it to reinstall.
5. Reboot again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-re
Alternatively, just disable Secure Boot in the BIOS :)
--
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 w
Verified,
~~~
$ uname -a
Linux u-Precision-5480 6.0.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 20
10:50:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ ubuntu-report show | grep -ie bios -a5
"BIOS": {
"Version": "1.3.0"
},
~~~
--
You received this bug notification because you are a m
Which one of the two?
** Attachment added: "Screenshot from 2023-07-03 14-35-03.png"
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683487/+files/Screenshot%20from%202023-07-03%2014-35-03.png
--
You received this bug notification because you are
Amd why are ALL the options disabled for me?
--
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 rejecte
47 matches
Mail list logo
