Arch Linux User Repository

@yochananmarqos: Not to start a tug-of-war but Arch’ guidelines don’t mention /usr/local at all, so wouldn’t it be a stretch to say that it is forbidden to use that spot? It would help differentiate between regularly sourced and AUR-sourced files. (Otherwise, the only way to tell if one’s forgotten is to ask pacman.)

@Chromie: Services should be installed to /usr/lib/systemd/. Nothing should be installed to /usr/local/. See https://wiki.archlinux.org/title/Arch_package_guidelines#Directories

Might I suggest altering the path where the service unit files for systemd are going to be installed? Currently, those are written to /etc/systemd/ which, according to systemd.unit(5)*, is meant for "[s]ystem units created by the administrator". The same man page states that /usr/local/lib/systemd/ is meant for "[s]ystem units installed by the administrator". It would seem that having Pacman write our freshly packaged service unit files into /etc is somewhat... improper?

Hence, I suggest the following change to the PKGBUILD:

32: install -Dm644 "${srcdir}/opt/tuxedo-control-center/resources/dist/tuxedo-control-center/data/dist-data/tccd.service" "${pkgdir}/usr/local/lib/systemd/system/tccd.service"
33: install -Dm644 "${srcdir}/opt/tuxedo-control-center/resources/dist/tuxedo-control-center/data/dist-data/tccd-sleep.service" "${pkgdir}/usr/local/lib/systemd/system/tccd-sleep.service"

• https://man.archlinux.org/man/systemd.unit.5

I think the SHA256 hash for the source file tuxedo-control-center-bin.install is incorrect in the current PKGBUILD.

after update of package tuxedo-control-center does not start from autostart on gnome wayland or wayfire. So i tried to start from console:

$ tuxedo-control-center
[2982:0329/120914.557864:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. 
Rather than run without sandboxing I'm aborting now. 
You need to make sure that /opt/tuxedo-control-center/chrome-sandbox is owned by root and has mode 4755.
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

The file "/opt/tuxedo-control-center/chrome-sandbox" has mode 755 at this time and is owned by root. After running

# chmod 4755 /opt/tuxedo-control-center/chrome-sandbox

tuxedo-control-center starts as expected.

@a_manthey where are you getting that message? I tried to reproduce the issue, but without success. journalctl | grep -E "SUID sandbox" founds nothing. I can add it, but without being able to reproduce the problem myself, I'd like to do so reluctantly

After every update i get this error:

The SUID sandbox helper binary was found, but is not configured correctly. 
Rather than run without sandboxing I'm aborting now. 
You need to make sure that /opt/tuxedo-control-center/chrome-sandbox is owned  by root and has mode 4755.
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

Adding this line to PKGBUILD solved it:

chmod 4755 "${pkgdir}"/opt/tuxedo-control-center/chrome-sandbox

When running this with linux kernel 6.2.6 in sway with wayland I get the following error:

The futex facility returned an unexpected error code.
[1]    5880 IOT instruction (core dumped)  tuxedo-control-center oruud

Though the tccd service starts successfully. Anyone faced a similar issue?

I made it working by uninstalling all dmks modules (and dkms itself) also cleaned the residual file in the src tree: /usr/src/tuxedo-keyboard-3.0.10 and /usr/src/tuxedo-keyboard-3.0.9, rebooted, then reinstalling this, and it worked

On Linux 5.15.62-1-lts, I installed tuxedo-keyboard version 3.0.9-1 (downgraded it from version 3.0.10-3) along with tuxedo-control-center-bin version 1.1.5-1. I rebooted and all was working as before.