Bug 1530079 - Screen blank after resume until virtual terminal switched
Summary: Screen blank after resume until virtual terminal switched
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 26
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-01 19:42 UTC by Matthew Cline
Modified: 2018-05-29 12:38 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:38:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg log file (456.08 KB, text/plain)
2018-01-01 19:42 UTC, Matthew Cline
no flags Details
Output of "grep -i radeon /var/log/messages" (1.21 KB, text/plain)
2018-01-01 19:43 UTC, Matthew Cline
no flags Details

Description Matthew Cline 2018-01-01 19:42:05 UTC
Created attachment 1375357 [details]
Xorg log file

Sometimes when I resume from suspend to RAM the screen will be blank even after pressing keys and wiggling the mouse, though the keyboard responds (capslock light toggles) and the USB mouse light is on.  If I press Ctrl-Alt-F2 to change to the first virtual console it comes up, then I can press Ctrl-Alt-F1 to switch back to X and the screen works again.  No relevant entries are in /var/log/messages or $HOME/.xsession-errors

Video hardware: AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G

Packages:

* xorg-x11-drv-ati-7.9.0-1.fc26.x86_64
* xorg-x11-server-Xorg-1.19.3-4.fc26.x86_64

Attached:

* /var/log/Xorg.0.log
* Output of "grep -i radeon /var/log/messages"

Comment 1 Matthew Cline 2018-01-01 19:43:01 UTC
Created attachment 1375358 [details]
Output of "grep -i radeon /var/log/messages"

Comment 2 Fedora End Of Life 2018-05-03 08:21:24 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Matthew Cline 2018-05-03 16:47:29 UTC
I think that this bug has been superseded by bug 1574619, since this bug stopped happening and the new bug started happening after I upgraded to Fedora 27.

Comment 4 Fedora End Of Life 2018-05-29 12:38:40 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.