As I noticed, when the VM is upgraded to R3.2 but dom0 stays at R3.1, this breaks qubes-gui-agent in the VM.
[1] What about the other way around...? I upgraded dom0 R3.2 but left whonix-gw / anon-whonix at R3.1. This broke networking inside Whonix and I have not been able yet to fix that or determine the cause. Is this to be expected? Or asking a bit similar... Would dom0 R3.2 and Debian VM R3.1 work? Or have broken networking? Or are any other issues derived from Qubes release version mixing to be expected? (I deliberately set up a test system this way [1] for Whonix development/testing purposes. I guess some users might run into this. So it would be worth knowing about symptoms [for support] and issues one would run into then.) Cheers, Patrick -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d163750c-f874-6f62-bf36-7c0b0f87dab6%40riseup.net. For more options, visit https://groups.google.com/d/optout.
