gondsman

Yes, it did work correctly some time ago. I started using ckb in the middle of august and it was working with the first version I tried. The issue is extremely weird as the driver itself does work. If I setup a key to launch yakuake it opens the terminal correctly, but only if it's already working. If I set it up to run konsole, it opens a new instance but only if there's already one open. I don't understand what the problem can be.

I'm not noticing any power consumption issue on my i5, the frequency scales normally. However, even compiling the latest testing version, binding a key to an external program still doesn't work correctly (I'm running plasma5, if that matters). It works if I setup a key to run yakuake as it's already running in the background, bu launching a new app doesn't work at all.

I'm 95% sure this is not an issue with ckb, but I have troubles binding my G keys to launch programs on linux. It used to work a few weeks ago, so I'm positive this is a plasma 5.4 quirk, but I'll ask here trying to troubleshoot it. Basically the option to launch a program doesn't work. The keys do work if I bind them to anything else. The commands are recognized somehow (I think) as binding a key to 'yakuake' successfully opens my yakuake window (as long as yakuake is already running). Binding them to whatever other program needs to be run (as simple as 'xterm') doesn't do anything. Is there a way to debug this issue? Thanks again!

This did the trick, thanks!

Corsair calls it European (EU). It's most definitely not the UK layout, the symbols are arranged differently (at least @ " ~ # and £ are). It's identical to the US layout apart from being ISO, so it has one more key and differently shaped enter and left shift. In linux the additional key is set up automatically as '<>' despite having '\|' printed on it. It is a particularly useful layout as I'm not a native English speaker and I switch between the US and my regional layout pretty often. Having one more key means I can directly map the keyboard to any international one without issues. EDIT: I realized that the picture I linked before didn't have all the symbols on the keys. Not finding any other picture online, I took a photo of my own keyboard: https://www.dropbox.com/s/wancsvocepbmzmi/IMG_20150814_195207.jpg?dl=0 On a different note, can I ask for one more feature (I know I'm annoying you, sorry). It's fairly minor, but would it be possible to set the application to open directly as a tray icon rather than a full window? Right now when I log in the window always opens by itself (which is good as I want the program to run, just I don't need to see it at every boot).

Good, now it works perfectly! One small feature request if possible, the software doesn't have an option to correctly set the layout of my K95 EU (it's basically an US ISO 105-keys keyboard). It has this layout: http://content.hwigroup.net/images/products_xl/130495/2/corsair-vengeance-k60.jpg apart from being a K95. Thanks!

Here it is (wow, I didn't think it was supposed to be so big). https://www.dropbox.com/s/lc5rnlkv3o3uooe/core.4010?dl=0 Let me know if you need more help. Thanks again!

Good job on the driver, it's fantastic that the community can step in to provide what should really be provided by Corsair itself. The fact that I couldn't use the G keys on my k95 on linux always bothered me way too much. At least my logitech mouse has an onboard memory, so even if I can't configure it from linux it still works there. Anyway, I've tried to install your software on my Archlinux and the driver runs fine, I can see my keyboard under /dev/input/ckb1. The frontend for the configuration though, segfaults when I run it ("segmentation fault (core dumped) ckb"). I can see the interface for a fraction of a second but then it crashes. Is there a way for me to provide debug data on this? Thanks a lot!