OpenRGBClient() fails on recent builds in linux about openrgb-python HOT 12 CLOSED

What versions of openrgb-python and openrgb are you using? Can you send screenshots of OpenRGB's software pane on the Information tab from each OS?

from openrgb-python.

I've tested with builds from the last week or so on linux and seen the same problem on each. Just built from source of the current master and I'll download the equivalent package on windows. Here's the linux screenshot:

Running openrgb-python 0.2.8 on linux, and I'll boot into windows and post the rest ASAP.

from openrgb-python.

Here's windows:

I didn't realize, but apparently I'm only running openrgb-python 0.2.5 on windows. I'll try updating now and see if it causes the same issue on windows.
Edit: the same version works fine on windows.

from openrgb-python.

Just to make sure that the version has nothing to do with the issue, can you try forcing v1 on linux?

cli = OpenRGBClient(protocol_version=1)

from openrgb-python.

Exact same message using v1, down to the byte that caused the error. I'll try downgrading to openrgb-python 0.2.5 on python to test that.

from openrgb-python.

Actually, here's a more important question: exactly which OpenRGB commit broke it?

from openrgb-python.

Okay I'm getting the same message on 0.2.5, which I was running on the same distro with no issues not very long ago. That's gotta mean the problem is coming from openrgb itself lol.
I haven't narrowed it down to the exact commit yet, but I'll try to do that now.

from openrgb-python.

I just realized that this looks very similar to #18, and you did recently add a device to OpenRGB. Might this function be returning something weird?

from openrgb-python.

Actually just narrowed it down, it stopped working on this commit, which ironically was also to add a device I requested. Thanks for your help!

from openrgb-python.

Yep, exactly the same problem as the issue you posted. I'm sorry to bother you for the same thing twice!
Thanks again for all your help.

from openrgb-python.

I or someone should probably implement @inlart's the solution to #18 across all HID devices in OpenRGB to prevent this from occurring again.

from openrgb-python.

Yeah, that's probably a good idea. I just borrowed his solution and recompiled, but it looks like the same problem is actually affecting my keyboard too, which I just added support for a few days ago.
I'll also stop starting my bug hunts over here, after making the issues on your repo when it's not to blame twice in a row lol. Thanks again!
Edit: patched the keyboard files too, and now it works flawlessly again.

from openrgb-python.