SoftMaker/FreeOffice collects some system information upon unlocking the
product. But in doing so, it attempts to execute /bin/ls. If the execve
syscall fails, the whole unlock procedure fails. This works around that
by rewriting /bin/ls to the proper path.

SoftMaker Office restarts itself upon some operations, such changing the
theme and unlocking. Unfortunately, we do not have control over its
environment then and it will fail with an error. Starting SoftMaker
Office from scratch will then work.

Fixes #71228

- Updated repo owner

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/diffoscope/versions

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/elementary-wallpapers/versions

…temd-oneshot

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/fanficfare/versions

Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/tridactyl-native/versions

openxcom: 1.0.0.2018.10.08 -> 1.0.0.2019.10.18

unixODBCDrivers.msodbcsql17: add missing openssl dependency

diffoscope: 125 -> 126

…pers

pantheon.elementary-wallpapers: 5.3 -> 5.4

nixos/redis: Disable hugepages for redis via sysctl and not via a systemd-oneshot

nixos/seahorse: Use seahorse's askpass by default

zabbix: init at 4.4.0

softmaker-office: fix product unlock error

Signed-off-by: Austin Seipp <aseipp@pobox.com>