Re: [PLUG] Anyone here have restore-from-suspend failures on F32?

[Adam Schaible via plug <plug@lists.phillylinux.org>]

Hi Floyd,

Fedora has been my daily driver on my ASUS TUF505D laptop going back over a year now, I upgraded to F32 about 3 weeks ago.

Suspend has never worked on it going back as far as Fedora 30 and has identical symptoms to what you see on your Chromebook, however its sibling Hibernate has always worked fine for me. It'd be easy for me to say just switch everything over to Hibernate on your box too, BUT since about 95% of all Chromebooks are backed with eMMC instead of a proper SSD like the one in my ASUS lappy, that is probably not the best option for you.  

So it looks like this might be a real issue with Fedora. Sure enough, when I Googled "Fedora 32 Suspend Not Working" it's a total clown show in the search results over a page long, so probably no need to file yet another Bugzilla #363653262345 for this unless you're super annoyed, a better use of your time is to either work around it like me or switch distros (although each of the other distros I thought of suggesting seem to have the exact same issues with Suspend...)

Anyway if you stick with Fedora, it seems like most people who don't use Hibernate like me just disable Suspend completely. Lengthening or completely disabling the sleep timer is easy enough in Power Options, but disabling it for the lid close action (a mandatory tweak for any laptop *I* ever own) can often be a bit trickier and will depend a lot on what desktop environment you use, for stock GNOME you typically (and very annoyingly) need to do some manual tweaking in GConf but for other desktops (such as Cinnamon, which is what I use) the lid close action is sensibly placed right there alongside all the rest of the power options. Choose wisely :-)

Hope this helps,

-- 
  Adam Schaible
  plug@schibes.com

On Sun, Jul 12, 2020, at 09:57, Floyd Johnson via plug wrote:
> Hello, Penguin-Powered Peeps!
> 
> In a quest for a modern kernel, I upgraded my Chromebook to Fedora 32 
> (kernel 5.7.8) . I've run into a stumper. When Suspend to RAM is invoked 
> (either by inactivity timeout or my own doing), it seems to suspend 
> properly, but the resume operation, after about ten seconds, ends in an 
> automatic reboot.
> 
> I didn't find any clues in the journal or Xorg log.
> 
> What's been your experience with F32's suspend/restore?
> 
> 
> 
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
>
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug