Hi,
I am running openSUSE Tumbleweed with KDE on a x86-64 desktop. The
system was updated (zypper dup) today, but I've been having an issue
with the upower service for a couple of months and have not been able to
discover a resolution amongst the openSUSE community.
The underlying cause appears to be a namespacing problem as it effects
both upower and systemd-localed in similar manner. Please refer to
snapshots from #systemctl and #journalctl -xe output below.
pepper:/var/log/zypp # service upower start
Job for upower.service failed because the control process exited with
error code.
See "systemctl status upower.service" and "journalctl -xe" for details.
pepper:/usr/lib/systemd # systemctl status upower.service
● upower.service - Daemon for power management
Loaded: loaded (/usr/lib/systemd/system/upower.service; disabled;
vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-10-16 10:10:36
BST; 1h 6min ago
Docs: man:upowerd(8)
Process: 18931 ExecStart=/usr/lib/upower/upowerd (code=exited,
status=226/NAMESPACE)
Main PID: 18931 (code=exited, status=226/NAMESPACE)
Oct 16 10:10:36 pepper systemd[1]: upower.service: Main process exited,
code=exited, status=226/NAMESPACE
Oct 16 10:10:36 pepper systemd[1]: upower.service: Failed with result
'exit-code'.
Oct 16 10:10:36 pepper systemd[1]: Failed to start Daemon for power
management.
Oct 16 10:10:36 pepper systemd[1]: upower.service: Service
RestartSec=100ms expired, scheduling restart.
Oct 16 10:10:36 pepper systemd[1]: upower.service: Scheduled restart
job, restart counter is at 5.
Oct 16 10:10:36 pepper systemd[1]: Stopped Daemon for power management.
Oct 16 10:10:36 pepper systemd[1]: upower.service: Start request
repeated too quickly.
Oct 16 10:10:36 pepper systemd[1]: upower.service: Failed with result
'exit-code'.
Oct 16 10:10:36 pepper systemd[1]: Failed to start Daemon for power
management.
pepper:/usr/lib/systemd #
pepper:/var/log/zypp # journalctl -xe
-- Automatic restarting of the unit upower.service has been scheduled,
as the result for
-- the configured Restart= setting for the unit.
Oct 16 10:10:36 pepper systemd[1]: Stopped Daemon for power management.
-- Subject: Unit upower.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit upower.service has finished shutting down.
Oct 16 10:10:36 pepper systemd[1]: Starting Daemon for power management...
-- Subject: Unit upower.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit upower.service has begun starting up.
Oct 16 10:10:36 pepper systemd[18931]: upower.service: Failed to set up
mount namespacing: No such file or directory
Oct 16 10:10:36 pepper systemd[18931]: upower.service: Failed at step
NAMESPACE spawning /usr/lib/upower/upowerd: No such file or directory
-- Subject: Process /usr/lib/upower/upowerd could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The files are present in their respective /usr/lib/ directories.
The main issue for me, is not that upower doesn't start, but that it
loops for a while and then invokes a 25 second timeout. Meaning that
applications calling it hang for 25, 50 seconds or more before
launching. e.g. Dolphin.
upower version 0.99.8-2.1 x86_64 is installed
Any assistance in finding a resolution to this problem will be most
appreciated.
Thanks and best regards,
Malcolm
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
