New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qubes Settings / Running applications #3522

Closed
ThierryIT opened this Issue Feb 3, 2018 · 13 comments

Comments

Projects
None yet
4 participants
@ThierryIT

Qubes OS version:

4.0 r4

Affected TemplateVMs:


Steps to reproduce the behavior:

Qube/Setting add applications

Expected behavior:

Be able to run chosen application from Applications/Domains: vname

Actual behavior:

Not working, have to run chosen applications from : Run command in Qube

General notes:

never work since move to Qubes 4.0


Related issues:

@marmarta

This comment has been minimized.

Show comment
Hide comment
@marmarta

marmarta Feb 9, 2018

How much RAM do you have? Maybe there's a problem with that. Do you have anything in .xessession-errors in dom0?

marmarta commented Feb 9, 2018

How much RAM do you have? Maybe there's a problem with that. Do you have anything in .xessession-errors in dom0?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 14, 2018

Member

It is about templates and/or standalone VMs restored from R3.2?

Member

marmarek commented Feb 14, 2018

It is about templates and/or standalone VMs restored from R3.2?

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 14, 2018

Seems to be coming from the ones who have been restored from 3.2 ...
I do not have any .xessession-errors

Seems to be coming from the ones who have been restored from 3.2 ...
I do not have any .xessession-errors

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Feb 14, 2018

oupsss my mistake, I do have an .xsession-errors
If starting keepassX :

  • executed QUBESRPC qubes.WaitForSession dom0 pid 2741
    send exit code 0
    pid 2741 exited with 0
    executed (nowait) QUBESRPC qubes.StartApp+keepassx dom0 pid 2753
    send exit code

and nothing else happen ....

oupsss my mistake, I do have an .xsession-errors
If starting keepassX :

  • executed QUBESRPC qubes.WaitForSession dom0 pid 2741
    send exit code 0
    pid 2741 exited with 0
    executed (nowait) QUBESRPC qubes.StartApp+keepassx dom0 pid 2753
    send exit code

and nothing else happen ....

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 4, 2018

Even if from dom0 I have done an: qvm-sync-appmenus vmname
In ~/.local/share/qubes-appmenus/vm_name I have as folders: apps apps.icons apps.tempicons apps.templates and whitelisted-appmenus.list
Thx

ThierryIT commented Mar 4, 2018

Even if from dom0 I have done an: qvm-sync-appmenus vmname
In ~/.local/share/qubes-appmenus/vm_name I have as folders: apps apps.icons apps.tempicons apps.templates and whitelisted-appmenus.list
Thx

@ThierryIT

This comment has been minimized.

Show comment
Hide comment

allo ?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Mar 8, 2018

Member

@ThierryIT:

allo ?

Rest assured, we have not forgotten about this issue, but the devs have been busy with the release of 4.0-rc5 and also have many other issues to attend to.

Member

andrewdavidwong commented Mar 8, 2018

@ThierryIT:

allo ?

Rest assured, we have not forgotten about this issue, but the devs have been busy with the release of 4.0-rc5 and also have many other issues to attend to.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2018

Member

3.2 VMs did not have qubes.StartApp service. I haven't yet fully developed template upgrade procedure (right now it is mostly manual, involving manual key import, repository switch etc).
But you should be able to switch to 3.2-way appmenus, by adding appmenus-legacy feature to that StandaloneVM/TemplateVM. Just to clarify - is it the case? It shouldn't be if you restore 3.2 AppVM but use a template from 4.0.

How to enable appmenus-legacy feature: qvm-features NAME_OF_VM appmenus-legacy 1

Member

marmarek commented Mar 8, 2018

3.2 VMs did not have qubes.StartApp service. I haven't yet fully developed template upgrade procedure (right now it is mostly manual, involving manual key import, repository switch etc).
But you should be able to switch to 3.2-way appmenus, by adding appmenus-legacy feature to that StandaloneVM/TemplateVM. Just to clarify - is it the case? It shouldn't be if you restore 3.2 AppVM but use a template from 4.0.

How to enable appmenus-legacy feature: qvm-features NAME_OF_VM appmenus-legacy 1

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 8, 2018

Hi,
Doesn't seems to work for me.
This is a StandaloneVM.
Thx

Hi,
Doesn't seems to work for me.
This is a StandaloneVM.
Thx

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2018

Member

Have you called qvm-sync-appmenus after this change?

Member

marmarek commented Mar 8, 2018

Have you called qvm-sync-appmenus after this change?

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 8, 2018

no I have restated the VM

no I have restated the VM

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 8, 2018

I have just called qvm-sync-appmenus but:
File "/usr/lib/python3.5/site-packages/qubesappm/receive.py" line 379, in main vm=args.domains[0] indexError: List index out of range

I have just called qvm-sync-appmenus but:
File "/usr/lib/python3.5/site-packages/qubesappm/receive.py" line 379, in main vm=args.domains[0] indexError: List index out of range

@ThierryIT

This comment has been minimized.

Show comment
Hide comment
@ThierryIT

ThierryIT Mar 12, 2018

After an update on my VM, seems to now work ...
Thx

After an update on my VM, seems to now work ...
Thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment