On 3/13/19 11:06 AM, unman wrote:
On Tue, Mar 12, 2019 at 06:57:41PM +0000, Jon deps wrote:
On 3/12/19 4:34 PM, unman wrote:
On Tue, Mar 12, 2019 at 08:35:04AM +0000, Jon deps wrote:
Hello, in Thunderbird when I do open-in-vm and check firefox it has
retained bookmarks from a previous session,
I believe this is Not how DVMs are supposed to work ?
If so how would I troubleshoot and/or remove old DVM data sesssions
please
You're right. It isn't how disposableVMs are supposed to work.
The obvious question is, what did you select when you "did" open-in-vm?
If you selected an appVM, have you made sure that you have made that
appVM in to a template for disposableVMs?
(qvm-prefs <qube> template_for_dispvms True)
Also check to see what you have set in
/etc/qubes-rpc/policy/qubes.OpeninVM and
/etc/qubes-rpc/policy/qubes.OpenURL
unman
What I did/have done is for secure printing(per Qubes docs advice) , cloned
fedora-29 -> fedora-29printtemplate, then I use the clone as the template
for an AppVM (named fedoraprintqube).
when I do :
$qvm-prefs fedoraprintqube
template - fedora-29printtemplate
template_for_dispvms - True
$qubes-prefs
default_dispvm - fedoraprintqube
re: "what did I choose" there is only 1 choice in Thunderbird
Open-in-dispvm
right click and choose and it open the atttachment in a dispvm
re: rpc policy everything is as default setup
further the AppVM in which Thunderbird is running has it's default DispVM
set to: fedoraprintqube
is there some directory I should clear where dispVM information would
be stored to perhaps reset the system ?
or any further ideas welcome regards
There was an issue before where disposableVMs were leaking information
but that was under 3 where the structure was somewhat different.
There may be 2 cases:
1. a disposableVM is created and you are seeing information from the
underlying fedoraprintqube - normal, and to be expected;
2. a disposableVM is created and you are seeing information from a previous
disposableVM session. Bug.
Are you able to rule out (1) and confirm that it is (2)? When a qube is
created, it is definitely named dispXX?
ah ok , so it's #1 , so what is disposed of in this configuration by
using the DVM based on a AppVM instead of a TemplateVM ?
or is there any benefit for the disposable-ness ? perhaps I should be
using a Template for true disposable data ?
--
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/aa853f6b-9a9e-d241-1411-464f40f8c98e%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
