On Fri, 2018-03-09 at 12:17 -0500, Owen Taylor wrote:
On Fri, Mar 9, 2018 at 12: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'.
>
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.
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 :(
Is this something that we could detect in the suspend triggering
code
rather than changing configuration for the live image?
Well......sorta. At least AIUI, I believe that there isn't a 100%
reliable way of determining "this is a live session". It's easy to
know, of course, "this is a *Fedora* live session", but that's not a
generic solution for an upstream like GNOME. There is not, so far as I
know anyway, a fully distro-agnostic indicator that "this system is
running live".
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net