LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   VirtualBox does not see USB devices in MATE (https://www.linuxquestions.org/questions/slackware-14/virtualbox-does-not-see-usb-devices-in-mate-4175693390/)

Jeebizz 04-09-2021 08:16 AM

VirtualBox does not see USB devices in MATE
 
2 Attachment(s)
I switched from LXDE to MATE - but it seems MATE handles USB devices differently. In short under MATE I can no longer get VirtualBox to detect my usb headset to pass through to a host OS (in this case Win10). Dmesg shows that Linux itself obviously detects it:

Code:

[32525.314051] usb 3-1.2: new full-speed USB device number 5 using ehci-pci
[32526.717647] usb 3-1.2: New USB device found, idVendor=046d, idProduct=0a8f
[32526.717651] usb 3-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0
[32526.717652] usb 3-1.2: Product: Logitech USB Headset
[32526.717654] usb 3-1.2: Manufacturer: Logitech USB Headset
[32526.731850] input: Logitech USB Headset Logitech USB Headset as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.3/0003:046D:0A8F.0004/input/input15
[32526.782146] hid-generic 0003:046D:0A8F.0004: input,hidraw3: USB HID v1.11 Device [Logitech USB Headset Logitech USB Headset] on usb-0000:00:1a.0-1.2/input3
[32527.366105] usbcore: registered new interface driver snd-usb-audio
root@slackmachine:/home/slackuser#

In the sound settings for MATE I have tried to toggle both the headset on and off , but virtualbox still no longer sees the headset:

USB device list in VirtualBox:

I use things like discord too, but I did make sure that discord did not use the headset, so I unplugged and plugged the USB headset back in, and when discord saw and asked, I opted discord to not grab the headset for itself, but seems nothing I do gets VirtualBox to see the headset. Nothing else really changed, and yes GuestAdditions for VirtualBox are installed. Yes I have checked the button in the USB list, and it still does not detect anything, and this is not under --Current but in 14.2.

Jeebizz 04-09-2021 08:25 AM

Also I noticed that even my keyboard and mouse aren't listed, unlike in LXDE - so again I suspect MATE handles USB differently. Not like I actually want to pass my keyboard and mouse, just my headset - but I can't.

michaelk 04-09-2021 09:34 AM

The way I understand VirtualBox USB filters it is a way to automatically connect a particular USB device to a guest. Otherwise you need to manually connect it via the Devices pull down menu. Is the headset listed in the guest's devices -> USB menu? Once it is connected to the Guest, the device is disconnected from the host.

Hmm, I expect/assume that USB devices are desktop independent regardless of OS.

Emerson 04-09-2021 09:42 AM

Probably has something to do with VBox settings for this particular VM and maybe missing VBox extras.

Jeebizz 04-09-2021 09:44 AM

Quote:

Originally Posted by michaelk (Post 6239019)
The way I understand VirtualBox USB filters it is a way to automatically connect a particular USB device to a guest. Otherwise you need to manually connect it via the Devices pull down menu. Is the headset listed in the guest's devices -> USB menu? Once it is connected to the Guest, the device is disconnected from the host.

Hmm, I expect/assume that USB devices are desktop independent regardless of OS.

The device is not listed anywhere - (see my screenshot) , NOTHING is, not even my USB keyboard and mouse. In LXDE it would show it, if I went in the USB devices in VirtualBox and clicked on the + icon to show the devices to add to the list, but again under MATE , nothing not even my keyboard and mouse. All I know is it worked in LXDE, I mean yea if push comes to shove I'll just go back to LXDE - but I kinda want to know why MATE is not allowed VirtualBox to even detect any of the USB devices, and I am wondering if Plasma5 (when Slackware 15 is out), will exhibit similar behavior like MATE, who knows.

Jeebizz 04-09-2021 09:46 AM

Quote:

Originally Posted by Emerson (Post 6239027)
Probably has something to do with VBox settings for this particular VM and maybe missing VBox extras.

No, the extras or in this case Guest additions are installed - otherwise I wouldn't actually be able to boot Windows - VirtualBox would throw errors - So I honestly have no idea, other than again to conclude that MATE is somehow preventing VirtualBox perhaps, I don't know. Again the only thing changed was me installing MATE.

brianL 04-09-2021 10:01 AM

Have you got the Extension Pack installed?
https://www.virtualbox.org/wiki/Downloads

Jeebizz 04-09-2021 10:06 AM

1 Attachment(s)
Quote:

Originally Posted by brianL (Post 6239041)
Have you got the Extension Pack installed?
https://www.virtualbox.org/wiki/Downloads

I have yes - which I would like to correct myself from my earlier post; because without the extension pack itself, I wouldn't be able to boot a guest OS - VirtualBox would throw errors - however it will boot the guest OS with or without GuestAdditions - which again I do have also installed on the guest OS too.


brianL 04-09-2021 10:11 AM

Must be a quirk of Mate. :)

michaelk 04-09-2021 10:14 AM

Ok, I get it now you clicked on the add button but it only shows an empty square.

Is your user a member of the vboxusers group?

Jeebizz 04-09-2021 10:25 AM

1 Attachment(s)
Quote:

Originally Posted by michaelk (Post 6239052)
Ok, I get it now you clicked on the add button but it only shows an empty square.

Is your user a member of the vboxusers group?

Thats it! I don't know how or why that got removed. *facepalm* :foot: Checked /etc/groups and added myself and now boom:

Quote:

Originally Posted by brianL (Post 6239050)
Must be a quirk of Mate. :)

Turns out the quirk was the user, experiencing the dreaded ID10T error :redface:

brianL 04-09-2021 10:28 AM

No vaccine for PEBCAK. Unfortunately.


All times are GMT -5. The time now is 04:13 PM.