On Fri, 6 Sep 2019 13:13:01 +0200 Elimar Riesebieter <[email protected]> wrote: > * 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. > Hi Michael,
you might want to document that a bit, maybe in a NEWS.Debian. I have the same issue here with a *Debian* kernel where user namespaces are disabled (with sysctl user.max_user_namespaces = 0). I'm definitely not a huge fan of user namespaces because of the attack surface they enable, and I'm a bit surprised to see upower start using them in a point release. I'll adjust the configuration but unfortunately that means enabling them systemwide, not just for upower. Regards, -- Yves-Alexis
