On Fri, Mar 9, 2018 at 6:10 AM, Adam Williamson <
adamwill(a)fedoraproject.org> wrote:
> Hi folks!
>
> So, Fedora 28 has inherited an upstream GNOME change to default to
> suspending after 20 minutes:
>
>
https://bugzilla.gnome.org/show_bug.cgi?id=681869
>
> I believe this will also apply to live images, unless we suppress it.
> Should we suppress it? Suspending live images does not work well and
> is, I think, expressly not really 'supported'.
>
Today, we have tested what happens when anaconda installation takes longer
than the auto-suspend timeout. The good news is that anaconda inhibits idle
timer, meaning the installation is not suspended during the installation
phase. The bad news is that once the installation is complete, and I mean
*immediately* after that, the system suspends. You can't even say whether
the installation finished or not. At one instant you see an "almost
finished" anaconda screen, and a split second later your system "shuts
down". (It really looks like the power cable was plugged off). There's no
screen dimming, no grace period to let the user react (as there is when the
screen is about to lock down). So overall this is a poor experience. In
this particular case, it's related to anaconda auto-exiting after
installation is complete:
https://bugzilla.redhat.com/show_bug.cgi?id=1553935
But the same thing would happen even if it didn't auto-exit, just released
the idle lock.
Thanks for testing it - did the system recover from suspend? (Was this
testing from a USB drive?)
Owen