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

sys-usb devices automatically removed after anon-whonix is shut down #4078

Closed
MartynasJanonis opened this Issue Jul 13, 2018 · 11 comments

Comments

Projects
None yet
4 participants
@MartynasJanonis

Qubes OS version: R4.0

Affected component(s):

sys-usb, anon-whonix


Steps to reproduce the behavior:

  • Start anon-whonix
  • After it starts, shut it down

Expected behavior:

All sys-usb devices remain connected

Actual behavior:

All sys-usb devices are automatically removed and not visible in the device manager menu.

General notes:

Whonix version 14. I have to restart the sys-usb qube for the devices to reappear and only devices marked "dom0:" remain connected.


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2018

Member

Have you connected any devices to anon-whonix, or is it totally independent? Check also "Devices" tab in anon-whonix settings - there should be no selected devices.

Member

marmarek commented Jul 13, 2018

Have you connected any devices to anon-whonix, or is it totally independent? Check also "Devices" tab in anon-whonix settings - there should be no selected devices.

@MartynasJanonis

This comment has been minimized.

Show comment
Hide comment
@MartynasJanonis

MartynasJanonis Jul 13, 2018

They are totally independent. Nothing is connected to anon-whonix. anon-whonix doesn't even have qubes-usb-proxy.

MartynasJanonis commented Jul 13, 2018

They are totally independent. Nothing is connected to anon-whonix. anon-whonix doesn't even have qubes-usb-proxy.

@MartynasJanonis

This comment has been minimized.

Show comment
Hide comment
@MartynasJanonis

MartynasJanonis Jul 13, 2018

Interestingly, the devices only disappear from the toolbar and qvm-usb still shows them. Attaching a random device to any qube makes all devices reappear in the toolbar.
sys-usb issue1

Interestingly, the devices only disappear from the toolbar and qvm-usb still shows them. Attaching a random device to any qube makes all devices reappear in the toolbar.
sys-usb issue1

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2018

Member

Hmm, do you see any errors in ~/.xsession-errors in dom0?

Member

marmarek commented Jul 13, 2018

Hmm, do you see any errors in ~/.xsession-errors in dom0?

@MartynasJanonis

This comment has been minimized.

Show comment
Hide comment
@MartynasJanonis

MartynasJanonis Jul 13, 2018

Yes,
(Thunar:5453): thunar-WARNING **: Failed to launch the volume manager (Failed to execute child process "thunar-volman" (No such file or directory)), make sure you have the "thunar-volman" package installed.

Yes,
(Thunar:5453): thunar-WARNING **: Failed to launch the volume manager (Failed to execute child process "thunar-volman" (No such file or directory)), make sure you have the "thunar-volman" package installed.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2018

Member

Anything else? Something with "qui" or "devices" in message?

Member

marmarek commented Jul 13, 2018

Anything else? Something with "qui" or "devices" in message?

@MartynasJanonis

This comment has been minimized.

Show comment
Hide comment
@MartynasJanonis

MartynasJanonis Jul 13, 2018

No, just a lot of "thunar-WARNING" messages.
Also, attaching USB devices fixes the problem (i.e. all devices become visible in the toolbar).
Attaching a screenshot of what happens after anon-whonix shuts down.
screenshot_2018-07-13_20-05-01

No, just a lot of "thunar-WARNING" messages.
Also, attaching USB devices fixes the problem (i.e. all devices become visible in the toolbar).
Attaching a screenshot of what happens after anon-whonix shuts down.
screenshot_2018-07-13_20-05-01

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2018

Member

What is qid of anon-whonix and sys-usb on your system (see qvm-prefs tool)? Devices widget identifies qubes using qid and maybe get confused by this specific values for some reason?

Member

marmarek commented Jul 13, 2018

What is qid of anon-whonix and sys-usb on your system (see qvm-prefs tool)? Devices widget identifies qubes using qid and maybe get confused by this specific values for some reason?

@MartynasJanonis

This comment has been minimized.

Show comment
Hide comment
@MartynasJanonis

MartynasJanonis Jul 13, 2018

qvm-prefs --get anon-whonix qid
1
qvm-prefs --get sys-usb qid
13
qvm-prefs --get anon-whonix qid
1
qvm-prefs --get sys-usb qid
13
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 13, 2018

Member

Ok, that's it. qid of anon-whonix is a prefix of sys-usb's qid. I can reproduce it by shutting down a VM with qid 1 (debian-9 in my case).
Apparently in some place comparing them is broken. @marmarta is looking where.

Member

marmarek commented Jul 13, 2018

Ok, that's it. qid of anon-whonix is a prefix of sys-usb's qid. I can reproduce it by shutting down a VM with qid 1 (debian-9 in my case).
Apparently in some place comparing them is broken. @marmarta is looking where.

@marmarta

This comment has been minimized.

Show comment
Hide comment
@marmarta

marmarta Jul 13, 2018

This is a truly magnificent bug! Hopefully we've got it and the fix is underway (just let me test if it won't break another surprising thing...)

This is a truly magnificent bug! Hopefully we've got it and the fix is underway (just let me test if it won't break another surprising thing...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment