"Qubes Devices" widget not working anymore

91 views
Skip to first unread message

john.e...@gmail.com

unread,
Apr 4, 2019, 12:15:05 PM4/4/19
to qubes-users
For no apparent reason, when I plug a USB flash drive into my computer (Qubes 4.0) the Qubes Devices widget in the upper right no longer displays the device. When I plug in the flash drive the system presents multiple black popups indicating the drive is available, but nothing shows in Qubes Devices.

I'm using a USB qube called sys-usb, and this function used to work perfectly.

Any suggestions would be greatly appreciated.

Thanks.
John

g80vm...@riseup.net

unread,
Apr 4, 2019, 2:11:37 PM4/4/19
to qubes...@googlegroups.com
john.e...@gmail.com:
This happens often for me. For some reason the UI seems to freeze. Try
running, in a terminal in Dom0:

$ systemctl --user restart qubes-...@qui-devices.service

Does that solve the issue? If so, maybe you should make a desktop
shortcut for that command--at least until the qui-devices widget is more
stable.

Lorenzo Lamas

unread,
Apr 4, 2019, 3:53:49 PM4/4/19
to qubes-users
Try updating to qubes-desktop-linux-manager 4.0.17 in current-testing.

john.e...@gmail.com

unread,
Apr 5, 2019, 9:15:44 AM4/5/19
to qubes-users
On Thursday, April 4, 2019 at 3:53:49 PM UTC-4, Lorenzo Lamas wrote:
> Try updating to qubes-desktop-linux-manager 4.0.17 in current-testing.

Thanks, Lorenzo. It is fixed now, however, I believe I made the mistake of enabling the repo rather than just installing the package from the repo. Nothing terrible happened, but now every time a new VM is started there's a loud "pop" from my speakers, and it's uneffected by the volume control within Qubes. Not terrible, but it means every time I open a disposable VM there's a loud pop (I'll turn down my speakers).

If you or anyone has any suggestions regarding that that would be fantastic.

Thanks.
John

Lorenzo Lamas

unread,
Apr 5, 2019, 10:34:21 AM4/5/19
to qubes-users

You could try rolling back the update:
"You could look at 'sudo dnf history' in dom0 to identify the last
update, then roll back to the prior one:

sudo dnf rollback <prior transaction ID>

So if the update that caused the problem is transaction 150, specify 149
on the command line."

And then install only qubes-desktop-linux-manager from current-testing: "sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-desktop-linux-manager". You may need to add "--best --allowerasing" to that.

john.e...@gmail.com

unread,
Apr 5, 2019, 11:26:26 AM4/5/19
to qubes-users

Again, thank you for this. Unfortunately, rolling back presents me with an error message that "A transaction connot be undone" and mentions "No package qubes-manager-0:4.0.28-1.fc25.noarch available."

I'm going to just live with it, and learn my lesson. Thanks again.

Reply all
Reply to author
Forward
0 new messages