Wootility inaccessible after running something using the SDK

[N00byKing]

This is a bit weird. If I run anything using the SDK (No matter if develop or master Branch), the Wootility will stop recognizing the Keyboard, even if the SDK Program exited cleanly, with the Wootility having been closed before running the Program.

So, it goes like this: Wootility recognizes Keyboard -> Close Wootility -> Run SDK Program until finished -> Wootility does not Recognize Keyboard upon reopening

Sample C++ Code:

#include <iostream>

#include "wooting-rgb-sdk.h"

int main() {
    std::cout << wooting_rgb_kbd_connected() << std::endl;
    std::cout << "G'day" << std::endl;
    wooting_rgb_close();
    return 0;
}

However, the SDK will continue to recognize the Keyboard. It's only the Wootility that doesn't.

[simon-wh]

Hmmmm, that behaviour is quite unusual. We're currently working on some improvements to the firmware side of RGB which hopefully will help with this issue. I assume you're on Linux, Arch?

[N00byKing]

Yep

[simon-wh]

Hmmm, that's what I've been using for my main dev machine up until recently and haven't run into that before. Hoping the firmware improvements happen to take care of it, should be pushing it pretty soon, will let you know when so we can see if it needs further investigation.

[simon-wh]

Updated firmware has been pushed to the Alpha channel, here's the link to the AppImage. The firmware version you'll want is >=v1.29

[N00byKing]

Currently away from my normal PC, but I have a laptop here that runs Manjaro.
Same Issue using 1.29.0 (on a different Machine!).

I ran the alpha-3.5.7 build, and the Issue persists using the same steps as described in the original Text. I start a Program that uses the SDK, start the Wootility, and it won't recognize the Keyboard anymore (Any RGB SDK Program will, though).
I also tested running as root (You won't harm my Devices right?), but, sadly, same Issue. Doesn't seem to have something to do with permissions.

The Hard Crash in #16 seems to be gone now though.

[simon-wh]

Currently away from my normal PC, but I have a laptop here that runs Manjaro.
Same Issue using 1.29.0 (on a different Machine!).

I ran the alpha-3.5.7 build, and the Issue persists using the same steps as described in the original Text. I start a Program that uses the SDK, start the Wootility, and it won't recognize the Keyboard anymore (Any RGB SDK Program will, though).
I also tested running as root (You won't harm my Devices right?), but, sadly, same Issue. Doesn't seem to have something to do with permissions.

Hmmm, yeah, I've been able to perfectly replicate it on my Arch machine. I'm trying to determine the root cause of the issue. Currently, the issue appears to be isolated to Linux

The Hard Crash in #16 seems to be gone now though.

Awesome!