So, I've tested some of the possible scenarios that Kamil pointed out. Here
are the results:
a) whether downloading files in Firefox will inhibit suspend or the
downloads will be aborted during progress? -
*broken*b) whether DNF inhibits suspend during operation or
$scary_consequences? - *broken* during downloading packages
c) whether Rhythmbox inhibits suspend when playing music? -
*works*d) whether gnome-disks inhibits suspend while operating on devices
(e.g. writing a disk clone, or checking SMART)? -
*broken*f) whether Nautilus inhibits suspend while copying files
(possibly to even a remote location)? - *works*
On Mon, Mar 19, 2018 at 2:36 PM, Kamil Paral <kparal(a)redhat.com> wrote:
On Mon, Mar 19, 2018 at 1:48 PM, Kamil Paral
<kparal(a)redhat.com> wrote:
> On Thu, Mar 15, 2018 at 10:46 AM, Kamil Paral <kparal(a)redhat.com> wrote:
>
>> For example, has anyone tested:
>>
>> a) whether downloading files in Firefox will inhibit suspend or the
>> downloads will be aborted during progress?
>> b) whether DNF inhibits suspend during operation or $scary_consequences?
>> c) whether Rhythmbox inhibits suspend when playing music?
>> d) whether gnome-disks inhibits suspend while operating on devices (e.g.
>> writing a disk clone, or checking SMART)?
>> e) whether Pitivi inhibits suspend while rendering video?
>> f) whether Nautilus inhibits suspend while copying files (possibly to
>> even a remote location)?
>>
>
> Here's another "broken" use case that we found today:
>
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/18
>
> Currently there seems to be no (graphical) way to disable auto-suspend
> system wide. Which means the system will auto-suspend regardless of your
> settings when you perform user switching. It's somewhat unintuitive that
> suspend, as a system-wide action, is considered a per-user setting (the
> active user overrides all inactive users), and there's no option to set it
> system-wide.
>
Here's even a "funnier" case. The system suspends when you connect over
SSH (the system shows a GDM screen locally), even if you're active (running
commands). And you can't do anything about it, because it ignores your
settings and uses the system default (20 minutes timeout).
So, if you sometimes start your system remotely and ssh in, or if you have
graphical issues and need to debug it over ssh, or in any other case that
you can imagine when you need to ssh in... your system *will* suspend in 20
minutes. I think advanced users will eat us alive.
What's even worse, there's no obvious way to disable this even for those
advanced users. There's no config file in /etc you could edit and adjust.
"sudo gsettings" (for setting the right key globally) fails with an error.
How do GNOME devs expect users to configure this? What do we tell them? Or
is ssh a no longer supported use case on Workstation?
_______________________________________________
desktop mailing list -- desktop(a)lists.fedoraproject.org
To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org
--
Best regards / S pozdravem,
František Zatloukal
Associate Quality Engineer
Red Hat