Package: nextcloud-spreed-signaling
Version: 1.2.2-1~bpo12+1
Severity: normal
Dear Maintainer,
* What exactly did you do (or not do) that was effective (or
ineffective)?
Installation of package through apt.
* What was the outcome of this action?
Systemd service cannot start due to namespace error.
* What outcome did you expect instead?
Systemd to be able to start the signaling service.
I noticed that the systemd service file contains an ExecPaths
instruction that excludes the location where the package installs the
binaries.
Currently v 1.2.2 (bookworm-backports, testing, and sid) ships with an
"ExecPaths=/usr/bin/signaling" whereas the binary is located at
/usr/bin/nextcloud-spreed-signaling-server.
Adjusting the ExecPaths to the actual file location makes the server
start as expected.
Best regards,
Gerald
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-17-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nextcloud-spreed-signaling depends on:
ii adduser 3.134
ii libc6 2.36-9+deb12u3
Versions of packages nextcloud-spreed-signaling recommends:
ii janus 1.1.2-1
ii nats-server 2.9.10-1+b3
nextcloud-spreed-signaling suggests no packages.
-- Configuration Files:
/etc/nextcloud-spreed-signaling/server.conf changed [not included]
-- no debconf information
