Hi,

this may be related to systemd. Things have gotten so complex since
then that I am at a loss about how to find out which actual component
is to blame. I hope that someone more knowledgeable will be able to
properly triage and reassign this. It may be possible that this is a
duplicate, which I was not able to determine myself for the same
reasons.

When I tell my system to suspend to RAM via K Menu - Leave - Suspend
to RAM, it properly goes to sleep. However, when I wake it up again, I
find myself at a useable, unlocked desktop with a dialog open saying
that authentication is necessary to suspend the system. When I enter
my password in that dialog, the system goes to sleep again.

The ugly bug is: When I tell the system to suspend, it suspends twice
in a row.

The security relevant bug is: When I tell the system to suspend, and
leave the system alone in this state, assuming that my session was
locked before going to sleep, I actually lose my session to anybody
able to hit the power button since my session is not locked any more
before sending the system to sleep.

Greetings
Marc