Upower causing system slowness

Support
1

G’day all,

I’m having issues with my system, which appears to be due to the upower service not able to start. If I reinstall upower, the problems seem to go away temporarily.

It may be related to gitlab.freedesktop.org/upower/upower/-/issues/104 , but i’m not sure how CONFIG_USER_NS is meant to be set.

Thanks

3

No reason at all… it’s just what is installed in my system. I did not explicitly install it. Should I uninstall it then?

4

systemctl status upower should give you some feedback to why it failed.

5

G’day mbb,

It simply said it timed out. I’ll try and capture some logs and attach them when I get a chance.

6

Well, lets restart:

Which issues exactly?

Doesn’t seem so, judging from what systemctl tells you. Please post the output of journalctl -p3 -b

Try to start the service manually: sudo systemctl start upower and then post here the output of systemctl status upower

1 Like
7

Not sure what’s going on, but its working fine now. I’ll update if it starts happening again.

1 Like
8

Started again this morning, here is the result of trying to start it manually:

[user@system-name ~]$ sudo systemctl start upower
Job for upower.service failed because a timeout was exceeded.
See "systemctl status upower.service" and "journalctl -xe" for details.
[user@system-name ~]$ sudo systemctl status upower
● upower.service - Daemon for power management
     Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled; vendor preset: disabled)
     Active: activating (start) since Sat 2020-10-17 07:06:01 AEST; 1min 16s ago
       Docs: man:upowerd(8)
   Main PID: 6746 (upowerd)
      Tasks: 4 (limit: 38464)
     Memory: 2.8M
     CGroup: /system.slice/upower.service
             └─6746 /usr/lib/upowerd

Oct 17 07:06:01 system-name systemd[1]: Starting Daemon for power management...

journalctl -p3 -b

-- Logs begin at Thu 2020-06-25 22:58:34 AEST, end at Sat 2020-10-17 07:08:54 AEST. --
Oct 17 07:01:40 system-name kernel: logitech-hidpp-device 0003:046D:C086.0008: Device not connected
Oct 17 07:02:50 system-name sddm-helper[1169]: gkr-pam: unable to locate daemon control file
Oct 17 07:02:52 system-name libvirtd[592]: operation failed: pool 'default' already exists with uuid 3b841165-d199-403a-a575-850512950cd2
Oct 17 07:03:00 system-name systemd[1]: Failed to start Daemon for power management.
Oct 17 07:03:02 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:03:06 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:03:10 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:03:14 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:04:31 system-name systemd[1]: Failed to start Daemon for power management.
Oct 17 07:04:31 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:06:01 system-name systemd[1]: Failed to start Daemon for power management.
Oct 17 07:06:04 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
Oct 17 07:07:31 system-name systemd[1]: Failed to start Daemon for power management.
Oct 17 07:07:33 system-name kernel: usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
9

Are you running Manjaro in a VM or is it installed in “bare metal”?

10

It’s installed bare metal:

Operating System: Manjaro Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.11-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: GeForce GTX 1080 Ti/PCIe/SSE2

11

Please provide inxi -Fayz maybe there’s an hardware known problem.

EDIT: in the meantime, you can try to install kernel 5.4 and see if this is still happening.