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

4.0rc1 incorrect DispVM startup notifications #3097

Closed
3hhh opened this Issue Sep 15, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@3hhh

3hhh commented Sep 15, 2017

Minor bug:

In 4.0rc1 (current testing repos pulled) the notifications during a DispVM startup are almost always incorrect: They display e.g. "DispVM777 started" when DispVM565 was started.

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Sep 16, 2017

@kalkin kalkin self-assigned this Sep 18, 2017

@kalkin

This comment has been minimized.

Show comment
Hide comment
@kalkin

kalkin Sep 18, 2017

Member

@marmarek I would fix this but currently I can't get dispvm to start at all.

Member

kalkin commented Sep 18, 2017

@marmarek I would fix this but currently I can't get dispvm to start at all.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 12, 2017

Contributor

I've seen the wrong VM name for normal VMs too in various UIs (IIRC at least notifications and qui-domains) when they share the same qid as an old VM.

edit: and I'm on R4-rc3 (qubes-desktop-linux-manager-4.0.5 and qubes-manager-4.0.9).

Contributor

jpouellet commented Dec 12, 2017

I've seen the wrong VM name for normal VMs too in various UIs (IIRC at least notifications and qui-domains) when they share the same qid as an old VM.

edit: and I'm on R4-rc3 (qubes-desktop-linux-manager-4.0.5 and qubes-manager-4.0.9).

@3hhh

This comment has been minimized.

Show comment
Hide comment
@3hhh

3hhh Mar 14, 2018

This one was fixed a while ago I believe.

3hhh commented Mar 14, 2018

This one was fixed a while ago I believe.

@3hhh 3hhh closed this Mar 14, 2018

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