@scops Does your Librem 5 shut down unexpectedly? That shouldn't happen and doesn't happen for me here. Are you sure it's not just a compositor crash? (asking since people very often confuse those) Which hardware batch is it?
@dos it's evergreen... for me it helped to deactivate the automatic updates. geany also had massive problems with my 5 mail accounts. with 2 (librem.one and one sharehoster) all is fine. i think it is the compositor ... mustly it just shuts down - if it "crashes" ^^
@scops If the compositor crashes, the screen goes blank for a few seconds. Then people tend to press the power button instead of waiting for phosh to come up again (which, well, is a natural reaction to screen suddenly going blank), which in turn triggers a full shutdown as that's what systemd does when it notices the power button being pressed and there's no compositor to intercept it.
I'll take a look whether we can block that power button behavior when the compositor isn't up.
@scops Dumping the systemd journal from the previous boot would do it. Make sure to skim it for personal data though before sharing :)
@dos like i said, at the moment it is all stable...maybe it was also fixed by one of the updates today/yesterday. i will turn the automatic updates on again and keepup testing. if it crashes; which logfiles you would like to see exactly?