Red Hat Bugzilla – Bug 1265375
Xwayland apps unable to keep display awake
Last modified: 2016-12-20 09:41:24 EST
Description of problem:
XWayland apps (Chrome, mplayer, ...) are not able to keep the display awake during video playback.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sign in to wayland session (Chrome with Youtube video, mplayer --stop-xscreensaver)
2. Open X11 app that keeps display awake
3. Wait for display timeout
Screen begins to dim after timeout. Requires mouse movement to reset.
Display sleep should be inhibited.
The XWayland apps have the same capabilities in Wayland as they do in X
Looking into mplayer --stop-xscreensaver option, it calls XResetScreenSaver() on a regular basis to avoid the screensaver to kick-in.
But for this to work under Wayland, it would need to be wired back to the Wayland compositor.
GNOME uses the following protocol based on dbus for this purpose of inhibiting the screensaver:
The possible limitations of this protocol are also discussed in this bugzilla:
Ideally, apps should use that protocol as well instead of relying on X, and that would work with GNOEM on Wayland as well.
See comment 1, this is unlikely to be addressed, apps should use the appropriate protocols instead of using hacks such as "simulating" key pressed to keep the screen saver from kicking in.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.