Debian Bug report logs - #939510
upower.service: Failed to set up user namespacing: Invalid argument

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Salvo Tomaselli <tiposchi@tiscali.it>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: upower.service: Failed to set up user namespacing: Invalid argument

Date: Thu, 05 Sep 2019 19:48:23 +0200

[Message part 1 (text/plain, inline)]

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.

Best

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.20.5 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= (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-7

Versions of packages upower recommends:
ii  policykit-1  0.105-26

upower suggests no packages.

-- no debconf information

[upower.service.patch (text/plain, attachment)]

Message #10 received at 939510@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Salvo Tomaselli <tiposchi@tiscali.it>, 939510@bugs.debian.org, 939468@bugs.debian.org, Elimar Riesebieter <riesebie@lxtec.de>

Subject: Re: [Pkg-utopia-maintainers] Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument

Date: Thu, 5 Sep 2019 20:41:12 +0200

[Message part 1 (text/plain, inline)]

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.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #17 received at 939510@bugs.debian.org (full text, mbox, reply):

From: Elimar Riesebieter <riesebie@lxtec.de>

To: Michael Biebl <biebl@debian.org>

Cc: Salvo Tomaselli <tiposchi@tiscali.it>, 939510@bugs.debian.org, 939468@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument

Date: Thu, 5 Sep 2019 21:10:38 +0200

* Michael Biebl <biebl@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!

Message #22 received at 939510@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Elimar Riesebieter <riesebie@lxtec.de>, 939510@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#939510: Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument

Date: Thu, 5 Sep 2019 21:36:57 +0200

[Message part 1 (text/plain, inline)]

Am 05.09.19 um 21:10 schrieb Elimar Riesebieter:
> * Michael Biebl <biebl@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?

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.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #27 received at 939510@bugs.debian.org (full text, mbox, reply):

From: Elimar Riesebieter <riesebie@lxtec.de>

To: Michael Biebl <biebl@debian.org>

Cc: 939510@bugs.debian.org, 939468-done@bugs.debian.org

Subject: Re: Bug#939510: Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument

Date: Fri, 6 Sep 2019 13:13:01 +0200

* Michael Biebl <biebl@debian.org> [2019-09-05 21:36 +0200]:

> Am 05.09.19 um 21:10 schrieb Elimar Riesebieter:
> > * Michael Biebl <biebl@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?
> 
> 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-

Message #33 received at 939510@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@corsac.net>

To: 939510@bugs.debian.org, Michael Biebl <biebl@debian.org>

Subject: Re: Bug#939510: Bug#939510: upower.service: Failed to set up user namespacing: Invalid argument

Date: Thu, 12 Sep 2019 11:48:59 +0200

On Fri, 6 Sep 2019 13:13:01 +0200 Elimar Riesebieter <riesebie@lxtec.de>
wrote:
> * Michael Biebl <biebl@debian.org> [2019-09-05 21:36 +0200]:
> 
> > Am 05.09.19 um 21:10 schrieb Elimar Riesebieter:
> > > * Michael Biebl <biebl@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?
> > 
> > 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

Send a report that this bug log contains spam.