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 upCan not find new domain with qubesadmin - Qubes #3875
Comments
donob4n
changed the title from
Can't find new domain with qubesadmin - Qubes
to
Can not find new domain with qubesadmin - Qubes
May 3, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Yes, caching, see |
andrewdavidwong
added
the
C: core
label
May 4, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
May 4, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
donob4n
commented
May 4, 2018
|
Ouch, ok thanks :) |
donob4n
closed this
May 4, 2018
andrewdavidwong
added
the
resolved
label
May 5, 2018
donob4n
referenced this issue
May 6, 2018
Closed
Refreshing Qube Manager Immediately after closing DispVM causes varied critical errors #3856
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
donob4n
May 6, 2018
Ey @marmarek
Could this cache be handled internally? I mean it gets cleared automatically when needed, otherwise I see a lot of places where it needs to be cleaned and also its pretty error prune.
donob4n
commented
May 6, 2018
•
|
Ey @marmarek Could this cache be handled internally? I mean it gets cleared automatically when needed, otherwise I see a lot of places where it needs to be cleaned and also its pretty error prune. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
donob4n commentedMay 3, 2018
•
edited
Edited 4 times
-
donob4n
edited May 4, 2018 (most recent)
-
donob4n
edited May 3, 2018
-
donob4n
edited May 3, 2018
-
donob4n
edited May 3, 2018
Qubes OS version:
R4
Affected component(s):
Potentially all things using import Qubes from qubesadmin
Steps to reproduce the behavior:
Currently I am trying to implement dbus events in Qube Manager. When recieve a 'DomainAdded' signal a callback function is called for handling it. Since it only knows the 'qid' of the domain it loops through qubes_app.domains and gets it. Unfortunately sometimes (maybe when there are some amount of domains) it does not find it. Here is a example log after creating two new domains:
Expected behavior:
If we recieved a 'DomainAdded' signal, that domain should be in Qubes.domains.
Actual behavior:
It is not.
General notes:
Maybe is this due some kind of caching? After restarting qube-manager the new domain appears fine.
Making new Qubes() objects when I need to find a new domain also works fine.
Related issues: