mirror of
https://gitlab.freedesktop.org/upower/upower.git
synced 2025-12-20 02:00:03 +01:00
read-only-mirror of https://gitlab.freedesktop.org/upower/upower
1ba5f3a55e
As some systems only allow for one charge threshold setting, the overall
process is treated as a success as long as one of the values is set
correctly. We only treat it as an error (and return FALSE) if both the
start and end threshold settings fail. For this reason, we don't need
to track specific errors for every write, so the GError parameter in
g_file_set_contents_full() is set to NULL.
Fedora upowerd[1326]: g_file_set_contents_full: assertion 'error == NULL || *error == NULL' failed
Fedora upowerd[1326]: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Failed to set charge control thresholds
Resolves: #331
|
||
|---|---|---|
| .ci | ||
| contrib | ||
| data/zsh-completion | ||
| dbus | ||
| doc | ||
| etc | ||
| libupower-glib | ||
| po | ||
| policy | ||
| rules | ||
| src | ||
| tools | ||
| .git-blame-ignore-revs | ||
| .gitconfig | ||
| .gitlab-ci.yml | ||
| .markdownlint.json | ||
| .pre-commit-config.yaml | ||
| AUTHORS | ||
| code-of-conduct.md | ||
| COMMITMENT | ||
| COPYING | ||
| HACKING.md | ||
| meson.build | ||
| meson_options.txt | ||
| NEWS | ||
| README.md | ||
| RELEASE | ||
UPower
Requirements:
glib-2.0 >= 2.66.0
gio-2.0 >= 2.16.1
gudev-1.0 >= 235 (Linux)
libimobiledevice-1.0 >= 0.9.7 (optional)
polkit-gobject-1 >= 124
UPower is an abstraction for enumerating power devices, listening to device events and querying history and statistics. Any application or service on the system can access the org.freedesktop.UPower service via the system message bus.
Debugging
When doing bug reports, the following information can be useful:
grep . /sys/class/power_supply/*/*
This includes the current kernel view of all power supplies in the system. It is always a good idea to include this information.udevadm info -e
This shows the hardware configuration and is relevant when e.g. the type of an external device is misdetected.upower -d
Shows upower's view of the stateupower --monitor-detail
Dumps device information every time that a change happens. This helps with debugging dynamic issues.udevadm monitor
Dumps the udev/kernel reported hardware changes (and addition/removal). This is helpful when debugging dynamic issues, in particular if it is not clear whether the issue is coming from the kernel or upower.
In addition, it can also be useful to run upower in debug mode and post the logs. There are two ways of doing so:
- Run upower daemon manually, you can do so using:
sudo /usr/libexec/upowerd -rd - Modify the systemd service and restart. This is best done by:
-
sudo systemctl edit upower.service -
Adding the two lines:
[Service] Environment=G_MESSAGES_DEBUG=all -
sudo systemctl restart upower.service -
Grab logs using
journalctl -u upower.serviceor similar
-