| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
|
|
| |
UnboundLocalError: local variable 'timeout' referenced before assignment
Fixes: 9fb72c027f9119e6992771e4ce1f0a33c80d3e7c
|
|
|
|
| |
Rather than wait for mainloop.
|
| |
|
|
|
|
|
| |
Check whether we've started the test more than ~28 seconds ago to avoid
having the whole test time out at the meson level.
|
|
|
|
|
|
| |
We have a private property to keep track of this already, let's use it
and bail out of _bluetooth_client_set_default_adapter_discovering() if
we're already discovering.
|
|
|
|
|
| |
Correctly loop for "timeout" seconds instead of returning after the
first iteration of the mainloop.
|
|
|
|
|
| |
It's unused since we split the gnome-bluetooth libraries in UI and
non-UI portions.
|
|
|
|
|
|
| |
This reverts commit bd2d06232e1cf967b20cd4fa0c7f47537d8410e2
and adds upower-devel to the list of packages to install as part of the
normal build dependencies.
|
| |
|
|
|
|
|
|
|
|
|
| |
Add missing gtk4 and libadwaita deps to the gnome-bluetooth-ui
pkg-config file. In reality, this didn't impact any software as the only
consumer of the UI library is gnome-control-center which already depends
on those 2 libraries.
Closes: #105
|
|
|
|
|
|
|
|
|
|
| |
On gcc < 11 and any version of clang (tested up to 13),
the build would fail with the following error:
error: label at end of compound statement
GCC 11+ seems to only complain with -Werror -Wpedantic,
otherwise it tolerates even completely empty default: case.
|
|
|
|
|
|
| |
The pairing-dialog was not added to GtkWindowClass' global list of
windows as we didn't call up to gtk_window_constructed(), so couldn't be
closed by gtk_window_destroy().
|
|
|
|
|
|
| |
Right now the pairing dialog doesn't open because we're not specifying
the correct parent class when creating the GtkDialog subclass, so fix
that.
|