Re: [qubes-users] removing "system tools" and "Create Qubes VM" etc from start menu ..

[WillyPillow]

On Thursday, June 4, 2020 3:12 AM, Dave  wrote:

> Is it possible to remove everything from the start menu but the different 
> domains ..?
> So the user can only see the different vm's in the start menu and non of the 
> stuff like "System Tools" and "Create Qubes VM"..

Related issue: .

> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/wLI4s3Fhe9kRvaT2HatZ7pn3T4Rc6t99eCHbc-E6aEY_25jrkpTCkVVyNfLQScnApda6b33NC8W4fKYt3XrZQ3BA7IZaXZppdesx7_fF4qY%3D%40nerde.pw.


publickey - wp@nerde.pw - 0xD02DCEFF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Another newbie question related to TemplateVMs

[WillyPillow]

On Saturday, May 30, 2020 6:48 AM, 'Jackie' via qubes-users 
 wrote:

> Frédéric Pierret:
> 

> > On 2020-05-29 18:26, viktor.ransm...@gmail.com wrote:
> > 

> > > Hello Frederic,
> > > Am Freitag, 29. Mai 2020 14:01:46 UTC+2 schrieb Frédéric Pierret:
> > > 

> > >  On 2020-05-29 13:53, viktor@gmail.com  wrote:
> > >  >
> > >  > I'm trying to continue my journey into the various Qubes OS 
> > > options from the smaller - and not - from the larger template POV.
> > >  >
> > >  > I'm not asking for any additions to the provided packages 
> > > available for example in 'fedora-31-minimal'.
> > >  >
> > >  > All I'm asking for is help to resolve the following question:
> > >  >
> > >  > *What do I need to do in order to activate / enable the copy / 
> > > paste pattern via copy-c/v for xterm?
> > >  > *
> > > 

> > >  Control+Middle mouse clic -> Select to Clipboard. Then, you can you 
> > > QubesOS clipboard shortcut (Control+Shift+C).
> > > 

> > > 

> > > It may be obvious to you, but for me - coming from the Windows world - it 
> > > is not really clear ...
> > 

> > The middle click simply the wheel click but indeed, with only left and 
> > right buttons it's both at the same time. Here when hold Control in 
> > addition to left and right mouse button (keep holding) on xterm, it makes 
> > appearing a little menu where the selection is made by unholding mouse 
> > buttons. On this little menu you would see the 'Select to Clipboard' option.
> 

> For what it's worth i can't get this to work on xterm either. I use
> gnome-terminal which lets you right click -> copy (or edit -> copy),
> 

> then qubes copy/paste shortcuts work like normal.

To enable simulating middle clicks that way, I had to follow
.


Alternatively, you should be able to add `XTerm.vt100.selectToClipboard: 1`
to `~/.Xresources` and run `xrdb -merge ~/.Xresources` to enable the
Select to Clipboard feature by default.

> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/D8mh0TS1VXTcEHlOF3LbQsxxocJpWMkyJLN7gwmkBGnMi84NjA8SdAodug2uu-tn6nc450WjklDTp7Y4KZ4gRi_-31x8fYSC5Rba9f8L_1M%3D%40nerde.pw.


publickey - wp@nerde.pw - 0xD02DCEFF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Unable to complete Step 3

[WillyPillow]

On Wednesday, April 1, 2020 8:32 AM, Ben  
wrote:

> Hello, thank you for the help with the second step. it worked as you said 
> when i changed the X to 4.
> 

> here's what i get when i try to verify the iso file on the 3rd step.
> 

> gpg2 -v --verify Qubes-RX-x86_64.iso.asc Qubes-RX-x86_64.iso
> gpg: can't open 'Qubes-RX-x86_64.iso.asc': No such file or directory
> gpg: verify signatures failed: No such file or directory
> 

> I also tried to change the X to a 4 but this also did not work this time.
> 

> Best
> Ben

Hi.

