On Tue, 3 Nov 2020 16:20:56 -0600 Roger Heflin wrote: > Generally if a reboot script someone wrote acts like that it means > that some part of it killed something that immediately caused the > logout prior to the reboot command happening. Could be. I'll try it without the final reboot command and see what happens. The script is unchanged from earlier versions of fedora where it was the only way to reboot without incessant "a stop job is running" messages from systemd taking hours to timeout (well, felt like hours, anyway). I also finally spotted this suspicious nonsense in the logs. I have no idea what it means. Nov 3 17:31:45 zooty systemd[2615]: Condition check resulted in Mark boot as successful after the user session has run 2 minutes being skipped. The word "boot" is the only reason it seems possibly relevant. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx