Re: [qubes-users] qvm-run fails silently with chromium

2017-02-15 Thread Unman
On Wed, Feb 15, 2017 at 05:35:31PM -0500, Jean-Philippe Ouellet wrote:
> Running execsnoop [1] in the AppVM while trying to start chromium may
> give you more insight into what is actually happening. Tracing
> observed behavior is often easier than digging through the source.
> 
> [1]: 
> https://raw.githubusercontent.com/brendangregg/perf-tools/master/execsnoop

Well yes, except that it's clear form the thread that Marc knows what
the issue is (Path not set), and I doubt execsnoop would add more
insight to that.

-- 
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/20170216001039.GB6697%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-15 Thread Jean-Philippe Ouellet
Running execsnoop [1] in the AppVM while trying to start chromium may
give you more insight into what is actually happening. Tracing
observed behavior is often easier than digging through the source.

[1]: https://raw.githubusercontent.com/brendangregg/perf-tools/master/execsnoop

-- 
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/CABQWM_BOi_S0wfWAXbRabyJcf-zPROgLCthTXQAAK00QH48qqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-13 Thread marc
> I'm probably wrong but I think what's happening is this:
> Look up the process list and you'll see the invocation:
> su -l user -c /usr/bin/xinit...

Right

> That's su starting a shell as a login shell: as you have zsh as default
> shell, .zprofile is read to set env variables, including path.
> 
> And I think you should have seen the output from qvm-run ps aux
> included something like "sh -c ps aux".

Right

> That call to sh is coming from qrexec-fork-server, I think.
> 
> I hope that makes it a little clearer.

Not too much, but I guess I lack some background in qubes internals :)

> It would be interesting to see what happened if you were to relink sh
> to zsh in the template. I'm looking at a number of issues arising using
> some non default user shells(tcsh, fish)

Doing so:

$ qvm-run -a -p qube "echo $0"
# => sh

$ qvm-run -a -p qube "ps aux"
# Inclues
# => /bin/bash /usr/bin/qubes-session
# => su -l user -c /usr/bin/xinit
# => ps aux (without `sh -c` before)

$ qvm-run -a -p qube 'echo $SHELL'
# => /bin/zsh

-- 
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/e281e3ca-d595-40ae-a5c7-e471346179dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-12 Thread Unman
On Sun, Feb 12, 2017 at 01:27:30AM -0800, m...@lamarciana.com wrote:
> > try this:
> > qvm-run -a -p qube "echo $0"
> 
> It returns `bash`
> 
> > and:
> > qvm-run -a -p qube "ps aux"
> 
> It includes a `/bin/bash /usr/bin/qubes-session`
>  
> > You may be surprised.
> 
> Also, `echo $SHELL` returns `/bin/bash`.
> 
> I thought that maybe that `bash` process was in fact a subprocess of the 
> actual `zsh` shell, but `ps aux|grep zsh` returns nothing.
> 
> So, yes, I'm very surprised, and now I understand even less why `~/.zprofile` 
> is sourced... :)
> 

I'm probably wrong but I think what's happening is this:
Look up the process list and you'll see the invocation:
su -l user -c /usr/bin/xinit...

That's su starting a shell as a login shell: as you have zsh as default
shell, .zprofile is read to set env variables, including path.

And I think you should have seen the output from qvm-run ps aux
included something like "sh -c ps aux".
That call to sh is coming from qrexec-fork-server, I think.

I hope that makes it a little clearer.
It would be interesting to see what happened if you were to relink sh
to zsh in the template. I'm looking at a number of issues arising using
some non default user shells(tcsh, fish)

-- 
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/20170212145841.GB18690%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-12 Thread marc
> try this:
> qvm-run -a -p qube "echo $0"

It returns `bash`

> and:
> qvm-run -a -p qube "ps aux"

It includes a `/bin/bash /usr/bin/qubes-session`
 
> You may be surprised.

Also, `echo $SHELL` returns `/bin/bash`.

I thought that maybe that `bash` process was in fact a subprocess of the actual 
`zsh` shell, but `ps aux|grep zsh` returns nothing.

So, yes, I'm very surprised, and now I understand even less why `~/.zprofile` 
is sourced... :)

-- 
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/23ff30d1-f131-467d-a729-2852fea32d58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-11 Thread Unman
On Sat, Feb 11, 2017 at 09:59:36AM -0800, m...@lamarciana.com wrote:
> > Yes, I know - that's why I said "using bash".
> > You are using zsh, so you said, so you need to put the path in ~/.zprofile
> > 
> > For example, with simple script 'logit' in home/user/newpath:
> > 
> > qvm-run -a -p qube logit
> > fails with "logit: not found"
> > 
> > append path=('home/user/newpath' $path) to ~/.zprofile
> > Then qvm-run succeeds
> 
> Yeah, you are right, this works. Thank you very much. But I don't quite 
> understand. I guess that I'm opening an interactive non-login shell, but 
> ~/.zprofile is sourced while ~/.zshrc isn't, while, from 
> http://zsh.sourceforge.net/Intro/intro_3.html:
> 
> > `.zshrc' is sourced in interactive shells
> 
> > [...]
> 
> > `.zlogin' is sourced in login shells. [...] `.zprofile' is similar to 
> > `.zlogin', except that it is sourced before `.zshrc'
> 

try this:
qvm-run -a -p qube "echo $0"

and:
qvm-run -a -p qube "ps aux"

You may be surprised.

-- 
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/20170211233845.GC14849%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-11 Thread marc
> Yes, I know - that's why I said "using bash".
> You are using zsh, so you said, so you need to put the path in ~/.zprofile
> 
> For example, with simple script 'logit' in home/user/newpath:
> 
> qvm-run -a -p qube logit
> fails with "logit: not found"
> 
> append path=('home/user/newpath' $path) to ~/.zprofile
> Then qvm-run succeeds

Yeah, you are right, this works. Thank you very much. But I don't quite 
understand. I guess that I'm opening an interactive non-login shell, but 
~/.zprofile is sourced while ~/.zshrc isn't, while, from 
http://zsh.sourceforge.net/Intro/intro_3.html:

> `.zshrc' is sourced in interactive shells

> [...]

> `.zlogin' is sourced in login shells. [...] `.zprofile' is similar to 
> `.zlogin', except that it is sourced before `.zshrc'

-- 
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/210bafbe-7d03-4752-a0ef-87162a6c6523%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-10 Thread Unman
On Fri, Feb 10, 2017 at 03:28:53AM -0800, m...@lamarciana.com wrote:
> > The issue you raise there arises because the xterm is not a login shell
> > so will not use .profile.
> > It is interactive so (using bash) will use .bashrc
> > 
> > On the immediate question here you can always set the path explicitly:
> > qvm-run -p qube "export PATH=$PATH: && foo"
> 
> Hey Unman. The issue is that neither `~/.bashrc` nor `/etc/bash.bashrc` from 
> my VM are used when I do `qvm-run` from dom0. Your workaround works but I 
> think it is quite cumbersome. I wonder if there is any way to change the VM 
> PATH seen from dom0 for every command.
> 
> Thanks
> 

Yes, I know - that's why I said "using bash".
You are using zsh, so you said, so you need to put the path in ~/.zprofile

For example, with simple script 'logit' in home/user/newpath:

qvm-run -a -p qube logit
fails with "logit: not found"

append path=('home/user/newpath' $path) to ~/.zprofile
Then qvm-run succeeds

-- 
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/20170211004810.GA9930%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-10 Thread marc
> The issue you raise there arises because the xterm is not a login shell
> so will not use .profile.
> It is interactive so (using bash) will use .bashrc
> 
> On the immediate question here you can always set the path explicitly:
> qvm-run -p qube "export PATH=$PATH: && foo"

Hey Unman. The issue is that neither `~/.bashrc` nor `/etc/bash.bashrc` from my 
VM are used when I do `qvm-run` from dom0. Your workaround works but I think it 
is quite cumbersome. I wonder if there is any way to change the VM PATH seen 
from dom0 for every command.

Thanks

-- 
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/a1304499-d30b-40bc-84ca-43bb7ec7def9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-09 Thread Unman
On Thu, Feb 09, 2017 at 04:08:54AM -0800, m...@lamarciana.com wrote:
> > Is chromium the only program with which you experience this problem?
> 
> Thanks for your answer Andrew.
> 
> Thanks to a private reply I got, I have been seen that the problem is related 
> with my `PATH`. I have installed chromium via nix package manager, and for 
> this reason it is not in the `PATH` that dom0 is able to see. Answering your 
> question, it happens with any other package I installed with nix.
> 
> It doesn't happen in my VM because there I have the `PATH` configured with 
> zsh when I log in.
> 
> So, now, the question comes down to: how could I change my VM `PATH` seen 
> from dom0? I tried with my VM `~/.profile` and `~/.bashrc` but without 
> success. I suspect this may be related with another topic I open some time 
> ago:
> 
> https://groups.google.com/forum/#!topic/qubes-users/G9F3EHpeU2Q
> 
> Thank you very much
> 

The issue you raise there arises because the xterm is not a login shell
so will not use .profile.
It is interactive so (using bash) will use .bashrc

On the immediate question here you can always set the path explicitly:
qvm-run -p qube "export PATH=$PATH: && foo"

