piengineering / x-keys_linux Goto Github PK

The solutions to this error seem to be about as varied as the environments it occurs in. Not sure where to go from here.

On Ubuntu Studio 19.04, x86_64.

While setting up an "xkeys-sdk" package for my favoured distro, I noticed that pietestgui was being correctly build (now with Qt5) but was not being installed. I just submitted PR #7 to fix that.

I noticed that the README.txt still refers to QT 4 rather than Qt5 - do you want a PR to correct that? Also, these days README.md is more usual, allowing visually nicer rendering - bold text, headlines, live links etc.

Do you have a Pi Engineering or X-Keys logo available in (preferably) svg format that could be added to the repo? If that were available, I could add the means (via a .desktop file) for pietestgui to appear in standard Linux menus. A logo is not strictly needed for that but would be nicer if a thumbnail appears with the menu item.
[edit] I just submitted PR #9 which adds a working .desktop file.

Also, what do you think about a new release?. The last one here was 1.0.0 quite a while ago. I noticed a pihid32-2.0.0 at your developer website dated 2017. Maybe a 3.0.0 release here would be a good way to push the new Qt5 era.

Hi,

How is this repository licensed? I see no LICENSE file, nothing in the README, and several files contain:

TODO LICENSE HERE

This makes it very difficult to use legally (e.g. in a Linux distribution).

Qt4 is pretty old now. I've submitted PR #5 which makes changes for Qt5.

new issue

I built as per the instructions without incident, and attempted to run the demo program build/testgui/pietestgui. I see a GUI window, but when I click start, I get:

`Error Setting up PI Engineering Device`

and then the program crashes if I try to actually do anything.

I instrumented the program a little and discovered that the error code (which the programmer didn't take the time to put in the error message) is 205: PIE_HID_SETUP_CANNOT_OPEN_READ_HANDLE and the path that it's trying to open at that point is 0003:0010:00 (whatever that means).

Here's what's printed on the console.

Continuing, vid: 2222 pivid: 5f3
Continuing, vid: 2222 pivid: 5f3
Continuing, vid: 2222 pivid: 5f3
Found XKeys Device:
    PID: 0405
    Usage Page: 000c
    Usage:      0001
    Version: 256

Found XKeys Device:
    PID: 0405
    Usage Page: 0001
    Usage:      0006
    Version: 256

Found XKeys Device:
    PID: 0405
    Usage Page: 0001
    Usage:      0002
    Version: 256

I'm running into a similar situation as #1
however, copying the sample udev file to /etc/udev/rules.d does not solve anything.

GUI error message is the same (Error Setting up PI Engineering Device) and the console output when clicking [start] is the same:

xkeys$ build/testgui/pietestgui 
Continuing, vid: 24f0 pivid: 5f3
Continuing, vid: 24f0 pivid: 5f3
Continuing, vid: 46d pivid: 5f3
Continuing, vid: 46d pivid: 5f3
Continuing, vid: 46d pivid: 5f3
Continuing, vid: 764 pivid: 5f3
Found XKeys Device:
	PID: 0405
	Usage Page: 000c
	Usage:      0001
	Version: 256

Found XKeys Device:
	PID: 0405
	Usage Page: 0001
	Usage:      0006
	Version: 256

Found XKeys Device:
	PID: 0405
	Usage Page: 0001
	Usage:      0002
	Version: 256

Segmentation fault (core dumped)

(The segfault happens when I click any button other than [start], [stop], [quit], or [clear].)

I have an xkeys XK-24, running linux (ubuntu 17.10).

thanks!

As mentioned elsewhere, there isn't a single tag/release or release since 2011. That makes it hard to know whether the current commit is at all stable and/or tested. To fix this someone with commit access needs to run:

git tag 1.5
git push --tags

Assuming version 1.5 is correct, which is what is currently in the .desktop file. That will create a tarball on GitHub for the repo, assuming what's currently committed is ready for release.

As a follow up task... navigate to the GitHub tags page, and create a "release" based on the tag. During the "release" process, you can attach RPM and DEB files... which will make installation much easier.