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#41761 - [systemd] systemd-networkd can't set hostname
Attached to Project:
Arch Linux
Opened by Ruben Kerkhof (ruben) - Saturday, 30 August 2014, 12:16 GMT
Last edited by Christian Heusel (gromit) - Tuesday, 05 September 2023, 18:08 GMT
Opened by Ruben Kerkhof (ruben) - Saturday, 30 August 2014, 12:16 GMT
Last edited by Christian Heusel (gromit) - Tuesday, 05 September 2023, 18:08 GMT
|
Detailssystemd-networkd can't set the hostname it receives from dhcp:
systemd-networkd[180]: eth0 : Could not set hostname: Permission denied This used to work in previous versions of systemd. Now that systemd-networkd doesn't run as root anymore, systemd-hostnamed needs a policykit rule to allow access, and upstream doesn't ship one yet. This probably also means polkit is now a hard dependency. This is upstream bug https://bugs.freedesktop.org/81626. I know this is an upstream issue, but can we at least ship the policy until they decided what to with it? Additional info: * package version(s) systemd 216-2 |
This task depends upon
Closed by Christian Heusel (gromit)
Tuesday, 05 September 2023, 18:08 GMT
Reason for closing: No response
Additional comments about closing: please open up a separate bug report if you still experience this issue
Tuesday, 05 September 2023, 18:08 GMT
Reason for closing: No response
Additional comments about closing: please open up a separate bug report if you still experience this issue
Sure does not....
> can we at least ship the policy until they decided what to with it?
Nope, that's not how Arch works. systemd is an enormous package, and I have enough trouble maintaining it on my own without bringing in distro local patches.
Ref: https://github.com/systemd/systemd/issues/13501