Skip to content

Fix phone discovery after Bluetooth adapter renumbering - #5

Merged
dmytrogajewski merged 2 commits into
masterfrom
fix/available-bluetooth-adapter
Oct 31, 2026
Merged

dmytrogajewski merged 2 commits into
masterfrom
fix/available-bluetooth-adapter

Conversation

@dmytrogajewski

@dmytrogajewski dmytrogajewski commented Oct 31, 2026 •

Copy link
Copy Markdown
Collaborator

When BlueZ renumbers the laptop controller from hci0 to hci1, the presence daemon keeps targeting the missing adapter. Advertisements fail, and restarting the old build leaves a live RPC service without Bluetooth transport.

Select BlueZ’s available default adapter at daemon startup, preserve explicit adapter selection for other callers, and bump the native Fedora RPM to release 5. Add an opt-in real-radio regression and document recovery. Automatic recovery after a later controller removal remains outside this change.

CI maintenance updates ctutils to 0.4.4 and Tokio to 1.53.3 to resolve their vulnerability advisories. Document a narrow exception for the informational basic-toml maintenance advisory: it is a build-only Askama parser, has no patched release, and remains required even by current UniFFI. The existing runtime/generator versions stay aligned.

Validation: make test and the complete make lint pass in an isolated PR worktree, including Clippy, formatting, scope discipline, and dependency policy. The radio regression failed before the repair and passed afterward. The installed adapter-repair RPM advertises successfully, the phone reconnected within four seconds, and fresh sudo authentication succeeded in 2.473 seconds. RPM verification and the original bond checksum pass. The host deployment predates the CI dependency updates.

Companion documentation: dmytrogajewski/sy#7

@dmytrogajewski
dmytrogajewski merged commit a06468a into master Oct 31, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants