When I start sys-net I can see the network-manager applet, but if I click on it it says "NetworkManager is not running..."
If I manually give
sudo NetworkManager then I can see all the wireless networks I usually see in my place (hence the network card is recognized) but when I try to connect to one of them I receive the message
(1) Not authorized to control networking.
I suspect there is some service that needs to be started when the VM boots that I haven't specified, but I don't know how to proceed.
Cheers,
Fab
Moreover, if I try to use the same template for sys-usb and then try to open some usb stick, I get the message:
Not authorized to perform operation (polkit authority not available and caller is not uid0), so again an authorization issue. I suspect this may have something to do with the procedure to make the minimal template passwordless ( https://www.qubes-os.org/doc/vm-sudo/ )
If someone has some insight about this I'd really appreciate it :)
Cheers,
Fab
Giving sudo dnf install polkit in the minimal template vm solves the authorization problems, both for sys-usb and sys-net.
Now I am able to use the minimal template as the underlying one for sys-usb, but I still have problems with sys-net.
sys-net keeps telling me that NetworkManager is not running. If I open up a terminal and give sudo NetworkManager then i can see the networks clicking on the wifi tray icon, but I can't connect. If I click on a network nothing happens (no error displayed, of any kind. Just nothing).
Any suggestions?
Cheers,
Fab
For future reference, problem solved. The packages
qubes-core-agent-nautilus
qubes-core-agent-networking
qubes-core-agent-network-manager
qubes-core-agent-passwordless-root
qubes-core-agent-dom0-updates
qubes-input-proxy-sender
qubes-usb-proxy
Are not included by default in the minimal template vm. The first one gives you the cute (send here/move there/open in dispVM) stuff in Nautilus.
The next two are (I suppose) to make networking not a pain in the bum.
The fourth one should do what is done in https://www.qubes-os.org/doc/vm-sudo/ for you.
The fifth one is needed if you are setting up a template you'll use as the underlying one for the vm that takes care of updating dom0.
The last two are to set up a template for sys-usb.
All this information was somewhere between here and the github issues page, but it should really (REALLY) be listed in https://www.qubes-os.org/doc/templates/fedora-minimal/ since nearly always one will end up needing at least one of the packages listed above.
At the moment setting up a template based on a minimal fedora distribution looks like a treasure hunt, and I am pretty sure it would save people a lot of energy and time to have this stuff added to the fedora-minimal reference page.
Cheers,
Fab
From here, dnf search qubes-core-agent gave me what I needed. I'd suggest to mention (at least) the existence of the qubes-core-agent-... packages in
https://www.qubes-os.org/doc/software-update-vm/
I'd also suggest to mention qubes-core-agent-passwordless-root in
https://www.qubes-os.org/doc/vm-sudo/
I am aware that building an entire operating system is a lot of work and there are literally thousands of packages, always changing, to consider. But pages like these should be kept up to date. I wouldn't suggest to edit them (some information that is still useful for previous qubes versions may be lost), but just to index them according to qubes new versions: I'd propose to have a qubes 3.1, a qubes 3.2 and a qubes 4.0 section, for each page.
Cheers,
Fab