| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Disabling kernel tunables blocked us from accessing /sys, meaning we
couldn't change keyboard backlight levels.
Closes: #73
|
|
|
|
| |
So that this particular setup is tested.
|
|
|
|
|
|
| |
When the layout of the build tree doesn't match the expectations in
up-self-test, the test would crash failing to find UPower.conf. Pass the
path as a macro during build so we always know where it is.
|
|
|
|
|
|
|
|
|
| |
The generated headers for the dbus service are in the build dir, not
the source dir.
../../libupower-glib/up-client.c:39:10: fatal error: up-daemon-generated.h: No such file or directory
#include "up-daemon-generated.h"
^~~~~~~~~~~~~~~~~~~~~~~
|
| |
|
|
|
|
|
|
|
|
|
| |
PrivateNetwork=true will cut off upower from the udev netlink socket, so
it's not what we want to use, as we want those events.
See https://lists.freedesktop.org/archives/systemd-devel/2018-July/041000.html
Closes: #68
|
|
|
|
| |
It doesn't return a UpClient.
|
| |
|
|
|
|
|
|
| |
This ensures consistent rendering.
See https://developer.gnome.org/gtk-doc-manual/stable/documenting_sections.html.en
|
|
|
|
|
|
|
|
|
|
| |
Without the braces on the same line gtk-doc adds function pointers as
functions to the documentation and fails to detect the types as
GObjects. This fixes object names in the index and cross refs.
See the examples in
https://developer.gnome.org/gtk-doc-manual/stable/documenting_symbols.html.en
|
|
|
|
|
| |
This makes sure we stay up to date and get the object hierarchy
generated.
|
| |
|
|
|
|
| |
See https://gitlab.freedesktop.org/upower/upower/issues/56
|
|
|
|
|
|
|
|
|
| |
Pull the 2 previous changes together to refresh the battery status for a
couple of seconds after receiving an event on the power line. This fixes
charge status being inaccurate for up to 120 seconds (the normal poll
timeout on MacBooks).
https://gitlab.freedesktop.org/upower/upower/issues/56
|
|
|
|
|
|
|
|
| |
When an event happens on the power line, and we are using a particular
device (in this case a MacBook or MacBookAir), we might need to poll
more aggressively after the event.
This adds a function to detect and export this.
|
|
|
|
|
| |
Rather than 5 calls to up_device_supply_setup_unknown_poll(), which
can happen pretty quickly together after receiving a uevent.
|
|
|
|
|
|
|
|
|
| |
Fix double-close on exit. If we created a GIOChannel from the file
descriptor, then g_io_channel_shutdown() will close that file descriptor
as well. Close the channel first, so that the file descriptor is only
closed manually if we didn't manage to create a GIOChannel from it.
https://gitlab.freedesktop.org/upower/upower/issues/60
|
|\
| |
| |
| |
| | |
build: Add CI
See merge request upower/upower!9
|
|/ |
|
|
|
|
|
|
| |
Don't leave the history files installed when running "make uninstall".
Those files will likely have been created by the test suite when running
"make distcheck"
|
| |
|
|
|
|
|
|
| |
sysfs_get_double_with_error() used to return -1.0 for errors, but in
some cases, we might want -1.0 to be a valid value, such as for negative
discharge rates. Return FALSE on error instead.
|
|
|
|
|
|
|
|
|
|
| |
This is part of more broader commitment Red Hat along with IBM, Google, and
Facebook made in November 2017.
More on this can be found online:
https://www.redhat.com/en/blog/fostering-greater-open-source-development &
https://www.redhat.com/en/about/gplv3-enforcement-statement
|
|\
| |
| |
| |
| | |
lib: Add a new version of up_client_get_devices which unrefs contents
See merge request upower/upower!1
|
|/
|
|
|
|
| |
The existing function didn't set the free function on the GPtrArray.
This means a libupower user can easily make a mistake in the reference
counting of the array contents.
|
|
|
|
|
|
| |
And print "should be ignored" next to the percentage.
https://bugs.freedesktop.org/show_bug.cgi?id=97484
|
|
|
|
|
|
|
|
| |
The current power_supply support in the kernel will advertise an unknown
capacity when a device is being charged. This tests this state as well
as the expected behaviour when the device is fully charged.
https://bugs.freedesktop.org/show_bug.cgi?id=97484
|
|
|
|
|
|
|
| |
Rather than relying on the percentage equivalence, which just doesn't
work for "Unknown" battery levels.
https://bugs.freedesktop.org/show_bug.cgi?id=97484
|
|
|
|
|
|
|
|
|
|
| |
Rather than leaving the percentage untouched, set the battery level at
50.0 as a "middle-ground".
This percentage is supposed to be ignored if a BatteryLevel is set so
this is better than showing "0%" which makes it look like a bug.
https://bugs.freedesktop.org/show_bug.cgi?id=97484
|
| |
|
|
|
|
| |
Use g_clear_pointer() and g_clear_object() when possible.
|
|
|
|
|
|
|
| |
Use systemd's service file to lockdown the UPower daemon to stop
eventual security problems.
https://bugs.freedesktop.org/show_bug.cgi?id=102898
|
|
|
|
|
|
|
|
| |
Newer kernels emit bind/unbind uevents that are not of interest to
powerd. To avoid littering logs with scary messages, let's lower their
severity to "debug".
https://bugs.freedesktop.org/show_bug.cgi?id=106018
|
| |
|
|
|
|
| |
For example, when using an incomplete mock logind.
|
|
|
|
|
|
|
|
|
| |
This adds an extra check to query if the iOS device has a
battery at all before actually trying to retrieve the battery
status. Should still work for older iOS versions which do not
provide this key.
https://bugzilla.freedesktop.org/show_bug.cgi?id=105625
|
|
|
|
|
|
|
|
| |
As Apple TVs do not have a battery and do not provide the
"BatteryIsCharging" lockdown key, upower would crash due to a
missing check whether the retrieved node is actually valid.
https://bugzilla.freedesktop.org/show_bug.cgi?id=105625
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When UPower would appear, or disappear, we'd get warnings like:
g_object_notify: object class 'UpDevice' has no property named 'g-name-owner'
or:
g_object_notify: object class 'UpClient' has no property named 'g-name-owner'
This was caused by the property proxying added in 7531dbd and 28438a7
being too lax about which properties it tried to proxy, which included
ones that didn't apply to the object types in question.
See https://bugs.freedesktop.org/show_bug.cgi?id=43001
https://bugs.freedesktop.org/show_bug.cgi?id=102350
|
| |
|
| |
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=92370
|
|
|
|
|
|
|
|
|
|
|
|
| |
As exported through BlueZ's org.bluez.Battery1 D-Bus interface. This
interface is only used for device where the battery information cannot
be processed in the kernel.
This is the first UpDevice type that doesn't use UdevDevice for the
Linux backend, and it is also the first that does not poll() status at
all.
https://bugs.freedesktop.org/show_bug.cgi?id=92370
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=103361
|
|
|
|
|
|
| |
Rather than using != NULL, followed by unref().
https://bugs.freedesktop.org/show_bug.cgi?id=103380
|
|
|
|
|
|
| |
Rather than using != NULL, followed by unref().
https://bugs.freedesktop.org/show_bug.cgi?id=103380
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=103380
|
|
|
|
|
|
|
| |
Those "API documentation" don't document the function below it, they
just name it, so aren't needed.
https://bugs.freedesktop.org/show_bug.cgi?id=103380
|
|
|
|
| |
https://bugs.freedesktop.org/show_bug.cgi?id=99906
|
|
|
|
|
|
| |
Since libimobiledevice 5a8449a, LOCKDOWN_E_NOT_ENOUGH_DATA was renamed
to LOCKDOWN_E_RECEIVE_TIMEOUT. We'll use "-7" to avoid having to use
build glue.
|
|
|
|
|
|
|
|
|
|
| |
The take_action_timeout_cb() function returns G_SOURCE_REMOVE which
makes GLib destroy the timeout. However the action_timeout_id
stayed != 0 so when warning level turned to "action" again the daemon
assumed that the timeout is already set and did nothing.
(It only logged: "Not taking action, timeout id already set")
https://bugs.freedesktop.org/show_bug.cgi?id=87791
|