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
fe36d9ee4a
Sometime we found the errors shows below when pipeline test was running. 379s ERROR: test_bluetooth_hidpp_mouse (__main__.Tests.test_bluetooth_hidpp_mouse) 379s Logitech Bluetooth LE mouse with HID++ kernel support 379s ---------------------------------------------------------------------- 379s Traceback (most recent call last): 379s File "/usr/libexec/upower/integration-test.py", line 4380, in test_bluetooth_hidpp_mouse 379s self.assertEventually( 379s ~~~~~~~~~~~~~~~~~~~~~^ 379s lambda: self.get_dbus_dev_property(bat0_up, "Model"), value=alias 379s ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 379s ) 379s ^ 379s File "/usr/libexec/upower/integration-test.py", line 399, in assertEventually 379s if condition() == value: 379s ~~~~~~~~~^^ 379s File "/usr/libexec/upower/integration-test.py", line 4381, in <lambda> 379s lambda: self.get_dbus_dev_property(bat0_up, "Model"), value=alias 379s ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^ 379s File "/usr/libexec/upower/integration-test.py", line 316, in get_dbus_dev_property 379s return self.dbus.call_sync( 379s ~~~~~~~~~~~~~~~~~~~^ 379s UP, 379s ^^^ 379s ...<7 lines>... 379s None, 379s ^^^^^ 379s ).unpack()[0] 379s ^ 379s gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/UPower/devices/mouse_dev_11_22_33_44_AA_BB” (19) 379s The upower and bluez daemons were started after the udev was initialized to avoid the random errors. |
||
|---|---|---|
| .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
-