| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Connect and monitor UPower devices for devices reporting their battery
status.
This makes sure that we can show battery status for devices
that emit their battery status through bluez (via the BATT LE service,
or the org.bluez.BatteryProviderManager1 API, as well as devices for
which the kernel is the battery info provider.
Closes: #102
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Now that libadwaita has the header-suffix property,
we can use AdwPreferencesGroup's built-in header.
|
|
|
|
|
|
|
| |
The property was forgotten in commit 6f611a67, which made the
connect button in the settings panel not work properly.
Fixes: 6f611a67
|
|
|
|
|
|
|
|
|
|
| |
Panels in g-c-c should be using these widgets wherever
possible. These are the widgets meant to be used
for boxed list panels, and libadwaita provides a
single source of truth for the styling.
The UI file will be further reduced once https://gitlab.gnome.org/GNOME/libadwaita/-/merge_requests/433
is merged.
|
|
|
|
|
| |
Significantly reduces the size of the UI file
and gives us consistent margins and padding.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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 will be used when enabling Bluetooth (eg. disabling the Bluetooth
rfkill).
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
"replacement" wasn't really a replacement, we were swapping a proxy for
a new one attached to the correct D-Bus owner.
|
|
|
|
|
|
| |
This would prefer hci1 as the default adapter, but that's already the
order in which g_dbus_object_manager_get_objects() returns the objects,
so it's more complicated code for the sake of clarity.
|
| |
|
| |
|
| |
|
|
|
|
| |
Add debug output when enabling or disabling discovery.
|
|
|
|
|
|
| |
To take into account that we can power up, as well as down.
Fixes: 96b89f86
|
| |
|
| |
|
|
|
|
|
| |
We don't need to pass the adapter we want to power, we only care about
the default adapter.
|
|
|
|
|
| |
This call isn't synchronous since commit
7bbbadd72a55595faaab063c758a7e53fc36b0a5.
|
|
|
|
|
|
| |
Rework the default adapter setting to allow for just the proxy object to
be updated, for the same reasons as mentioned earlier for the device
proxies.
|
| |
|
|
|
|
|
|
|
| |
It's possible, when bluetoothd is coming and going, that we'll still
have a BluetoothDevice around when the service owner changes. Make
sure to avoid duplicates and update the device already in the store
instead.
|
| |
|
|
|
|
|
|
|
| |
Fix the inverted logic that meant that adapter_set_powered() was never
called when the adapter was unpowered.
Fixes: 7956dd42630fd52ba30417fbd4a65894f5fb0d3c
|
|
|
|
|
| |
When bluetoothd is restarted, it's possible that the proxy will need to
be changed as the owner changed.
|
| |
|
| |
|
|
|
|
| |
Bluetooth-CRITICAL **: bluetooth_agent_register: assertion 'agent->path != NULL' failed
|
| |
|
|
|
|
| |
Remove the last synchronous call in BluetoothClient.
|
|
|
|
|
| |
gnome-bluetooth-enum-types.h could be missing at this point, make sure
it's built before we compile the test program.
|
| |
|
|
|
|
|
|
| |
BluetoothClient doesn't have any GTK types in its header or
implementation, so remove the GTK header and "lower it down" to a GIO
include.
|
|
|
|
|
|
| |
_setup_device() was ported to a GIO-style function in commit
162d9fea90b664ddd822c6167065a93218a04829 but there were bits left
around.
|
|
|
|
|
| |
Return success or error from the function, and require an address to be
passed, now that bluetooth-sendto doesn't include a device chooser.
|
| |
|