* Michael Biebl <bi...@debian.org> [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? Elimar -- Experience is something you don't get until just after you need it!
