My initial setup on LM was to disable SSL, input the host IP address and when this “not starting” happened upon the next reboot, I figured I needed to check the “auto config” box and that would remedy this. I did not have this issue before on other systems (Windows 11, KDE, etc.) Why is is not retaining the IP address of the Barrier host? I gave it time and more than a few keystrokes, but nothing in the password box for login on LM.īUT I noticed that even though settings in Barrier have the “Start Barrier on startup” checked, it does NOT start (it says it is not running and the “start” button is active) and I see that the IP address is blank. Since the keyboard is a bluetooth connection, sometimes there is a delay in the response when logging into KDE system, but it always works (via bluetooth) after a few taps. I tested using the mouse from my KDE pc running barrier and it did not work. Perhaps a second opinion of the instructions above by some forum members But the process sounds logical, I guess.Īnd as always, take anything ChatGPT says with a grain of salt. If you have installed Barrier in a different location, you may need to modify the ExecStart line in the systemd service unit file accordingly. Please note that the instructions provided assume that you have installed Barrier in the default location. Once you log in, Barrier should be ready to use. You can test it by rebooting your system and verifying that Barrier is running before the login screen appears. Now, Barrier should start automatically before login on your Linux Mint laptop. In nano, you can do this by pressing Ctrl+O, then Enter to save, followed by Ctrl+X to exit.Įnable the Barrier service to start on boot:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |