Well, you don't give us much to go on, but my first thought was dmesg, which I guess translates to journalctl -k. You will also see other messages if you look at the user side with --user. I think the gui runs on the user side, not the system side. If you aren't seeing anything, I would check to see how you are configed and if you are trying to start a gui and/or run startx, or similar, manually and see what happens. I assume you are running X and not Wayland. I don't know anything about Wayland and I understand it is still a bit limited and buggy. Come to think of it, I don't know much about systemd either. Only what I've come across in my own troublshooting. I just had a goround with a bunch of sound system issues. Annoying, but I guess I learned a lot LOL. I guess I've mellowed a bit on systemd and am a little less hostile. I'm not quite sure I'm a fan yet. I wanted to have an ssh connection established on behalf of a specific user at start up, regardless of if they log in. I tried several different systemd "approaches" but it just keeps restarting until it reaches the max and dies. I can see how this way is a little more integrated than the "old" way. If only I could get it to work LOL. I'll probably end up using cron @reboot, which has its own set of issues to deal with. On Sat, Nov 01, 2025 at 04:06:52PM -0700, Brian E. Lavender wrote: -- -Gary It is a simple thing to make things complex, a complex thing to make things simple.