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
Avoid opening a new issue in case a similar one already exists (don't worry, we get the notifications for closed issues as well, it will be reopened if needed).
Keep unrelated issues separate (create a new one if you are sure yours is unique).
UseMarkdown to write on GitHub. Use triple backticks if copy-pasting more than one line.
Now, before you proceed even further, make sure you are following the recommendations above. It will save a lot of time for you and us in the future.
Devices information
Run ckb-dev-detect from the root of the source code tree:
$ ./ckb-dev-detect
Upload ckb-dev-detect-report.gz on GitHub with this issue.
kais-mbp:~ kaixu$ ./ckb-dev-detect
This script will collect information about the Corsair devices in your system.
Please make sure they are plugged in and press Enter.
2018-01-12 11:26:24.257 system_profiler[2088:173730] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
Done! Please send the following report to the developers.
Switch on the "Preview" mode for better reading experience.
Use it to put ticks and then switch back to write in the details where needed.
Before you proceed
README.md
in full..md
documents in the project's root. They contain more specific information.Now, before you proceed even further, make sure you are following the recommendations above. It will save a lot of time for you and us in the future.
Devices information
Run
ckb-dev-detect
from the root of the source code tree:$ ./ckb-dev-detect
Upload
ckb-dev-detect-report.gz
on GitHub with this issue.ckb-dev-detect-report.gz
New device support request
leave empty if you have no new device support requests
You should upload:
ckb-dev-detect-report.gz
is enoughFeature request
leave empty if you have no feature requests
What is the program's current behavior?
What would you like it to do instead?
Any other notes & comments?
Bug report
leave empty if you have no bug reports
General information
The keyboard seems to still use the layout from the Mac 'Input Sources' ('British') rather than the key bindings defined in ckb-next.
Source
(how and where did you get this program, e.g.: "
ckb-next-git
package in AUR" or "built manually using quickinstall script" or "pkg for macOS")ckb-next prebuild
Branch
(fill in if ckb-next was compiled manually, e.g.: "master" or "newdev")
Logs & crash reports
(any useful information - an OS crash report, debugger's backtrace, any non-standard way of usage (BIOS mode ...) etc.)
You should upload:
Linux:
ckb-dev-detect-report.gz
is enoughmacOS:
ckb-daemon
:ckb: Corsair RGB driver v0.2.8
[I] Root controller ready at /var/run/ckb0
[I] Connecting Corsair K70R Gaming Keyboard at /var/run/ckb1
[I] Registering EventTap for modifier keys.
[I] Starting input thread for /var/run/ckb1
[I] Setup finished for /var/run/ckb1
[W] hid_kb_translate (keymap.c:266): Got unknown key press 254 on EP 1
[I] Disconnecting /var/run/ckb1
ckb
(open another terminal):kais-mbp:~ kaixu$ sudo killall -9 ckb
Password:
No matching processes were found
kais-mbp:~ kaixu$
What is the program's current behavior?
Not using the key binding defined in ckb-next
What is the expected behavior of the program?
Using the key binding defined in ckb-next
Any other notes & comments?
Something else
if your issue is about something else, try your best to describe it here, otherwise leave empty
The text was updated successfully, but these errors were encountered: