https://bugs.freedesktop.org/show_bug.cgi?id=109526
--- Comment #5 from Johannes Hirte johannes.hirte@datenkhaos.de --- Created attachment 144083 --> https://bugs.freedesktop.org/attachment.cgi?id=144083&action=edit dmesg log from suspend->resume->suspend->resume
When this bug occurs, from sddm it is possible to put the system into suspend again via hotkey. In most cases the second resume works. Attaching a dmesg output from such a suspend->resume->suspend->resume cycle. Maybe this helps debugging this.