Arch Linux

user4467

Member

Registered: 2019-10-14

Posts: 1

upowerd problem on system startup

Hello

After updating to newest stable arch I have a problem with upowerd, which slows up start of kde to something about one minute.
But if I start upowerd from another virtual console (I switch to it, login and start upowerd by hand), start after that step is ok.

Why I have to start it? because if I dont kde wont load power management which has impact on other functions.

I start the deamon by :

sudo /usr/lib/upowerd --verbose

Could You point me where I can fix it to work as before.
I tried to reinstall upower by pacman - no effect

journalctl -r

oct 11 16:26:19 myComp sddm-greeter[710]: qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:125:5: Type Keyboard unavailable
oct 11 16:26:19 myComp sddm-greeter[710]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:22:1: Type InputPanel unavailable
oct 11 16:26:17 myComp dbus-daemon[348]: [system] Successfully activated service 'org.freedesktop.UPower'
oct 11 16:26:17 myComp sudo[1026]: pam_unix(sudo:session): session opened for user root by myUser(uid=0)
oct 11 16:26:17 myComp sudo[1026]:     myUser : TTY=tty2 ; PWD=/home/myUser ; USER=root ; COMMAND=/usr/lib/upowerd --verbose
oct 11 16:26:11 myComp systemd[1]: systemd-hostnamed.service: Succeeded.
oct 11 16:26:09 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:09 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:09 myComp systemd[1]: upower.service: Start request repeated too quickly.
oct 11 16:26:09 myComp systemd[1]: Stopped Daemon for power management.
oct 11 16:26:09 myComp systemd[1]: upower.service: Scheduled restart job, restart counter is at 5.
oct 11 16:26:09 myComp systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
oct 11 16:26:09 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:09 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:09 myComp systemd[1]: upower.service: Main process exited, code=exited, status=217/USER
oct 11 16:26:09 myComp systemd[1020]: upower.service: Failed at step USER spawning /usr/lib/upowerd: Invalid argument
oct 11 16:26:09 myComp systemd[1020]: upower.service: Failed to set up user namespacing: Invalid argument
oct 11 16:26:09 myComp systemd[1]: Starting Daemon for power management...
oct 11 16:26:09 myComp systemd[1]: Stopped Daemon for power management.
oct 11 16:26:09 myComp systemd[1]: upower.service: Scheduled restart job, restart counter is at 4.
oct 11 16:26:09 myComp systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
oct 11 16:26:09 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:09 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:09 myComp systemd[1]: upower.service: Main process exited, code=exited, status=217/USER
oct 11 16:26:09 myComp systemd[1016]: upower.service: Failed at step USER spawning /usr/lib/upowerd: Invalid argument
oct 11 16:26:09 myComp systemd[1016]: upower.service: Failed to set up user namespacing: Invalid argument
oct 11 16:26:08 myComp systemd[1]: Starting Daemon for power management...
oct 11 16:26:08 myComp systemd[1]: Stopped Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Scheduled restart job, restart counter is at 3.
oct 11 16:26:08 myComp systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
oct 11 16:26:08 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:08 myComp systemd[1]: upower.service: Main process exited, code=exited, status=217/USER
oct 11 16:26:08 myComp systemd[1009]: upower.service: Failed at step USER spawning /usr/lib/upowerd: Invalid argument
oct 11 16:26:08 myComp systemd[1009]: upower.service: Failed to set up user namespacing: Invalid argument
oct 11 16:26:08 myComp systemd[1]: Starting Daemon for power management...
oct 11 16:26:08 myComp systemd[1]: Stopped Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Scheduled restart job, restart counter is at 2.
oct 11 16:26:08 myComp systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
oct 11 16:26:08 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:08 myComp systemd[1]: upower.service: Main process exited, code=exited, status=217/USER
oct 11 16:26:08 myComp systemd[1005]: upower.service: Failed at step USER spawning /usr/lib/upowerd: Invalid argument
oct 11 16:26:08 myComp systemd[1005]: upower.service: Failed to set up user namespacing: Invalid argument
oct 11 16:26:08 myComp systemd[1]: Starting Daemon for power management...
oct 11 16:26:08 myComp systemd[1]: Stopped Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Scheduled restart job, restart counter is at 1.
oct 11 16:26:08 myComp systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart.
oct 11 16:26:08 myComp systemd[1]: Failed to start Daemon for power management.
oct 11 16:26:08 myComp systemd[1]: upower.service: Failed with result 'exit-code'.
oct 11 16:26:08 myComp systemd[1]: upower.service: Main process exited, code=exited, status=217/USER
oct 11 16:26:08 myComp systemd[992]: upower.service: Failed at step USER spawning /usr/lib/upowerd: Invalid argument
oct 11 16:26:08 myComp systemd[992]: upower.service: Failed to set up user namespacing: Invalid argument
oct 11 16:26:08 myComp systemd[1]: Starting Daemon for power management...
oct 11 16:26:08 myComp dbus-daemon[348]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.31' (uid=989 pid=710 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:>
oct 11 16:26:08 myComp sddm-greeter[710]: QObject::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString)
oct 11 16:26:08 myComp sddm-greeter[710]: QObject::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString)

n0noob

Member

Registered: 2015-06-02

Posts: 4

Re: upowerd problem on system startup

I am facing the same issue. Need help !!

As per my current findings, this is something related to linux-lts49.

Last edited by n0noob (2019-10-20 14:59:55)

StyxFromTheNile

Member

Registered: 2019-10-23

Posts: 1

Re: upowerd problem on system startup

I found a temporary, and potentially ugly fix for this!

open up /usr/lib/systemd/system/upower.service and comment out the lines

...
#Namespaces
#PrivateUsers=yes
#RestrictNamespaces=yes
...

I am looking for a nicer fix, but at least for now i can see my battery percentage again,

Last edited by StyxFromTheNile (2019-10-23 22:08:00)

loqs

Member

Registered: 2014-03-06

Posts: 18,891

Re: upowerd problem on system startup

PrivateUsers requires CONFIG_USER_NS [1]
Please note /usr/lib/systemd/system/upower.service will be overwritten on package upgrade.
I would suggest using a drop-in.

[1] https://github.com/systemd/systemd/blob/v243/README#L77

Last edited by loqs (2019-10-23 23:18:55)