I suggest that all files in the repository should end with a newline. Rationale: here.

Ideas for outlining the new feature/plan roadmap.

CKB Randomly hangs on Ubuntu 16.04 with a simple rainbow effect running.
Attaching strace to the main process reveals that is waiting for a child to finish.

strace: Process 17818 attached
futex(0x2472d74, FUTEX_WAIT_PRIVATE, 1, NULL

In this case, the only child is ckb-wave, attaching strace to it shows

strace: Process 19971 attached
read(0, 

meaning it's waiting endlessly.

Lsof for the child pid:

# lsof -p 19971
COMMAND    PID    USER   FD   TYPE DEVICE SIZE/OFF     NODE NAME
ckb-wave 19971 tatokis  cwd    DIR   8,18    32768   901581 /home/tatokis
ckb-wave 19971 tatokis  rtd    DIR   8,18     4096        2 /
ckb-wave 19971 tatokis  txt    REG   8,18    22584  7275854 /usr/bin/ckb-animations/ckb-wave
ckb-wave 19971 tatokis  mem    REG   8,18  1864888  5970818 /lib/x86_64-linux-gnu/libc-2.23.so
ckb-wave 19971 tatokis  mem    REG   8,18  1088952  5970828 /lib/x86_64-linux-gnu/libm-2.23.so
ckb-wave 19971 tatokis  mem    REG   8,18   162632  5970609 /lib/x86_64-linux-gnu/ld-2.23.so
ckb-wave 19971 tatokis    0r  FIFO   0,10      0t0 95761765 pipe
ckb-wave 19971 tatokis    1w  FIFO   0,10      0t0 95761766 pipe
ckb-wave 19971 tatokis    2w  FIFO   0,10      0t0 95761767 pipe
ckb-wave 19971 tatokis   20w  FIFO    0,6      0t0    21002 /dev/input/ckb1/cmd
-----
# lsof -n -P | grep 95761765
ckb       17818                   tatokis   34w     FIFO               0,10          0t0   95761765 pipe
QXcbEvent 17818 17819             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
gmain     17818 17820             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
gdbus     17818 17821             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
dconf\x20 17818 17822             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
QThread   17818 17827             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
Kb        17818 17837             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
Qt\x20bea 17818 17839             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
Qt\x20HTT 17818 17840             tatokis   34w     FIFO               0,10          0t0   95761765 pipe
ckb-wave  19971                   tatokis    0r     FIFO               0,10          0t0   95761765 pipe

Tried some of the ways found in google but nothing works actually. Uninstalling CKB works good except the indicator lights ( which was also not working correctly with ckb)

Where as I type sometimes some keys will keep on doing the heat map effect on certain keys.
I had this issue with the newdev branch on the original CKB as well (i have the K70 LUX).
Is my settings by any chance wrong for the heatmap to work properly?
Here is a video demonstrating what is happening.
It does it on random keys at random intervals

Sometimes it works fine, but now my keyboard is not responding.
This problem repeats in both my macs(imac and mackbook pro)
https://puu.sh/tGvWB/0ab4722308.png
https://puu.sh/tGFdB/ccebb18dbd.png
ckb-dev-detect-report.gz

pid:1012
version:beta-v0.2.7
connected:

I have a scimitar RGB that I purchased this last christmas and installed ckb on my iMac. Initially ckb work perfectly, it recognized my mouse (after having updated the firmware with my windows laptop), and allowed me to create profiles and the like exactly as intended. The first time I restarted my computer things started to get fucky, ckb would recognize my Scimitar but whenever I clicked (left or right) the cursor would be sent to the upper left corner of the screen. Super weird problem that could potentially be fixed by a series of restarts. I got fed up with this and decided to uninstall and try a binary install, so I installed Xcode, installed QT 5.8, and used the quick install. This has gotten rid of the top left corner problem, however now CKB won't recognize the mouse at all, I can still use it to the extent of the left and right click but I can't map the number pad on the side. I've tried the Mattranger version as well as version 0.2.6 but as of now I cannot get ckb to recognize my mouse anymore.

So i have tried with ccMSC's software and it recognizes my Scimitar RGB but not my k70 LUX RGB. Some people told me to come to here as it is a more updated fork of it. It recognizes my mouse but doesn't change the colors, just stays as default. And my k70 lux rgb is not recognized at all.

--- Please help if you can. :D

Hi there, been pulling my hair out for hours trying to get the CKB software to pick up my K70 LUX RGB. It's new, I've force updated the firmware on Windows and I'm running macOS Sierra 10.12.2. I've installed Xcode and the command line tools for Xcode as well. Ensured I'm running the correct version of Qt which is 5.6.2. Attached my log which has tons of errors, hopefully that helps.
log.txt

The driver currently works fine, but I wonder if anyone has any idea about the slow loading. There are also some error messages. I'm just wondering if this is specific for only this keyboard model (K70 LUX non-RGB), or if the other keyboards suffer from this, too. Maybe there is still something missing in the driver for this specific model? (I was the one that added initial support for it in ccMSC/ckb#530)

When loading the driver, it takes almost a minute to get the keyboard working, and this is on a fast i7 platform. The keyboard is a K70 LUX non-RGB keyboard with latest firmware. Linux kernel is 4.9.4 on Fedora 25. I'm now running ckb-next master from 2017-01-20.

During boot the following messages are logged:

jan 22 15:58:30 yggdrasil kernel: usb 3-9: unable to read config index 0 descriptor/all
jan 22 15:58:30 yggdrasil kernel: usb 3-9: can't read configurations, error -110
jan 22 15:58:30 yggdrasil kernel: usb 3-9: new full-speed USB device number 7 using xhci_hcd
jan 22 15:58:30 yggdrasil kernel: usb 3-9: New USB device found, idVendor=1b1c, idProduct=1b36
jan 22 15:58:30 yggdrasil kernel: usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
jan 22 15:58:30 yggdrasil kernel: usb 3-9: Product: Corsair Gaming K70 LUX Keyboard
jan 22 15:58:30 yggdrasil kernel: usb 3-9: Manufacturer: Corsair
jan 22 15:58:30 yggdrasil kernel: usb 3-9: SerialNumber: 16030015AEB89C4755BB595DF5001940
jan 22 15:58:30 yggdrasil kernel: input: Corsair Corsair Gaming K70 LUX Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/0003:1B1C:1B36.0002/input/input7
jan 22 15:58:30 yggdrasil kernel: hid-generic 0003:1B1C:1B36.0002: input,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:00:14.0-9/input0
jan 22 15:58:30 yggdrasil kernel: input: Corsair Corsair Gaming K70 LUX Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.1/0003:1B1C:1B36.0003/input/input8
jan 22 15:58:30 yggdrasil kernel: hid-generic 0003:1B1C:1B36.0003: input,hiddev0,hidraw2: USB HID v1.11 Keyboard [Corsair Corsair Gaming K70 LUX Keyboard ] on usb-0000:00:14.0-9/input1
jan 22 15:58:30 yggdrasil kernel: usbhid 3-9:1.2: couldn't find an input interrupt endpoint

When unloading and loading the driver again, the following messages are logged (see the attached file ckb_upgrading.txt). (the log is actually from when updating the driver with dnf from an older rpm package to a later one).

ckb_upgrading.txt

At the point where "Connection timed out" and "usbfs: USBDEVFS_CONTROL failed cmd ckb-daemon..." is appearing at the end of the log, the keyboard starts working (possibly at the point "jan 22 18:40:19 yggdrasil systemd[1]: Reloading."), but the error messages are still logged a while after the keyboard is working. Then after about 20 seconds the messages stop and don't repeat again.

The new democratically selected name for this for is now ckb-next. To give everyone fair warning, I'll be changing the repo name to 'ckb-next' tomorrow morning, 7:00AM (GMT-5). So, be prepared update any remotes then.

The keyboard is detected and connected to by ckb-daemon.

The issues so far:

• The keyboard layout in ckb is incorrect, as it is the regular k95 layout where the k95 Platinum has a slightly different key-set (6 G-keys and the top rgb bar).
• More drastically: when starting the ckb client application the keyboard stops working. The animation that was already playing on the keyboard (HW profile) stays on but no key presses are registered until I quit the client and re-plug the keyboard.

@light2yellow and I are both working on the conversion from qmake to cmake. We'll be using this issue to track progress and note issues related to building with cmake.

• Move VERSION into CMake build script.
• Use sys quazip if exists or warn and build from included.

This issue comes from the original CKB driver but still present on this fork:

ccMSC/ckb#534

This Issue is for me to remember. But if someone is faster than me :-)
Scenario is as follows:

1. open ckb
2. duplicate one of the profiles on the left (tested with KB K95RGB)
3. delete the upper one of the two siblings
4. crash.
   Crash-protocol from gdb ist here:
   Absturz-beim-Profillöschen.txt
   It is reproducable an error (nil-ptr) somewhere in the button-handler (action).

There is currently a package for the original ckb, but not for ckb-next. I would love to see this put in the AUR.

@tatokis I saw that in the issue ccMSC/ckb#549 you were talking to someone about the required Qt version. Do you or @fleischie have any opposition to making the Qt 5.6 minimum version an explicit requirement in the documentation? I've finally made some time to work on the CMake version, and I've made 5.6 the min there.

Also, @tatokis what did you mean by not 5.7? Not as in one doesn't need it?

I have done a lot of testing to why my wifi speeds and ping were so wonky and out of the blue I quit CKB and ran another speed test. This time, my speeds were normal and where they should be.

Is there a reason as to why this is occurring? Im not sure what kind of information I could provide but this is without a doubt the cause.

On MacOS Sierra 10.12.2

Thread 6 "ckb-daemon" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5be1700 (LWP 25990)]
0x00000000004094da in os_inputmain (context=0x8) at usb_linux.c:105
105	        urbs[2].buffer_length = MSG_SIZE;
(gdb) bt full
#0  0x00000000004094da in os_inputmain (context=0x8) at usb_linux.c:105
        kb = 0x624a38 <keyboard+248>
        fd = 3
        vendor = 6940
        product = 6931
        index = 1
        urbcount = 0
        urbs = 0x7fff00000015
#1  0x00007ffff7bc16ba in start_thread (arg=0x7ffff5be1700) at pthread_create.c:333
        __res = <optimized out>
        pd = 0x7ffff5be1700
        now = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737316263680, 1718746363551489728, 0, 140737335160399, 140737316264384, 140737219939488, -1718723823047860544, -1718728203071054144}, 
              mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = <optimized out>
        pagesize_m1 = <optimized out>
        sp = <optimized out>
        freesize = <optimized out>
        __PRETTY_FUNCTION__ = "start_thread"
#2  0x00007ffff78f782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

From what I've gathered so far, the urbcount isn't supposed to be 0.
This broke ever since ccMSC updated the USB handling code to work with newer firmware versions.

If so, might be a good idea to note it in the readme.

Thanks!

macOS Sierra 10.12.2 & K70 RGB LUX

Attempt 1: Packaged app = no device recognised.
Attempt 2: ZIP file = ./quickinstall creates multiple warnings (too many to post right here).
Attempt 3: Building from source file =

"/Users/Alisha/Desktop/ckb-newdev/src/ckb-daemon/os.h:70: warning: 'CLOCK_MONOTONIC' macro redefined [-Wmacro-redefined]
#define CLOCK_MONOTONIC 1
^"

/Users/Alisha/Desktop/ckb-newdev/src/ckb-daemon/os.h:72: error: typedef redefinition with different types ('int' vs 'enum clockid_t')
typedef int clockid_t;
^
I tried the fix that was in another thread, but changing the code lead to over 400 issues being produced.

