librepods-org / librepods-org/librepods
Linux: device type dropdown only shows “Nothing” for paired AirPods Pro
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Environment:
- LibrePods branch: linux/rust
- Built from source with
cargo build --release - OS: Arch Linux
- Desktop: GNOME 49 on Wayland
- Kernel: Linux 6.19.6-arch1-1
- Device: AirPods Pro (shown in app as
AirPods Pro - Find My)
Summary:
LibrePods launches successfully, detects the paired AirPods device, but the device type selector appears broken. The dropdown only shows Nothing, so I cannot select the correct AirPods model and add the device properly.
Steps to reproduce:
- Build LibrePods from the
linux-rustdirectory:
cargo build --release - Launch:
./target/release/librepods - Click the
+button to add a paired device - Select the entry shown as
AirPods Pro - Find My - Open the
Select device typedropdown
Expected behavior:
The dropdown should offer valid device types/models for supported AirPods devices, such as AirPods Pro or other supported variants.
Actual behavior:
The dropdown only contains a single option:
Nothing
Because of that, the device cannot be assigned the correct type.
Additional notes:
- The app had previously crashed on startup due to a missing StatusNotifier watcher, but that was resolved and LibrePods now launches normally.
- This issue appears after startup and specifically affects the device type selection UI.
- Another paired Bluetooth device (
MX Anywhere 3) is also visible in the add-device view, but the issue reported here is with the AirPods entry. - The AirPods entry is displayed as:
AirPods Pro - Find My
AC:07:75:D5:90:F3
Screenshot:
Attached screenshot showing the dropdown with only Nothing.
Potential clue:
It may be related either to:
- the Linux UI/device-type dropdown population logic, or
- device identification/parsing for
AirPods Pro - Find My
Let me know if logs from a debug run would help. I can provide output from:
RUST_BACKTRACE=1 RUST_LOG=debug ./target/release/librepods
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the linux-rust directory and inspect the device-type dropdown population and AirPods Pro - Find My identification paths. Reproduce with cargo build --release and the reported launch command, then use RUST_LOG=debug if needed. Done means the dropdown offers valid supported AirPods models instead of only Nothing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100