Your message dated Fri, 6 Sep 2019 13:13:01 +0200 with message-id <[email protected]> and subject line Re: Bug#939510: Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument has caused the Debian Bug report #939468, regarding upower failed to start to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 939468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939468 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: upower Version: 0.99.11-1 Severity: important Dear maintainer, $ systemctl status upower.service ● upower.service - Daemon for power management Loaded: loaded (/lib/systemd/system/upower.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-09-05 11:45:40 CEST; 1min 14s ago Docs: man:upowerd(8) Process: 3931 ExecStart=/usr/lib/upower/upowerd (code=exited, status=217/USER) Main PID: 3931 (code=exited, status=217/USER) Sep 05 11:45:39 galadriel systemd[1]: Failed to start Daemon for power management. Sep 05 11:45:40 galadriel systemd[1]: upower.service: Service RestartSec=100ms expired, scheduling restart. Sep 05 11:45:40 galadriel systemd[1]: upower.service: Scheduled restart job, restart counter is at 5. Sep 05 11:45:40 galadriel systemd[1]: Stopped Daemon for power management. Sep 05 11:45:40 galadriel systemd[1]: upower.service: Start request repeated too quickly. Sep 05 11:45:40 galadriel systemd[1]: upower.service: Failed with result 'exit-code'. Sep 05 11:45:40 galadriel systemd[1]: Failed to start Daemon for power management. Reverting to upower 0.99.10-1 seems to work fine. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-rc7-galadriel-lxtec-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages upower depends on: ii dbus 1.12.16-1 ii libc6 2.28-10 ii libglib2.0-0 2.60.6-2 ii libgudev-1.0-0 232-2 ii libimobiledevice6 1.2.1~git20181030.92c5462-1 ii libplist3 2.0.1~git20190104.3f96731-1 ii libupower-glib3 0.99.11-1 ii libusb-1.0-0 2:1.0.23-1 ii udev 242-6 Versions of packages upower recommends: ii policykit-1 0.105-26 upower suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---* Michael Biebl <[email protected]> [2019-09-05 21:36 +0200]: > Am 05.09.19 um 21:10 schrieb Elimar Riesebieter: > > * Michael Biebl <[email protected]> [2019-09-05 20:41 +0200]: > > > >> Control: forcemerge -1 939468 > >> > >> Am 05.09.19 um 19:48 schrieb Salvo Tomaselli: > >>> Package: upower > >>> Version: 0.99.11-1 > >>> Severity: important > >>> Tags: patch > >>> > >>> Dear Maintainer, > >>> > >>> upon reboot I could not access my graphical session because upowerd was > >>> failing > >>> to be started by systemd. > >>> > >>> And apparently without it running sddm only shows garbage on screen. > >>> > >>> set 05 19:04:52 serenity systemd[1]: Stopped Daemon for power management. > >>> set 05 19:04:52 serenity systemd[1]: Starting Daemon for power > >>> management... > >>> set 05 19:04:52 serenity systemd[950]: upower.service: Failed to set up > >>> user namespacing: Invalid argument > >>> set 05 19:04:52 serenity systemd[950]: upower.service: Failed at step > >>> USER spawning /usr/lib/upower/upowerd: Invalid argument > >>> set 05 19:04:52 serenity systemd[1]: upower.service: Main process exited, > >>> code=exited, status=217/USER > >>> set 05 19:04:52 serenity systemd[1]: upower.service: Failed with result > >>> 'exit-code'. > >>> set 05 19:04:52 serenity systemd[1]: Failed to start Daemon for power > >>> management. > >>> set 05 19:04:53 serenity systemd[1]: upower.service: Service > >>> RestartSec=100ms expired, scheduling restart. > >>> set 05 19:04:53 serenity systemd[1]: upower.service: Scheduled restart > >>> job, restart counter is at 2. > >>> > >>> I have a long list of those. > >>> > >>> Commenting the user namespace directive solves the issue for me. > >>> > >> > >> > >> Duplicate of #939468 > >> > >> You are both using a custom kernel. > >> If I had to guess, I'd say that's the culprit. > > > > 0.99.10-1 runs fine, though. Which kernelconfig is necessary to run > > 0.99.11? > > I'd start with what's documented in /usr/share/doc/systemd/README.gz > and if that is not sufficient, diff your config with the one from the > Debian kernel. CONFIG_USER_NS was not set. Thanks for the hint. Elimar -- The path to source is always uphill! -unknown-
--- End Message ---
