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://r

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

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 pat

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

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

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 lo

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)

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 e

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

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 ch

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 >

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 wit

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

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: > >>> > >>> ``` > >>

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: > > >

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: