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
** Description changed:
[Description]
Since Noble, turning Bluetooth slider on ON after toggling it OFF for
~1min seems to only power on and unblock rfkill on the controller, but
not enable scanning. This makes the "Devices" list shows no devices, as
if the controller wasn't functioni
** Description changed:
- Since Noble, toggling the Bluetooth slider repeatedly and leaving at the
- ON state seems to only power on and unblock rfkill on the controller,
- but not enable scanning. This makes the "Devices" list shows no devices,
- as if the controller wasn't functioning.
+ [Descri
** Tags added: jira-wtn-5 oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2081672
Title:
Scanning not enabled by the Bluetooth slider
Status in OEM Priority
Public bug reported:
Since Noble, toggling the Bluetooth slider repeatedly and leaving at the
ON state seems to only power on and unblock rfkill on the controller,
but not enable scanning. This makes the "Devices" list shows no devices,
as if the controller wasn't functioning.
This is observable
[ Regression Test Plan - Nvidia+LUKS ]
Tested on a HP desktop machine with Nvidia graphic card with 550.107.02
driver
1. Install the stock 24.04.1 image fresh (with the additional drivers option
selected) and enabled disk encryption.
2. Install the proposed ubuntu-drivers-common after booting in
Hi @zorro-zhang. Could you share how you tested it? I tried on both Dell
and HP platforms on Noble, and none of them seemed to work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1966635
` and enable `Fingerprint Login`
* Enroll finger and then logout
* Login system with enrolled finger
[Where problems could occur]
* If the vendor uses the same ID for other devices, the new device may
not work properly.
** Affects: oem-priority
Importance: Critical
Assignee: Leo Lin
8 matches
Mail list logo
