Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#49687 - [minidlna] Systems service broken in 1.1.5-2
Attached to Project:
Community Packages
Opened by Simon Nagl (simonnagl) - Sunday, 12 June 2016, 15:10 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 June 2016, 17:03 GMT
Opened by Simon Nagl (simonnagl) - Sunday, 12 June 2016, 15:10 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 June 2016, 17:03 GMT
|
DetailsDescription:
I cannot start minidlna with the systemd file. Solution: Uncommenting "NoNewPrivileges=on" in "/usr/lib/systemd/system/minidlna.service" fixes the issue. Steps to reproduce: systemctl start minidlna.service systemctl status minidlna.service The last command gives this output: Jun 12 16:56:43 BananaPi systemd[1]: minidlna.service: Failed with result 'exit-code'. Jun 12 16:56:43 BananaPi systemd[1]: minidlna.service: Unit entered failed state. Jun 12 16:56:43 BananaPi systemd[1]: minidlna.service: Main process exited, code=exited, status=227/NO_NEW_PRIVILEGES Jun 12 16:56:43 BananaPi systemd[2712]: minidlna.service: Failed at step NO_NEW_PRIVILEGES spawning /usr/bin/minidlnad: Invalid argument Jun 12 16:56:43 BananaPi systemd[1]: Started minidlna server. |
This task depends upon

Seems to work fine here. Is this ARM specific?

Ping?