Reading through the comments, I think there is some misunderstanding
about to what extent this is hardware-specific.
The reproducer in the test plan (which is the same as bug 2127718) is
not at all hardware-specific. This is just completely broken in
questing. I observe the same problem in a questing VM on my amd64 host.
Also, it is clear from the patches in unapproved that there is nothing
hardware-specific being changed.
The reason the broader impact ("After updating to Questing I wasn't able
to use my Bluetooth mouse") is observed in x13s specifically is because
hwe-lenovo-x13s-bluetooth-addr.service (see comment #4) uses btmgmt to
configure the device's bluetooth address[1][2]. This comes from
ubuntu-x13s-settings, and is hence an integration quirk. I don't know
how the equivalent setup is done for other hardware, however.
Now, given that these patches are actually restricted to the btmgmt
tool, and are not actually touching any protocol or hardware-specific
things, I personally do not think it is necessary to run a full
compliance test suite or the cert team's automated testing for this
change.
Instead, I propose the following test plan:
(1) Keep the existing plan, i.e. run the btmgmt tool directly
(2) Check that a bluetooth mouse can be used on x13s, and that
hwe-lenovo-x13s-bluetooth-addr.service is no longer failing
(3) On non-x13s hardware, check that bluetooth devices (e.g. mouse, headphones,
etc.) can still be used
Part (1) gives direct feedback on what the bluez patches are addressing,
which affects all questing installs. Part (2) tests the reported user
impact, i.e. the x13s-specific case. Finally, (3) provides very basic
regression testing (as noted above, it's unclear to me at least that
btmgmt is required for functioning bluetooth on most other hardware, so
this may be completely artificial, but it is easy enough).
Chris, Tobias - what do you think?
[1]
https://git.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/tree/share/set-bt-public-addr
[2]
https://git.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/tree/systemd/hwe-lenovo-x13s-bluetooth-addr.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127186
Title:
[SRU] bluetooth is not working with x13s with Questing
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/2127186/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
