Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1513773 - display does not wake from sleep
Summary: display does not wake from sleep
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-15 23:01 UTC by Ralph Giles
Modified: 2018-11-30 18:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 18:24:58 UTC

Attachments (Terms of Use)

Description Ralph Giles 2017-11-15 23:01:43 UTC
Description of problem:

Since upgrading to Fedora 27, I generally can't wake the display after it goes to sleep on my desktop. Sometimes one or two of the displays will wake and show the lockscreen wallpaper, but the primary display never does. In any case, neither mouse nor keyboard input opens the password prompt to unlock the screen.

Generally I can recover by logging in from another machine and executing 'kill -HUP' on the gnome-shell process, then logging in again through gdm.

Version-Release number of selected component (if applicable):


Lenovo P710 with Radeon RX 480 and three displays connected.

How reproducible:

Always when I've been away from my desk more than a few minutes.

Steps to Reproduce:
1. Log in.
2. Wait for displays to sleep. Wait another couple of minutes.
3. Move mouse or press keys on the keyboard.

Actual results:

Primary monitor remains in power-save standby.

Expected results:

All monitors wake and pressing any key prompts for a password to unlock the screen.

Additional info:

Comment 1 Ralph Giles 2017-11-23 00:36:46 UTC
Like bug 1417778, this issue is specific to wayland. I haven't been able to reproduce after logging in to 'GNOME on Xorg'.

Comment 2 Ben Cotton 2018-11-27 18:04:09 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 Ben Cotton 2018-11-30 18:24:58 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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

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.