| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The serial for Bluetooth devices is the Bluetooth address, make sure to
export it.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use new adapter property in bluez to implement the
default-adapter-state. It should work better, as it doesn't rely only on
internal BluetoothClient state in a single process, and can get
information when bluetoothd is powering up the adapter.
Note that this property still works in the absence of a new enough
bluetoothd, without the transitional states.
Closes: #121
|
|
|
|
|
|
|
|
|
| |
Unfortunately, powering on/off Bluetooth adapters has become longer,
and less reliable over time, so front-ends need more information to
be able to figure out what it happening.
As a first pass, export whether the adapter is in the process of being
turned on, or turned off, based on our own request.
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
As we will defer device removal slightly.
|
|
|
|
| |
Fixes: 49799919f1078d1bb1d8bddede552e9f1806c321
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
That will make it easier to have control over the object references.
|
| |
|
|
|
|
|
|
| |
NOTICE: Future-deprecated features used:
* 0.55.0: {'ExternalProgram.path'}
* 0.56.0: {'meson.source_root', 'meson.build_root'}
|
|
|
|
|
|
|
| |
WARNING: You should add the boolean check kwarg to the run_command call.
It currently defaults to false,
but it will default to true in future releases of meson.
See also: https://github.com/mesonbuild/meson/issues/9300
|
| |
|
| |
|
|
|
|
| |
By using smaller timeouts when waiting for events on the mainloop.
|
|
|
|
| |
This would have made the CI fail a couple of commits earlier...
|
|
|
|
|
| |
unittest_inspector.py lists the tests in the integration-test.py script,
which are then added as individual tests.
|
|
|
|
| |
Not when loading the script
|
|
|
|
| |
Add the python suffix.
|
|
|
|
|
|
|
|
| |
This will figure out whether there are any connected input devices, so
that gnome-shell (or gnome-control-center) can show a confirmation
dialogue before really turning things off.
Closes: #101
|
|
|
|
|
|
| |
Both UI and non-UI libraries export a pkg-config file. Only the non-UI
library exports a Gir as it's the only one that gets to be used from a
non-native program (gnome-shell).
|
|
|
|
|
| |
Remove the adapter power-up when a new default adapter is added. This
should avoid unwanted power-up on the adapter.
|
| |
|
|
|
|
|
|
|
|
|
| |
This makes sure that whether, say, hci1 is plugged in before starting
the programme using gnome-bluetooth, or after it's been started, the
default adapter will still be hci1.
The old behaviour could have caused discrepancies in what gnome-shell
(long-running) and gnome-control-center saw as the default adapter.
|
|
|
|
|
| |
We weren't waiting for a mainloop update, so the newly added adapter
never got processed.
|
|
|
|
|
| |
Compare descriptive names rather than Bluetooth addresses to make the
tests easier to understand.
|
|
|
|
| |
To match the software's version number too.
|
| |
|
| |
|
|
|
|
|
| |
gnome-bluetooth-enum-types.h could be missing at this point, make sure
it's built before we compile the test program.
|
|
|
|
| |
We have a GDBusProxy object, so require GIO.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Since we made it possible for wait_for_condition() to return before the
condition was actually reached, to avoid build system test timeout, make
sure to double-check the conditions we're waiting for were actually
achieved.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
See https://mesonbuild.com/Unit-tests.html#skipped-tests-and-hard-errors
|
| |
|