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

usb-c passthrough USB-HUB are 'forgotten' #617

Open
commandline-be opened this issue Apr 14, 2024 · 3 comments
Open

usb-c passthrough USB-HUB are 'forgotten' #617

commandline-be opened this issue Apr 14, 2024 · 3 comments

Comments

@commandline-be
Copy link

commandline-be commented Apr 14, 2024

Though use of 'gsettings set org.gnome.desktop.privacy usb-protection false' has some effect there is no permanent fix.

Set-up is a Monitor with USB-C and USB-A ports, there is a USB-A (3.1) hub connected to the monitor USB-A port, the usb-c port is connected to the computer. The monitor steering happens over USB-C, the USB-HUB(s) in the monitor are found on the computer.

Whenever the computer reboots are resumes from suspend or hibernate the USB HUBs must be permitted again, the connect-type is reported as 'unknown'

There is one allow-action required for the via-port (N-N.N) and one for the child via-port (N-N.N.n) There is no difference on the with-interface mentioned for these ports. So, though there's some variance in the hashes this setup seems mostly if not entirely stable.

In other words, it seems the connection are forgotten while they're now repeatedly found in the rules.conf file

Is this a known issue ?

edit: looking a bit deeper into this it seems a hub connected to a hub is prone to cause such issues and these seem reproducible. Connecting a hub to a hub happens with devices offering pass through, monitor, docking, keyboard with a pass-through etc.

@bwildenhain
Copy link

I can confirm forgotten devices connected via a USB-C screen (Dell P3223DE) (USB 3.2 internal Ethernet adapter and USB 2.1 Logitech C930e webcam), while other devices on the same screen work (no additional hub involved).

@secretmango
Copy link

Did you try this with the usbguard interface or just the gsettings one?

use this

usbguard list-devices
usbguard allow-device -p NUMBER

this allows a device permanently. The number is something like 1,2,3

@commandline-be
Copy link
Author

@secretmango would not report such if it worked would I/we ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants