Bug#756247: Failed to start unit user@1000.service: Unknown unit: user@0000.service

Michael Biebl

unread,

Jul 27, 2014, 7:30:01 PM7/27/14

to

Package: systemd-shim
Version: 6-4
Severity: normal

When running logind v205+ under systemd-shim 6-4 / cgmanager, I get this
error message:

Failed to start unit us...@0.service: Unknown unit: us...@0.service
Failed to start user service: Unknown unit: us...@0.service

This is particularly visible on the console, where the error message is
shown on the users console upon login.

Ther user@.service provides a per user session which is started by the
pam_systemd module. [1] has a few more details.

[1] https://wiki.archlinux.org/index.php/Systemd/User

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

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd-shim depends on:
pn cgmanager <none>
ii libc6 2.19-7
ii libglib2.0-0 2.40.0-3

systemd-shim recommends no packages.

Versions of packages systemd-shim suggests:
ii pm-utils 1.4.1-15

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Michael Biebl

unread,

Jul 27, 2014, 7:40:01 PM7/27/14

to

The relevant code in logind calling the StartUnit D-Bus interface on
org.freedesktop.systemd1.Manager:

http://sources.debian.net/src/systemd/208-6/src/login/logind-user.c?hl=426#L368

http://sources.debian.net/src/systemd/208-6/src/login/logind-dbus.c#L2683
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc

Steve Langasek

unread,

Aug 1, 2014, 10:30:02 PM8/1/14

to

Control: tags -1 moreinfo

On Mon, Jul 28, 2014 at 01:17:51AM +0200, Michael Biebl wrote:
> Package: systemd-shim
> Version: 6-4
> Severity: normal

> When running logind v205+ under systemd-shim 6-4 / cgmanager, I get this
> error message:

> Failed to start unit us...@0.service: Unknown unit: us...@0.service
> Failed to start user service: Unknown unit: us...@0.service

> This is particularly visible on the console, where the error message is
> shown on the users console upon login.

> Ther user@.service provides a per user session which is started by the
> pam_systemd module. [1] has a few more details.

And what are you expecting systemd-shim to do to fix this? By definition,
systemd-shim is used only when PID1 is not systemd; it is therefore
meaningless to start a systemd unit, and certainly meaningless to start a
systemd unit whose function is to spawn a systemd user session. Are you
expecting libpam-systemd to now enforce the use of systemd user sessions?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slan...@ubuntu.com vor...@debian.org

signature.asc

Francesco Poli

unread,

Aug 28, 2014, 1:10:03 PM8/28/14

to

On Mon, 18 Aug 2014 17:35:55 +0200 Michael Biebl wrote:

[...]
> I simply wanted to point out that when running logind under
> systemd-shim, you'll get the error messages as shown in the attached
> screenshots. I'm pretty sure, some of our users will be concerned about
> this.

Hello, I am a concerned user! ;-)

I haven't studied the details of all this systemd session management
thing, but I don't expect this to be a pre-requisite for running any
Debian system...
So, from the point of view of a user unfamiliar with the systemd
internals, I think that:

• if these error messages do not correspond to any actual issue,
they should be suppressed and never shown to the user

• if, on the other hand, these error messages are a symptom of
a real misbehavior, this should be fixed, so that users of
sysvinit-core + systemd-shim may run Debian without trouble

By the way, should this bug report be merged with #756076 ?

Thanks for your time and for the effort in maintaining systemd-shim!
Bye.

--
http://www.inventati.org/frx/
fsck is a four letter word...
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE

Vincent Lefevre

unread,

Sep 9, 2014, 10:50:03 AM9/9/14

to

Control: found -1 7-3

On 2014-08-28 18:59:17 +0200, Francesco Poli wrote:
> So, from the point of view of a user unfamiliar with the systemd
> internals, I think that:
>
> • if these error messages do not correspond to any actual issue,
> they should be suppressed and never shown to the user
>
> • if, on the other hand, these error messages are a symptom of
> a real misbehavior, this should be fixed, so that users of
> sysvinit-core + systemd-shim may run Debian without trouble

I agree.

I have the same problem when logging in from a virtual text terminal
(since gdm3 does not work after the upgrade to systemd 208-8):

[ 174.808740] systemd-logind[2521]: Failed to start unit us...@1000.service: Unknown unit: us...@1000.service
[ 174.808763] systemd-logind[2521]: Failed to start user service: Unknown unit: us...@1000.service

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Martin Pitt

unread,

Nov 4, 2014, 6:20:03 AM11/4/14

to

Control: tag -1 fixed-upstream pending

Michael Biebl [2014-07-28 1:17 +0200]:

> When running logind v205+ under systemd-shim 6-4 / cgmanager, I get this
> error message:
>
> Failed to start unit us...@0.service: Unknown unit: us...@0.service
> Failed to start user service: Unknown unit: us...@0.service

Fixed the warning upstream:
https://github.com/desrt/systemd-shim/commit/729b958d9d97

Thanks,

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

signature.asc