DLAM stuck in voice only mode Ubuntu 24

issues & bugs
1

Hi Everyone, I ran into this really annoying user permissions issue with DLAM so I wrote this guide assuming I am not the only one running into it. It seems to have started after my previous Kernel update but back dating the kernel didn’t fix the issue so maybe it overwrote some files related to permissions? in any case here is the guide.

Fixing DLAM on Ubuntu

Fix Rabbit R1 DLAM “voice only” on Ubuntu (permission denied on USB)

Symptoms

  • DLAM on dlam.rabbit.tech connects to the Rabbit R1.

  • Screen sharing and voice work, but DLAM never moves the mouse or types.

  • It still works on Windows/macOS.

  • In Chrome’s chrome://device-log you see errors like:

    • Failed to open /dev/bus/usb/001/010: Permission denied (13)

On Ubuntu, the R1 often shows up as a MediaTek USB device, and recent kernel/udev changes can make it inaccessible to normal users.

1. Confirm the problem

Open a terminal and run:

bash
lsusb | grep -i r1

You’ll likely see something like:

text
Bus 001 Device 010: ID 0e8d:2304 MediaTek Inc. r1

Then check the device node:

bash
ls -l /dev/bus/usb/001/010

(Substitute the correct bus and device numbers from your lsusb output.)

If you see:

text
crw-rw-r-- 1 root root ...

the device is owned by root:root with mode 0664, so your user can’t fully access it.

2. Create a udev rule for the Rabbit R1

Give normal users permission to talk to that USB device.

  1. Create a new udev rules file:

    bash
sudo nano /etc/udev/rules.d/99-rabbit-r1.rules

  1. Add this line (using the vendor/product from lsusb):

    text
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="2304", MODE="0666"

    • 0e8d = MediaTek vendor ID

    • 2304 = the specific R1 product ID

    If you prefer more restrictive access and your user is in a group like plugdev, you can use:

    text
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="2304", GROUP="plugdev", MODE="0660"

  2. Save and exit (Ctrl+O, Enter, then Ctrl+X in nano).

3. Reload udev and replug the R1

Apply the new rule:

bash
sudo udevadm control --reload
sudo udevadm trigger

Now unplug the Rabbit R1, wait a second, and plug it back in.

Check the permissions again (bus/device may have changed):

bash
lsusb | grep -i r1
ls -l /dev/bus/usb/XXX/YYY   # replace XXX/YYY with the new bus/device

You should now see something like:

text
crw-rw-rw- 1 root root ... /dev/bus/usb/XXX/YYY

(or root plugdev with 0660 if you used the group option).

4. Restart the browser and test DLAM

  1. Close all Rabbit/DLAM tabs (or restart Chrome/Brave).

  2. Go to https://dlam.rabbit.tech.

  3. Select your R1, start screen sharing, and begin a session.

If you re‑open chrome://device-log:

  • You should still see the R1 being detected as a USB device.

  • The previous Permission denied (13) errors when opening /dev/bus/usb/... should be gone, and DLAM should now be able to move the mouse and type.

5. Notes and variations

  • If your lsusb output shows different IDs, adjust the rule:

    text
SUBSYSTEM=="usb", ATTR{idVendor}=="VENDOR", ATTR{idProduct}=="PRODUCT", MODE="0666"

  • This guide assumes:

    • Ubuntu 24.04 (but it should apply to other modern Ubuntu flavors).

    • R1 works fine on another OS, which confirms the issue is permissions, not the device itself.

1 Like