summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* linux: Postpone importing libraries for testswip/hadess/fix-ciBastien Nocera2021-09-071-18/+17
| | | | | They're not needed and might not be available when we're trying to list the included tests.
* build: Fix idevice support always being offBastien Nocera2021-09-072-1/+3
|
* build: Remove unused variable assignmentBastien Nocera2021-09-071-9/+0
|
* build: Require GIR to be created to run testsBastien Nocera2021-09-071-0/+1
|
* ci: Fix Linux integration tests all being skippedBastien Nocera2021-09-071-0/+1
| | | | | | | | | 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
* ci: Enable all the features explicitlyBastien Nocera2021-09-071-1/+1
|
* ci: Fail CI on skipped testsBastien Nocera2021-09-072-0/+26
| | | | Parse the junit results and check whether there are any skipped tests.
* ci: Always export the test logsBastien Nocera2021-09-071-1/+1
| | | | In case we want to read them even if successful (or skipped).
* ci: Fix path to test logBastien Nocera2021-09-071-1/+1
| | | | It changed when we switched to meson.
* linux: Split the integration test into individual testsBastien Nocera2021-09-072-6/+60
| | | | | unittest_inspector.py lists the tests in the integration-test.py script, which are then added as individual tests.
* linux: Rename integration test scriptBastien Nocera2021-09-072-1/+1
| | | | Add the python suffix.
* etc: Document Time* unitpacien2021-09-071-3/+3
|
* build: Remove autotoolsBastien Nocera2021-09-0626-1567/+1
|
* build: Clean up include_directories usageBastien Nocera2021-09-063-3/+2
|
* meson: Depend on upowerd_dbus for the entire daemonBenjamin Berg2021-09-061-2/+2
|
* meson: Fix header/source extraction from gdbus_codegenBenjamin Berg2021-09-061-2/+2
| | | | | Otherwise we depend on the C sources being ready rather than the headers for building the rest of upowerd.
* ci: Ignore ABI changes for keyboard backlight symbolsBastien Nocera2021-09-061-0/+8
| | | | | | | 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.
* tools: Include top-level library includeBastien Nocera2021-09-021-3/+1
| | | | So we don't need to define UP_COMPILATION
* ci: Build using mesonBenjamin Berg2021-09-021-12/+10
|
* build: Support building upower with mesonBenjamin Berg2021-09-0216-0/+600
|
* tests: Return 77 when skipping testsBenjamin Berg2021-09-022-4/+6
| | | | | | | | | 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.
* build: Remove "deprecated" optionBenjamin Berg2021-09-021-9/+0
| | | | | The functionality that this option was disabling/enabling has been removed.
* build: Remove systemdutildir optionBenjamin Berg2021-09-021-9/+0
| | | | It appears that this option is not used (anymore).
* README: Update dependenciesBastien Nocera2021-09-021-2/+1
| | | | libgudev got a version bump and libusb isn't used anymore.
* ci: Remove libusb dependencyBenjamin Berg2021-09-021-1/+0
| | | | | This was missed in commit 64582256a8c7 ("build: Remove libusb dependency in Linux").
* lib: Mark device refresh function as deprecatedBastien Nocera2021-08-191-0/+1
| | | | | | As the daemon API will soon be removed. See https://gitlab.freedesktop.org/upower/upower/-/merge_requests/66
* lib: Mark lid related functions and properties as deprecatedBastien Nocera2021-08-192-2/+4
| | | | | | As we want to eventually remove them. See https://gitlab.freedesktop.org/upower/upower/-/merge_requests/5
* 0.99.13UPOWER_0_99_13Bastien Nocera2021-08-172-1/+15
|
* tests: Run test suite in verbose mode by defaultBastien Nocera2021-08-171-1/+1
| | | | So we can see progress better.
* tests: Export test log on failureBastien Nocera2021-08-171-0/+4
|
* tests: Test inhibitor lock for critical actionDylan Van Assche2021-08-172-5/+59
| | | | | | | | | | 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.
* up-daemon: prevent suspending for critical actionDylan Van Assche2021-08-171-0/+13
| | | | | | Take inhibitor lock when notifying the user about a critical battery level and release lock when executing critical battery action.
* up-backend: add inhibitor lock interfaceDylan Van Assche2021-08-174-43/+70
| | | | | | | | 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.
* build: Require new gudev to fix battery detectionBastien Nocera2021-08-101-1/+1
| | | | | | | | | | 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
* linux: Add test for touchpads being tagged as miceBastien Nocera2021-08-101-2/+2
| | | | udev adds both tags to touchpads, so replicate that behaviour.
* linux: Fix touchpad not being the right typeBastien Nocera2021-08-101-3/+3
| | | | | Touchpads are also tagged as mice, so make sure that we check for the touchpad property before checking for mouse one.
* linux: Don't throw away large but possible energy ratesBastien Nocera2021-08-101-2/+2
| | | | | | | | | 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
* etc: Tweak default percentage levelsBastien Nocera2021-07-222-6/+6
| | | | | | | | | | | | | 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%.
* device: Don't update properties when device isn't exportedPablo Correa Gómez2021-06-301-8/+4
| | | | | | | 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).
* tests: Add test for non-default low levelPablo Correa Gómez2021-06-301-0/+36
|
* daemon: Sync icon and warning for non-default low levelPablo Correa Gómez2021-06-303-5/+13
| | | | | | | | | | | | | Before, the low level for changing the battery icon was hardcoded. However, as the `low_percentage` property is settable by the user using `PercentageLow` option. That can lead to inconsistencies when PercentageLow is not the default. For example, if PercentageLow is set higher than 10, the Low Battery level warning will be sent at the user-set level, but the battery icon would not be updated to "caution" until the percentage drops below 10%. This issue is solved in this commit by using the `low_percentage` property for the comparison instead of hardcoding the default.
* daemon: Make get_device_charge_icon() publicPablo Correa Gómez2021-06-183-37/+40
|
* tests: Add a test case for batteries with zero power drawPhilipp Zabel2021-06-171-0/+22
| | | | | | | Make sure that the issue reported in #7 and #44 is fixed. The mocked battery has a zero power_now attribute and a non-zero legacy current_now attribute on purpose, to detect if upowerd tries to read current_now if the power_now value is small.
* linux: Fix < 0.01 W energy-rate readings from power_now sysfs propertyPhilipp Zabel2021-06-171-2/+3
| | | | | | | | | | | | | | | | | Currently, if a power supplies' power_now sysfs file reports discharge rates < 0.01 W, the code will try to calculate the discharge rate from the legacy sysfs files. On new kernels where those don't exist, this produces wrong results. For example, on a dual-battery Thinkpad T450s, while the external battery is discharging, the internal battery reports power_now = 0, but the corresponding upower energy-rate field incorrectly reads about 2.3 W. This patch fixes the issue by falling back to the legacy code only if the legacy current_now sysfs file exists. Closes: #7, #44
* 0.99.12UPOWER_0_99_12Bastien Nocera2021-06-171-0/+16
|
* build: Force enable introspection for "make distcheck" to workBastien Nocera2021-06-171-1/+2
| | | | | Introspection support is needed to be able to instatiate a UPClient object in the test suite.
* ci: Export the tarball in the artifactsBastien Nocera2021-06-171-1/+10
| | | | Saves us from generating it locally.
* data: Also remove HID++ udev rulesBastien Nocera2021-06-172-11/+1
| | | | Now that HID++ user-space support has been removed.
* ci: Ignore changes to "kind" enumsBastien Nocera2021-06-172-1/+4
|
* linux: Make unknown Bluetooth devices appear as genericBastien Nocera2021-06-172-6/+7
| | | | | | | | | | Make Bluetooth devices for which we can't guess the "kind" or form factor be "generic Bluetooth" devices, rather than "unknown" devices. That should make it clearer in UIs that the devices are Bluetooth rather than connected to the computer somehow. Closes: #137
View Lorry Controller Status