Qubes-prefs acting erratically in 4.2

User Support Testing Release
1

In 4.2, qubes-prefs seems to require --set sometimes, and other times it requires you not have --set depending on what value you are setting a property to.
Anyone have a idea what’s going on?

[user@dom0 qubes-scripts]$ qubes-prefs default_netvm sys-firewall
usage: qubes-prefs [--verbose] [--quiet] [--help] [--help-properties] [--hide-default] [--get] [--set]
                   [--default]
                   [PROPERTY] [VALUE]
qubes-prefs: error: no such property: 'default_netvm'

[user@dom0 qubes-scripts]$ qubes-prefs --set default_netvm sys-firewall
[user@dom0 qubes-scripts]$ qubes-prefs --set default_netvm sys-firewall
[user@dom0 qubes-scripts]$ qubes-prefs --set default_netvm sys-firewall
[user@dom0 qubes-scripts]$ qubes-prefs --set default_netvm sys-firewall-localnet
usage: qubes-prefs [--verbose] [--quiet] [--help] [--help-properties] [--hide-default] [--get] [--set]
                   [--default]
                   [PROPERTY] [VALUE]
qubes-prefs: error: no such property: 'default_netvm'

[user@dom0 qubes-scripts]$ qubes-prefs default_netvm sys-firewall-localnet
[user@dom0 qubes-scripts]$
2

The real issue here seems to be that the setting won’t happen if the current value of the property is “None”

I temporarily set the value of management_dispvm to None while I created a new-named disposable template for the job and now cannot set it to the new name.

And Oh By The Way I’m still on 4.1