| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This matches the ACPI and linux kernel specifications.
|
| |
|
|
|
|
| |
Closes: #152
|
| |
|
| |
|
|
|
|
|
| |
When libplist-2.0 isn't available, fallback to requiring libplist 1.x
to build the iDevice support.
|
| |
|
|
|
|
|
|
|
| |
src/linux/up-device-supply.c: In function ‘up_device_supply_refresh_line_power’:
src/linux/up-device-supply.c:89:22: warning: unused variable ‘native_path’ [-Wunused-variable]
89 | const gchar *native_path;
| ^~~~~~~~~~~
|
|
|
|
|
| |
We always have a config.h now, and don't rely on autotools setting this
cflags for us to know it.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The Linux integration tests were skipped since we started installing
python-dbusmock by hand, which meant that package dependencies like
python3-gobject were never installed, and the whole test would be
skipped.
Fixes: 3acbedca26619e6313f70b147024c1c3b92efbd9
|
|
|
|
|
|
| |
We need a higher than default timeout as the
test_critical_action_is_taken_repeatedly test takes at least 2 suspend
cycles and those take at least UP_DAEMON_ACTION_DELAY (20 seconds).
|
|
|
|
|
| |
They're not needed and might not be available when we're trying to list
the included tests.
|
| |
|
|
|
|
|
|
|
|
| |
The daemon sources and libupower-glib were built without their historic
log domains which meant some debug messages did not appear when running
upowerd in verbose mode.
This fixes the test_no_poll_batteries test.
|
|
|
|
| |
Parse the junit results and check whether there are any skipped tests.
|
|
|
|
| |
In case we want to read them even if successful (or skipped).
|
|
|
|
| |
It changed when we switched to meson.
|
|
|
|
|
| |
unittest_inspector.py lists the tests in the integration-test.py script,
which are then added as individual tests.
|
|
|
|
| |
Add the python suffix.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Otherwise we depend on the C sources being ready rather than the headers
for building the rest of upowerd.
|
|
|
|
|
|
|
| |
We don't care that the up_exported_kbd_backlight_* symbols and functions
were removed from the libupower-glib ABI, they should never have been
exported in the first place as this API is only used server-side, in the
daemon.
|
|
|
|
| |
So we don't need to define UP_COMPILATION
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
77 is the special value meaning that the test was skipped. Both meson
make check will display the information correctly.
Note that the test is currently executed directly in check-local. So add
a workaround to ignore the 77 error code and exit 0 instead in that
case.
|
|
|
|
|
| |
The functionality that this option was disabling/enabling has been
removed.
|
|
|
|
| |
It appears that this option is not used (anymore).
|
|
|
|
| |
libgudev got a version bump and libusb isn't used anymore.
|
|
|
|
|
| |
This was missed in commit 64582256a8c7 ("build: Remove libusb
dependency in Linux").
|
|
|
|
|
|
| |
As the daemon API will soon be removed.
See https://gitlab.freedesktop.org/upower/upower/-/merge_requests/66
|
|
|
|
|
|
| |
As we want to eventually remove them.
See https://gitlab.freedesktop.org/upower/upower/-/merge_requests/5
|
| |
|
|
|
|
| |
So we can see progress better.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Inhibitor lock should be taken between the critical
action notification and the execution of the critical action.
Requires python-dbusmock > 0.23.1, test is skipped on lower versions.
python-dbusmock in the CI is installed from git and bumped version
to 0.23.2 until a new release is available.
|
|
|
|
|
|
| |
Take inhibitor lock when notifying the user
about a critical battery level and release lock
when executing critical battery action.
|
|
|
|
|
|
|
|
| |
Phones are suspended most of the time so they are not awake for > 20s
to allow UPower to take action when battery is critical.
Add an interface to take and release inhibitor locks which
prevent the device from suspending to allow UPower to execute
the critical power action.
|
|
|
|
|
|
|
|
|
|
| |
gudev 234 had bugs converting cached sysfs properties to boolean which
caused upower to think that batteries were not there, as the "present"
sysfs attribute was misread.
Require at least gudev 235 to avoid battery detection being broken.
Closes: #149
|
|
|
|
| |
udev adds both tags to touchpads, so replicate that behaviour.
|
|
|
|
|
| |
Touchpads are also tagged as mice, so make sure that we check for
the touchpad property before checking for mouse one.
|
|
|
|
|
|
|
|
|
| |
USB PD 3.1 allows up to 240W (48V, 5A) and some proprietary supplies
already delivered more than 100W over USB-C (USB PD 3.0 limit).
Closes: #147
Reported by StefanBruens
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we want the computer to be able to take useful action about the low
battery, we should have a slightly higher "low" percentage level so that
power saving made really makes a difference in runtime.
Also bump "critical" slightly so that doom isn't quite as near but in the
distance nonetheless.
The "action" level stays the same, as 1% is too close to some batteries'
actual switch off point, eg. the computer might brown out before we see
1%.
|
|
|
|
|
|
|
| |
The code in up_device_notify() will still eventually be reached when the
up_device_coldplug() implementations are called, and properties are set
for the device type for the first time (rather than during instance
construction).
|