-- 
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/20170209171726.GA2064%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-09 Thread marc
> Hello, did you run "Add more shortcuts" at least once (look which apps
> are there)? I got very confused by this point in another, maybe related
> situation: when changing the templateVM you *must* do so, since symbolic
> links to all apps are different in fedora and debian, for example.   All
> the best, Bernhard

Thanks for your answer haaber. Yes, I run that... now I see it is related with 
the application PATH. Please, see previous replies for details.

-- 
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/8d03a102-ece2-4642-9a61-bd803b8a6259%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-09 Thread marc
> I dont see this behaviour in a TemplateBased qube, or a standalone.
> In both, the browser just opens.
> That's with a standard Debian-8 template.
> 
> You can try running with '-p' option to see if any errors are being
> thrown.

Thanks for your answer Unman. The issue is that I installed it with nix package 
manager and then it ends up in another path. Please, see my previous reply for 
details.

-- 
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/3d9b1e42-870c-4e93-8835-807a727c417b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-09 Thread marc
> Is chromium the only program with which you experience this problem?

Thanks for your answer Andrew.

Thanks to a private reply I got, I have been seen that the problem is related 
with my `PATH`. I have installed chromium via nix package manager, and for this 
reason it is not in the `PATH` that dom0 is able to see. Answering your 
question, it happens with any other package I installed with nix.

It doesn't happen in my VM because there I have the `PATH` configured with zsh 
when I log in.

So, now, the question comes down to: how could I change my VM `PATH` seen from 
dom0? I tried with my VM `~/.profile` and `~/.bashrc` but without success. I 
suspect this may be related with another topic I open some time ago:

https://groups.google.com/forum/#!topic/qubes-users/G9F3EHpeU2Q

Thank you very much

-- 
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/acc2936b-4c14-4dbd-b426-624820d0d58b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-08 Thread haaber
On 02/09/2017 03:31 AM, Unman wrote:
> On Wed, Feb 08, 2017 at 01:42:44PM -0800, Andrew David Wong wrote:
> On 2017-02-07 06:35, m...@lamarciana.com wrote:
> >>> Hi,
> >>>
> >>> I installed chromium browser in a debian-8 based standalone VM
> called 'work'. If I run, from dom0:
> >>>
> >>> ```
> >>> qvm-run work chromium
> >>> ```
> >>>
> >>> it outputs:
> >>>
> >>> ```
> >>> Running command on VM: 'work'...
> >>> ```
> >>>
> >>> but nothing happens. It is the same if I use shortcut desktop menu
> (which I guess executes the same command).
> >>>
> >>> If, instead, I run `chromium` from within a terminal in 'work' it
> works fine.
> >>>
> >>> I thought maybe it was a permissions problem with folder
> `~/.config/chromium`, but I granted everything to everybody just to
> check it and nothing changes.
> >>>
> >>> I'm quite lost because, as there is nothing in dom0 stderr, I
> don't know how I could debug it.
> >>>
> >>> I would be thankful for any help.
> >>>
> >>> Thanks!
> >>>
>
> Is chromium the only program with which you experience this problem?
>
> > I dont see this behaviour in a TemplateBased qube, or a standalone. >
In both, the browser just opens. > That's with a standard Debian-8
template. > > You can try running with '-p' option to see if any errors
are being > thrown. >

Hello, did you run "Add more shortcuts" at least once (look which apps
are there)? I got very confused by this point in another, maybe related
situation: when changing the templateVM you *must* do so, since symbolic
links to all apps are different in fedora and debian, for example.   All
the best, Bernhard

