Slow Shut down and login screen gets stuck TW KDE

English Install/Boot/Login
#1

Hi there! so whenever I want to shut down my laptop it takes so long. around 3 minutes, and after that when I start it up again it gets stuck at the login screen after entering the password. then I need to force shut down my laptop using the power key. after that, it boots normally and everything works smoothly.
this doesn’t happen if I first log out and then shut down my device.

I have an Asus r565 laptop with an i5-1135G7 processor and Nvidia mx330 graphics. these issues also happened before when I didn’t have Nvidia drivers installed.

Edit: slow shut down mostly happens when my laptop is on for a long time.

#2

Welcome to the forum!

A couple questions …

Has this behavior been like this since you initially installed TW ?

Or has the problem recently occurred? If yes, did you notice what “event” might have happened just before the problem cropped up ?

Is this laptop a dual-boot, with maybe Windows as the other OS?

When the laptop is on for “for a very long time”, does it go into Sleep mode ??
… or Hibernate mode ?

#3

@myswtest

On the first boot I just ran sudo zypper dup so I’m not sure if the default image had this behaviour or not but my image was from a couple months ago and when I installed it then it had the same behaviour. So it hasn’t happened recently. It’s been there for a very long time

Yes it’s a dual boot with windows 11

It goes into hibernate mode if untouched for around 10 minutes cause that’s what the KDE set by default

#4

press ESC at shut down to view the log and see if some process is not shutting dow n

#5

I don’t have any splash screen on shutdown so by pressing esc nothing happens.
It just shows this:

IMG_20230423_160931
IMG_20230423_1609311920×1317 36.1 KB

#6

I just set the after login settings to only save app states manually and restartedy laptop. Now I can’t get past the login screen :sob:

#7

System will not power down until all running process are stopped . Some process seems to be hanging generally this should be shown on the log screen normally available with esc after you initiate shutdown. Not sure why it is not for you.

#8

I removed the .cache directory via tty an now I’m in.

#9

Isn’t there other options to see which process is hanging? I think there was a command to calculate those and write the result into a file. Can’t remember the exact command tho

#10

@gogalthorp

result of journalctl -rb -1

Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Reached target Exit the Session.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Finished Exit the Session.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Reached target Shutdown.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Removed slice User Application Slice.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped Create User's Volatile Files and Directories.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Closed PipeWire Multimedia System Socket.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Closed PipeWire PulseAudio.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Closed Socket to launch DrKonqi for a systemd-coredump crash.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Closed D-Bus User Message Bus Socket.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped Daily Cleanup of User's Temporary Directories.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped target Timers.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped target Sockets.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped target Paths.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped target Basic System.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Stopped target Main User Target.
Apr 23 16:26:00 localhost.localdomain systemd[1794]: Activating special unit Exit the Session...
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Startup finished in 172ms.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Reached target Main User Target.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Reached target Basic System.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Reached target Sockets.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Finished Create User's Volatile Files and Directories.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Listening on D-Bus User Message Bus Socket.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Starting Create User's Volatile Files and Directories...
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Listening on PipeWire Multimedia System Socket.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Listening on PipeWire PulseAudio.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Listening on Socket to launch DrKonqi for a systemd-coredump crash.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Starting D-Bus User Message Bus Socket...
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Reached target Timers.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Reached target Paths.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Started Daily Cleanup of User's Temporary Directories.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Created slice User Application Slice.
Apr 23 16:24:27 localhost.localdomain systemd[1794]: Queued start job for default target Main User Target.
#11

somewhere it took around a minute and a half to finish a process. from 16:24:27 to 16:26:00

#12

also, I have to mention that this only happens on distros with kernel 6 and higher. it wasn’t happening on Kubuntu 22.10 with kernel 5.19 I think.

#13

@myswtest , @gogalthorp
setting the session-restore setting to manual mode in KDE settings fixed the long shutdown issue but the login screen still gets stuck sometimes and the only way to get in is to erase the .cache folder from tty

#14

Maybe something you start in auto-start have you tried an other user??with clean home

#15

@gogalthorp
I have outline VPN client as an app image which keeps starting after login and when I remove it from autostart list it comes back