Arch Linux User Repository

PLEASE CONSIDER USING chrysalis-bin, using the system Electron executable as this package does is (according to upstream developers) known to cause issues, bundling the project one here goes against Arch packaging guidelines and runs into other issues. This arrangement works for some tasks (me and my Atreus keyboard are happy) but not others (e.g. see reports below of not being able to flash Model 01s). If you just want your keyboard to work and be supported by upstream the -bin package is the way to go. If you a source purist and want to debug issues yourself, go for it.

If you have some problem while using chrysalis installed from this package, try to use chrysalis-bin (from AUR). chrysalis-bin use the AppImage which is the official way to go.

For my part I wasn't able to upgrade the firmware of my keyboardio model 100 with this package, while I have no problem with chrysalis-bin.

I think the 60-kaleidoscope.rules file may need to be moved to /usr/lib/udev/rules.d/. I tried to use this with the Model 100 and couldn't get it to work, and flashing the Kaleidoscope firmware also failed with a LIBUSB_ERROR_ACCESS error. I managed to solve both issues by symlinking the rules file:

# ln -s /usr/lib/chrysalis/static/udev/60-kaleidoscope.rules /usr/lib/udev/rules.d/

@xeruf Because I made a mistake and refactored code after I built it as a test. And apparently I wasn't thinking very well because that syntax was bogus.

Why is the binary now called "stdin"?

@gishten I just locked this to Electron 12. Hopefully that works for you.

For future reference I'm usually happy to accept patches; email or post in comments (using git format-patch) or open a PR to this repo.

I've run into the issue that was already reported here https://github.com/keyboardio/Chrysalis/issues/713, and confirmed that electron 13 and 14 were incompatible with chrysalis 0.8.4-1 on my newly updated system. Only when rolling electron back to version 12 did it start up properly, I recommend that this package is updated to reflect that.

This started segfaulting for me when the latest bump to Electron 11 hit. I bumped the release just now but that doesn't fix the segfault issue. I tried downgrading it to Electron 10 and playing around with other things but haven't found the source of the trouble yet. Since the bump seems unrelated I passed it through, but 0.8.1 was broken too (it worked when it first came out, but not for later builds).

building it in clean container showed that 'git' 'node-gyp' makedepends are missing.

Alse namcap is showing following for a built package:

chrysalis W: ELF file ('usr/bin/chrysalis') lacks FULL RELRO, check LDFLAGS.
chrysalis W: ELF file ('usr/bin/chrysalis') lacks PIE.
chrysalis E: Dependency zlib detected and not included (libraries ['usr/lib/libz.so.1'] needed in files ['usr/bin/chrysalis'])
chrysalis W: Dependency included and not needed ('fuse2')
chrysalis W: Dependency included and not needed ('uucp')

So I've added libz to depends.

Even aftervards I have the same issue as @xerus

Doesn't work for me :/

❯ chrysalis
This doesn't look like a squashfs image.

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
open dir error: No such file or directory

It is probably worth putting a note here that this is not the package people will have previously installed. If you are looking for the prebuilt AppImage that is available on the github releases, this has moved to chrysalis-bin