TUI hangs on empty terminal screen when no bluetooth adapter is present (but bluetoothd is started)
@pythops is already working on this.
Since Jan 24, 2026.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Sorry, me again... ;)
Another minor bug, but not a blocker: If the TUI is started, with a running bluetoothd (on OpenRC, not Systemd), but no bluetooth device present, the TUI hangs on an empty terminal screen "forever". Exiting that state with "q" works fine though.
Apparently, this is not a situation the code anticipates, but it can happen if one uses a USB dongle (like me) which is just not plugged in, or wasn't usb_modeswitch'ed yet (and therefore identifies as mass storage rather than a BT adapter device).
Maybe just exit with some error "No bluetooth adapter detected" or something similar, or ensure that drawing the TUI "framework" does not depend on (or wait for), an adapter to be detected before being drawn for the first time.
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.
Assessment
This issue has not been assessed yet.