Please help, I've tried downloading patches and all sorts, following all the trending solutions.
None have worked. Am I missing something here?

My keyboard works fine on a windows VM.

@light2yellow @tatokis @ccMSC

[edit]: I FIXED IT OMG

Hallo there,

I've stumbled upon a weird bug, whenever the ckb daemon is running Alsa/PulseAudio won't recognize my USB Headset Microphone correctly.
If i disable ckb and reboot the Microphone works just fine.

Headset: Corsair Void USB RGB
OS: Linux Mint 18 w/ kernel 4.9.0-040900-lowlatency

I also had this Issue on Fedora 25 w/ kernel 4.8 and Arch Linux w/ kernel 4.8

Mac OS X 10.10.5, K70 LUX, QT 5.6, Xcodes command line tools installed. Already connected to a Windows PC and updated the firmware.
After hours of reading and troubleshooting, I still cannot get any version to build. The .pkg version of the old ckb is the only thing that actually installed on my machine, and that doesn't help since my LUX is not supported by it, and thus the device is not recognized by it. I am still able to type, however.
At the end of compiling using the quickinstall script, I always get an error displayed in the Terminal, and a ckb.app IS made, but it's "damaged or incomplete".

I will paste what the errors are that I am getting:

In file included from main.cpp:1:
In file included from ./mainwindow.h:4:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtGui.framework/Headers/QCloseEvent:1:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtGui.framework/Headers/qevent.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtGui.framework/Headers/qwindowdefs.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qglobal.h:1110:
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:5: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
    ^
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:48: note: non-literal type 'QAtomicInteger<int>' cannot be used in a constant expression
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
                                               ^
