You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing issues when trying to start barrierc with sddm (kde).
Server is Windows 10 2004, latest builds of barrier on server and clients.
If I start the client via SDDM /usr/local/share/sddm/scripts/Xsetup - The keys on the client get scrambled ( #662 ):
barrierc --daemon --display :0 --no-xinitthreads --debug INFO --name dev --enable-drag-drop --enable-crypto [ServerIP]:24800
So far I haven't figured out a way to be able to use barrier to "log in" onto a client (sddm / gdm / etc), I'm forced to use autologin and start barrierc after log in, however, that is not a proper solution (its not a solution at all).
If someone knows a workaround on how to start barrierc with linux "greeters" and not have the keyboard keys swapped / missing - let me know.
The text was updated successfully, but these errors were encountered:
I'm seeing issues when trying to start barrierc with sddm (kde).
Server is Windows 10 2004, latest builds of barrier on server and clients.
If I start the client via SDDM /usr/local/share/sddm/scripts/Xsetup - The keys on the client get scrambled ( #662 ):
barrierc --daemon --display :0 --no-xinitthreads --debug INFO --name dev --enable-drag-drop --enable-crypto [ServerIP]:24800
So far I haven't figured out a way to be able to use barrier to "log in" onto a client (sddm / gdm / etc), I'm forced to use autologin and start barrierc after log in, however, that is not a proper solution (its not a solution at all).
If someone knows a workaround on how to start barrierc with linux "greeters" and not have the keyboard keys swapped / missing - let me know.
The text was updated successfully, but these errors were encountered: