summaryrefslogtreecommitdiff
path: root/libupower-glib
AgeCommit message (Collapse)AuthorFilesLines
2014-05-20Do not print a critical warning when misusing up_device_set_object_path_sync()Richard Hughes1-2/+11
2014-05-07all: Remove IsDocked propertyBastien Nocera2-38/+0
Removes the deprecated (for not very long) property, before we do a 1.0 release. https://bugs.freedesktop.org/show_bug.cgi?id=78380
2014-05-07lib: Fix API doc for up_client_get_on_battery()Bastien Nocera1-1/+1
2014-05-07lib: Hard-code the IsDocked valueBastien Nocera1-5/+6
2014-04-23lib: Fix typo in g-i annotationBastien Nocera1-1/+1
Missing colon.
2013-11-08lib: Fix segfault on getting property when daemon is not runningMartin Pitt1-0/+3
This fixes "upower --version" when the daemon is not running, and thus the client proxy is NULL.
2013-10-17lib: Fix possible warning when type changesBastien Nocera1-1/+4
UpDevice on the daemon side has a "type" property, but the libupower-glib object has a "kind" type instead. Translate that.
2013-10-17lib: Fix compile-time warningBastien Nocera1-1/+1
2013-10-17lib: Remove up_client_enumerate_devices_sync()Bastien Nocera2-95/+41
And make device-removed send an object path, not a UpDevice. This means that we don't keep all the remote devices as local UpDevices object, getting woken up any time any of them have a property changed, without anybody listening. This should greatly cut down on the wakeups on the client side, especially for applications that only use a small portion of the API like the "on-battery" or "warning-level" properties.
2013-10-17all: Remove *changed signalsBastien Nocera4-88/+0
Now that we send out PropertiesChanged signals (on the daemon side) and "notify" signals (on the client side), there's no need for the all encompassing DeviceChanged and Changed signals. They would have woken up any client, even if they were not interested in receiving the signals.
2013-10-17lib: Proxy notify changes from UpDevice glueBastien Nocera1-2/+3
2013-10-17lib: Simplify proxying glue properties in UpClientBastien Nocera1-14/+2
2013-10-17all: Add GetCriticalAction daemon methodBastien Nocera2-0/+26
This allows desktop front-ends to get which action will actually be taken when we hit critical battery. This is not a property as availability of actions might change over the course of the run of the system, and we didn't want to make unnecessary D-Bus calls on startup.
2013-10-17all: Remove WarningLevel from the daemon propertiesBastien Nocera2-37/+0
The WarningLevel property just replicated the warning level on the display device, or at least should have. So we fix the latter to remove the former.
2013-10-17lib: Trim properties when printing the display deviceBastien Nocera1-7/+14
2013-10-17lib: Add up_client_get_display_device()Bastien Nocera2-0/+25
Add a helper to get to the display device.
2013-10-17lib: Remove unneeded up_client_get_properties_sync()Bastien Nocera2-25/+0
It doesn't do anything, and we already broke the ABI by removing some functions, so remove this as well.
2013-10-15lib: Fix compilationBastien Nocera1-2/+2
2013-10-15lib: Use slices to allocate cached propertiesBastien Nocera1-2/+2
Saves on memory fragmentation.
2013-10-15lib: Print property name when cached property doesn't existBastien Nocera1-1/+1
2013-10-15lib: Cache property values correctlyBastien Nocera1-1/+2
This is cleaner.
2013-10-14daemon: Add new WarningLevel "Discharging"Bastien Nocera2-0/+5
When UPSes are discharging, we should have a warning already, as it means that mains power has been lost to the UPS (though not to the computer).
2013-10-14lib: Add support for the IconName propertyBastien Nocera1-0/+22
2013-10-14lib: Emit notify:: signalsBastien Nocera1-0/+28
In the UpClient object. https://bugs.freedesktop.org/show_bug.cgi?id=43001
2013-10-14lib: up_device_to_text() won't work for fake devicesBastien Nocera1-0/+1
For now, up_device_to_text() won't work for devices that aren't backed by a UPower device.
2013-10-14lib: Make it possible to create local UpDevicesBastien Nocera1-0/+41
gnome-settings-daemon creates a composite UpDevice that's not backed by any real D-Bus object in UPower, so we shouldn't try and poke the inexistant proxy in this case. We'll cache the properties that the caller sets in this case, but will not support sending back default/unset values.
2013-10-14lib: Update for property removal and additionsBastien Nocera2-21/+22
Remove on-low-battery and add warning-level daemon properties.
2013-10-14lib: Fix alignment of "online" in device dumpBastien Nocera1-1/+1
2013-10-14lib: Add warning-level device propertyBastien Nocera1-0/+23
2013-10-14lib: Add UpDeviceLevel enumBastien Nocera2-1/+72
2013-10-14lib: Remove dbus-glib from the dependenciesBastien Nocera1-3/+1
libupower-glib now uses GDBus.
2013-10-14lib: Port UpWakeUps to GDBusBastien Nocera1-160/+64
Using the new proxy.
2013-10-14lib: Port UpDevice to GDBusBastien Nocera1-429/+225
Using the new proxy.
2013-10-14lib: No need to set private members to NULLBastien Nocera6-18/+0
GObject already makes sure of that for us.
2013-10-14lib: Port UpClient to GDBusBastien Nocera1-205/+46
Using the new proxy.
2013-10-14lib: Build the new D-Bus glueBastien Nocera1-1/+6
2013-10-14lib: Add autogenerated glue to the daemonBastien Nocera1-0/+38
2013-10-14Remove QoS interfaceBastien Nocera6-771/+0
It was added for some workloads, but ill-suited and never really got traction. Using cgroups to manage the resources of particular services (using systemd), or something separate like rtkit is a better bet.
2013-10-14Remove obsolete battery recall propertiesBastien Nocera1-83/+0
The recalls for that broken batch of Sony batteries dates back from 2006. All the batteries that could have been recalled have now been recalled, and somebody particularly interested in supporting them can match the batteries using the old rules file, in a user session or a separate daemon.
2013-10-14lib: Remove deprecated featuresBastien Nocera5-453/+0
All this is now handled by logind.
2013-10-14lib: Simplify _new() functionsBastien Nocera5-15/+5
No need to use a temporary variable.
2013-10-14lib: Simplify _to_string() callsBastien Nocera1-58/+29
2013-10-14lib: Add missing "element-type" introspection metadataBastien Nocera3-4/+4
https://bugs.freedesktop.org/show_bug.cgi?id=55419
2013-10-13lib: Fix crasher calling _about_to_sleep_sync()Bastien Nocera1-1/+1
https://bugs.freedesktop.org/show_bug.cgi?id=54976
2013-10-10lib: Fix a small memory leakBastien Nocera1-0/+2
The bus was never unreferenced in the UpWakeups object.
2013-10-10up-client: Really don't overwrite retval with prop valuesBastien Nocera1-9/+9
db89e5a32bf2c16c0d3d00f6c8f0ef7e5e7efa8f was incomplete and "ret" was being used instead of prop_val to set some of those properties. It's likely your laptop would have been seen as docked for example.
2013-10-08libupower-glib: Fix error handlingMartin Pitt1-1/+2
In up_client_get_properties_sync(), don't set the passed GError** to NULL, instead set the actual pointed-to GError* to NULL by default. Fixes proper error reporting back to the client if something does fail.
2013-10-08up-client: Don't error out gathering deprecated propertiesBastien Nocera1-1/+5
We would error out when trying to get properties that are disabled by default (deprecated). Ignore those properties when building without the deprecations. This is still broken if the library is built with the deprecations enabled, but not the daemon isn't, but that's an edge case. https://bugs.freedesktop.org/show_bug.cgi?id=70283 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
2013-10-08up-client: Don't overwrite retval with property valuesBastien Nocera1-15/+16
If one of the properties is FALSE, we'll end up return FALSE without setting an error (and making the caller crash if they expect an error being filled in). https://bugs.freedesktop.org/show_bug.cgi?id=70283 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
2013-08-29Make GetHistory() array order consistentMartin Pitt1-1/+3
When requesting fewer history elements than we actually have, fix the interpolation loop to not reverse the returned elements; this already does not happen if we request more elements than available, which led to the returned list order depending on the history size. Now the first array element is always the most recent one. Update documentation accordingly. Add test case to reproduce the problem. We now add three sample points to be able to request a subset and still assert its correct order, and make the charge values be further apart to ensure correct interpolation. https://bugs.freedesktop.org/show_bug.cgi?id=68384
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-07 01:26:11 +0000