Repository navigation
Fix phone discovery after Bluetooth adapter renumbering - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When BlueZ renumbers the laptop controller from
hci0tohci1, 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
ctutilsto 0.4.4 and Tokio to 1.53.3 to resolve their vulnerability advisories. Document a narrow exception for the informationalbasic-tomlmaintenance 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 testand the completemake lintpass 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