# DLAM stuck in voice only mode Ubuntu 24
**URL:** https://forum.rabbitcommunity.tech/t/dlam-stuck-in-voice-only-mode-ubuntu-24/15692
**Category:** issues & bugs
**Created:** [February 8, 2026, 1:17pm UTC](https://forum.rabbitcommunity.tech/t/dlam-stuck-in-voice-only-mode-ubuntu-24/15692 "2026-02-08T13:17:17Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@dcmike](https://forum.rabbitcommunity.tech/u/dcmike)
#### Post date: [February 8, 2026, 1:17pm UTC](https://forum.rabbitcommunity.tech/t/dlam-stuck-in-voice-only-mode-ubuntu-24/15692/1 "2026-02-08T13:17:17Z")
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:
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:
```auto
bash
lsusb | grep -i r1
```
You’ll likely see something like:
```auto
text
Bus 001 Device 010: ID 0e8d:2304 MediaTek Inc. r1
```
Then check the device node:
```auto
bash
ls -l /dev/bus/usb/001/010
```
(Substitute the correct bus and device numbers from your `lsusb` output.)
If you see:
```auto
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:
```auto
```
1. Add this line (using the vendor/product from `lsusb`):
2. Save and exit (`Ctrl+O`, `Enter`, then `Ctrl+X` in nano).
* * *
## 3. Reload udev and replug the R1
Apply the new rule:
```auto
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):
```auto
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:
```auto
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:
- This guide assumes:
---
### Author:  [@rabbitears](https://forum.rabbitcommunity.tech/u/rabbitears)
#### Post date: [April 8, 2026, 7:22am UTC](https://forum.rabbitcommunity.tech/t/dlam-stuck-in-voice-only-mode-ubuntu-24/15692/2 "2026-04-08T07:22:55Z")
Thanks for putting this together. I’m also running Ubuntu and haven’t even tried DLAM because I figured it wouldn’t work. Good to know it can 👍