In file included from mainwindow.cpp:1:
In file included from ./ckbsettings.h:4:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/QSettings:1:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qsettings.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qobject.h:40:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qobjectdefs.h:41:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qnamespace.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qglobal.h:1110:
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:5: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
    ^
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:48: note: non-literal type 'QAtomicInteger<int>' cannot be used in a constant expression
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
                                               ^
In file included from main.cpp:1:
In file included from ./mainwindow.h:9:
In file included from ./kbwidget.h:7:
In file included from ./kb.h:7:
In file included from ./kbprofile.h:9:
In file included from ./kbmode.h:6:
In file included from ./kbbind.h:10:
./keyaction.h:164:44: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline void operator=(const KeyAction& rhs) {}
                                           ^
./keyaction.h:165:39: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline KeyAction(const KeyAction& rhs) : QObject() {}
                                      ^
2 warnings and 1 error generated.
In file included from kbwidget.cpp:2:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtWidgets.framework/Headers/QFileDialog:1:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtWidgets.framework/Headers/qfiledialog.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qdir.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qstring.h:41:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qchar.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qglobal.h:1110:
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:5: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
    ^
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:48: note: non-literal type 'QAtomicInteger<int>' cannot be used in a constant expression
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
                                               ^
In file included from mainwindow.cpp:2:
In file included from ./kbmanager.h:8:
In file included from ./kb.h:7:
In file included from ./kbprofile.h:9:
In file included from ./kbmode.h:6:
In file included from ./kbbind.h:10:
./keyaction.h:164:44: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline void operator=(const KeyAction& rhs) {}
                                           ^
./keyaction.h:165:39: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline KeyAction(const KeyAction& rhs) : QObject() {}
                                      ^