-- 
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/0451a2b5-2749-0825-c11c-fbfc0fb21130%40web.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-08 Thread Unman
On Wed, Feb 08, 2017 at 01:42:44PM -0800, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-02-07 06:35, m...@lamarciana.com wrote:
> > Hi,
> > 
> > I installed chromium browser in a debian-8 based standalone VM called 
> > 'work'. If I run, from dom0:
> > 
> > ```
> > qvm-run work chromium
> > ```
> > 
> > it outputs:
> > 
> > ```
> > Running command on VM: 'work'...
> > ```
> > 
> > but nothing happens. It is the same if I use shortcut desktop menu (which I 
> > guess executes the same command).
> > 
> > If, instead, I run `chromium` from within a terminal in 'work' it works 
> > fine.
> > 
> > I thought maybe it was a permissions problem with folder 
> > `~/.config/chromium`, but I granted everything to everybody just to check 
> > it and nothing changes.
> > 
> > I'm quite lost because, as there is nothing in dom0 stderr, I don't know 
> > how I could debug it.
> > 
> > I would be thankful for any help.
> > 
> > Thanks!
> > 
> 
> Is chromium the only program with which you experience this problem?
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYm5DQAAoJENtN07w5UDAwqF8QAIAFoV8PSp3JseDUXT4OLemO
> fmFtz79wNyUMmcj010XHpCg0mMb/QcKZh0gDZaQLqjHyH55YoIg+RfxV6Sntm1qL
> MTmnNBlDjMfspViZ2y0F63LnIZA5VNiHVzY9DHQqv2sPn5mkECgB7YrpfO/viatd
> 8EUmynutXojfXYvIjVwoaIq+bV5NB7XkoVij48dDHMSUJEqwMj7NxdnKSv6bVa6w
> jP01a67KHF84gaVgaiPvkxVhfuDOM5Euj8hR6aXZaUEHNVM4CmjKm1ZtZjVwm2Lv
> 3dlbylbPAlixr/GDYtGlQ8UyIfziSZ3oFLprwGPdeBAoY8nFI8RDzmvzyD1L/gr2
> oR3yURw1pnD91fUo4zO5lQS0Ry37kejeCrCfdD8GgrrhB6QpUbwsuV9tChsSHB5G
> T27JMg7YR+6fLI8UxqsQ028xXqolWb/fBcwnBR6pfSL3c/sXLjyog3fFKDmowEsz
> FlPNt6rNSAQVprBU7RLrIt7g89wQfliSro4pUXbr1BcQz1hbxCMAd9C051fE6Bnu
> buSW0sCD+FT8i/UN7FYue2M6qERXUkHBnTR7JeCDV6N+DkNLwAWMG57UryLenKm0
> DD+cQ78OBmMfbbwo+aGeKPooX3xXxgb8Yarpwh2BmBgt3beD461GudkZ3I1YKCeU
> IAw9S91T3yQnJGEJsm6H
> =+KIj
> -END PGP SIGNATURE-

I dont see this behaviour in a TemplateBased qube, or a standalone.
In both, the browser just opens.
That's with a standard Debian-8 template.

You can try running with '-p' option to see if any errors are being
thrown.

-- 
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/20170209023152.GA29750%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] qvm-run fails silently with chromium

2017-02-08 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-02-07 06:35, m...@lamarciana.com wrote:
> Hi,
> 
> I installed chromium browser in a debian-8 based standalone VM called 'work'. 
> If I run, from dom0:
> 
> ```
> qvm-run work chromium
> ```
> 
> it outputs:
> 
> ```
> Running command on VM: 'work'...
> ```
> 
> but nothing happens. It is the same if I use shortcut desktop menu (which I 
> guess executes the same command).
> 
> If, instead, I run `chromium` from within a terminal in 'work' it works fine.
> 
> I thought maybe it was a permissions problem with folder 
> `~/.config/chromium`, but I granted everything to everybody just to check it 
> and nothing changes.
> 
> I'm quite lost because, as there is nothing in dom0 stderr, I don't know how 
> I could debug it.
> 
> I would be thankful for any help.
> 
> Thanks!
> 

Is chromium the only program with which you experience this problem?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYm5DQAAoJENtN07w5UDAwqF8QAIAFoV8PSp3JseDUXT4OLemO
fmFtz79wNyUMmcj010XHpCg0mMb/QcKZh0gDZaQLqjHyH55YoIg+RfxV6Sntm1qL
MTmnNBlDjMfspViZ2y0F63LnIZA5VNiHVzY9DHQqv2sPn5mkECgB7YrpfO/viatd
8EUmynutXojfXYvIjVwoaIq+bV5NB7XkoVij48dDHMSUJEqwMj7NxdnKSv6bVa6w
jP01a67KHF84gaVgaiPvkxVhfuDOM5Euj8hR6aXZaUEHNVM4CmjKm1ZtZjVwm2Lv
3dlbylbPAlixr/GDYtGlQ8UyIfziSZ3oFLprwGPdeBAoY8nFI8RDzmvzyD1L/gr2
oR3yURw1pnD91fUo4zO5lQS0Ry37kejeCrCfdD8GgrrhB6QpUbwsuV9tChsSHB5G
T27JMg7YR+6fLI8UxqsQ028xXqolWb/fBcwnBR6pfSL3c/sXLjyog3fFKDmowEsz
FlPNt6rNSAQVprBU7RLrIt7g89wQfliSro4pUXbr1BcQz1hbxCMAd9C051fE6Bnu
buSW0sCD+FT8i/UN7FYue2M6qERXUkHBnTR7JeCDV6N+DkNLwAWMG57UryLenKm0
DD+cQ78OBmMfbbwo+aGeKPooX3xXxgb8Yarpwh2BmBgt3beD461GudkZ3I1YKCeU
IAw9S91T3yQnJGEJsm6H
=+KIj
-END PGP SIGNATURE-

-- 
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/94a9f836-120c-4b23-1903-dee7447481c5%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.