fdo-mirrors/upower
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/upower/upower.git synced 2025-12-20 02:00:03 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

README: Rename to README.md and fix markdown with markdownlint

Browse source
This commit is contained in:
Kate Hsuan 2025-01-08 14:14:56 +08:00
parent d11300fac6
commit 99de6c9744
1 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
README → README.md
View file

@ -1,7 +1,8 @@
# UPower # UPower
Requirements: Requirements:
```
```text
glib-2.0 >= 2.66.0 glib-2.0 >= 2.66.0
gio-2.0 >= 2.16.1 gio-2.0 >= 2.16.1
gudev-1.0 >= 235 (Linux) gudev-1.0 >= 235 (Linux)
@ -17,32 +18,36 @@ org.freedesktop.UPower service via the system message bus.
## Debugging ## Debugging
When doing bug reports, the following information can be useful: When doing bug reports, the following information can be useful:
- `grep . /sys/class/power_supply/*/*`:
- `grep . /sys/class/power_supply/*/*`
This includes the current kernel view of all power supplies in the This includes the current kernel view of all power supplies in the
system. It is always a good idea to include this information. system. It is always a good idea to include this information.
- `udevadm info -e`: - `udevadm info -e`
This shows the hardware configuration and is relevant when e.g. the This shows the hardware configuration and is relevant when e.g. the
type of an external device is misdetected. type of an external device is misdetected.
- `upower -d`: - `upower -d`
Shows upower's view of the state Shows upower's view of the state
- `upower --monitor-detail`: - `upower --monitor-detail`
Dumps device information every time that a change happens. This helps Dumps device information every time that a change happens. This helps
with debugging dynamic issues. with debugging dynamic issues.
- `udevadm monitor`: - `udevadm monitor`
Dumps the udev/kernel reported hardware changes (and addition/removal). Dumps the udev/kernel reported hardware changes (and addition/removal).
This is helpful when debugging dynamic issues, in particular if it is This is helpful when debugging dynamic issues, in particular if it is
not clear whether the issue is coming from the kernel or upower. 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 In addition, it can also be useful to run upower in debug mode and post the
logs. There are two ways of doing so: logs. There are two ways of doing so:
- Run upower daemon manually, you can do so using: - Run upower daemon manually, you can do so using:
`sudo /usr/libexec/upowerd -rd` `sudo /usr/libexec/upowerd -rd`
- Modify the systemd service and restart. This is best done by: - Modify the systemd service and restart. This is best done by:
1. `sudo systemctl edit upower.service` 1. `sudo systemctl edit upower.service`
2. Adding the two lines: 2. Adding the two lines:
```
```text
[Service] [Service]
Environment=G_MESSAGES_DEBUG=all Environment=G_MESSAGES_DEBUG=all
``` ```
3. `sudo systemctl restart upower.service` 3. `sudo systemctl restart upower.service`
4. Grab logs using `journalctl -u upower.service` or similar 4. Grab logs using `journalctl -u upower.service` or similar