After updating the kernel to:
5.19.0-45-generic #46~22.04.1
The problem NMI-lock has (so far) not showed: No alarm in ILO, blue
light instead of Red flashing light on the server.
I submitted the updated from the cli of apport on the server. I am not
sure why these updates have been submitted lik
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680926/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680929/+files/acpidump.txt
--
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/20
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680927/+files/UdevDb.txt
--
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/2012366
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680928/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680924/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680921/+files/Lsusb.txt
--
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/2012366
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680925/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680923/+files/Lsusb-v.txt
--
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/2012
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680922/+files/Lsusb-t.txt
--
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/2012
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680919/+files/Lspci.txt
--
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/2012366
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2012366/+attachment/5680920/+files/Lspci-vt.txt
--
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/20
apport information
** Tags added: apport-collected
** Description changed:
After distro upgrade to new LTS "22" from 20 the HP microserver shows a
critical NMI event in ILO
Unrecoverable System Error (NMI) has occurred. System Firmware will log
additional details in a separate IML en
u82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1336 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 21:23:25 2022
InstallationDate: Installed on 2022-11-18 (9 days ago)
Installation
5.15.0-25, Bluettoth
stopped working via menu. Before I used versions 20.04 and 21.10, the
latter with kernel 5.13, and Bluetooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
rsion 22.04, with kernel 5.15.0-25, Bluettoth
stopped working via menu. Before I used versions 20.04 and 21.10, the
latter with kernel 5.13, and Bluetooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.se
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Acti
5.13, and Bluetooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running)
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running)
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (runn
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
d normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running)
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (runn
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (runn
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (runn
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running)
recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (runn
d normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running)
. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: active (running) since Thu
etooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: activ
n Ubuntu:
New
Bug description:
After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
stopped working via menu. Before I used versions 20.04 and 21.10, the
latter with kernel 5.13, and Bluetooth was recognized normally. The
bluetooth status in the terminal is this:
diego@diego-
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
r kernel version. Is it possible to
go back to the previous version? It was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/de
t was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p:
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
sion? It was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/s
t was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p:
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
t was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0
t was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0
ious version? It was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
t was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
sion? It was working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/s
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
working really well.
What can I do? Well, thank you very much in advance.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: diego 1800 F pulseaudio
/dev/snd/pcmC0D0p: d
I do? Well, thank you very much in advance.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: diego 1800 F pulseaudio
+ /dev/snd/pcmC0D0p: diego 1800 F...m
Public bug reported:
Hi, I am testing image deploy in order to promote them from candidate to
stable in the https://images.maas.io/
During this task I could not deploy and boot our server: IBM 8247-22L
[0]
Please find attached the log I captured with ipmiconsole.
Let me know any other informat
Thanks a lot dann.
I dont know the release process of the kernel, and when our public
images are generated by CPC.
I have to test it when is uploaded here:
https://images.maas.io/ephemeral-v3/candidate/impish/arm64/
Do you have any tip about how to be aware when this should happen?
--
You rece
Hi Chis Chiu, I had a similar issue here with all kernels after
5.8.0-63-generic. I found this bug report and just finished trying your
suggestion I'm pleased to tell you that at least in my Dell notebook it
worked. The as previously reported the issue only happens after login
into the X env.
If I
Im not able to run: apport-collect
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1942633
Title:
Can not boot impish
** Attachment added: "debug_impish_arm_machine_20210830.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+attachment/5522867/+files/debug_impish_arm_machine_20210830.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic
5.11.7) in
arm64
description: Computer
product: Cavium ThunderX CN88XX board
width: 64 bits
I tried 2 releases:
- 20210817 (
https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/
Thanks, this seems to have resolved my problem.
--
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/1931574
Title:
Lost network connection, seems like an older kernel bug
Status in linux pac
Response to FairMiles (fermilesi) #22
I also had this error. I fixed it forcing login screen to load with Xorg
(instead of wayland)
These are the steps:
https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
--
You received this bug not
Thanks dannf,
We updated the BIOS to F02 and its working well now.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/19232
Im not able to run: apport-collect
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1923230
Title:
Can not boot Cavium
I exectued `lspci -vnvn` using a focal server in the same machine .
Let me know if there is any else I may help with
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230/+attachment/5486189/+files/lspci-vnvn.log
--
You received this bug notifica
Public bug reported:
Hi I am tryring to deploy a Hirsute server (Ubuntu 5.11.0-13.14-generic
5.11.7) in
arm64
description: Computer
product: Cavium ThunderX CN88XX board
width: 64 bits
Im getting a kernel panic occurs during the boot:
[8.417589] Code: a90
Hi I am getting Failed to send firmware data (-38), even after cool boot
diego@lfb-Desktop:~$ dmesg | grep -i bluetooth
[5.985839] Bluetooth: Core ver 2.22
[5.985858] Bluetooth: HCI device and connection manager initialized
[5.985864] Bluetooth: HCI socket layer initialized
Hi, can someone help... Cold boot is not working for me I am
getting Failed to send firmware data (-38)
$ dmesg | grep -i bluetooth
[5.985839] Bluetooth: Core ver 2.22
[5.985858] Bluetooth: HCI device and connection manager initialized
[5.985864] Bluetooth: HCI socket layer
Still happening on 2020-10-01 (since at least 2019-10-01) on multiple
computers.
Quoting what bug description says:
"Kernel should be fixed to correctly parse lz4 compressed initrds, or at
least lower the warning, to not be user visible as an error."
--
You received this bug notification becaus
It also happens with driver nvidia-340.108 in elementary OS 5.1.6 Hera.
In my case the error happens with VLC when trying to open the Hikvision rstp
streaming (H264), the error lines run fast but stop when closing VLC.
I leave some lines of the error.
VLC media player 3.0.11 Vetinari (revision
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
Same error here using a Lenovo Yoga X1 3rd with fully updated Ubuntu
20.04 (focal).
Removing "quiet splash" seems to work and also observed (when I was
trying to debug this) that pressing Esc key to avoid s
Public bug reported:
I follow this bug, and still happend
https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug/e91ee546-b48f-
11ea-a86b-68b5996a96c8
dpkg --status bluez | grep '^Version:'
Version: 5.53-0ubuntu3
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=foc
Hi, Thank you for your feedback
Upgrade my system? I'm using the developer version of Ubuntu (20.04)
Can I offer any other information to help?
Sorry I'm not a advanced user, but certainly my system isn't outdated.
Ps.: I'm not using nvidia-340. I'm using nvidia-390.132
Thank you again =D
--
Y
Apport create automatically this page:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bug
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1867663
Title:
nvidia-persistenced assert failure: malloc(): inval
Apport create automatically this page:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1867663
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bug
** Attachment added: "nvidia bug report"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860847/+attachment/5337596/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-grap
** Attachment added: "Xorg log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860847/+attachment/5337595/+files/Xorg.1.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubu
After my laptop suspend, Ubuntu take a while (near 1 min.) to back login screen.
I'll added journalctl -b-1 and Xorg.1.log
If you need something, let me know =D
** Attachment added: "jornalctl after suspend"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860847/+a
Hi Daniel. I've the same problem. System crash using nvidia 390-132.
In my case, the system crash aleatory when I'm using laptop. Don't in a
specific situation.
I've attached journalctrl -b-1 (after crash) like your recommendation. I see
nvidia error at the end of file.
My ubuntu have the follow
Tnks!
Any solution should be backported to kernel v. 4.15 LTS to be effective.
diego
---
Diego Maniacco, Bolzano (Italy)
diego.mania...@gmail.com
---
[image: Not f'd — you won't find me on Facebook] <https://w
hoi: got "freedesktop.org Bugzilla is no longer in use".
---
Diego Maniacco, Bolzano (Italy)
diego.mania...@gmail.com
---
[image: Not f'd — you won't find me on Facebook] <https://www.fsf.org/fb>
N
Update:
checked all 4.15 kernel versions.
any version > 4.15.0-54 (LTS 2020) shows the bug.
kernel 5.3 is not supported after Aug.2020).
--
Again Ask for backport of bug-fix to Kernel 4.15.0 or other LTS Kernel.
--
You received this bug notification because you are a member of Kernel
Packages, w
Hi!
Confirm that problem rise with kernel 4.15.0.55 (is LTS, supported till
2022).
Locked kernel update to 4.15.0 54 for now, which is enough for normal use.
---
Diego Maniacco, Bolzano (Italy)
diego.mania...@gmail.com
Same issue as reported in the Bug, with some diffs:
Laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. [SAME]
Distro: Linux Mint 19.3 MATE 64bit; base: Ubuntu 18.04 bionic.[UPDATE]
This happen trying any distro. I tried Ubuntu 18.04.3, ElementaryOS.
--
I'm also stuck with Kern
Hello,
I have exactly the same problem. I'm running Ubuntu 18.04 LTS on Lenovo Legion
Y540, I have configured a swap partition instead of a swap file and I have
updated both /etc/fstab and /etc/default/grub files (and run update-initramfs
and update-grub).
When I try to hibernate with systemctl
** Description changed:
· Ubuntu version: 18.04.3 LTS
$ uname -a
Linux diego-PE62 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
$ apt-cache policy linux-firmware
linux-firmware:
- Installed: 1.173.12
- Candidate: 1.173.12
Public bug reported:
· Ubuntu version: 18.04.3 LTS
$ uname -a
Linux diego-PE62 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
$ apt-cache policy linux-firmware
linux-firmware:
Installed: 1.173.12
Candidate: 1.173.12
Version table
I have integrated graphics Intel HD4600 (Haswell) and discrete Nvidia
GTX750M as well, which is managed by the Nvidia binary blob (the nouveau
module is blacklisted) but usually disabled. I also have an external
monitor always plugged in while at home, and nothing elsewhere.
Unfortunately the bug h
I have some new information: the bug is still happening as before, today
I resumed my session and the login screen got stuck as usual; I left it
there for a couple of minutes, then I unplugged and replugged the
ethernet cable and, as soon as the network was up again, the session was
unlocked! Maybe
A temporary solution is to install lightdm before installing the nvidia driver.
sudo apt install lightdm
** Summary changed:
- Nvidia Persistence Daemon stops Ubuntu 18.10 from booting
+ Gnome Display Manager stop after installing Nvidia driver
** Also affects: gdm3 (Ubuntu)
Importance: Undec
I don't know if it's the same problem
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1798827
I did 3 installations from scratch and updated before installing the Nvidia
driver and the problem persists.
In Ubuntu Budgie does not occur.
--
You received this bug notifica
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204476/+files/Lsusb.txt
--
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/1798833
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204473/+files/CRDA.txt
--
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/1798833
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204479/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
After coming back from the weekend, the issue is now also occurring on
the 4.15.0-20 kernel. I am not sure what is up. I had tried the
4.15.0-22 and 4.15.0-36 kernels, prior to booting up 4.15.0-20 again. In
this particular machine, I had tried resetting the power saving settings
of the network car
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204475/+files/Lspci.txt
--
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/1798833
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1798833/+attachment/5204482/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
1 - 100 of 222 matches
Mail list logo
