Re: [qubes-users] Cannot update dom0, fedora-26 botched
On Tue, May 8, 2018 3:04 am, b...@disroot.org wrote: > This all happened after a fresh install of RC4 (4.0 stable installer will > not boot on my hardware) where no Fedora-based VMs or fedora-26 itself > would launch anything. All qvm-run's just hanged, and logs only report > after killing a VM: ``libvchan_is_eof > Icon size: 128x128 > domain dead Failed to connect to gui-agent`` > > > I tried reinstalling the template and here we are. Cannot update with any > repository enabled, disabled. I have changed all mirrorlists from https > to http and back. Try running "qubes-hcl-report" and look for the 5 lines at the end about HVM, IOMMU, etc. Does "qvm-ls" show any running VMs? Can you start a console session in any of them? Debian template based AppVMs work better? If so, try changing your UpdateVM to a Debian based one then updating all your templates and dom0. -- 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/a4e32d4ae6edf7c4c9170c72fbcd0528%40elude.in. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot update dom0, fedora-26 botched
This all happened after a fresh install of RC4 (4.0 stable installer will not boot on my hardware) where no Fedora-based VMs or fedora-26 itself would launch anything. All qvm-run's just hanged, and logs only report after killing a VM: ``libvchan_is_eof Icon size: 128x128 domain dead Failed to connect to gui-agent`` I tried reinstalling the template and here we are. Cannot update with any repository enabled, disabled. I have changed all mirrorlists from https to http and back. After going through hundreds of packages like this, it gives the output: ``/var/lib/qubes/dom0-updates/packages/python-ipaddress-1.0.16-4.fc26.noarch.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/python2-pycparser-2.14-10.fc26.noarch.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/python-2.7.13-3.fc25.x86_64.rpm already exists and appears to be complete python2-nose-1.3.7-13.fc26.noarch.rpm | 266 kB 00:00 /var/lib/qubes/dom0-updates/packages/NetworkManager-libnm-1.4.6-1.fc25.x86_64.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/boost-thread-1.63.0-5.fc26.x86_64.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/libpkgconf-1.3.7-1.fc26.x86_64.rpm already exists and appears to be complete python-xpyb-1.3.1-7.fc26.x86_64.rpm | 138 kB 00:00 /var/lib/qubes/dom0-updates/packages/dnf-plugins-core-0.1.21-5.fc25.noarch.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/python3-cryptography-2.0.2-2.fc25.x86_64.rpm already exists and appears to be complete /var/lib/qubes/dom0-updates/packages/python2-cryptography-2.0.2-2.fc25.x86_64.rpm already exists and appears to be complete find: '/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory *** ERROR while receiving updates: Error while verifing libICE-1.0.9-9.fc26.x86_64.rpm signature: /var/lib/qubes/updates/rpm/libICE-1.0.9-9.fc26.x86_64.rpm: (RSA) sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: RSA#64dab85d (MD5) PGP#64dab85d) Domain sys-net sent not signed rpm: libICE-1.0.9-9.fc26.x86_64.rpm --> if you want to use packages that were downloaded correctly, use yum directly now`` -- 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/62517b4929d4a21f94f0f5475d7a6526%40disroot.org. For more options, visit https://groups.google.com/d/optout.
