Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](8616af08d9/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
As a result of #350268, the tlp NetworkManager dispatch script no longer worked. It creates a broken
link to `/usr/lib/NetworkManager/dispatcher.d/99tlp-rdw-nm`.
This removes the `/usr/` prefix so the script is pointing to the right file.
This allows viewing and/or modifying the tlp package used by the module,
which is especially important since it might be different from
`pkgs.tlp` due to RDW.
These daemons should not be stopped, as they're foundational to a
proper functioning of the system. When switching configurations, they
only need a restart instead of that stop/start cycle.
Since version 6.0.0 asusd supports multiple aura devices. Since each of
them may have a different configuration, the `aura.ron` file, previously
used for configuration, is now ignored in favor of device specific
`aura_{prod_id}.ron` configuration. This change adds support for
specifying multiple aura configs via `auraConfigs` attribute and removes
the old `auraConfig` attribute.
For a user to be able to scan with an USB scanner, it must have write access
to the corresponding file in /dev/bus/usb. Enabling the sane module
adds SANE's upstream hwdb file and udev rules to udev search path. The
hwdb file tags the scanner as `libsane_matched` and a builtin (from
systemd upstream) udev rule marks all `libsane_matched` devices as
uaccess. When a physical user logins, logind adds an acl allowing them
to write to the device.
Unfortunately, saned is a daemon. Therefore, uaccess has no effect for
it, and if no other udev rule changes the device to belong to the
scanner group or the lp group, (there are such rules, but they are not
complete enough, in that some scanners known by SANE rules are not known
by these rules), it will not be able to write to the scanner.
This solves this by adding a udev rule so that all libsane_matched
devices have an acl rules so that users in the scanner group can write.
A similar rule is present on Arch and Debian at least.
Note that we don't chgroup the file instead, because this posed problems
in the past: scanners are often also printers, and a device's group
cannot be simultaneously lp and scanner.
Fixes: https://github.com/NixOS/nixpkgs/issues/361981
