Am Freitag, 9. März 2018 08:53:41 UTC+1 schrieb sevas: > I deleted my original sys-net and sys-fw and I received similar errors. What > I did to fix it was > > dom0$ sudo nano /etc/qubes-rpc/policy/qubes-update-policy > > and fixed the command which was pointing to the wrong sys-net.
Thanks a lot, that pointed me in the right direction! I set up updates via Whonix and for some reason `dnf update` does not like the `sys-whonix` VM. When I change the `target` in `qubes.UpdatesProxy` to `sys-net` I can update as expected. My `qubes.UpdatesProxy` file looks like this, when I change the `target` in the first line from `sys-whonix` to `sys-net` everything works out. Is there something wrong with the configuration in this file? (I do have a NetVM `sys-whonix` that works and has `qubes-updates-proxy` running) $type:TemplateVM $default allow,target=sys-whonix $tag:whonix-updatevm $default allow,target=sys-whonix $tag:whonix-updatevm $anyvm deny ## Note that policy parsing stops at the first match, ## so adding anything below "$anyvm $anyvm action" line will have no effect ## Please use a single # to start your custom comments # Default rule for all TemplateVMs - direct the connection to sys-net $type:TemplateVM $default allow,target=sys-net $anyvm $anyvm deny -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b6f12e08-4f5f-4118-b387-b01dede77567%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
