Description of problem:
With latest GNOME, the auto-suspend timeout defaults to 20 minutes. If you run an app which holds the idle lock (e.g. a movie player, or a web browser showing an online video), and it runs longer than the default timeout (e.g. watching a movie), then the system suspends _immediately_ after the app releases the lock (e.g. movie ends).
This bug is filed just to track this in Fedora and have the ability to mark it as a CommonBug or discuss blockerness.
The upstream discussion is here:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. It's easier if you set the auto-suspend interval very low, e.g. 60 seconds:
$ gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 60
2. Run e.g. a movie player/online video with a movie longer than the timeout
3. See system suspend immediately after it ends
Nominating this as a PrioritizedBug, because it's extremely annoying for our users (while at the same time probably not a blocker).
This bug is accepted as Prioritized one. It will be brought to Workstation WG asking for taking an action.
This bug has been accepted as a PrioritizedBug. Since it is still in the "NEW" state, the triage team will revisit it at the 2018-08-29 meeting. If you have any updates, you can provide them here or email firstname.lastname@example.org.
At today's Prioritized Bugs and Issues meeting, we agreed to remove this as a Prioritized Bug since it is addressed by reverting the auto-suspend behavior (https://pagure.io/fedora-workstation/issue/42#comment-504425) and fixed upstream (https://gitlab.gnome.org/GNOME/mutter/merge_requests/54).
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.
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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.