Say when a paired device is present over something other than Bluetooth #18

New issue

Closed

opened 2026-08-16 23:22:01 +01:00 by joshquinlan · 1 comment

joshquinlan commented

2026-08-16 23:22:01 +01:00

Owner

Reported as the pane misreporting a connected Magic Trackpad.
It is not: the pane is telling the truth and the trackpad is not
on Bluetooth at all.

bluetoothctl info 04:B5:B2:7B:01:23
  Paired: yes   Trusted: yes   Connected: no

/sys/class/input/input53 ->
  .../usb3/3-1/3-1:1.0/0003:05AC:0324.0012/input/input53
  DRIVER=magicmouse  HID_PHYS=usb-0000:00:14.0-1/input0

It is plugged in over USB, so BlueZ is right and the pane is
faithful. What is wrong is what it reads like: a device that is
plainly working, listed as paired and not connected, looks like
a broken pane.

Worth doing: notice that a paired device is present on another
transport and say so, rather than leaving it looking
disconnected. The HID bus already knows, and matching is
possible on the name or the vendor and product.

Also wanted, a Bluetooth TUI on SUPER+SHIFT+C so there is always
a working way in. Neither bluetuith nor bluetui is in the Fedora
repositories; blueman is there but is a GTK application rather
than a TUI. So the options are a pinned release binary of
bluetuith, a COPR if a trustworthy one exists, or bluetoothctl,
which is already installed and interactive if not pretty.

Reported as the pane misreporting a connected Magic Trackpad. It is not: the pane is telling the truth and the trackpad is not on Bluetooth at all. bluetoothctl info 04:B5:B2:7B:01:23 Paired: yes Trusted: yes Connected: no /sys/class/input/input53 -> .../usb3/3-1/3-1:1.0/0003:05AC:0324.0012/input/input53 DRIVER=magicmouse HID_PHYS=usb-0000:00:14.0-1/input0 It is plugged in over USB, so BlueZ is right and the pane is faithful. What is wrong is what it reads like: a device that is plainly working, listed as paired and not connected, looks like a broken pane. Worth doing: notice that a paired device is present on another transport and say so, rather than leaving it looking disconnected. The HID bus already knows, and matching is possible on the name or the vendor and product. Also wanted, a Bluetooth TUI on SUPER+SHIFT+C so there is always a working way in. Neither bluetuith nor bluetui is in the Fedora repositories; blueman is there but is a GTK application rather than a TUI. So the options are a pinned release binary of bluetuith, a COPR if a trustworthy one exists, or bluetoothctl, which is already installed and interactive if not pretty.

joshquinlan added the

feature

labels

2026-08-16 23:22:01 +01:00

joshquinlan commented

2026-08-22 18:59:30 +01:00

Author

Owner

Moved to donbox#5 as part of the rewrite.

joshquinlan closed this issue

2026-08-22 18:59:30 +01:00