3hhh

Well, I'm sorry, but I cannot reproduce your issue.

> ``` > ***@***.*** ~]$ sudo journalctl --boot 0 | grep -i dhcp > Oct 20 17:20:03 sys-net NetworkManager[495]: [1666300803.8714] dhcp-init: Using DHCP client 'internal' > ``` Interesting. Mine on...

I double checked the salt state I apply to my `debian-11` template used by `sys-net-dvm`: It creates two root-owned 644 files: `/etc/NetworkManager/conf.d/use-dhclient.conf`: ``` [main] dhcp=dhclient ``` `/etc/dhcp/dhclient.conf`: ``` # Configuration...

So all of the above needs to be applied to the base template, i.e. `debian-11`. That might be a bit unclear in https://github.com/Qubes-Community/Contents/blob/master/docs/privacy/anonymizing-your-mac-address.md#anonymize-your-hostname. Btw I also tested different owners. That...

@tlaurion I just tested on `fedora-36` as well and it gave me the `dhcp-init: Using DHCP client 'dhclient'` log entry. So maybe you got something wrong, too? Btw on Fedora...

@tlaurion Maybe I'm missing something obvious here... but what is the point you want to make? I'm asking because I can see from the below that you did **not** deploy...

LOL. I just realized that neither `debian-11` nor `fedora-36` templates send the hostname anymore in their default configuration. I guess `NetworkManager` changed its behaviour. It would be nice if someone...

Well, it would be nice to identify the root cause of the different behaviour across templates then. At least on the `NetworkManager` end, the doc doesn't state any changes from...

> AFAIK, client icon_name property is readonly in our API. (As identified by the issue #3457, we indeed need to explicitly show this flag in the documentation) Yes, having it...

On 7/4/22 14:41, Lucas Schwiderski wrote: > On the topic of spec compliance: > >> The window manager will not change properties written by the client. >> - https://x.org/releases/X11R7.6/doc/xorg-docs/specs/ICCCM/icccm.html#client_properties >...