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 upQubes 4.0-rc2 Device Widget Ghost Entries #3215
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Oct 26, 2017
Member
This goes without saying, I don't really understand how the widget organizes itself in the first place. There are two sets of rows what is the difference between them?
Those are different type/layers of devices - at the top are block devices, below are usb devices. If a device is both, it is in both places (but you can choose how you want to attach it).
Those are different type/layers of devices - at the top are block devices, below are usb devices. If a device is both, it is in both places (but you can choose how you want to attach it). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ERFier
Oct 26, 2017
I could confirm this issue yesterday. It was also the case if one restarts the usb-vm for some reason. It's not the thumbdrive getting displayed as general usb device as well as block device but non blockdevices, like WWAN Card or Yubikey in my case, getting duplicated.
Today, I think due to some update I applied yesterday, I cant reproduce the behavior. But the widget still lacks a proper update. If I shutdown the usb-vm the devices are still shown despite the fact they are not accessible anymore. The devices are also still shown as connected and there is no way to detach them and reattach them as the usb-vm starts again or the device is plugged in again. Maybe a force update function accessible thru a right-click context menu is a good idea to at least empower the user to recover the widget once it displays nonsense.
ERFier
commented
Oct 26, 2017
|
I could confirm this issue yesterday. It was also the case if one restarts the usb-vm for some reason. It's not the thumbdrive getting displayed as general usb device as well as block device but non blockdevices, like WWAN Card or Yubikey in my case, getting duplicated. Today, I think due to some update I applied yesterday, I cant reproduce the behavior. But the widget still lacks a proper update. If I shutdown the usb-vm the devices are still shown despite the fact they are not accessible anymore. The devices are also still shown as connected and there is no way to detach them and reattach them as the usb-vm starts again or the device is plugged in again. Maybe a force update function accessible thru a right-click context menu is a good idea to at least empower the user to recover the widget once it displays nonsense. |
andrewdavidwong
added
bug
C: qubes-manager
UX
labels
Oct 27, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Oct 27, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
quaterniol
Nov 12, 2017
When the menu for the USB device widget is open and an USB mouse (e.g. Logitech mouse) is removed, then almost always the entry for the mouse stays in the menu. Inserting the mouse again creates a new entry. Repeating this creates a lot of entries. (I am using qubes 4.0-rc2 and saw the entry disappear when the mouse was removed only once.)
quaterniol
commented
Nov 12, 2017
|
When the menu for the USB device widget is open and an USB mouse (e.g. Logitech mouse) is removed, then almost always the entry for the mouse stays in the menu. Inserting the mouse again creates a new entry. Repeating this creates a lot of entries. (I am using qubes 4.0-rc2 and saw the entry disappear when the mouse was removed only once.) |
added a commit
to marmarta/qubes-desktop-linux-manager
that referenced
this issue
Nov 20, 2017
marmarta
referenced this issue
in QubesOS/qubes-desktop-linux-manager
Nov 20, 2017
Merged
Fixed errors with qui-devices #13
qubesos-bot
referenced this issue
in QubesOS/updates-status
Nov 21, 2017
Closed
desktop-linux-manager v4.0.5 (r4.0) #306
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
awokd
Jan 30, 2018
In 4.0 rc3, clicking Eject on an attached USB device seems to do nothing. Selecting it again from the widget shows it still connected to the AppVM. Seems like it might be related to this issue, but should I open a new one?
awokd
commented
Jan 30, 2018
|
In 4.0 rc3, clicking Eject on an attached USB device seems to do nothing. Selecting it again from the widget shows it still connected to the AppVM. Seems like it might be related to this issue, but should I open a new one? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ThierryIT
Feb 3, 2018
same for 4.0 rc4 and doesn't show anything in the Qubes manager has it was possible with the Qubes 3.2.
ThierryIT
commented
Feb 3, 2018
|
same for 4.0 rc4 and doesn't show anything in the Qubes manager has it was possible with the Qubes 3.2. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Feb 3, 2018
Member
In 4.0 rc3, clicking Eject on an attached USB device seems to do nothing. Selecting it again from the widget shows it still connected to the AppVM. Seems like it might be related to this issue, but should I open a new one?
Sure, that sounds different enough to merit a separate issue. It could turn out to be the same cause, but we have no way of knowing that right now.
Sure, that sounds different enough to merit a separate issue. It could turn out to be the same cause, but we have no way of knowing that right now. |
andrewdavidwong
modified the milestones:
Release 4.0,
Release 4.0 updates
Mar 31, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
RefinedSoftwareLLC
Jun 14, 2018
- Also, when the DVD in a drive is changed, the displayed title of the current DVD isn't updated.
RefinedSoftwareLLC
commented
Jun 14, 2018
•
|
section0x8 commentedOct 26, 2017
The widget fails to keep a real time list of devices. If a device is not properly removed, the widget will not realize that it is gone. This can happen if the device is unplugged without detaching it. It can happen if a VM powers off without the device being removed first. And it can probably happen a number of other ways.
Screenshot:

This goes without saying, I don't really understand how the widget organizes itself in the first place. There are two sets of rows what is the difference between them?