Issue by Mazhaa
_Sunday Dec 03, 2017 at 16:44 GMT_
_Originally opened as https://github.com/mattanger/ckb-next/issues/356_
I have the Corsair Strafe no Rgb keyboard and ckb-next 0.2.8 show me "No devices connected" when I plug my keyboard . Can someone help me ?
Comment by light2yellow
_Sunday Dec 03, 2017 at 17:33 GMT_
Output of launchctl list | grep ckb-daemon?
Comment by Mazhaa
_Sunday Dec 03, 2017 at 18:02 GMT_
- 0 com.ckb.ckb
1293 0 com.apple.xpc.launchd.oneshot.0x1000000b.ckb
There are this two things when I type launchctl list on terminal
Comment by light2yellow
_Wednesday Dec 27, 2017 at 13:24 GMT_
Sorry, I forgot to answer.
First of all, it looks like you did launchctl list | grep ckb instead of the above. Secondly, [newer] Strafe non-RGB was added after 0.2.8, so build the program from source. Thirdly, I probably forgot to mention sudo, I don't remember whether launchd requires sudo to view root jobs. So, in case it still isn't detected after being built manually, execute sudo launchctl list | grep ckb-daemon (and post it here). In case there will be no output, execute sudo launchctl load -w /Library/LaunchDaemons/com.ckb.daemon.plist.
Comment by monsonjeremy
_Thursday Jan 04, 2018 at 23:33 GMT_
I've noticed that this issue happens after restarting my macbook. It works fine when i reinstall CKB but as soon as i perform a restart i lose it :(
Comment by Ricardonacif
_Sunday Jan 07, 2018 at 18:18 GMT_
For me when I restart the computer it doesn't work. What I have to do to make it work is: kill the unplug keyboard, kill ckb-daemon process, open ckb appllication, then plug keyboard again. I believe it has something to do with starting the MacOS with the keyboard plugged in.
Comment by light2yellow
_Sunday Jan 07, 2018 at 18:50 GMT_
Anyways, with the default setup after quickinstall I cannot reproduce on hackintosh on 10.13.whatever.
As of now whenever the daemon is not running, GUI will show a message with the instruction you need to execute in your terminal. If that doesn't help, unplug the keyboard, wait ~30 seconds and plug it back in. Unless somebody provides a patch that fixes it or at least a repro, there's not much we can do with limited amount of time.
FWIW, I had to run ...
sudo launchctl unload /Library/LaunchDaemons/org.ckb-next.daemon.plist
sudo launchctl load -w /Library/LaunchDaemons/org.ckb-next.daemon.plist
... to get things working. I use a KVM between machine, and every time I switch it fails. Running this gets it working again.
Most helpful comment
FWIW, I had to run ...
... to get things working. I use a KVM between machine, and every time I switch it fails. Running this gets it working again.