Well, I think I found the reason:
When I updated my debian-9 template, there was a conflict of packages
dependencies that made `qubes-gui-agent` become uninstalled. Obviously, with
that package missing, any GUI interaction with the VMs depending on that
template fails (and qvm-* commands hang forever).
I fixed the issue by messing with `aptitude` and the "(b) broken packages"
option, and then selecting a solution that did this:
Start-Date: 2018-08-27 18:56:55
Install: xserver-xorg-video-dummyqbs:amd64 (4.0.15-1+deb9u1, automatic),
qubes-gui-agent:amd64 (4.0.15-1+deb9u1)
Downgrade: xserver-xorg-video-vesa:amd64 (1:2.4.0-1, 1:2.3.4-1+b2),
xserver-xorg-video-nouveau:amd64 (1:1.0.15-3, 1:1.0.13-3),
xserver-xorg-video-amdgpu:amd64 (18.0.1-1+b1, 1.2.0-1+b1),
xserver-xorg-core:amd64 (2:1.20.1-1, 2:1.19.2-1+deb9u2),
xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.4.4-1+b5),
xserver-xorg-video-ati:amd64 (1:18.0.1-2, 1:7.8.0-1+b1),
xserver-xorg-video-radeon:amd64 (1:18.0.1-2, 1:7.8.0-1+b1)
Remove: xserver-xorg-video-dummy:amd64 (1:0.3.8-1+b1),
libmagickcore-6.q16-5-extra:amd64 (8:6.9.9.34+dfsg-3+b1),
xserver-xorg-video-r128:amd64 (6.11.0-1), libavformat57:amd64 (7:3.4.3-1),
xserver-xorg-video-qxl:amd64 (0.1.5-2+b1), libargon2-0:amd64 (0~20171227-0.1),
xserver-xorg-video-cirrus:amd64 (1:1.5.3-1+b3),
linux-headers-4.16.0-2-common:amd64 (4.16.16-2), libmagickwand-6.q16-5:amd64
(8:6.9.9.34+dfsg-3+b1), xserver-xorg-video-trident:amd64 (1:1.3.8-1+b1),
libxatracker2:amd64 (18.1.6-1), linux-headers-4.16.0-2-amd64:amd64 (4.16.16-2),
xserver-xorg-video-savage:amd64 (1:2.3.9-2), libpostproc54:amd64 (7:3.4.3-1),
libgeoclue-2-0:amd64 (2.4.12-1), libstdc++-7-dev:amd64 (7.3.0-28),
libnfs8:amd64 (1.11.0-2), xserver-xorg-video-mach64:amd64 (6.9.6-1),
libx264-148:amd64 (2:0.148.2748+git97eaef2-1), libx265-95:amd64 (2.1-2+b2),
g++-7:amd64 (7.3.0-28), libgfortran4:amd64 (7.3.0-28),
xserver-xorg-video-intel:amd64 (2:2.99.917+git20171229-1+b1),
xserver-xorg-video-tdfx:amd64 (1:1.4.7-1+b1), xserver-xorg-video-vmware:amd64
(1:13.3.0-2), xserver-xorg-video-all:amd64 (1:7.7+19), libswscale4:amd64
(7:3.4.3-1), libdns-export1100:amd64 (1:9.11.3+dfsg-2),
libmagickcore-6.q16-5:amd64 (8:6.9.9.34+dfsg-3+b1), libgcab-1.0-0:amd64
(1.1-3), bdf2psf:amd64 (1.184), xserver-xorg-video-neomagic:amd64
(1:1.2.9-1+b3), libva-wayland1:amd64 (1.7.3-2), liblivemedia57:amd64
(2016.11.28-1), linux-kbuild-4.16:amd64 (4.16.16-2), libbluray1:amd64
(1:0.9.3-3), xserver-xorg-video-mga:amd64 (1:1.6.5-1+b1), libavresample3:amd64
(7:3.4.3-1), xserver-xorg-video-openchrome:amd64 (1:0.6.0-3+b1)
End-Date: 2018-08-27 18:57:05
After that, it is possible to do
systemctl enable qubes-gui-agent.service
systemctl start qubes-gui-agent.service
and from that point on, the template is operating normally.
Hope it helps!
///Pablo
El miércoles, 15 de agosto de 2018, 8:29:40 (UTC-3), tier...@gmail.com escribió:
> On Tuesday, August 14, 2018 at 4:36:29 PM UTC+1, Pablo Di Noto wrote:
> > Kudos to the `qvm-volume revert` feature!
> >
> > I just did
> > ```
> > qvm-volume info debian-9-root
> > qvm-volume revert debian-9-root XXXXXXXXXX-back
> > ```
> > and went back to the pre-update template and the issue disappeared.
> >
> > Later today will try to see what happened by updating a clone of the
> > template (as I should have done in the first place)
>
> Not an option for me. I shall file a bug report.
--
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/be4b921c-1d0a-48b2-8c80-b0656ecf008b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
