-
-
Notifications
You must be signed in to change notification settings - Fork 14k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xow: libusb buggy #135678
Comments
This depends on upstream releasing 1.0.25, which they said they'd do soon-ish. So I guess it's best to wait for that? I don't think the patch would apply cleanly, but haven't tried. |
I see, then I'll have to use my patch until then. For others who might run into this problem. { inputs = { libusb.url = "github:steav005/xow/0fe9cd9"; }; And override the used {
nixpkgs.config.packageOverrides = pkgs: {
xow = pkgs.xow.overrideAttrs (orig: {
version = "pre-1.0.25";
buildInputs = [ inputs.libusb.packages.x86_64-linux.libusb ];
});
};
} This way only the used libusb is touched |
They are getting close to a release: libusb/libusb#777 |
libusb-1.0.25 was released |
I made a PR, but haven't done any testing yet. If anyone has some spare time, testing would be appreciated. |
Update was released and packaged. Hopefully this solves your issue and the need to carry your own overlay/patches. Reopen if there's still issues (you may have to wait until it's through staging). |
Followed this guide: https://dee.underscore.world/blog/home-manager-flakes/ But I don't understand where to put the override: NixOS/nixpkgs#135678 (comment) Build: apply-users.sh cd /home/reinis/dotfiles/nix/home-manager/reinis nixFlakes build '.#homeConfigurations."reinis@localhost".activationPackage'
Checklist
Project name
nix search
name: xowNotify maintainers
maintainers: @jansol
Note for maintainers
Xow itself is not out-of-date, but the used libusb is known to be buggy.
There are multiple reports of high cpu usage which can be fixed by using the latest libusb:
I was able to use the official libusb repo within a flake for circumventing the CPU issue
sevenautumns/xow@5e469a3
The text was updated successfully, but these errors were encountered: