Nixpkgs version

• Unstable (25.05)

Describe the bug

My zwave-js-ui crashes with SIGSYS, I think in fchown?

workaround is systemd.services.zwave-js-ui.serviceConfig.SystemCallFilter = lib.mkForce [];

Steps to reproduce

1. start up zwave-js-ui
2. Configure a device
3. Crashes immediately and after every startup (now that it's configured to use a device)

Expected behaviour

Not to crash and for the server to keep running

Screenshots

No response

Relevant log output

Message: Process 82653 (node) of user 64428 dumped core.
                
                Module libgcc_s.so.1 without build-id.
                Module libstdc++.so.6 without build-id.
                Module libicudata.so.74 without build-id.
                Module libicuuc.so.74 without build-id.
                Module libicui18n.so.74 without build-id.
                Module libz.so.1 without build-id.
                Module node without build-id.
                Stack trace of thread 82672:
                #0  0x00007f61a8d07dcb fchown (libc.so.6 + 0x107dcb)
                #1  0x00007f61ac3050c0 uv__fs_copyfile (libuv.so.1 + 0x150c0)
                #2  0x00007f61ac30589a uv__fs_work (libuv.so.1 + 0x1589a)
                #3  0x00007f61ac2fc8c5 worker (libuv.so.1 + 0xc8c5)
                #4  0x00007f61a8c96a72 start_thread (libc.so.6 + 0x96a72)
                #5  0x00007f61a8d1a014 __clone (libc.so.6 + 0x11a014)

Additional context

No response

System metadata

• system: "x86_64-linux"
• host os: Linux 6.13.1, NixOS, 24.11 (Vicuna), 24.11.20250206.f5a32fa
• multi-user?: yes
• sandbox: yes
• version: nix-env (Nix) 2.24.12
• channels(root): "home-manager, nixos"
• channels(kuba): "home-manager, nixpkgs"
• nixpkgs: /nix/store/lap5laq2kl6ncr4jqa28inp6xqqq8kcw-source

Notify maintainers

@cdombroski

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.