On Tue, Nov 15, 2016 at 1:14 AM, Marek Marczykowski-Górecki <
marma...@invisiblethingslab.com> wrote:

> Hash: SHA256
> On Tue, Nov 15, 2016 at 12:34:19AM +0000, Alex wrote:
> > This is the second time I encounter this freaky issue on R3.1:
> >
> > Start a DispVM Firefox, login to a website, close Firefox, observe the
> disposable VM is gone from the VM manager. Fine so far.
> >
> > Launch a new disposable Firefox which creates a new VM with a different
> name (dispN) - notice with horror that you are already logged on to the
> website you had logged on to from the terminated VM.
> >
> > Surely this is not supposed to happen. How to troubleshoot?
> I believe you've hit this issue:
> https://github.com/QubesOS/qubes-issues/issues/2200
> The issue is fixed in R3.2, but it hasn't been yet backported to R3.1...
> For now, make sure that files in /var/lib/qubes/appvms/fedora-23-dvm (or
> other - depending on what template you use for DispVM) are owned by your
> user. Then recreate DispVM savefile with qvm-create-default-dvm.
All files in /var/lib/qubes/appvms/fedora-23-dvm are owned by my user,
group qubes - but volatile.img is -rw-r--r-- while all other files are
-rw-rw-r-- (so, group can't write to it). I changed this with chmod 664
volatile.img but on running qvm-create-default-vm the permissions are reset
to their earlier state - and volatile.img is not group-writeable.

Should people on R3.1 just chmod 664 volatile.img right after recreating
the DVM?



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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to