Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upQubes Settings / Running applications #3522
Comments
andrewdavidwong
added
bug
C: qubes-manager
labels
Feb 3, 2018
andrewdavidwong
added this to the Release 4.0 milestone
Feb 3, 2018
ThierryIT
referenced this issue
Feb 4, 2018
Open
Apps do not open when starting VM from launcher #3533
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
It is about templates and/or standalone VMs restored from R3.2? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
ThierryIT
commented
Feb 14, 2018
|
Seems to be coming from the ones who have been restored from 3.2 ... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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 ....
ThierryIT
commented
Feb 14, 2018
|
oupsss my mistake, I do have an .xsession-errors
and nothing else happen .... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThierryIT
commented
Mar 7, 2018
|
allo ? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Mar 8, 2018
Member
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.
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
|
3.2 VMs did not have How to enable |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThierryIT
commented
Mar 8, 2018
|
Hi, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Have you called |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThierryIT
commented
Mar 8, 2018
|
no I have restated the VM |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
ThierryIT
commented
Mar 8, 2018
|
I have just called |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThierryIT
commented
Mar 12, 2018
|
After an update on my VM, seems to now work ... |
ThierryIT commentedFeb 3, 2018
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: