I'm troubleshooting some video problems with a used laptop I got for cheap.
For the day is was pretty nice, Dell Latitude D620 with Nvidia Quadro
graphics (the problem I'm troubleshooting).
I was looking through the journal when I saw this shortly after logging in:
Feb 03 17:47:15 localhost.localdomain systemd-logind[676]: Removed session
c1.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Default.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Default.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Basic System.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Basic
System.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Paths.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Paths.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Timers.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Timers.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Sockets.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Sockets.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Shutdown.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Reached target
Shutdown.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Exit the
Session...
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Received SIGRTMIN+24
from PID 2173 (kill).
Why does systemd think I'm trying to shut down the computer right after
logging in?
The computer doesn't actually shut down and I'll get a usable desktop after
what I assumed was a hard lock but it takes well over 5 minutes, I haven't
put a stopwatch to it.
Thanks,
Richard