Installation Command does not work, see: https://dnf.readthedocs.io/en/latest/command_ref.html
Please also check line 68: the (Fedora) "polkit" equivalent Debian package is called "policykit-1".
For reference: https://packages.debian.org/stretch/policykit-1
But I´m not sure if policykit-1 is needed, since with qubes-template-debian-9-minimal-4.0.1-201901271906 it is enough to
1) install the template,
2) [user@dom0 ~]$ qvm-run -u root debian-9-minimal xterm
3) bash-4.4# apt install qubes-core-agent-passwordless-root
4) update the template
Best Regards,
Vinzenz
Otherwise nm-applet is not able to control NetworkManager over dbus, and
you get the following error messages:
```
(nm-applet:19808): nm-applet-WARNING **: 17:24:56.716: disconnect_cb: Device disconnect failed: (1) org.freedesktop.NetworkManager.network-control request failed: not authorized
```
This is unfortunate, but I don't see a better way around it.
See also: https://groups.google.com/d/topic/qubes-users/b_yEFCMazuM/discussion
This patch changes all non-code, non-command instances of "DispVM" to
"DisposableVM". It also fixes a variety of orthographic errors
pertaining to this term, e.g., by correcting "Disposable VM" to
"DisposableVM".
This is for R4.0 and fedora-28-minimal, but might also apply to R3.2 (not tested). Without adding 'gnome-keyring' the user will not get the 'enter password' dialog when selecting a WiFi connection and has to enter the password under 'Edit connections...' | 'WiFi security' instead.
Without installing perl-Digest-MD5 and perl-Digest-SHA, the build will fail. The source code documentation does mention it but if one follows the route via Qubes Builder, it isn't mentioned.
When studying the document for 4.0 , I overlooked the fact that `qubes-core-agent-networking` is generally required for any network access, not just for using the minimal template as `sys-net` or `sys-firewall`.
I found the existing doc misleading, as it claims sudo is not installed. This misled me to try to install sudo, which dnf said was already there. Also, the fact that the template does not have passwordless root is not a bug and therefore the relevant install should not be described as a "fix" in the doc.
I have also included explicit instructions to enable passwordless root, which will also serve as an example to newcomers of how to install the packages listed in the following section.