Justin@lemmy.kde.social to Linux@lemmy.mlEnglish · 3 months agoThis week in KDE: looking forward towards Plasma 6.1pointieststick.comexternal-linkmessage-square14fedilinkarrow-up1166arrow-down16cross-posted to: news@lemmy.linuxuserspace.show
arrow-up1160arrow-down1external-linkThis week in KDE: looking forward towards Plasma 6.1pointieststick.comJustin@lemmy.kde.social to Linux@lemmy.mlEnglish · 3 months agomessage-square14fedilinkcross-posted to: news@lemmy.linuxuserspace.show
minus-squareISOmorph@feddit.delinkfedilinkarrow-up2·3 months agoThe command itself isn’t complex: YDOTOOL_SOCKET="$HOME/.ydotool_socket" ydotool key 28:1 28:0 The hard part is getting ydotool to run on boot for your user (no sudo). I had to create a bash script to run on login with the following line: ydotoold --socket-path="$HOME/.ydotool_socket" --socket-own="$(id -u):$(id -g)" It’s a bit hacky but it works.
minus-squaredeliriousn0madlinkfedilinkarrow-up1·3 months agoThank you, I didn’t know about ydotool, I’ll get it working on openSuse
The command itself isn’t complex:
YDOTOOL_SOCKET="$HOME/.ydotool_socket" ydotool key 28:1 28:0The hard part is getting ydotool to run on boot for your user (no sudo). I had to create a bash script to run on login with the following line:
ydotoold --socket-path="$HOME/.ydotool_socket" --socket-own="$(id -u):$(id -g)"It’s a bit hacky but it works.
Thank you, I didn’t know about ydotool, I’ll get it working on openSuse