Package: gnunet
Version: 0.15.3-4
Severity: important
I installed the gnunet package and the GNUnet daemon probably didn't
start successfully. I haven't change any config files.
"# service gnunet status" on a Debian Sid system reports:
●gnunet.service - A framework for secure peer-to-peer networking
Loaded: loaded (/lib/systemd/system/gnunet.service; enabled; vendor
preset: enabled)
Active: failed(Result: exit-code) since Sun 2022-01-30 19:54:54
CET; 30min ago
Process: 448 ExecStart=/usr/bin/gnunet-arm -s -c /etc/gnunet.conf
(code=exited, status=217/USER)
CPU: 1ms
Jan 30 19:54:54 debian systemd[1]: Starting A framework for secure
peer-to-peer networking...
Jan 30 19:54:54 debian systemd[448]: gnunet.service: Failed to determine
user credentials: No such process
Jan 30 19:54:54 debian systemd[448]: gnunet.service: Failed at step USER
spawning /usr/bin/gnunet-arm: No such process
Jan 30 19:54:54 debian systemd[1]: gnunet.service: Control process
exited, code=exited, status=217/USER
Jan 30 19:54:54 debian systemd[1]: gnunet.service: Failed with result
'exit-code'.
Jan 30 19:54:54 debian systemd[1]: Failed to start A framework for
secure peer-to-peer networking.
I belief that this behavior is not intended.
I first backported the package for myself to my Bullseye system and
tested it there. It probably has similar problems to the original
package from unstable. After that I installed the package on a freshly
installed (Debian 11 without GUI) and upgraded (to Unstable) VM. The
GNUnet daemon seems not to work out of the box there too I guess.
