I obeserved the dbus method call on Noble with:
$ sudo dbus-monitor --system "type='method_call'"
For g-c-c, it simply powers on the adapter:
method call time=1727343233.473107 sender=:1.134 -> destination=:1.9 serial=69
path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member=Set
string "org.bluez.Adapter1"
string "Powered"
variant boolean true
While the proper way to enable scanning is to call the StartDiscovery()
method, as the bluetoothctl does:
method call time=1727343620.537801 sender=:1.141 -> destination=org.bluez
serial=26 path=/org/bluez/hci0; interface=org.bluez.Adapter1;
member=SetDiscoveryFilter
array [
dict entry(
string "UUIDs"
variant array [
]
)
]
method call time=1727343620.537852 sender=:1.141 -> destination=org.bluez
serial=27 path=/org/bluez/hci0; interface=org.bluez.Adapter1;
member=StartDiscovery
Also, on Jammy, the g-c-c did enable scanning in the similiar fashion,
with StartDiscovery():
method call time=1727403536.849653 sender=:1.93 -> destination=:1.14 serial=69
path=/org/bluez/hci0; interface=org.bluez.Adapter1; member=SetDiscoveryFilter
array [
dict entry(
string "Discoverable"
variant boolean true
)
]
method call time=1727403536.850196 sender=:1.93 -> destination=:1.14 serial=70
path=/org/bluez/hci0; interface=org.bluez.Adapter1; member=StartDiscovery
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081672
Title:
Scanning not enabled by the Bluetooth slider
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2081672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
