The original post: /r/debian by /u/ms40ms40ms40ms40 on 2024-05-11 19:07:16.

Hello!

I just installed Debian 12 with KDE (fresh install on a new 1TB SSD, LUKS encrypted).

All fine so far, I wanted to shut the machine down and the screen turned black, but the machine still running running and running. After a few minutes I forced shutdown with the on/off button.

I dont want to have to do that again, so I am trying to fix it.

Story behind it:

Before that, I was running Debian Xfce on that same machine, had similar shutdown issues, but thought it was a problem with the SSD so I changed the SSD.

But now it seems as the problem persists with Debian KDE…

Before I continue with tweaking everything to my liking, I would like to just fix that shutdown time issue, which is why I read this article: https://itsfoss.com/long-shutdown-linux/

and tried with “journalctl -rb -1” , which gave me the following ouput:

https://pastecode.io/s/4krcwa19

Now I try to understand what can be the problem.

Are those lines possibly a part of the problem?

Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Failed with result 'exit-code'.
Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Control process exited, code=exited, status=1/FAILURE
Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Failed with result 'exit-code'.
Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Control process exited, code=exited, status=1/FAILURE
Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Failed with result 'exit-code'.
Mai 11 21:09:51 acer-xc780 systemd[1]: systemd-cryptsetup@nvme0n1p3_crypt.service: Control process exited, code=exited, status=1/FAILURE
Mai 11 21:09:51 acer-xc780 systemd-cryptsetup[18631]: Failed to deactivate: Device or resource busy
Mai 11 21:09:51 acer-xc780 systemd-cryptsetup[18631]: Device nvme0n1p3_crypt is still in use.

Do u have any idea?

Especially I ask myself the question if the encryption can have anything to do with this? Earlier I did the same partitioning and the same encryption via LUKS and LVM and it has never been a problem… or is there a complete other reason for that behaviour?

If you want to read more about my hardware, or some logs: https://linux-hardware.org/?probe=8870125513

UPDATE:

I tried it with a KDE Wayland Session instead of X11, and the shutdown is fulfilled immediately and without any problem. Maybe that helps finding a solution? In the long term I would rather use X11, as wayland doesnt seem very developed right now…