make[2]: *** [release/main.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from colorbutton.cpp:1:
In file included from ./colorbutton.h:4:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtWidgets.framework/Headers/QPushButton:1:
In file included from ../../../../Qt5.6.2/5.6/clang_64/lib/QtWidgets.framework/Headers/qpushbutton.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtWidgets.framework/Headers/qabstractbutton.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtGui.framework/Headers/qicon.h:37:
In file included from /Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qglobal.h:1110:
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:5: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
    ^
/Users/<username removed>/Qt5.6.2/5.6/clang_64/lib/QtCore.framework/Headers/qatomic.h:155:48: note: non-literal type 'QAtomicInteger<int>' cannot be used in a constant expression
    QAtomicInt(int value = 0) Q_DECL_NOTHROW : QAtomicInteger<int>(value) {}
                                               ^
In file included from kbwidget.cpp:7:
In file included from ./fwupgradedialog.h:7:
In file included from ./kb.h:7:
In file included from ./kbprofile.h:9:
In file included from ./kbmode.h:6:
In file included from ./kbbind.h:10:
./keyaction.h:164:44: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline void operator=(const KeyAction& rhs) {}
                                           ^
./keyaction.h:165:39: warning: unused parameter 'rhs' [-Wunused-parameter]
    inline KeyAction(const KeyAction& rhs) : QObject() {}
                                      ^
1 error generated.
mainwindow.cpp:257:64: warning: unused parameter 'reason' [-Wunused-parameter]
void MainWindow::iconClicked(QSystemTrayIcon::ActivationReason reason){
                                                               ^
make[2]: *** [release/colorbutton.o] Error 1
3 warnings and 1 error generated.
kbwidget.cpp:168:91: warning: unused parameter 'previous' [-Wunused-parameter]
void KbWidget::on_modesList_currentItemChanged(QListWidgetItem *current, QListWidgetItem *previous){
                                                                                          ^
make[2]: *** [release/mainwindow.o] Error 1
3 warnings and 1 error generated.
make[2]: *** [release/kbwidget.o] Error 1
make[1]: *** [release] Error 2
make: *** [sub-src-ckb-make_first] Error 2

ANY help at all is appreciated. Thank you.

I connected my laptop up to my usb hub this morning and keyboard lit up as usual. However, i couldn't type, nothing was being registered. So I quit CKB keyboard went white like usual and reloaded it but still keys wouldn't be registered when typing. At that point i was running the ckb-beta v0.2.7 from ccMSC. I deleted that CKB and downloaded the master version from here. Once it installed keyboard lit up with original animations and seemed to work for a minute but then the key bindings stopped registering and i believe the whole keyboard stopped being registered then. So i quit CKB again restored it and now it doesn't register the keyboard as being connected.

Using Strafe RGB on firmware 2.05 and ck�b�-next beta-v0.2.7

Any help would be appreciated,

James

Need a help.

I`m trying to build newfx branch using Ubuntu 16.04 x64 with gcc 5.4 / g++ 5.4.

Can you try to build newfx branch and provide me version of gcc and g++ you using?
Also, i will need "uname -a" information. Thanks.

So, in the issue below about adding in a donation link I replied that I could work on a site for ckb-next. @mattanger , I know you said you would rather produce a stable release first; however, C++ is not my forte, but html, css, javascript, etc are. I have the basic layout of the site down just adding in more information. If you have any questions or would like to see a very early version of it just let me know. The site is still very new, I have only put like 5 hours or so into it so it isn't great but, it should be ready if you ever decide to use it.

Hello,

I was able to get ckb working via building from git however, when I select the Change color button I get an error and the application window freezes. I am running arch on Gnome Shell. I have both a K70 LUX RGB keyboard and a Sabre RGB mouse. This issue happens when I try to use the change color buttons on both devices.

The output I get from the command line is listed below.

libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Scanning  "/usr/bin/ckb-animations/ckb-gradient"
Scanning  "/usr/bin/ckb-animations/ckb-heat"
Scanning  "/usr/bin/ckb-animations/ckb-mviz"
Scanning  "/usr/bin/ckb-animations/ckb-pinwheel"
Scanning  "/usr/bin/ckb-animations/ckb-rain"
Scanning  "/usr/bin/ckb-animations/ckb-random"
Scanning  "/usr/bin/ckb-animations/ckb-ripple"
Scanning  "/usr/bin/ckb-animations/ckb-wave"
Downloaded new firmware list. 6 entries found.
libpng warning: iCCP: known incorrect sRGB profile

(ckb:17110): GLib-GObject-WARNING **: cannot register existing type 'GtkWidget'

(ckb:17110): GLib-GObject-WARNING **: cannot add class private field to invalid type '<invalid>'

(ckb:17110): GLib-GObject-WARNING **: cannot add private field to invalid (non-instantiatable) type '<invalid>'

(ckb:17110): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(ckb:17110): GLib-GObject-WARNING **: cannot register existing type 'GtkBuildable'

(ckb:17110): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(ckb:17110): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(ckb:17110): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(ckb:17110): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(ckb:17110): GLib-GObject-WARNING **: cannot add private field to invalid (non-instantiatable) type '<invalid>'
fish: “ckb” terminated by signal SIGKILL (Forced quit)

So in the latest testing branch, support for the Harpoon gaming mouse was added. After testing this, I found that it wasn't showing up in CKB, I thought I should restart, and when I did, my mouse no longer worked, but it did show up in CKB now. I couldn't configure the colour because it was designed for a different mouse for testing purposes. I then went into the mouse settings in system preferences, and disconnected and reconnected my mouse, and it started working again, but it no longer showed up in CKB. Using the latest testing build.

Hello,

I'm attempting to run ckb-next on arch. The application opens but does not detect any of my devices. I've installed from the aur and tested using the git installer neither way seems to get the app to detect the devices. I've rebooted into Windows to verify that the official software works (it does).
The keyboard and mouse seem to work fine but I am unable to set any of t he RGB lighting on either product.

I've included the output from ckb-dev-detect for reference. Any help you could provide would be much appreciated.

ckb-dev-detect-report.gz

As far as I can tell, commands sent to the /dev/input/ckb1/cmd pipe are executed only if the CKB desktop application is actually running--they're ignored at all other times. Even if I open up the CKB GUI and suspend the process, CLI commands suddenly start working when they were ignored before.

It seems the daemon is performing some overeager check and not proceeding unless it has what it considers a stable connection to the GUI. Instead, it should dumbly accept line input from the pipe and execute the command provided.

I am using an M65 Pro mouse on Arch.

right now i have problem with building newfx branch on Ubuntu 16.04 (problem with pusleaudio library). Is it possible to have a complete manual how to build it?

Thanks.

Tried compiling the latest version using quickinstall and running K65 LUX RGB Firmware 2.0.5.

It seemed everything installed correctly as I had the application created however I get a no device detected error. I have tried all of the troubleshooting tips along with trying different USB ports but none have worked.

If there is any information I can provide to troubleshoot this please let me know and I will reply back with it.

Thanks!

Using version 0.2.4 on Mac OS 10.12.2 (Sierra)

I am currently maintaining ckb-git (based on master) and ckb-git-latest (based on testing) for Arch Linux. What should I do? Replace them with this fork? Create new ones? Wait until the fork becomes more stable and/or more developers join?

I cannot do this I do not believe even through a PR, but could we get a ckb beta 0.2.7 pkg release file for easy download and installation for users being directed here? I apologize if this is in the works and you guys are waiting on a few other items before doing a 0.2.7 release but I thought it might be nice to have. Of course, feel free to close this if it is in the works.

So, as the new project is launched I guess we need to partially rewrite README. For example, what do you think about donation buttons? I suggest that for now we should at least introduce the situation around the original ckb and then mark the donation buttons as the donations to the original author. Then packaging: at least for Arch Linux the links are valid for ckb and so we need to explicitly say this. And the general structure is rather cluttered and the file is too big to quickly find something. Maybe we should split it into TROUBLESHOOTING.md, CONTRIBUTON.md etc.? And other cosmetic changes that will make the text shorter and more clear. As a side note, there are a lot of people with corsair keyboards on mac knowing nothing about github and yet finding ckb repo (and maybe ckb-next) without any clue where to start with because the instructions are too long and a bit unclear.

Just wondering if there's a ckb counterpart to something like xset r rate 200 30. Not sure if I overlooked it or if it's not implemented.

Comment with your vote, or suggest another and I'll add it to the list.

Suggestions so far:
ckb-next >> 4 votes
ckb-ULTRA >> 1 vote
ckb-reloaded >> 1 vote
ckb2 >> 2 votes

I was doing a clean installation (all previous ckb files including daemon were removed manually) with ./quickinstall on sierra .2 and at the end got this:

Start ckb now [Y/n]? y
./quickinstall: line 228: 31827 Abort trap: 6           $APP --close > /dev/null 2>&1

I feel like there's a bug in src/ckb/main.cpp: isRunning(), look at this part of main():

case CommandLineClose:
        // If launched with --close, kill existing app
        if (isRunning("Close"))
            printf("Asking existing instance to close.\n");
        else
            printf("ckb is not running.\n");
        return 0;

This is supposed to print the statement in the else close, isn't it? Instead it doesn't print any of them. From what I googled about this error, it happens for the same reason when segfault does - no access to the particular chunk of memory allowed.

If a Corsair device isn't supported, leave a comment with the device details, and it may get added eventually. Good places to start with are the outputs of lsub, dmesg, etc for the Corsair device.

If new versions may be downloaded and installed, src/ckb/kbfirmware.cpp references a file in github which belongs to ccMSC (line 35):
(tableDownload = networkManager->get(QNetworkRequest(QUrl("https://raw.githubusercontent.com/ccMSC/ckb/master/FIRMWARE")));
That file is signed by him via GnuPG and needs an update for the M65RGB at least.

The incidents looks as follows:
My current FW is 1.19 for the M65RGB, but corsair has a new one (2.04).

So I get a hint in ckb to upgrade, but that hint is wrong: Because in the file mentioned the latest version is 2.02, it tries to update to this version, but gets 2.04 from corsair.

The manual activation was a bit difficult, because ckb did not recognize the "alt" key. I hacked the code and could burn the new FW manually. M65RGB runs fine.

I understand why you removed the donation link that was going to the original author, Please add a donation link so that those of use that wish to can still support the on-going development with this project.

I'm using Ubuntu with a K95 RGB and upgraded to CKB-next to try to fix a problem that CKB was having, but it only partially fixed my issue.

After quitting CKB-next and restarting it (or rebooting or logging out and back in), it always sets the keyboard back to the CKB demo profile. Unlike with the original CKB, it still remembers my custom profile, but I have to select it manually and I can't seem to get rid of or change the demo or HwProfile1 (they just come back like they were before). Furthermore, the custom profile loses all the animation settings and only remembers key colors.

What do I need to do to figure out why this is happening and help get it fixed? I would think it would be a permission issue on some configuration file or something else that is keeping it from saving changes, but I don't know enough about the software to know what to look for.

ckb does not connect to devices after waking up from sleep, and fails to connect to devices that have been plugged in some time after Linux has finished booting.

If you guys want to get full credit in github's system for your commits** to this project you need to tell them to disassociate you from the project you forked from. Since you've renamed the project it is probably a good time to do this. http://stackoverflow.com/questions/16052477/delete-fork-dependency-of-a-github-repository explains it in a bit more detail, but all you have to do is get in touch with github support and they'll take care of this for you in a few days. Putting in a link to the "old" project and asking for them to link to you would seem fair, but just getting the "forked from" killed off is all I'm asking for in this issue.

** commits to a fork don't show up in your personal profile graphs until they're accepted by the parent of the fork.

Using beta .27, I am unable to detect my K65 Non RGB in macOS.

When using ./qmake-auto && make or building via Qt Creator, an error is reported that it cannot find Frameworks available on macOS Sierra. It starts at Availability.h but I'm quite positive that the error persists immediately after.

Here's what is shown after running ./qmake-auto && make:

➜  ckb git:(master) ./qmake-auto && make
Info: creating stash file /Users/username/Documents/develop/github/ckb/.qmake.stash
cd src/ckb-daemon/ && ( test -e Makefile || /Users/username/Qt/5.7/clang_64/bin/qmake /Users/username/Documents/develop/github/ckb/src/ckb-daemon/ckb-daemon.pro -o Makefile ) && /Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile 
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile.Debug
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -c -std=gnu99 -Wno-unused-parameter -Werror=all -g -fPIC -DCKB_VERSION_STR=\"`cat /Users/username/Documents/develop/github/ckb/src/ckb-daemon/../../VERSION`\" -I. -I/Users/username/Qt/5.7/clang_64/mkspecs/macx-clang -o debug/device.o device.c
In file included from device.c:1:
In file included from ./command.h:4:
In file included from ./includes.h:4:
./os.h:47:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^
1 error generated.
make[2]: *** [debug/device.o] Error 1
make[1]: *** [debug] Error 2
make: *** [sub-src-ckb-daemon-make_first] Error 2

If anyone has an suggestions to fix this problem but does not have access to macOS Sierra, I can test it out. I'm just not familiar enough with qmake and Qt to debug this one unfortunately. I thought I had an idea of what could fix this problem by modifying something in ckb-daemon.pro after doing some tests with a new clean project, but couldn't duplicate this solution in this project unfortunately.

If you need anymore details about this, I'd be happy to assist in any way I can.

For anyone who wants to suggest new features for the ckb driver. Please leave a reasonably detailed description of your idea and reasoning as to why it should be added. Thanks!

This error happened in the same way in the original ckb as well (the latest one available there). Upgraded to ckb-next last week (like Jan 26) but it didn't go away.

Let me know if there are any logs I can provide you with. It just happens randomly, but every day for sure.

This is a quick list to be used as a reference for which PRs have been merged from the original repository and which haven't.

• ccMSC/ckb#541
• ccMSC/ckb#530
• ccMSC/ckb#516
• ccMSC/ckb#514
• ccMSC/ckb#511
• ccMSC/ckb#508
• ccMSC/ckb#507
• ccMSC/ckb#467
• ccMSC/ckb#455
• ccMSC/ckb#437
• ccMSC/ckb#403
• ccMSC/ckb#367

You might notice that some pull requests are not listed here, despite being open.
That is because they were merged to the testing branch and then pulled into this fork.