this bug still occurs for me on ubuntu 18.04 using gdm 3.28.2 and gnome-shell 3.28.2. However, my laptop (x1 carbon gen6) only supports S0i3 (activated with the kernel parameter "acpi.ec_no_wakeup=1") and not s3. So is it possible that this bug is only fixed for S3? It does not occur when using wayland.
this bug still occurs for me on ubuntu 18.04 using gdm 3.28.2 and gnome-shell 3.28.2. However, my laptop (x1 carbon gen6) only supports S0i3 (activated with the kernel parameter "acpi.ec_ no_wakeup= 1") and not s3. So is it possible that this bug is only fixed for S3? It does not occur when using wayland.