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

VM Manager doesn't load after user re-login #2175

Open
lhaeberle opened this Issue Jul 15, 2016 · 3 comments

Comments

3 participants
@lhaeberle

Qubes OS version R3.2

Affected TemplateVMs: none


Expected behavior:

loadable VM Manager

Actual behavior:

After re-login into QubesOS VM Manager doesn't load any more // isn't loadable

Steps to reproduce the behavior:

  1. log off
  2. re-login
  3. try to load VM Manager

General notes:


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 15, 2016

Member

I can confirm this issue. The problem is that qubes-manager is still running in the background, so the new instance refuses to start...

Member

marmarek commented Jul 15, 2016

I can confirm this issue. The problem is that qubes-manager is still running in the background, so the new instance refuses to start...

@lhaeberle

This comment has been minimized.

Show comment
Hide comment
@lhaeberle

lhaeberle Jul 15, 2016

ok. Will kill the process to work around. Thanks.

ok. Will kill the process to work around. Thanks.

@Zrubi

This comment has been minimized.

Show comment
Hide comment
@Zrubi

Zrubi Sep 14, 2016

Member

relogging involves more issues:

  • the tray icons stop changing ("animating") for example the NM icon shows the disconnected state even if it is actually connected.
  • all the opened windows, from started VMs are not closed
    I see no real difference between lock and logout.
    logout only resets the KDE/Xfce session related things, leving all the VMs alone.
Member

Zrubi commented Sep 14, 2016

relogging involves more issues:

  • the tray icons stop changing ("animating") for example the NM icon shows the disconnected state even if it is actually connected.
  • all the opened windows, from started VMs are not closed
    I see no real difference between lock and logout.
    logout only resets the KDE/Xfce session related things, leving all the VMs alone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment