Issues after in-place 3.1.17 -> 3.2 upgrade

[Richard]

I just finished doing an in-place upgrade to 3.2 following https://www.qubes-os.org/doc/upgrade-to-r3.2/

However, I ran into a problem when I reached step "6. Update configuration files."

The system will not allow me to open Konsole (I can open run command, choose Konsole and nothing happens).

Also, now whenever I open Qubes VM Manager I receive the following message:

libvirtError: internal error: client socket is closed

line: if ret == -1: raise libvirtError ('virDomainlsActive() failed', dom=self)
func: isActive
line no.: 1338
file: /usr/lib64/python2.7/site-packages/libvirt.py
---
line: if libvirt_domain.isActive()
func: get_power_state
line no.: 876
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py

and soforth.

The only VMs that are running are sys-firewall and sys-net. I've tried to shut down the firewall from the Qubes VM Manager and receive the following message:

AssertionError:
line: assert vm.is_running()
func: action_shutdownvm_triggered
line no: 1261
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

I've tried to restart and shutdown my system and that is also not possible...nothing happens when I click on shutdown or restart.

I should be grateful if anyone can provide me the steps I need to do to continue upgrading my system.

Thanks,
Richard

[Richard]

Update:
I was able to open Konsole and complete step 6

I also used 'qvm-shutdown -all' to shutdown all VMs.

However, I noticed that the Qubes VM Manager is not reflecting the changes (i.e. it is still showing VMs running), even after I close and reopen it.

I was going to use the 'shutdown now' command, but wanted to check if there is anything I should be doing, before I shutdown, to fix the above errors.

Thanks.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Nov 06, 2016 at 11:44:25AM -0800, Richard wrote:
> However, I noticed that the Qubes VM Manager is not reflecting the changes (i.e. it is still showing VMs running), even after I close and reopen it.

This is expected (until system restart). Also, just closing the manager
window isn't enough to really restart it - if you want to, right click
on its icon and choose "exit". Then start it again from the menu.

> I was going to use the 'shutdown now' command, but wanted to check if there is anything I should be doing, before I shutdown, to fix the above errors.

Just restarting the system should be enough.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJYH42JAAoJENuP0xzK19csLdIIAIAIwf1z3m8Jj1eim8obJCUj
QHC2UrgNTqvl0rFwx0JzsfGvh33ft/SPZoVPwhO8Y9Tp0rhgvjRZVpsN1zF8NQZi
6J2zQg8nnT7AQLrF0WntDO/N8zb8C8lVLkpbr5NHSVveSyDmB1BqrGyLVW7K46py
TMBuhdfT0aEjNuUNBC1uCVknU7uOgIGce9KnWqDp59UmyKecIUhEyPvIZC3QoXmE
BrXuceoRUTj1REoa1FG1GTTlnZms9OL0zOl90wT3fbWcmyKBlCuQLolKKoUuTQIE
UgmnZCYSPMAM7l5fFJMcYpXW30y0O5KMIFGG1/ScRlFaCXAKJIjXF8/lar6QCwU=
=joII
-----END PGP SIGNATURE-----

[Richard]

Thank you Marek