Luna

@hipersayanX https://gist.github.com/Lunarequest/9f8585f82b4d5ad6d870e43aa9a4e254

It looks like you need to add this to the cxxflags `-include /usr/include/c++/11*/limits` based since gcc 11 https://stackoverflow.com/questions/4798936/numeric-limits-was-not-declared-in-this-scope-no-matching-function-for-call-t or explicitly add `#include ` to any files that use `std::numeric_limits`

manually patching the file and adding `#include ` fixed the compile issue

Okay will switch

I've gotten a working flatpak using this commit edab00879feb32311383d0d7cac5e3c946f4fced. There are some things that aren't possible like using the virtual web cam support and privilege escalation as suid binaries can't...

There isn't really a need to integrate into deploy tools, flathub handles the building and publishing of flatpaks. Flathub also has https://github.com/flathub/flatpak-external-data-checker which can keep the dependencies up to date...

> > There are some things that aren't possible like using the virtual web cam support and privilege escalation as suid binaries can't run in a flatpak > > Can...

I have tried the appimage and it works there, I would like to resolve the issue in the flatpak since it doesn't effect archlinux but fedora 35.

It looks like an issue with scard. I'm not to sure why it is caused ``` Traceback (most recent call last): File "/app/lib/python3.9/site-packages/ykman/device.py", line 139, in scan_devices devs = list_devs()...

I believe its an issue with fedora in some form, not sure what about fedora 35 causes the issue