New kernel 4.13.0-16 is buggy on session lock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
I updated my distro from 17.04 to 17.10 in the last week.
My 'budgie-desktop' is 10.4.
My graphic card is an Nvidia GTX 1070.
Since the update, when I lock my session with new kernel, my screen don't wakeup correctly when I try to login again. The screen light is off, but I can hardly distinct login window. I can login, but screen light doesn't get back until I reboot my computer.
I have to set GRUB_DEFAULT to old kernel '4.10.0-38' for no getting this problem.
If you need more information feel free to ask !
---
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: Budgie:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=
MachineType: ASUSTeK COMPUTER INC. GL502VSK
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.169
Tags: artful
Uname: Linux 4.13.0-
UpgradeStatus: Upgraded to artful on 2017-11-10 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/28/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL502VSK.303
dmi.board.
dmi.board.name: GL502VSK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: GL
dmi.product.name: GL502VSK
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
no longer affects: | ubuntubudgie |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1731913
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.