Linux: device type dropdown only shows “Nothing” for paired AirPods Pro

[kkin1995]

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:

1. Build LibrePods from the linux-rust directory:
   cargo build --release
2. Launch:
   ./target/release/librepods
3. Click the + button to add a paired device
4. Select the entry shown as AirPods Pro - Find My
5. Open the Select device type dropdown

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:

1. the Linux UI/device-type dropdown population logic, or
2. 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

[kkin1995]

Update:

I found a reliable workaround and it narrows down the bug significantly.

Behavior on my system:

• If I connect the AirPods to the laptop first and then launch LibrePods, LibrePods works smoothly and correctly recognizes the device as AirPods.
• If LibrePods is already running and I go through the add-device flow / device-type selection flow, the UI can show only Nothing in the device-type dropdown.

So this does not appear to be a general “LibrePods cannot detect AirPods” issue.

It looks more like a Linux Rust app state/discovery bug related to one of these paths:

1. app launched before AirPods are connected
2. add-device UI flow
3. device-type population for not-yet-initialized / not-yet-connected devices

In other words:

• connected first, then launch LibrePods -> works
• use add-device/device-type flow -> incorrect Nothing option

That suggests the recognition logic works once the AirPods are already connected, but the add-device / late-detection path is broken or incomplete.