| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Traceback (most recent call last):
File "/builds/GNOME/gnome-bluetooth/_build/../tests/integration-test.py", line 429, in test_connectable_devices
self.assertEqual(list_store.get_n_items(), 3)
AssertionError: 0 != 3
|
|
|
|
|
| |
Better explain what _connect_service() does, so it's not used for
devices which can't be "connected" to.
|
| |
|
| |
|
|
|
|
| |
Makes the window look better.
|
|
|
|
|
|
| |
Adds support for dark mode.
Fixes: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/114
|
| |
|
|
|
|
|
| |
Can't really explain the purpose of this variable by just naming it, so
document it in the structure that defines it.
|
|
|
|
|
|
|
|
|
|
| |
Reorganise functions called from
_bluetooth_client_set_default_adapter_discovering() so that we only call
StartDiscovery() if SetDiscoveryFilter() is successful, and we disable
the "in-flight" ->discovery_started variable so the next default-adapter
changes would try to enable discovery again if needed.
Closes: #100
|
|
|
|
|
| |
When somebody requests the "default-adapter-setup-mode" to be disabled
but there's no default adapter, consider that we're not in setup mode.
|
|
|
|
| |
This reverts commit 3ace233030d1d4140a114604b17b334ac211fd74.
|
|
|
|
|
|
|
|
|
|
|
| |
As recommended in the BluetoothClient documentation:
"
Note that #BluetoothClient::device-removed will not be called
for each individual device as the model is cleared when the
#BluetoothClient:default-adapter property changes.
"
Closes: #116
|
|
|
|
| |
See https://github.com/martinpitt/python-dbusmock/issues/137
|
| |
|
| |
|
|
|
|
|
|
| |
Escape the device name/alias before using it as a label.
Closes: #115
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
As supported by bluez in its MIDI plugin.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
"The latest", always, as we add new functionality to python-dbusmock
that we rely on to run our tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an adapter is removed while bluetoothd is still running (eg. not
crashing as we also want to handle), suppress the emission of
device-removed so that front-ends don't think that every device is
removed.
We implement this by queue device-removed signals until the next
mainloop iteration instead of sending it straight away.
Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1426
Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5058
|
|
|
|
| |
As we will defer device removal slightly.
|
|
|
|
| |
Fixes: 49799919f1078d1bb1d8bddede552e9f1806c321
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix possible race between UPower and Bluez when creating the
BluetoothClient.
Bluetooth-DEBUG: Successfully created UpClient
Bluetooth-DEBUG: Got initial list of 2 UPower devices
Bluetooth-DEBUG: Considering UPower device /org/freedesktop/UPower/devices/mouse_dev_11_22_33_44_55_66
Bluetooth-DEBUG: Could not find bluez device for upower device /org/bluez/hci0/dev_11_22_33_44_55_66
Bluetooth-DEBUG: Considering UPower device /org/freedesktop/UPower/devices/mouse_dev_11_22_33_44_55_67
Bluetooth-DEBUG: Could not find bluez device for upower device /org/bluez/hci0/dev_11_22_33_44_55_67
Bluetooth-DEBUG: Adding adapters from ObjectManager
Bluetooth-DEBUG: Inserting adapter :1.2 /org/bluez/hci0 org.bluez.Adapter1
Bluetooth-DEBUG: Setting '/org/bluez/hci0' as the new default adapter
Bluetooth-DEBUG: Emptying list store as default adapter changed
Bluetooth-DEBUG: Coldplugging devices for new default adapter
Bluetooth-DEBUG: Adding device '11:22:33:44:55:66' on adapter '/org/bluez/hci0' to list store
Bluetooth-DEBUG: Adding device '11:22:33:44:55:67' on adapter '/org/bluez/hci0' to list store
Bluetooth-DEBUG: New default adapter so invalidating all the default-adapter* properties
The UpDevices are enumerated before we've even enumerated the Bluetooth
adapters, so we don't have any BluetoothDevices to attach the UpDevices
to. Wait until we've at least run through setting a default adapter
before enumerating the UPower devices.
|
|
|
|
|
|
|
| |
Fix a warning when closing the file chooser without selecting a file,
using keyboard shortcuts.
GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GtkWindow'
|
|
|
|
|
| |
When running `bluetooth-sendto` without arguments and selecting some files,
the app would try to access memory after the model list returned by gtk_file_chooser_get_files.
|
|
|
|
|
| |
When running `bluetooth-sendto` without arguments,
no window was shown.
|