Loss of keyboard and mouse input after "Log Out User"

[pkazmier]

I have installed borders, configured it with a bordersrc, and added it to brew services for startup. Every time I go to "Log Out User" in the Apple menu, windows close, and I'm returned to the login screen except that my keyboard input no longer works, so I cannot log back in. And my mouse pointer is able to move, but you can't click on anything like the power button to restart, so I have to hold down the power button to reboot.

#!/bin/bash

options=(
  width=8.0
  hidpi=on
  active_color=0xffa6e3a1
  inactive_color=0x00000000
  )

borders "${options[@]}"

I'm running the following on an Intel iMac Pro with Sonoma 14.6.1. Borders version 1.6.0 installed from home-brew today.

I initially thought this might be an issue with aerospace as I had added borders to my config there. However, I was able to reproduce the issue eliminating aerospace altogether and launching up borders via brew services. And because I think something is hanging, I'm not sure there are any good logs to look at. But any pointers would be appreciated.

Thanks!

[Bellavene]

I believe, it has nothing to do with border. When you log out all user processes are closed automatically, and you need special system rights to interfere with login screen after log out. I highly doubt that you can even give those rights by mistake.

[mbender71]

I have to submit that I have this same issue as well. Initially, I started JankyBorders via the Aerospace config. Everytime I would try to logout, I would have to wait minutes before the keyboard would react to any input at the MacOS screen. When I removed JankyBorders from the startup (and thus disabling it all together), I could logout and login back in instantly. I then kept JankyBorders out of the Aerospace configuration and started it automatically by having Brew start it as a service. Although JankyBorders did work, I was once again left with minutes delay on keyboard control at the login screen. I can only assume that JankyBorders is restarting itself after being killed and thus a nasty loop. Just a guess though. I hope this can be fixed. Thanks!