(I presume the context was 
https://groups.google.com/d/msg/qubes-devel/BdjHoVhKs7I/1b5z24StBgAJ)

Not entirely sure why you are sending this (only) to me instead of the ML, so 
forwarded.

Did you forget to download the signature file from the downloads page by any 
chance?

--WillyPillow

> https://blog.nerde.pw/
>
> PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154 217F 1C16 C70E E7C3 1C84
>
> Protonmail PGP = D02D CEFF ACE5 5A7B FF5D 871E 4004 1CB1 F52B 127E

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/QRukAYbeGN8pGMBDt8e7KGJKNYwW6NVkkQrrFpl4beDFpqrofI98qOWdn9QRKfzZSL9p7kR_6BFTsTWsRS-QVkAMZ5OqjrzDcxvX_4Wd7M8%3D%40nerde.pw.


publickey - wp@nerde.pw - 0xD02DCEFF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

[WillyPillow]

 Original Message 
On 2018年2月17日 10:30, pixel fairy wrote:
On Friday, February 16, 2018 at 4:07:10 PM UTC-8, Marek Marczykowski-Górecki 
wrote:
> Yes, there is "xpti=false" option for Xen command line (xen.gz option in
> grub, or options= line in xen.cfg for UEFI).
tried that by editing the multiboot /xen-4.8.3.gz line while booting. no 
change. maybe its a different change between rc3 and rc4. seems like a stretch, 
but one that only affects supermicro c7z motherboards?

I did some timing, and for PVH, my Fedora 26 VMs take about 30s, while Debian 9 
takes about 45s. For HVM, qrexec usually times out (did not bother to adjust 
the timeout).

Just to clarify, my mobo is an ASRock Z170, not a Supermicro one.

--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154  217F 1C16 C70E E7C3 1C8
--

-- 
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/feIj1otJTWDwda2aJVKqIsscwlqCmyDknsPVwOrKhcRXKZidQ0J6gyKrycBdVTYxQuOOUTF4KzOO8PnhdStxTn9CEbAASNZtxOCETNOchV8%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] q4rc4 very slow. VMs take 23 - 33 seconds to start

[WillyPillow]

I also noticed similar slowdowns. I have no experience with rc3 (upgraded 
directly from 3.2), but your numbers seem to councide with my experience. 
Hardware is also pretty similar, namely Z170/6700K.

--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = 6CCF 3FC7 32AC 9D83 D154  217F 1C16 C70E E7C3 1C8
--

-- 
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/_u34bjS6AXj5CHBS0GgzGXhvql6dmV8Qa5ABa-NOi-JKjSal18usCoqxPpf01YSQp6FQ0vnvgGNIKUbKiyOrl_gjIrlgsRBW4K8iZGM7Lcc%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Linux HVM Hangs On Boot On Qubes 3.2

[WillyPillow]

>  Original Message 
> Subject: [qubes-users] Linux HVM Hangs On Boot On Qubes 3.2
> Local Time: September 13, 2017 1:15 PM
> UTC Time: September 13, 2017 1:15 PM
> From: w...@nerde.pw
> To: qubes-users <qubes-users@googlegroups.com>
>
> I've been trying to install a Linux HVM on a Qubes 3.2 system. However, all 
> the ISOs I tried (Debian, Debian netinst, and Arch) seemed to get stuck at 
> boot with blank console.
>
> In addition, if I pass `debug ignore_loglevel` as boot arguments to the Arch 
> ISO, it shows something like `probing EDD ...ok` and then hangs.
>
> Does anyone know what is going on? Thanks.

UPDATE: For some reason, after I switched the netVm from a Mirage firewallVm to 
a regular Linux one, it started to work fine.

> --WillyPillow
> --
> https://blog.nerde.pw/
> PGP fingerprint = B57E 7237 B211 419C 35C4  AF5B EB4D 3264 A318 73CB
> --

-- 
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/5bBzGRCM9GcS_xDbeUkrEEJU1l5E7GPFQ2NQqkZb1eusDAbsTuccKe0K-sdzpyHGkalf_N25nXEJqP7VwdSDWosox2n2lTWLpnWo38knvxI%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Linux HVM Hangs On Boot On Qubes 3.2

[WillyPillow]

