EDIT: Downgrading to FW 1.30 also fixed my issues. That's unfortunate for my Windows usage of the 'board, but whatever, it's working. Again, thanks a bunch!!
First off: huge thank you for all the work you've done supporting the *nix crowd. I don't know if you're still around or if you've passed development, but here goes.
I'm a Linux noob, about to take Linux+ (I'm refreshing 4 certs and taking 12 new ones this year) and have somehow never touched it yet.
Fresh install of Fedora (4.4.9-300.fc23.x86_64), Gnome 3.18.2. I have a K65 and used the unpack->quickinstall method after pulling deps listed on the github. My keyboard was functioning as a keyboard before (sometimes F-keys and PgUp/PgDn would act funny) but I wanted to see how 'perfectly' I could get things running. This is mostly a learning experience for me--please, put the pitchforks down.
The instant I installed CKB I could no longer type. I've tried every combination of reboot/quit ckb/relaunch ckb/reconnect k65 possible. The funny thing is, with the check box to start on boot it will let me log in fine, but as soon as the login is finished, no more typing.
I did what you said to in this post and set Permissive, ensured driver was running (PID 900), and got the following output: (note: immediately after, K65 stopped functioning)
[wildcardNP@joker ~]$ /bin/ckb
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
I've had this device set up with my own very simple profile on Win7/Win10 for months, is that profile somehow breaking the driver because it's stored in device memory? How can I fix this?
