On Fri, Mar 9, 2018 at 7:02 PM, Adam Williamson <adamwill@fedoraproject.org> wrote:
On Fri, 2018-03-09 at 12:17 -0500, Owen Taylor wrote:
> On Fri, Mar 9, 2018 at 12:10 AM, Adam Williamson <adamwill@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'.
> >
>
> Any more details about how suspending live images doesn't work? It's
> obviously not good if you boot the Fedora installer, wait 20 minutes, and
> then find that the system is crashed in some bad state.

Well, the live image basically runs in RAM already; suspending then
attempts to dump the whole running state to...RAM...

I honestly don't have a detailed tech explanation of how/why it doesn't
work, but it's one of those things I've just always kinda had on my
'yeah of course that doesn't work' list, and every so often someone
*does* try doing it and report that it doesn't work.

Hmm, clearly hibernating wouldn't work for the live session - but I still don't see any fundamental reason that suspending wouldn't work. Perhaps there are problems with suspending when having your root filesystem on a USB device?
 
I appreciate this is a bit squishy. :) I'll try and test it out a bit
and see just how much it does / doesn't work, if I get time, but I've
got a lot of more urgent stuff on right now :(

Would be good to know, and if we know what the basic issue is, perhaps we can figure out how to disable the suspend at the right level. So, if you remember to investigate if and when time shows up, or someone else wants to try it out and report back what the actual issue is, that would be appreciated.

Thanks!
Owen