Skip to content
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

qui-devices can become stale #5223

Closed
jpouellet opened this issue Aug 7, 2019 · 2 comments
Closed

qui-devices can become stale #5223

jpouellet opened this issue Aug 7, 2019 · 2 comments
Assignees
Labels
C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.

Comments

@jpouellet
Copy link
Contributor

Qubes OS version:

r4.0.2-rc1 / qubes-desktop-linux-manager-4.0.20-1.fc25.noarch

Affected component(s) or functionality:

qui-devices tray (qubes-manager)

Steps to reproduce the behavior:

  1. Start a DispVM
  2. Attach one or more devices
  3. Somehow terminate the DispVM (either shutdown or killing)
  4. Repeat

Expected or desired behavior:

The devices tray to show the same information as qvm-block

Actual behavior:

stale-devices

General notes:

I noticed this in a DispVM which probed an LVM pool with many (several hundred) devices.

I have consulted the following relevant documentation:

I am aware of the following related, non-duplicate issues:

Seemingly similar state-desynchronization issues:

@andrewdavidwong andrewdavidwong added C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug labels Aug 7, 2019
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Aug 7, 2019
@marmarta
Copy link
Member

marmarta commented Aug 7, 2019

are you using the current-testing repo? ( https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories )

@marmarta
Copy link
Member

marmarta commented Aug 8, 2019

it should have been fixed in QubesOS/qubes-desktop-linux-manager@2056e1a and looks like it works on my side; if you still experience this issue while using current-testing repository, please reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: manager/widget P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Projects
None yet
Development

No branches or pull requests

3 participants