Age | Commit message (Collapse) | Author | Files | Lines |
|
The test cases for AllowRiskyCriticalPowerAction=true and false when
CriticalPowerAction=Suspend.
|
|
If AllowRiskyCriticalPowerAction is true and the CriticalPowerAction
is "Suspend", The "Suspend" can be the CriticalPowerAction.
Otherwise, "HybridSleep" will be the CriticalPowerAction.
|
|
|
|
The warning message will be shown when CriticalPowerAction is "Suspend".
One iwarning message is for enabling the risky CriticalPowerAction and
the other is to show the potential risk when
AllowRiskyCriticalPowerAction is true.
|
|
When using UPower in a non-hybernate setup, the result of a
CriticalPowerAction would be PowerOff. Certain users prefer
Suspend instead, because this is the only way to recover
graceful from that state.
Suspend action will only used, when explicit configured.
Closes: #23
Closes: #59
Signed-off-by: Kate Hsuan <hpa@redhat.com>
|
|
Test is based on umockdev package without compile it
during runner creation step.
|
|
- Update change information to NEWS
|
|
|
|
1. Resolved high disk and CPU rate.
2. Update glib2 requirement to 2.66.0.
3. Stop guessing the unknown battery as a power supply.
4. Continue to support lid handling.
5. Document fixes and bug fixes.
|
|
g_get_current_time was deprecated in 2.62 and can be directly replaced with
g_get_real_time.
|
|
Bump glib2 to 2.66 so we can use g_file_set_contents_full
|
|
This resolves the following deprecation warning, meson these days has a
special function for installing an empty directory:
* 0.60.0: {'install_subdir with empty directory'}
|
|
We only had documentation for the first 9 device types, ending with
Phone. Document all the current 29 device types.
|
|
Remove the history when the device id was changed.
|
|
Ignore all the unknown events from the devices.
|
|
up_history_is_device_id_equal() is used to compare the history device_id
with a given string.
|
|
Include:
Liebert
usb:v10AFp0000*
usb:v10AFp0002*
Link: https://github.com/networkupstools/nut
Link: https://raw.githubusercontent.com/networkupstools/nut/master/scripts/upower/95-upower-hid.hwdb
|
|
Link: https://github.com/networkupstools/nut
Link: https://raw.githubusercontent.com/networkupstools/nut/master/scripts/upower/95-upower-hid.hwdb
|
|
This reverts commit 520939242e65e2428b43af41889696d0f50ead40.
Revert the last ABI break since API has been reverted.
|
|
This reverts commit a94c94fe6bc7c4e92d0ec34bc64d53de68fc4f32.
Revert so verion bump up since the API has been reverted.
Resolves: https://gitlab.freedesktop.org/upower/upower/-/issues/261
|
|
This reverts commit 07565ef6a1aa4a115f8ce51e259e408edbaed4cc.
In the current systemd stable release 255 org.freedesktop.login1 does
not emit a LidisClosed event, this has added in systemd `main` and will
be availble in the next release.
As GNOME control panel still uses UPower's `LidIsclosed` property and
many other DE's such as Xfce/LXQt/Deepin as well revert this until the
systemd changes are available in all Distributions.
https://github.com/systemd/systemd/pull/30706
Resolve: https://gitlab.freedesktop.org/upower/upower/-/issues/260
|
|
This reverts commit 67666029543f12d423619df4e8d1ad32faa928e9.
Removing this and renaming up_client_get_devices2 to
up_client_get_devices means consumers have to support three cases to
support older UPower versions. So for example GNOME Control center now
uses up_client_get_devices2 and would have to now check if UPower
version > 0.92.
|
|
The EnergyRate is a positive value since most of the laptops are ACPI
based system and report the power status through power_now sysfs
attribute. Moreover, the ACPI specification mention that the battery
power status is a positive value, measured in watt.
https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/acpi-battery-and-power-subsystem-firmware-implementation
Fix: https://gitlab.freedesktop.org/upower/upower/-/issues/252
Signed-off-by: Kate Hsuan <hpa@redhat.com>
|
|
dbusmock 0.30.1 changed the BlueZ template to set the default "Class"
property to `MOCK_PHONE_CLASS` right away instead of in PairDevice() [1].
test_bluetooth_le_device() relied on the previous implicit default of a
"0" Class value. Set this explicitly to expect a "generic" device. This
makes the test work with old and current dbusmock versions.
https://bugs.debian.org/1059467
[1] https://github.com/martinpitt/python-dbusmock/pull/192
|
|
Some vendor kernel (most notably Android devices) expose various types
of BMS (battery management system) as power supplies. This is something
UPower has never designed to deal with, and thus UPower should not
represent or consider it to be a battery.
Fortunately, most of the time the actual "battery" power supply has the
correct type, so we can safely ignore those devices which have unknown
type. Also, the code that assumes power supply of unknown type seems
pretty dated and probably doesn't make sense anymore. So, let's remove
this assumption altogether.
|
|
|
|
Compare on object identity not equality.
|
|
udev is available only on Linux, so limit their usage when the backend
is 'linux'.
This fixes the build when the backend is different than 'linux', i.e.
typically on non-Linux OSes.
|
|
Work-around rawhide being broken:
Problem: The operation would result in removing the following protected packages: dnf
|
|
|
|
|
|
And rename up_client_get_devices2() to up_client_get_devices().
|
|
It is now handled solely in logind to take power management decisions,
and in the compositor for making decisions related to available
displays.
See:
https://www.freedesktop.org/software/systemd/man/org.freedesktop.login1.html
|
|
|
|
This will allow running the tests to target installed binaries.
|
|
Fixes: 648abe9c2742 ("tests: Test a client running while daemon restarts")
|
|
|
|
|
|
|
|
|
|
Closes: #240
|
|
So we can know whether a device was registered when hiding it and
eventually send the appropriate "device-removed" signal.
|
|
Return whether up_device_register() registered a device, so we can
announce it through a device-added signal.
|
|
Fixes: 648abe9c2742 ("tests: Test a client running while daemon restarts")
Closes: #241
|
|
Some of the functionality will be broken with older versions, in
particular when it comes to newline stripping when reading sysfs
attributes.
|
|
Until the image creation CI job can run all the way through:
https://gitlab.freedesktop.org/upower/upower/-/issues/242
install a newer libgudev by hand.
|
|
|
|
|
|
|
|
Some devices change the 'present' sysfs attribute after upower
registers them. This should be updated in upower, otherwise
applications will ignore present devices, or listen to absent devices.
Fixes: 0b7d7cfc08bf ("linux: Fix is-present for devices at startup")
|