Black screen after waking from suspend, need to reboot to use the PC

Bug #1668062 reported by Márton 'Sigmond
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi,

I installed a fresh Ubuntu 16.10.
When I try to wake the system from suspend, I only get a black screen.
The LCD back-light gets light up, the mouse pointer shows up, and it can be moved, but then I do not get anything else on the screen.

I can still use Ctrl+Alt+F1 to switch to text screen.
Switching back with Alt+F7 leads back to the black screen.

This makes it impossible to use Ubuntu 16.10, please address.
I use Fedora 25 now, and does not suffer the same issue.

I am happy to provide more details (hardware, logs), please let me know.

Best regards,
Marton
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D7p: csalad2 2310 F...m pulseaudio
 /dev/snd/controlC1: csalad2 2310 F.... pulseaudio
 /dev/snd/controlC0: csalad2 2310 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=0d7c78b5-bcee-4f78-ac98-35861e943e69
InstallationDate: Installed on 2017-02-22 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IwConfig:
 lo no wireless extensions.

 enp4s0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=080d6932-790b-4bd2-84a7-c81995d324cc ro quiet splash
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-39-generic N/A
 linux-backports-modules-4.8.0-39-generic N/A
 linux-firmware 1.161.1
RfKill:

Tags: yakkety
Uname: Linux 4.8.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2507
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F1A75-V PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2507:bd01/29/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A75-VPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1668062/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Vej (vej) wrote :

Filed against linux, which tends to be the right place for triaging suspend related problems.

no longer affects: ubuntu
tags: added: yakkety
Vej (vej)
tags: added: kernel-graphics-blankscreen
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1668062

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : CRDA.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : JournalErrors.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : Lspci.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : Lsusb.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : ProcEnviron.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : ProcModules.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : PulseList.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : UdevDb.txt

apport information

Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Márton 'Sigmond (marton-sigmond) wrote :

I tried to reproduce the problem after a reboot.
Here is what I found:
1) No apps started: not reproducible
2) VLC play paused: not reproducible
3) SMPlayer paused: not reproducible
4) Both Chrome and Firefix played YouTube video and paused: reproducible - instead of black screen the latest scene froze to the screen (i.e. dash, windows, status bar, etc.), mouse still working, but nothing else, rebooted the system with Ctrl-Alt-F1 and Ctrl-Alt-Del.

Revision history for this message
nullsteph (p-stephenwille) wrote :

I had to downgrade Nvidia driver from 384.xx to 381.34, running Ubu 17.04.

Revision history for this message
nullsteph (p-stephenwille) wrote :

Nope, it stopped working again. I have the same problem as the OP.

Revision history for this message
dino99 (9d9) wrote :

This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

Changed in linux (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.