Suspend Screen Looping (will not go away)
Describe the bug When using Oxide without lockscreen (not if with with one as well rn but i think not or less pronounced), both models will stop waking up and upon a second press on the Power button will start what I call a "Suspend Screen Loop". On of it seems to be fake (and can be exited on the rM 1). The one that makes the screen flash usually seems to be the "real" suspend screen.
To Reproduce Steps to reproduce the behavior:
- Install either Oxide v2.1 (as in testing rn) or the packages from here
- Starting
- Suspending and resuming one time
- Doing that again
Expected behavior Suspend screen working as expected and not looping
Screenshots
Video (each time I move my finger to the standby button, I press it once). https://transfer.cosmos-ink.net/MZlpk/20210118_214910_ffmpegged.mp4
to help explain your problem.
Version Information:
- Device: Both
- OS: Current on both devices
- Version: Latest packages from here. Same also happened when building from the pr in toltec.
v2 1 is expected. This was suppose to be resolved in v2.1.1 so I'm confused as to why it's happening for you.
@LinusCDE Please attach the list of files in /opt/usr/share/applications as well as the contents of your tarnish.conf and decay.conf
@LinusCDE Also, please attach the tarnish logs.
@LinusCDE Could you attach a screenshot of htop after resuming?
Sorry, didn't see the response until now.

FYI - pressing F5 will display processes in a tree that makes it much easier to understand.
It looks like decay is crashing on resume though, which is likely the issue. Not sure why it's not happening for @dixonary or myself.
@LinusCDE are you still able to replicate this on the latest version?
Seems to be resolved. Tested with the testing release of oxide. I think this was resolved some time ago when you ensured, corrupt would still show up. I don't consider the brief appearance of corrupt a problem as the suspend loop was far more annoying.
Here is a side-by-side test. I tried to make all actions pretty much simultaniously. So it can probably also serve as some kind of speed comparison.
Closing since you reported it as being resolved.