> > Maybe better question is, why was the template installed to begin with when
> > I opted out of any initial configuration?
> >
>
> That's a known bug, recently fixed:
>
> https://github.com/QubesOS/qubes-issues/issues/2105
I'm getting quite good at finding bugs - six months after the fact.
On Thursday, August 18, 2016 at 7:04:01 PM UTC, 3n7r...@gmail.com wrote:
> On Thursday, August 18, 2016 at 5:41:58 AM UTC, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > On 2016-08-17 12:17, entr0py wrote:
> > > New Qubes 3.1 installation with Advanced
On Thursday, August 18, 2016 at 5:41:58 AM UTC, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-08-17 12:17, entr0py wrote:
> > New Qubes 3.1 installation with Advanced (No Configuration)
> > option.
> >
> > After restoring dom0 + serviceVMs +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-17 12:17, entr0py wrote:
> New Qubes 3.1 installation with Advanced (No Configuration)
> option.
>
> After restoring dom0 + serviceVMs + serviceTemplates, tried to
> `sudo yum remove qubes-template-fedora-23`
>
> Received: Error in
New Qubes 3.1 installation with Advanced (No Configuration) option.
After restoring dom0 + serviceVMs + serviceTemplates, tried to
`sudo yum remove qubes-template-fedora-23`
Received: Error in PREUN scriptlet in rpm package...
libvirt.libvirtError: Domain not found [from libvirt.py line 4066
