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

fedora 26 dvm not displayed as disposable #3464

Open
kototama opened this Issue Jan 15, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@kototama

kototama commented Jan 15, 2018

Qubes OS version:

Q4RC3

Affected TemplateVMs:

fedora 26


Steps to reproduce the behavior:

Install fedora 26 template with:

sudo qubes-dom0-update qubes-template-fedora-26
qvm-create -l red -t fedora-26 fedora-26-dvm
qvm-prefs fedora-26-dvm template_for_dispvms True
qvm-features fedora-26-dvm appmenus-dispvm 1
qubes-prefs default-dispvm fedora-26-dvm

Expected behavior:

A menu entry with Disposable: fedora-26-dvm is created

Actual behavior:

A menu entry with Domain: fedora-26-dvm is created

General notes:

Is there a workaround? How can I start a fedora 26 disposable VM?


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 15, 2018

Member

qvm-features fedora-26-dvm appmenus-dispm 1

Typo, should be appmenus-dispvm.
If that doesn't help, try qvm-appmenus --update fedora-26-dvm

Member

marmarek commented Jan 15, 2018

qvm-features fedora-26-dvm appmenus-dispm 1

Typo, should be appmenus-dispvm.
If that doesn't help, try qvm-appmenus --update fedora-26-dvm

@kototama

This comment has been minimized.

Show comment
Hide comment
@kototama

kototama Jan 15, 2018

Sorry what is the typo? You mean it should be appmenu-dispvm ??

Sorry what is the typo? You mean it should be appmenu-dispvm ??

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 15, 2018

Member

You wrote appmenus-dispm, should be appmenus-dispvm.

Member

marmarek commented Jan 15, 2018

You wrote appmenus-dispm, should be appmenus-dispvm.

@kototama

This comment has been minimized.

Show comment
Hide comment
@kototama

kototama Jan 15, 2018

I see. I had it right in the bash history, just typed it wrongly for this bug report.
Typing qvm-appmenus --update fedora-26-dvm solved it. Thank you very much.

One more question, I have: update-availables 1 in fedora-25-dvm prefs but not in fedora-26-dvm. Do I need to set it?

I see. I had it right in the bash history, just typed it wrongly for this bug report.
Typing qvm-appmenus --update fedora-26-dvm solved it. Thank you very much.

One more question, I have: update-availables 1 in fedora-25-dvm prefs but not in fedora-26-dvm. Do I need to set it?

@kototama

This comment has been minimized.

Show comment
Hide comment
@kototama

kototama Jan 15, 2018

I am editing the bug report for the typo, since the bug is not due to a typo...

I am editing the bug report for the typo, since the bug is not due to a typo...

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 15, 2018

Member

One more question, I have: update-availables 1 in fedora-25-dvm prefs but not in fedora-26-dvm. Do I need to set it?

No. It should be on the template (fedora-26), not fedora-26-dvm. It is info that you have some updates pending for that template. updates-available should be handled automatically, no manual action should be required.

Member

marmarek commented Jan 15, 2018

One more question, I have: update-availables 1 in fedora-25-dvm prefs but not in fedora-26-dvm. Do I need to set it?

No. It should be on the template (fedora-26), not fedora-26-dvm. It is info that you have some updates pending for that template. updates-available should be handled automatically, no manual action should be required.

@andrewdavidwong andrewdavidwong added this to the Documentation/website milestone Jan 16, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 16, 2018

Member

@kototama, would you be willing to help us document this? Please see the Documentation Guidelines for details.

Member

andrewdavidwong commented Jan 16, 2018

@kototama, would you be willing to help us document this? Please see the Documentation Guidelines for details.

marmarek added a commit to marmarek/qubes-desktop-linux-common that referenced this issue Jan 19, 2018

appmenus: update event names one more time
Rollback the change (names here were ok, it was wrong in core-admin
side). But keep other fixes by @jpouellet

QubesOS/qubes-issues#3464

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Jan 23, 2018

Closed

desktop-linux-common v4.0.9 (r4.0) #382

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