I've been trying to install a Linux HVM on a Qubes 3.2 system. However, all the 
ISOs I tried (Debian, Debian netinst, and Arch) seemed to get stuck at boot 
with blank console.

In addition, if I pass `debug ignore_loglevel` as boot arguments to the Arch 
ISO, it shows something like `probing EDD ...ok` and then hangs.

Does anyone know what is going on? Thanks.

--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = B57E 7237 B211 419C 35C4  AF5B EB4D 3264 A318 73CB
--

-- 
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/gvU-RG5YDugUL5VT9csY6Mk9iZCxuug84b_fyq4QMCfD8Aki_yxc32fRLgoY-v6gqWX-fy_7Jv89Mmk3S7imr9E_8Im6d2f9OZPE1qqe-Pc%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Number of cores and other CPU characteristics

[WillyPillow]

 Original Message 
Subject: [qubes-users] Number of cores and other CPU characteristics
Local Time: February 2, 2017 9:50 AM
UTC Time: February 2, 2017 9:50 AM
From: groups-no-private-mail--contact-me-at--contact.v6ak@v6ak.com
To: qubes-users <qubes-users@googlegroups.com>

Choosing the right CPU is about choosing the right tradeoff. The tradeoff is 
not only between price, power consumption and performance. We can also balance 
single-core performance to multi-core performance, or we might want some 
enhancements for some specific tasks, like AES-NI. And many more.

I'd like to ask how should Qubes affect my choice (looking at Qubes 4 and 
newer):

* Obviously, it needs to meet the requirements mentioned at 
https://www.qubes-os.org/doc/system-requirements/ .
* I might want TXT for AEM (this is not performance-related, though).
* Qubes has GPU for all VMs emulated on CPU. (I believe the GPU emulation runs 
in the VM itself or in its stubdom.) This might increase need for multiple 
cores. (Unsure how much.) This might become more important when considering 
hiDPI or other GPU-intensive tasks.
* Qubes will typically use encryption (at least for data storage), which makes 
AES-NI potentially useful. It might also utilize an extra core.
* Qubes typically runs multiple VMs at once. I believe this introduces just a 
minor CPU overhead – while you have more OSes running at once, one VM will have 
fewer processes. Typically, IMHO at most one VM is performing CPU-bound tasks.

There are my more specific questions:

1. Does Qubes affected desicion between dual-core and quad-core CPUs? While 
Qubes will more likely utilize multiple cores, I believe that dual-core should 
be enough in most cases.
2. Is there anything wrong with Intel's U-series? One of considered CPUs is 
Intel i7 7500U, which seems to provide excellent single-core performance with 
low power consumption.

AFAIK, [this 
attack](http://blog.ptsecurity.com/2017/01/intel-debugger-interface-open-to.html)
 only work on the U-series.


3. Should I be picky about integrated graphics? Since it is used in dom0 only, 
I don't think its performance is important in QubesOS. Maybe it will become 
important when XenGT is integrated in QubesOS (which is not sure if it happens 
at all).
4. Is there anything else I should be aware of when looking at recent i7 (or 
maybe i5) CPUs?

Regards,
Vít Šesták 'v6ak'

--
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/509f624e-267a-407e-aadb-5672f562dd35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = B57E 7237 B211 419C 35C4 AF5B EB4D 3264 A318 73CB
--

-- 
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/If3P9npSvWYiqwpqZhWK0FlICfwGvItZBIukXTipuHwtQ4DAUN8yEy49DRcq3oXSJ5N3t8S73cW0Yd86hthwBvWeIRn2z8H9_1vldIQaVDQ%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Devilspie2 integration

[WillyPillow]

 Original Message 
Subject: Re: [qubes-users] Devilspie2 integration
Local Time: February 2, 2017 10:05 PM
UTC Time: February 2, 2017 10:05 PM
From: tas...@openmailbox.org
To: Hack <mistermys...@outlook.com>, qubes-users@googlegroups.com

On 02/02/2017 09:09 AM, Hack wrote:
> Hi,
>
> Could it be possible to provide Qubes OS with Devilspie2 at first
> install?
>
> Like this, we could have, by default? some virtual desktops attributed
> to some task.
>
> For example:
>
> * Desktop 1 = administration tasks (sys-firewall, sys-net, etc…)
> * Desktop 2 = Personal
> * Desktop 3 = Work
> * and so on
>
> Maybe with some color "matching" on the tool bars?
>
> Of course, with the option to customize it.


This is one of the things I love about using KDE on Qubes.

Chris


Also, with AwesomeWM it should be possible to set up custom rules that 
automatically tags clients in different domUs, though I've never tried this.



--WillyPillow
--
https://blog.nerde.pw/
PGP fingerprint = B57E 7237 B211 419C 35C4 AF5B EB4D 3264 A318 73CB
--

-- 
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/2rX_S64575-cMWOioc0-M6b7W4wXPgYwCLdkIUedrhxvmDjtGQ3Y_3hzTh-JQom0AjnYuqr2jA-FsCN-nG609jHYDQxq0xt7C45s_X93d2M%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[WillyPillow]

 Original Message 
>On 2017年1月21日 02:24, Антон Чехов wrote:
>I tried again with the existing template, recompiled but the result stayed the 
>same. So I did try from scratch, including the modified coldkernel.config. 
>Everything is working so far, also behind a proxyVM. I did stop and restart 
>the appVM but I did not yet reboot my system. I added the template to these 
>groups:
sudo groupadd -g 9001 grsecproc
sudo groupadd -g 9002 tpeuntrusted
>
>I am a little reluctant with “sudo groupadd -g 9003 denysockets” because I 
>don't know what it does in detail (or whether it might lead to problems).

It's the same as the previous two commands, creating a group with certain 
privileges. For that specific one, IIRC the users assigned to that group is 
denied the use of sockets.

--WillyPillow

-- 
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/U8IU_dPoc3w2DhUZKUW0ISj53eeLC6achx5GNgae0CRirjBLF-2oMeK42OOrACwierlu0Pp5jICt4gBKeFoEh7sebUHdZ-btVrflIUGnNE8%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Question to Mirage OS firewall users

[WillyPillow]

 Original Message 
Subject: [qubes-users] Re: Question to Mirage OS firewall users
Local Time: January 19, 2017 12:06 AM
UTC Time: January 19, 2017 12:06 AM
From: r...@reginaldtiangha.com
To: qubes-users@googlegroups.com

On 2017-01-18 7:30 AM, Антон Чехов wrote:
> Hi!
>
> Is anyone using the mirage firewall in connection with a proxyVM? How do you 
> configure it properly? Does it handle qubes-firewall-users-scripts?
>

I've run a Mirage-based firewall both in front of and behind a
firewallVM and they chain together fine. Mirage Firewall in its current
iteration does *not* respect modifications to firewall rules via Qubes
and has to be inputted manually (there are some instructions on how to
do that on the software author's blog). It isn't to say that Mirage
Firewall couldn't do it one day, but I believe the author of the code is
leaving it up as an exercise for the reader. Maybe he'll get around to
implementing it, or maybe not, but from a purely technical standpoint,
there's no reason why it couldn't be modified to work with Qubes
firewall user scripts, it's just that it hasn't been implemented yet.

Note that even if you're running the latest code off of GitHub,
currently, Mirage Firewall still doesn't work correctly with DispVMs (or
at least, I haven't been able to get it to work; the DispVM connects to
it, but there's no traffic), even though there were some minimal fixes
applied to try to handle how it handles IP addresses from a different
pool. Works fine with AppVMs, though, as well as TemplateVMs, at least
in my experience.


A workaround for dispVMs is creating the savefile without a firewallVM (i.e. 
set as "none"), then for each fresh dispVM, manually assign it to sys-mirage 
after it has been started.

--WillyPillow

-- 
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/ot6Ty_X0rMsx8y3qav_PGnwBpU9Tm32TkWWKoTZnhB4IkTKgp1Yg1OgTG5_hXwyp6VVpX1VENyICnabB0jgTByaWlB56n2Yl5JY_7R9tPo4%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] What decides which VM is the FirewallVM?

[WillyPillow]

 Original Message 
On 2017年1月1日 11:11, wrote:
Hi, From my understanding, the FirewallVM is where the firewall rules are put 
into place from the Qubes VM Manager. The sys-firewall VM acts as the 
FirewallVM by default but what decides which VM gets that role? Is it 
automatically the first ProxyVM connected through the NetVM? Does naming a 
ProxyVM "sys-firewall" make it the FirewallVM? I can't find anything on how the 
FirewallVM is decided in the documentation at 
https://www.qubes-os.org/doc/firewall/. It would be handy to know if creating 
all VMs from scratch instead of using the defaults when Qubes OS is installed. 
Thanks

When you create an VM, you have the option of making it a ProxyVM. After that, 
you can connect other VMs (even ProxyVMs) to that ProxyVM, making the ProxyVM 
the FirewallVM of the VM. IIRC, the option in Qubes Manager that decides what 
ProxyVM an VM connects to is simply called "NetVM".
In short, there's not really an "one and only FirewallVM" in the system, but 
FirewallVMs that are assigned to each AppVM.

--WillyPillow

-- 
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/2dNAY7ocElKwM_2BrI8TUHr83iN4DsWNkatgUIOvnth_K46PzbRlKJxXSXonhhCeh_JzgIewZjkp4WqoqunGPxJHeOHCETcbfVdtt_Fql_4%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Sudo dnf list qubes-template* does not list all templates

[WillyPillow]

 Original Message 
Subject: [qubes-users] Sudo dnf list qubes-template* does not list all templates
Local Time: January 1, 2017 4:44 AM
UTC Time: December 31, 2016 8:44 PM
From: 169...@gmail.com
To: qubes-users@googlegroups.com <qubes-users@googlegroups.com>









Hello,
While most templates appear, a couple of templates does not appear using

sudo dnf list qubes-template*

I was trying to delete one of them with

sudo dnf remove qubes-template-debian-8-e

and got a

no match for argument: qubes-template-debian-8-e

But both unlisted templates are present in Qubes Manager and work perfectly as 
far as I can understand.

I do not know if it is related but I am using btrfs and recently removed and 
reinstalled debian-8 in relation to Debian upgrade security problem. The two 
unlisted templates where originally cloned from debian-8 now removed.

Happy new Year
Fran

Sorry if I misunderstood you, but it seems like you're trying to remove a 
cloned template with dnf. If so, dnf only work with templates installed via 
packages (i.e. qubes-dom0-update) and not custom cloned ones.

Happy new year too :)
--WillyPillow

-- 
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/10Z_bASoblAmL-gXTtpfADjXc6wRA77x-CiAqhzAz__y6YFhI-C8HTN6tZkpffYkPyvCcuw7JC3y64Con7NHPAkKqJOjC28Q4t80LpoyPQU%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to set file association in disposable VMs?

[WillyPillow]

 Original Message 
Subject: [qubes-users] How to set file association in disposable VMs?
Local Time: December 29, 2016 7:48 PM
UTC Time: December 29, 2016 11:48 AM
From: gree...@gmail.com
To: qubes-users <qubes-users@googlegroups.com>

I have configured Nautilus in an AppVM to open PDF files with Okular, and I've 
then done the same configuration (as user "user") in the TemplateVM that the 
disposable VMs are also based on. However, when I choose "Open in disposable 
VM" from that reconfigured AppVM, even though the dispvm savefile is updated 
before launching the dispvm, it still uses the default PDF viewer instead of 
Okular.

Sounds similar to this:
https://groups.google.com/forum/#!searchin/qubes-users/open$20in$20dvm|sort:relevance/qubes-users/GZ2zWcoMuwc/vwAzmYS5DgAJ

--WillyPillow

-- 
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/6-lUcWnJUTWGJKq5P3baXnx5oF9mQ-LEn1X-9pnIiOPyPH9YkaQy8RmVpyyo0WvOR0ur6AdM4UD0byzKPeCJymwkMapV3HT9plcH03sF7QI%3D%40nerde.pw.
For more options, visit https://groups.google.com/d/optout.