Debian Bug report logs - #764298
"Failed to start Login Service." after upgrade to 215-5+b1

Toggle useless messages

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

From: "I. Schrey" <sy@schreyben.de>

To: Debian bugs <submit@bugs.debian.org>

Subject: "Failed to start Login Service." after upgrade to 215-5+b1

Date: Tue, 07 Oct 2014 01:11:04 +0200

Package: systemd
Version: 215-5+b1

Greetings,

see below, errors after the latest apt-get (dist-)upgrade on a
minimal install Jessie VM which was running fine before.

Before the upgrade, I had the impression that the system wasn't
using logind at all. At least a search in my remote syslog db
doesn't find anything with the string 'logind' in it, up to the point
when I restarted the VM after the upgrade.


Maybe related:
after the upgrade, it suggested to autoremove

libdbus-1-3                          1.8.6-2
libgcrypt11                          1.5.4-3
libsystemd-daemon0                   208-8
libsystemd-journal0                  208-8
libsystemd-login0                    208-8

so I did.


I see in b.d.o that the "exit status 32" is being worked on - not sure
if that's related? The mounts look okay to me, after bootup,
nothing seems missing or read only.


Please tell me if you need more info, and what you need.
If it helps, I could do a rollback and redo the upgrade.


Regards
Ingmar


---snip journalctl---

Oct 06 23:13:53 bpo-jessie-s systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct 06 23:13:53 bpo-jessie-s systemd-logind[433]: Failed to connect to 
system bus: No such file or directory
Oct 06 23:13:53 bpo-jessie-s systemd-logind[433]: Failed to fully start 
up daemon: No such file or directory
Oct 06 23:13:53 bpo-jessie-s systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct 06 23:13:53 bpo-jessie-s systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-logind.service has failed.
--
-- The result is failed.
Oct 06 23:13:53 bpo-jessie-s systemd[1]: Unit systemd-logind.service 
entered failed state.


---snip syslog---

Oct  6 23:13:53 jessie-test kernel: alg: No test for crc32 (crc32-pclmul)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda3): re-mounted. Opts: 
errors=remount-ro
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda6): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda5): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda1): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test kernel: EXT4-fs (vda4): mounted filesystem 
with ordered data mode. Opts: (null)
Oct  6 23:13:53 jessie-test systemd-fsck[108]: /dev/vda3: clean, 
2773/117856 files, 119073/471040 blocks
Oct  6 23:13:53 jessie-test systemd-udevd[132]: Network interface 
NamePolicy= disabled on kernel commandline, ignoring.
Oct  6 23:13:53 jessie-test systemd-fsck[161]: /dev/vda1: clean, 
297/12288 files, 34551/49152 blocks
Oct  6 23:13:53 jessie-test systemd-fsck[174]: /dev/vda5: clean, 
3857/65536 files, 24471/261888 blocks
Oct  6 23:13:53 jessie-test systemd-fsck[187]: /dev/vda6: clean, 
29/98304 files, 22686/393216 blocks
Oct  6 23:13:53 jessie-test keyboard-setup[135]: Setting preliminary 
keymap...done.
Oct  6 23:13:53 jessie-test systemd-remount-fs[229]: mount: /usr not 
mounted or bad option
Oct  6 23:13:53 jessie-test systemd-remount-fs[229]: /bin/mount for /usr 
exited with exit status 32.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-remount-fs.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Remount Root and 
Kernel File Systems.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-remount-fs.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main 
process exited, code=exited, status=1/FAILURE
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for 
unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such 
file or directory.
Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service start 
request repeated too quickly, refusing to start.
Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service 
entered failed state.
Oct  6 23:13:53 jessie-test munin-node[463]: Process Backgrounded
Oct  6 23:13:53 jessie-test munin-node[463]: 2014/10/06-23:13:53 
Munin::Node::Server (type Net::Server::Fork) starting! pid(463)
Oct  6 23:13:53 jessie-test munin-node[463]: Resolved [*]:4949 to 
[::]:4949, IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Not including resolved host 
[0.0.0.0] IPv4 because it will be handled by [::] IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Binding to TCP port 4949 on 
host :: with IPv6
Oct  6 23:13:53 jessie-test munin-node[463]: Setting gid to "0 0"
Oct  6 23:13:54 jessie-test postfix[414]: Starting Postfix Mail 
Transport Agent: postfix.
Oct  6 23:13:57 jessie-beta rsyslogd: -- MARK --

---snip---

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

From: Michael Biebl <biebl@debian.org>

To: "I. Schrey" <sy@schreyben.de>, 764298@bugs.debian.org

Subject: Re: Bug#764298: "Failed to start Login Service." after upgrade to 215-5+b1

Date: Tue, 07 Oct 2014 01:32:54 +0200

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

Am 07.10.2014 um 01:11 schrieb I. Schrey:
> Oct  6 23:13:53 jessie-test systemd[1]: systemd-logind.service: main
> process exited, code=exited, status=1/FAILURE
> Oct  6 23:13:53 jessie-test systemd[1]: Failed to start Login Service.
> Oct  6 23:13:53 jessie-test systemd[1]: Unit systemd-logind.service
> entered failed state.
> Oct  6 23:13:53 jessie-test systemd[1]: Cannot add dependency job for
> unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such
> file or directory.

You don't have the dbus package installed, which is a recommends of the
systemd package and required by the logind service. See also the
changelog message:


systemd (215-3) experimental; urgency=medium

[...]

  * Make systemd recommend dbus so it is installed on upgrades. The dbus
    system bus is required to run systemd-logind and the autovt feature
relies
    on logind. (Closes: #758111)



I assume you have installation of recommends disabled.
If you install the dbus package, your problem should be gone.


-- 
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 #15 received at 764298@bugs.debian.org (full text, mbox, reply):

From: "I. Schrey" <sy@schreyben.de>

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

Subject: Re: Bug#764298: "Failed to start Login Service." after upgrade to 215-5+b1

Date: Tue, 07 Oct 2014 02:44:10 +0200

Am 07.10.2014 um 01:32 schrieb Michael Biebl:
>
> You don't have the dbus package installed, which is a recommends of the
> systemd package and required by the logind service. See also the
> changelog message:
>
>
> systemd (215-3) experimental; urgency=medium
>
> [...]
>
>    * Make systemd recommend dbus so it is installed on upgrades. The dbus
>      system bus is required to run systemd-logind and the autovt feature
> relies
>      on logind. (Closes: #758111)
>
>
>
> I assume you have installation of recommends disabled.
Yes.

> If you install the dbus package, your problem should be gone.
>

Duh, the changelog. *hides*

'autovt' got me digging, and I ended up disabling the
'systemd-logind.service' by removing the symlink in
/lib/systemd/system/multi-user.target.wants/ -
no more errors on boot.
(if that's not the correct way to disable, don't bother -
I'll figure out tomorrow how to do it properly)

I'd like to keep this system as lean as possible, and
reading the systemd-logind.service manpage suggests
that this system can do without logind (headless).


So case closed I guess.
I'll be back though, if dbus becomes a hard dependency. ;)

Nah, just kidding.

In any case, a big 'Thank you!' for all your Debian related work.

Regards
Ingmar

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

From: Mathieu Parent <math.parent@gmail.com>

To: "I. Schrey" <sy@schreyben.de>, 764298@bugs.debian.org

Subject: How to mask the service

Date: Fri, 24 Oct 2014 16:15:36 +0200

Hello,

I also tried a minimal install, and got the same error.

The proper solution seems to be to mask it:
$ sudo systemctl mask   systemd-logind.service
Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.

Regards
-- 
Mathieu

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

From: Michael Biebl <biebl@debian.org>

To: Mathieu Parent <math.parent@gmail.com>, 764298@bugs.debian.org

Subject: Re: Bug#764298: How to mask the service

Date: Fri, 24 Oct 2014 16:39:26 +0200

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

Am 24.10.2014 um 16:15 schrieb Mathieu Parent:
> Hello,
> 
> I also tried a minimal install, and got the same error.
> 
> The proper solution seems to be to mask it:
> $ sudo systemctl mask   systemd-logind.service
> Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.

Not really. We added a condition to systemd-logind.service to not start
the service if dbus is not installed. If it's started, it means dbus is
installed, but it  failed for other reasons, and you should investigate
that.


-- 
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 #30 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Mathieu Parent <math.parent@gmail.com>

To: Michael Biebl <biebl@debian.org>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: How to mask the service

Date: Fri, 24 Oct 2014 17:14:29 +0200

2014-10-24 16:39 GMT+02:00 Michael Biebl <biebl@debian.org>:

Hello Michael,

> Not really. We added a condition to systemd-logind.service to not start
> the service if dbus is not installed. If it's started, it means dbus is
> installed, but it  failed for other reasons, and you should investigate
> that.

=====================
$ sudo aptitude search dbus~i
(nothing)

=====================
$ sudo systemctl status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
   Active: failed (Result: start-limit) since ven. 2014-10-24 17:06:27
CEST; 58s ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
  Process: 529 ExecStart=/lib/systemd/systemd-logind (code=exited,
status=1/FAILURE)
 Main PID: 529 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

oct. 24 17:06:27 testjessie systemd[1]: systemd-logind.service start
request repeated too quickly, refusing to start.
oct. 24 17:06:27 testjessie systemd[1]: Failed to start Login Service.
oct. 24 17:06:27 testjessie systemd[1]: Unit systemd-logind.service
entered failed state.

=====================
$ cat /lib/systemd/system/systemd-logind.service
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Login Service
Documentation=man:systemd-logind.service(8) man:logind.conf(5)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
Wants=user.slice
After=nss-user-lookup.target user.slice

# Ask for the dbus socket. If running over kdbus, the socket will
# not be actually used.
Wants=dbus.socket
After=dbus.socket

[Service]
ExecStart=/lib/systemd/systemd-logind
Restart=always
RestartSec=0
BusName=org.freedesktop.login1
CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
CAP_SYS_TTY_CONFIG
WatchdogSec=1min

# Increase the default a bit in order to allow many simultaneous
# logins since we keep one fd open per session.
LimitNOFILE=16384

=====================
And side-note: #764298, is not marked as fixed.

I'm using systemd 215-5+b1.

Regards
--
Mathieu

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

From: Michael Biebl <biebl@debian.org>

To: Mathieu Parent <math.parent@gmail.com>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: How to mask the service

Date: Fri, 24 Oct 2014 17:18:42 +0200

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

Am 24.10.2014 um 17:14 schrieb Mathieu Parent:
> 2014-10-24 16:39 GMT+02:00 Michael Biebl <biebl@debian.org>:
> 
> Hello Michael,
> 
>> Not really. We added a condition to systemd-logind.service to not start
>> the service if dbus is not installed. If it's started, it means dbus is
>> installed, but it  failed for other reasons, and you should investigate
>> that.
> 
> =====================
> $ sudo aptitude search dbus~i
> (nothing)
> 
> =====================
> $ sudo systemctl status systemd-logind.service
> ● systemd-logind.service - Login Service
>    Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
>    Active: failed (Result: start-limit) since ven. 2014-10-24 17:06:27
> CEST; 58s ago
>      Docs: man:systemd-logind.service(8)
>            man:logind.conf(5)
>            http://www.freedesktop.org/wiki/Software/systemd/logind
>            http://www.freedesktop.org/wiki/Software/systemd/multiseat
>   Process: 529 ExecStart=/lib/systemd/systemd-logind (code=exited,
> status=1/FAILURE)
>  Main PID: 529 (code=exited, status=1/FAILURE)
>    Status: "Shutting down..."
> 
> oct. 24 17:06:27 testjessie systemd[1]: systemd-logind.service start
> request repeated too quickly, refusing to start.
> oct. 24 17:06:27 testjessie systemd[1]: Failed to start Login Service.
> oct. 24 17:06:27 testjessie systemd[1]: Unit systemd-logind.service
> entered failed state.
> 
> =====================
> $ cat /lib/systemd/system/systemd-logind.service
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
> 
> [Unit]
> Description=Login Service
> Documentation=man:systemd-logind.service(8) man:logind.conf(5)
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
> Wants=user.slice
> After=nss-user-lookup.target user.slice
> 
> # Ask for the dbus socket. If running over kdbus, the socket will
> # not be actually used.
> Wants=dbus.socket
> After=dbus.socket
> 
> [Service]
> ExecStart=/lib/systemd/systemd-logind
> Restart=always
> RestartSec=0
> BusName=org.freedesktop.login1
> CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
> CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
> CAP_SYS_TTY_CONFIG
> WatchdogSec=1min
> 
> # Increase the default a bit in order to allow many simultaneous
> # logins since we keep one fd open per session.
> LimitNOFILE=16384
> 
> =====================
> And side-note: #764298, is not marked as fixed.
> 
> I'm using systemd 215-5+b1.
> 

My bad, we discussed to add that check but haven't released a version
with that condition so far.
The idea is to have ConditionFileIsExecutable=/usr/bin/dbus-daemon
in systemd-logind.service



-- 
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 #40 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Mathieu Parent <math.parent@gmail.com>

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

Cc: Michael D <me@md-5.net>

Subject: Re: Bug#769728: Release Critical?

Date: Sat, 31 Jan 2015 10:15:51 +0100

2015-01-30 23:42 GMT+01:00 Michael Biebl <biebl@debian.org>:
[...]
> Let's bump the severity to RC, just to make sure this remains on the radar.

Shouldn't we bump the severity of #764298 which has a clear solution?

Regards

-- 
Mathieu Parent

Message #51 received at 772700-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 772700-close@bugs.debian.org

Subject: Bug#772700: fixed in systemd 218-8

Date: Mon, 09 Feb 2015 19:08:10 +0000

Source: systemd
Source-Version: 218-8

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 772700@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 09 Feb 2015 18:07:22 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 218-8
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description:
 gir1.2-gudev-1.0 - libgudev-1.0 introspection data
 libgudev-1.0-0 - GObject-based wrapper library for libudev
 libgudev-1.0-dev - libgudev-1.0 development files
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 python3-systemd - Python 3 bindings for systemd
 systemd    - system and service manager
 systemd-dbg - system and service manager (debug symbols)
 systemd-sysv - system and service manager - SysV links
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 772700 777115
Changes:
 systemd (218-8) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * boot-and-services autopkgtest: Ensure that there are no failed units,
     except possibly systemd-modules-load.service (as that notoriously fails
     with cruft in /etc/modules).
   * Revert "input" system group creation in systemd.postinst from 218-7. It's
     already done in udev.postinst.
   * ifup@.service: Revert checking for existance of ifupdown config for that
     interface, net.agent already does that.
   * Drop Also-redirect-to-update-rc.d-when-not-using-.service.patch; not
     necessary any more with the current version (mangle_names() already takes
     care of this).
   * Merge into Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch:
     - Do-not-order-rcS.d-services-after-local-fs.target-if.patch, as it
       partially reverts the above, and is just fixing it.
     - Map-rcS.d-init-script-dependencies-to-their-systemd-.patch as it's just
       adding some missing functionality for the same purpose.
   * Merge Run-update-rc.d-defaults-before-update-rc.d-enable-d.patch into
     Make-systemctl-enable-disable-call-update-rc.d-for-s.patch as the former
     is fixing the latter and is not an independent change.
   * Drop Launch-logind-via-a-shell-wrapper.patch and systemd-logind-launch
     wrapper. The only remaining thing that we need from it is to create
     /run/systemd/, move that into the D-BUS service file directly.
   * /lib/lsb/init-functions.d/40-systemd: Avoid deadlocks during bootup and
     shutdown. DHCP/ifupdown and similar hooks which call "/etc/init.d/foo
     reload" can easily cause deadlocks, since the synchronous wait plus
     systemd's normal behaviour of transactionally processing all dependencies
     first easily causes dependency loops. Thus during boot/shutdown operate
     only on the unit and not on its dependencies, just like SysV behaves.
     (Closes: #777115, LP: #1417010)
   * Only start logind if dbus is installed. This fixes the noisy startup
     failure in environments without dbus, such as LXC containers or servers.
     (part of #772700)
   * Add getty-static.service unit which starts getty@.service on tty 2 to 6 if
     dbus is not installed, and hence logind cannot auto-start them on demand.
     (Closes: #772700)
 .
   [ Michael Biebl ]
   * Update insserv-generator and map $x-display-manager to
     display-manager.service, following the recent change in sysv-generator.
     This avoids creating references to a no longer existing
     x-display-manager.target unit.
Checksums-Sha1:
 cb8436e8849ce7d18bbeb32548b9a86299bc6571 3838 systemd_218-8.dsc
 c1031af03d59ae040cde02273c201d672a34ff05 136292 systemd_218-8.debian.tar.xz
 4ca9529c65c6fdda4c329df24ba6dde15f77e2b4 3113700 systemd_218-8_amd64.deb
 c68a67586ab849742f2c2db4696d4310a5ea4d0a 36126 systemd-sysv_218-8_amd64.deb
 c2bb1070f793b21dec476f70f4cd71f3dfe868be 133586 libpam-systemd_218-8_amd64.deb
 6a415054d89e95913b2b2a42fa3ae6c10e11c5f4 94850 libsystemd0_218-8_amd64.deb
 0076a1fe6d5cf382248b9dc8c3b9542924b4d38f 96670 libsystemd-dev_218-8_amd64.deb
 5b04d21a92150a8cd50464c0b6cdfb6ed50746f0 31744 libsystemd-login-dev_218-8_amd64.deb
 6b84a307c13b0fc3dfcbf4e86fce8e8f72c5afc9 31748 libsystemd-daemon-dev_218-8_amd64.deb
 9510795af7c69bacbe869da8505a401f72b383f1 31724 libsystemd-journal-dev_218-8_amd64.deb
 af9868b430b4b9bf55ef58c214d5bcca5b5c2e2e 31718 libsystemd-id128-dev_218-8_amd64.deb
 4a8b0b81b85f1966b638dd8371e43657c1743a2e 920390 udev_218-8_amd64.deb
 6fde2226e08f2480f985c47d133023c58f9c33d6 58876 libudev1_218-8_amd64.deb
 71d827bb3f2ac6c7f3e72e03284a3057c73192c0 22966 libudev-dev_218-8_amd64.deb
 7a0f07dbd9b6d62480e5baaa35d34c5b2ed72c34 225670 udev-udeb_218-8_amd64.udeb
 2b4e4576c84b941c4166725c4d4fb985a9608c94 26546 libudev1-udeb_218-8_amd64.udeb
 20d051849cb6304970881157ddebb4a86938789f 42028 libgudev-1.0-0_218-8_amd64.deb
 69548547dbe134ad97f569c34ad0b05a35072167 2826 gir1.2-gudev-1.0_218-8_amd64.deb
 b691ce4c80d5a4f300205a912a4db20470b8b416 24474 libgudev-1.0-dev_218-8_amd64.deb
 23240d94fd9a615ee85a6278757a07aa9370f64d 61736 python3-systemd_218-8_amd64.deb
 b267cf35c19d094648c73844160fc325d8ce9621 20368558 systemd-dbg_218-8_amd64.deb
Checksums-Sha256:
 061826532282a45615e761b5893da9bd60c5401c35a956426555560928c1044f 3838 systemd_218-8.dsc
 da6ba7a6cdec14b2e3e5de6ce7437cfb0f2e19092d5c6b461d3dba14352ca0c0 136292 systemd_218-8.debian.tar.xz
 5a95215f0a47c091ddf33308cb235d4879c781d02c0c25d7bf8cfd77e915cce6 3113700 systemd_218-8_amd64.deb
 f748f07bb1c2a261037ca1d517c058adb46f9e5ed34dfb46e826ae234d331419 36126 systemd-sysv_218-8_amd64.deb
 49243fb149395d327b4c49851357ad4be2b2f70aa663597b682169825b0e3cf4 133586 libpam-systemd_218-8_amd64.deb
 1cbe6f63bd90ae25424385adbe590934848fa0efea519c0e424bee402bdbf42c 94850 libsystemd0_218-8_amd64.deb
 962abe1844d12c02182d62b50626d7ad178879b28155051891588e33de18938f 96670 libsystemd-dev_218-8_amd64.deb
 0b43ef653e4a328fdc385f48d2927ff0ad3261772fd3e30f66cbda21171e6f85 31744 libsystemd-login-dev_218-8_amd64.deb
 810158e34179b0dc77af3ed5659eb5d4181ad3c26b6524d876e6f04bad45b56e 31748 libsystemd-daemon-dev_218-8_amd64.deb
 77c093a07cbfe7fcbf422babd2aeee81c5974e7e816338359c5a9045a9b10fac 31724 libsystemd-journal-dev_218-8_amd64.deb
 ab3bae6b6ec9465df69dac4d6d870ece39d559fdc800aebddaf12fd3546471ee 31718 libsystemd-id128-dev_218-8_amd64.deb
 b56a1bca9ac48d0b523171165595a6f24ada1c8863c46db4a414f8f3b714fd08 920390 udev_218-8_amd64.deb
 a2299b0c2531b1458b68767e3d4a5962c795ff3ef8d0fc193b61d21ae7f271a5 58876 libudev1_218-8_amd64.deb
 3720b6142a198c69b2d442c33c3bf9a0beabe6fb22a6264553483f7636b01c20 22966 libudev-dev_218-8_amd64.deb
 77d13a61cd5aaa000a266f741f1f64081481b0b936b756c7901d86803f96d62e 225670 udev-udeb_218-8_amd64.udeb
 ab8a78fa1c354b8a198a0693b54c795c106a2b0f96fa4dee451195a1b5f6f7b2 26546 libudev1-udeb_218-8_amd64.udeb
 9b8b92446f1f0a8af098960ebddc72e5a70977dd98084c85ecd751c7c5e7b694 42028 libgudev-1.0-0_218-8_amd64.deb
 ff27a0face64bd95934c2b462ade93897a0b0c0e7253b5dbbd85efd887c1884c 2826 gir1.2-gudev-1.0_218-8_amd64.deb
 773cf244627d0041c927284564047bd94ca69c0dc6e587cb58935d06e5c7ce0a 24474 libgudev-1.0-dev_218-8_amd64.deb
 a4f6fc5c2da912a59d4cc3bcef6965f32de123cf1647b171519dbaeb05bf2003 61736 python3-systemd_218-8_amd64.deb
 62b1e4b26147fdd659b2133dc98fce6b7361e578412d4f49c45aec686f98a2ff 20368558 systemd-dbg_218-8_amd64.deb
Files:
 55300afb7986a9432041e9149360f89f 3838 admin optional systemd_218-8.dsc
 84f30bf3f4fa46254ba14b34ebe1ccae 136292 admin optional systemd_218-8.debian.tar.xz
 b8991638104e6c9b9ed5fba0ff98dadb 3113700 admin optional systemd_218-8_amd64.deb
 267ec602ee4976fd86dcc08ab702b5bf 36126 admin extra systemd-sysv_218-8_amd64.deb
 a25bcc433890fdf8aa65ee8fc4ad8dd1 133586 admin optional libpam-systemd_218-8_amd64.deb
 1a655c6e17493594d41fd6e938aa8103 94850 libs optional libsystemd0_218-8_amd64.deb
 d95e85ba5e36f6d7bd8d56dd3425da9a 96670 libdevel optional libsystemd-dev_218-8_amd64.deb
 aa48e110eb8f4de5db7a6a2465c66ab9 31744 oldlibs extra libsystemd-login-dev_218-8_amd64.deb
 f50877b2f428b45cfd027ec1daa7e455 31748 oldlibs extra libsystemd-daemon-dev_218-8_amd64.deb
 18741a54fd1e81d9c505d478766602b3 31724 oldlibs extra libsystemd-journal-dev_218-8_amd64.deb
 557d868e4d1cee4f3e11ea74ea48f268 31718 oldlibs extra libsystemd-id128-dev_218-8_amd64.deb
 68a7e28fe0b34171d549f4376eb47431 920390 admin important udev_218-8_amd64.deb
 c93cf3b14d0b18f0055f23337a0b80ac 58876 libs important libudev1_218-8_amd64.deb
 1b631e10cb2e7091379ad0de914c62af 22966 libdevel optional libudev-dev_218-8_amd64.deb
 ee046043e82752dabcc5f7843dbbc02d 225670 debian-installer optional udev-udeb_218-8_amd64.udeb
 421becb6d1ccd79f9a3ba945ed1d151b 26546 debian-installer optional libudev1-udeb_218-8_amd64.udeb
 c80f3bc459d21177675e36ebe6f12966 42028 libs optional libgudev-1.0-0_218-8_amd64.deb
 14eb285019b8b7425e2574ad9ff74032 2826 introspection optional gir1.2-gudev-1.0_218-8_amd64.deb
 256483eeac7581d51a3fa581cb4f3781 24474 libdevel optional libgudev-1.0-dev_218-8_amd64.deb
 7e701af8777ea0d899ad7d80cfa3ec67 61736 python optional python3-systemd_218-8_amd64.deb
 f38e3e20d84b681a85b0bf1e02cdb17e 20368558 debug extra systemd-dbg_218-8_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU2OyxAAoJENFO8V2v4RNHb+gP/iqDea6IdbfWGnFkM6eueRwI
8eJhWduEE8c1mt8GhIV/3aeQNNHXWBj40ozRTgjU0gc9zTXPd14F5irImeDLhXDf
eLlgfiDKx++r+eVTUAMSwSV/bAX8GRMf85PfZtrdURUYmLuXq6fdZEVQi2+Kinx3
NmlfNJX5jh5urG3erol3SlXeTD4dwRefRk62svHyvSV57lc7LEVi7uuH5wmPX4W1
0G6cko6wsgdcoVxhgpogCaLWrlQMo5yZzd9iLkaQ1BjT65SZdo9Uu/1++GNY0Ysc
qBGvwmqNjK5LbCGfihU0CzJGi+xP3c2qRG61QsveDoz2Jr5PEJz7iH3rd3WuhAuZ
IPZbxpc2JFx0jHm0zBDBWi7XGAsuFOnCIj3GKk5RLX+9OSqZcfO/20n6Bi/3AMcO
5Af9AKeo1KLMx6wEk7GUA7nRA10ykU3Us9fHkSZdtKqKvCQIQ/R9dgrvHEea7dRJ
oBngk486YOgHRhyoylKt3pYspn6ZVjYkzfVfB1AXoskfmhX0R9gTPhqguaK/kkXx
Y6XtpnJgKt9khZrgGSC/UB1NyDqsIKGyQbkdDyGc0kgUb4pmMVWJ3Iq78J5BxEl2
1+W1V0HiGSttFNxi5XJ2vNmQWHxd3d1YN21DKF4d+ARwFdQZz8GF/4qnYJIho3RE
oryKlNdvaNYTCn/pXXX4
=G1h4
-----END PGP SIGNATURE-----

Message #52 received at 772700-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 772700-close@bugs.debian.org

Subject: Bug#772700: fixed in systemd 215-12

Date: Fri, 13 Feb 2015 11:34:11 +0000

Source: systemd
Source-Version: 215-12

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 772700@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 13 Feb 2015 12:08:31 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 215-12
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description:
 gir1.2-gudev-1.0 - libgudev-1.0 introspection data
 libgudev-1.0-0 - GObject-based wrapper library for libudev
 libgudev-1.0-dev - libgudev-1.0 development files
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-daemon0 - systemd utility library (deprecated)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated)
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-journal0 - systemd journal utility library (deprecated)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd-login0 - systemd login utility library (deprecated)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 python3-systemd - Python 3 bindings for systemd
 systemd    - system and service manager
 systemd-dbg - system and service manager (debug symbols)
 systemd-sysv - system and service manager - SysV links
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 759320 767267 772700 776546 777601
Changes:
 systemd (215-12) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * debian/udev.README.Debian: Trim the parts which are obsolete, wrong, or
     described in manpages. Only keep the Debian specific bits.
     (Part of #776546)
   * Actually install udev's README.Debian when building for Debian.
     (Closes: #776546)
   * Only start logind if dbus is installed. This fixes the noisy startup
     failure in environments without dbus such as LXC containers or servers.
     (part of #772700)
   * Add getty-static.service unit which starts getty@.service on tty 2 to 6 if
     dbus is not installed, and hence logind cannot auto-start them on demand.
     (Closes: #772700)
   * Add unit-config autopkgtest to check systemd unit/sysv init enabling and
     disabling via systemctl. This avoids bugs like #777613 (did not affect
     unstable).
   * cgroup: Don't trim cgroup trees created by someone else, just the ones
     that systemd itself created. This avoids cleaning up empty cgroups from
     e.g. LXC. (Closes: #777601)
   * boot-and-services autopkgtest: Add CgroupsTest to check cgroup
     creation/cleanup behaviour. This reproduces #777601 and verifies the fix
     for it.
   * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids
     kernel buffer I/O errors and timeouts. (LP: #1333140)
   * Document systemctl --failed option. (Closes: #767267)
 .
   [ Michael Biebl ]
   * core: Don't fail to run services in --user instances if $HOME is missing.
     (Closes: #759320)
 .
   [ Didier Roche ]
   * default-display-manager-generator: Avoid unnecessary /dev/null symlink and
     warning if there is no display-manager.service unit.
Checksums-Sha1:
 1b08b6b62484622cac91195ae9c2caf1ca5cc03a 4107 systemd_215-12.dsc
 8cd669cd4e7307850a0f3fc6871b31fc492ae91e 195008 systemd_215-12.debian.tar.xz
 cc0fd4b7a9daf0baa79df9a0e2240ea4a3ed2b3c 2535716 systemd_215-12_amd64.deb
 f6e7ed5ceefa109c965f0b1f6fd864eed7ebd8a1 32652 systemd-sysv_215-12_amd64.deb
 bf23d7e7df0725f8aeccf3b0e59c6990b5e3590b 121920 libpam-systemd_215-12_amd64.deb
 2bf33aaafc3f3022949ea03f6c64b34882eda637 85382 libsystemd0_215-12_amd64.deb
 335784b9867561dc6d5a8b3dafbbdc9a5ce2ff22 91572 libsystemd-dev_215-12_amd64.deb
 fb6220ccc290498f1aedd1d79d29db9c81bb6590 45742 libsystemd-login0_215-12_amd64.deb
 546b90e2e78cb298f545b6bde3df1bb593591a90 28238 libsystemd-login-dev_215-12_amd64.deb
 bc46e772b17e19f749af7f2cd7a4d4b13b40e9de 34852 libsystemd-daemon0_215-12_amd64.deb
 e1e5d150ba2123121be255b9071e6e04f65da288 28252 libsystemd-daemon-dev_215-12_amd64.deb
 b3495d216ec16e145d0e143bb9242ba99259fe0c 70964 libsystemd-journal0_215-12_amd64.deb
 8c8dadbe409d0f5552efea84658e9fb8b369765f 28234 libsystemd-journal-dev_215-12_amd64.deb
 4d6a1840d917ea5d76ca24dad8e62652faa3f102 33810 libsystemd-id128-0_215-12_amd64.deb
 73c59cca9a3ad4dc4b2bb2580968ce43607123bd 28226 libsystemd-id128-dev_215-12_amd64.deb
 9b7a2b6c9576202aed425c435dce4971c55ffee5 872820 udev_215-12_amd64.deb
 13a49101e4d18dbfec09b23e1402f81b9d3d9b28 53746 libudev1_215-12_amd64.deb
 17e685989d27e346afd857d18d23ec61cae3032b 23100 libudev-dev_215-12_amd64.deb
 0dc5cd4108fb213e7cdbe3ae2690484509ba5cac 195012 udev-udeb_215-12_amd64.udeb
 895675fea0a44fa0b453e949e6987adf16e97afd 24734 libudev1-udeb_215-12_amd64.udeb
 185807f30a3916175aa0c287ab4411523e7bb9b3 38544 libgudev-1.0-0_215-12_amd64.deb
 130695acc7cc383b317da5c6f41b8377d5b00ce0 2828 gir1.2-gudev-1.0_215-12_amd64.deb
 968192f9590e86b79efcd09e17b1b09603b24edc 24486 libgudev-1.0-dev_215-12_amd64.deb
 8887d359c2fb772cfc7b9a02d71db65834647dbf 58080 python3-systemd_215-12_amd64.deb
 b426b32f4b77da5ecf72d9e78cc0eef5f4a19c0e 15919764 systemd-dbg_215-12_amd64.deb
Checksums-Sha256:
 e31d7b5f8aaaf3b4345d2cfe8a4f2410a909a24e5e0d2e171ade8a68f8d7a33d 4107 systemd_215-12.dsc
 978bb65a4d91544cc7787080f9c7e3bd3a667649cf04b2f67ae8b325688064d7 195008 systemd_215-12.debian.tar.xz
 7144d85d694b99b8e942915a8e4a7508f64cda2cf4b4be360d969c74244346d0 2535716 systemd_215-12_amd64.deb
 32387909655e34935d23f2b3956d4c3bb861b787b301a2a581abc795a709f7c8 32652 systemd-sysv_215-12_amd64.deb
 1d1871d60d714ec7ae63d7a73ff4b3788b3d97d485ca1db3a603d85b4bcddf57 121920 libpam-systemd_215-12_amd64.deb
 f1d10620f2548965d3d80890da216d685f6973b168fcdfeba287e1e6e7652bab 85382 libsystemd0_215-12_amd64.deb
 3a662c612c12239c561bdc1046a2a1db383137d22e994d167c93ea7dbedf19a5 91572 libsystemd-dev_215-12_amd64.deb
 4163d0726603df191b42ccfc292409b8c4dfd100101d0945e8c0ae2fe709dcf3 45742 libsystemd-login0_215-12_amd64.deb
 70d4a3bf81cca9b16225c5536f9e23facfb11b416574c89d36e1dfd77f5b8395 28238 libsystemd-login-dev_215-12_amd64.deb
 46ebea227ca993211c11472a42d16da036e71bb4abb28ff77c3a08f7ccb24f3e 34852 libsystemd-daemon0_215-12_amd64.deb
 71270c1f77221530c681f7b7d97dcd18d5bbfd19deb3fdff003e9c99a9ce451e 28252 libsystemd-daemon-dev_215-12_amd64.deb
 59d1e0c0eabd1cfc3dd8029ab0a4ac58ad2c1893bd9fe0644507890c7b47aa56 70964 libsystemd-journal0_215-12_amd64.deb
 33e9058aee26823b191e509ac29d4a84c80b89885dcd518e8520a47f94993957 28234 libsystemd-journal-dev_215-12_amd64.deb
 8b5df234294d98f7cab5d6612ba2d3aa31bdd4333583265492a927a79c437022 33810 libsystemd-id128-0_215-12_amd64.deb
 312b8838b86a70816a0ab2e86c1120c04ee66e908b638fffbbdd45489f36d689 28226 libsystemd-id128-dev_215-12_amd64.deb
 aa55009b90ce5dd6884a0c1db6cb2780e5eb678f9ae58d66f15dbc6fb14ee0d9 872820 udev_215-12_amd64.deb
 50120503ead88592c0025e994002624439b961c03ba839d92b69ad0fa9ef3b6a 53746 libudev1_215-12_amd64.deb
 5e3eb375dc804ffb34b642048aed6a8d4ac0e16bead7ea84d8850a81d41faf09 23100 libudev-dev_215-12_amd64.deb
 13a35a22b2ab8a54e9e3710bffb12d18ad4f139996d7ea744ba301a81a3b0bdb 195012 udev-udeb_215-12_amd64.udeb
 1dabbd89c482adef4d0513f966628a1b4311643b93b7b763f85318f1dfacf4c9 24734 libudev1-udeb_215-12_amd64.udeb
 461a06b650bbdf3405a5125fd5e9132b798bed0d3b106d094bff870631ec4c78 38544 libgudev-1.0-0_215-12_amd64.deb
 2ba2fa71121204ec7a10b59d91abe211c2c551b443f077d4059004a47ab5a0a6 2828 gir1.2-gudev-1.0_215-12_amd64.deb
 9eea91febd58c322d053f566f013934a5c71f712d502fc773fe9c0fe8ceaefc7 24486 libgudev-1.0-dev_215-12_amd64.deb
 518e39c69ed70424aaf4e4206c6f0d41cd6df4e8f22ee41440e464d5b0614788 58080 python3-systemd_215-12_amd64.deb
 918f4a5fe68c3c46659e48c1097dbf8292578e2972e30e9baa01c9a6f76f8a7b 15919764 systemd-dbg_215-12_amd64.deb
Files:
 b80f8d8efb5d9229244c57607009d4c0 4107 admin optional systemd_215-12.dsc
 3f436d80b82e116892090108c7eeab96 195008 admin optional systemd_215-12.debian.tar.xz
 0ed89080727a9232be559f5a6f3661ee 2535716 admin optional systemd_215-12_amd64.deb
 5d1562dfbad9c9516d9bc758d16fbf28 32652 admin extra systemd-sysv_215-12_amd64.deb
 9b4f6f3f92c182fa718d7e4f8a2405be 121920 admin optional libpam-systemd_215-12_amd64.deb
 b712aebe9ba9b804a7faae876ee94efc 85382 libs optional libsystemd0_215-12_amd64.deb
 ed1fb58c435ff43f792217e2f38bb0b2 91572 libdevel optional libsystemd-dev_215-12_amd64.deb
 d1ba5e35f2b7a9a84ad8634f5b328536 45742 oldlibs extra libsystemd-login0_215-12_amd64.deb
 eabff19c5effe461cd83cb46539b33a7 28238 oldlibs extra libsystemd-login-dev_215-12_amd64.deb
 991957e3e035d0fdce45d5771a2976e4 34852 oldlibs extra libsystemd-daemon0_215-12_amd64.deb
 0bde7279650afdae6cdd08e0c5de5041 28252 oldlibs extra libsystemd-daemon-dev_215-12_amd64.deb
 15fe237af6d2ad804259409cba551762 70964 oldlibs extra libsystemd-journal0_215-12_amd64.deb
 dd85e5f68ac1f17a370e1c035a5d5f77 28234 oldlibs extra libsystemd-journal-dev_215-12_amd64.deb
 97e495bb4711b0188a465da9acc279be 33810 oldlibs extra libsystemd-id128-0_215-12_amd64.deb
 4f66192a449ad70607e13e9ac193e938 28226 oldlibs extra libsystemd-id128-dev_215-12_amd64.deb
 31c972de43f420863937878c0186ed6a 872820 admin important udev_215-12_amd64.deb
 6e8570977f9246bf7a0e7fce3e332063 53746 libs important libudev1_215-12_amd64.deb
 ad7b307321e88e7c750957a1efb7f312 23100 libdevel optional libudev-dev_215-12_amd64.deb
 aac34a60bdf745ede5a46d6e3eb56d5a 195012 debian-installer optional udev-udeb_215-12_amd64.udeb
 e4549dd4e440ccd2bbf6058270a8f5d8 24734 debian-installer optional libudev1-udeb_215-12_amd64.udeb
 a47cb2cae0f2b1d2580c8257502dc780 38544 libs optional libgudev-1.0-0_215-12_amd64.deb
 62dcdd6c57d90b65324e01afb61ffec7 2828 introspection optional gir1.2-gudev-1.0_215-12_amd64.deb
 2d05402b2b6c808f8e0394ec0678ac54 24486 libdevel optional libgudev-1.0-dev_215-12_amd64.deb
 0cce32b548432efa8621d9af6b704dca 58080 python optional python3-systemd_215-12_amd64.deb
 0e7c133f226cde61b103766b2b578fd9 15919764 debug extra systemd-dbg_215-12_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU3d6jAAoJENFO8V2v4RNHqR0P/1fNNrAKOUx1hsbBRPvCKBGb
cw+OCLCzi38JwbB/crjz5yaNzjd7KWt84maV1f/tiYaIHCTGZW1Gs3cD5Yov1tlA
+i2In8hXE9qZ70FVGjr/wrC8niyK/uSdQBO+sKT9HyhnLbvfnHhY1/WeJNw1U6n3
Q+qzN0W5LnFmiKm7Wq+XsOGJyyFPmqkL0nuTfRHXulhw5j/JgDtVDL9Im5b+x0Dq
3Lk7fzbLnUi5vVdkbHNlgUAGYgj4H/VbMsHYldXjHtAHck6Mz+/Yuj4Tu6WnrQuM
esQKGDwfk3reReDfOO8bFLbwCxmac+XJmA8Hahp1LfwZZdcg5INzLf7CjlII9SQM
Dh5FVUPrRC9nzZJLWB4kC9wRnMega99I9qgYjlawwBWNY4pCnSRaZ1VBIloD1RmC
iWHplqu8K2GeMA6X6Gal7dV5uD0bIjw9yrBpbBSy6wT2vz19TUpqYdOO5ROdf/8I
0gQX24Z/RCypVJ62XsyBCQHFOzu/P070BZdOe6banWkYV5aIXYV9drAgp0tm1ETa
bog8FrWqZbEB77eCFifOZsUAJBSysUCVspRBoNtieaWnVmKEO+FdhirTkooGZUiv
CJN1G1rx74kF8fry4T+bhhRUaeDu3JbXuSu5ecihp5JoSkmu2BW1X1Nqis3OAP7t
mwHgM4Cx2+NvP5ees+hg
=PVYV
-----END PGP SIGNATURE-----

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

From: Daurnimator <quae@daurnimator.com>

To: 764298@bugs.debian.org

Subject: Still an issue

Date: Tue, 3 Mar 2015 18:19:48 -0500

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

I just installed a fresh systemd (via amazon AMI:
https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd
215-12
I still got the log message:

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to
system bus: No such file or directory
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main
process exited, code=exited, status=1/FAILURE
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service
entered failed state.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no
holdoff time, scheduling restart.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...

(and then again a few times)

[Message part 2 (text/html, inline)]

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

From: Daurnimator <quae@daurnimator.com>

To: Michael Biebl <biebl@debian.org>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Tue, 3 Mar 2015 18:37:47 -0500

On 3 March 2015 at 18:35, Michael Biebl <biebl@debian.org> wrote:
>
> What's the output of
> systemctl status dbus.service dbus.socket?


I do not have dbus installed.

$ sudo systemctl status dbus.service
● dbus.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)


$ sudo systemctl status dbus.socket
● dbus.socket
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.
Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Cannot add dependency job
for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No
such file or directory.

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

From: Michael Biebl <biebl@debian.org>

To: Daurnimator <quae@daurnimator.com>, 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Wed, 04 Mar 2015 00:42:20 +0100

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

Am 04.03.2015 um 00:37 schrieb Daurnimator:
> On 3 March 2015 at 18:35, Michael Biebl <biebl@debian.org> wrote:
>>
>> What's the output of
>> systemctl status dbus.service dbus.socket?
> 
> 
> I do not have dbus installed.
> 
> $ sudo systemctl status dbus.service
> ● dbus.service
>    Loaded: not-found (Reason: No such file or directory)
>    Active: inactive (dead)
> 
> 
> $ sudo systemctl status dbus.socket
> ● dbus.socket
>    Loaded: not-found (Reason: No such file or directory)
>    Active: inactive (dead)
> 

What's the output of
systemctl cat systemd-logind.service
systemctl status systemd-logind.service


-- 
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 #72 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Daurnimator <quae@daurnimator.com>, 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Wed, 04 Mar 2015 00:35:14 +0100

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

Am 04.03.2015 um 00:19 schrieb Daurnimator:
> I just installed a fresh systemd (via amazon AMI:
> https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd
> 215-12
> I still got the log message:
> 
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to
> system bus: No such file or directory
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main
> process exited, code=exited, status=1/FAILURE
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service
> entered failed state.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no
> holdoff time, scheduling restart.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
> 
> (and then again a few times)
> 

What's the output of
systemctl status dbus.service dbus.socket?

-- 
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 #77 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Daurnimator <quae@daurnimator.com>

To: Michael Biebl <biebl@debian.org>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Tue, 3 Mar 2015 19:07:18 -0500

On 3 March 2015 at 18:42, Michael Biebl <biebl@debian.org> wrote:
> What's the output of
> systemctl cat systemd-logind.service
> systemctl status systemd-logind.service

$ sudo systemctl cat systemd-logind.service
# /lib/systemd/system/systemd-logind.service
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Login Service
Documentation=man:systemd-logind.service(8) man:logind.conf(5)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
Wants=user.slice
After=nss-user-lookup.target user.slice
ConditionPathExists=/lib/systemd/system/dbus.service

# Ask for the dbus socket. If running over kdbus, the socket will
# not be actually used.
Wants=dbus.socket
After=dbus.socket

[Service]
ExecStart=/lib/systemd/systemd-logind
Restart=always
RestartSec=0
BusName=org.freedesktop.login1
CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
CAP_SYS_TTY_CONFIG
WatchdogSec=1min

# Increase the default a bit in order to allow many simultaneous
# logins since we keep one fd open per session.
LimitNOFILE=16384


$ sudo systemctl status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
   Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56
UTC; 4h 3min ago
           start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 341 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
has no holdoff time, scheduling restart.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
start request repeated too quickly, refusing to start.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit
systemd-logind.service entered failed state.
Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service.
Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service.

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

From: Michael Biebl <biebl@debian.org>

To: Daurnimator <quae@daurnimator.com>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Wed, 04 Mar 2015 01:34:16 +0100

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

Am 04.03.2015 um 01:07 schrieb Daurnimator:
> On 3 March 2015 at 18:42, Michael Biebl <biebl@debian.org> wrote:
>> What's the output of
>> systemctl cat systemd-logind.service
>> systemctl status systemd-logind.service
> 
> $ sudo systemctl cat systemd-logind.service
> # /lib/systemd/system/systemd-logind.service
> #  This file is part of systemd.
> #
> #  systemd is free software; you can redistribute it and/or modify it
> #  under the terms of the GNU Lesser General Public License as published by
> #  the Free Software Foundation; either version 2.1 of the License, or
> #  (at your option) any later version.
> 
> [Unit]
> Description=Login Service
> Documentation=man:systemd-logind.service(8) man:logind.conf(5)
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind
> Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat
> Wants=user.slice
> After=nss-user-lookup.target user.slice
> ConditionPathExists=/lib/systemd/system/dbus.service

That looks ok.

> # Ask for the dbus socket. If running over kdbus, the socket will
> # not be actually used.
> Wants=dbus.socket
> After=dbus.socket
> 
> [Service]
> ExecStart=/lib/systemd/systemd-logind
> Restart=always
> RestartSec=0
> BusName=org.freedesktop.login1
> CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN
> CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER
> CAP_SYS_TTY_CONFIG
> WatchdogSec=1min
> 
> # Increase the default a bit in order to allow many simultaneous
> # logins since we keep one fd open per session.
> LimitNOFILE=16384
> 
> 
> $ sudo systemctl status systemd-logind.service
> ● systemd-logind.service - Login Service
>    Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
>    Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56
> UTC; 4h 3min ago
>            start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago
>      Docs: man:systemd-logind.service(8)
>            man:logind.conf(5)
>            http://www.freedesktop.org/wiki/Software/systemd/logind
>            http://www.freedesktop.org/wiki/Software/systemd/multiseat
>  Main PID: 341 (code=exited, status=1/FAILURE)
>    Status: "Shutting down..."
> 
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
> has no holdoff time, scheduling restart.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service...
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service
> start request repeated too quickly, refusing to start.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service.
> Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit
> systemd-logind.service entered failed state.
> Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service.
> Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service.

Did you dist-upgrade the VM and those failures are from before the upgrade?
Can you attach your /var/log/dpkg.log

Is the problem reproducible after a reboot?

Fwiw, I can't reproduce the problem in a VM without dbus installed, so
we need to find what's special in your case.

-- 
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 #87 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Daurnimator <quae@daurnimator.com>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Wed, 04 Mar 2015 02:13:18 +0100

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

Am 04.03.2015 um 01:34 schrieb Michael Biebl:
> Am 04.03.2015 um 01:07 schrieb Daurnimator:
> Did you dist-upgrade the VM and those failures are from before the upgrade?
> Can you attach your /var/log/dpkg.log

The reason why I'm asking is, that the fixed version 215-12 migrated to
testing on 2015-02-28.
The latest AMI according to [1] is from 20150213, so it can't have
215-12 yet. So this looks like the VM was upgraded and the error
messages are from before the upgrade when systemd < 215-12 was installed.

[1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie
-- 
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 #92 received at 764298@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 764298@bugs.debian.org

Cc: Daurnimator <quae@daurnimator.com>

Subject: Re: Bug#764298: Still an issue

Date: Wed, 04 Mar 2015 01:45:52 +0000

Am 2015-03-04 01:13, schrieb Michael Biebl:
> Am 04.03.2015 um 01:34 schrieb Michael Biebl:
>> Am 04.03.2015 um 01:07 schrieb Daurnimator:
>> Did you dist-upgrade the VM and those failures are from before the 
>> upgrade?
>> Can you attach your /var/log/dpkg.log
> 
> The reason why I'm asking is, that the fixed version 215-12 migrated to
> testing on 2015-02-28.
> The latest AMI according to [1] is from 20150213, so it can't have
> 215-12 yet. So this looks like the VM was upgraded and the error
> messages are from before the upgrade when systemd < 215-12 was 
> installed.
> 
> [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie

Just double checked: The latest AMI provided by Debian ships 215-11.
So, if you have 215-12 installed, this means the VM was upgraded after 
the VM was instantiated and booted and the error messages you see are 
most likely from 215-11, which does not ship the fix yet.

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

From: Daurnimator <quae@daurnimator.com>

To: Michael Biebl <biebl@debian.org>

Cc: 764298@bugs.debian.org

Subject: Re: Bug#764298: Still an issue

Date: Wed, 4 Mar 2015 11:31:03 -0500

On 3 March 2015 at 20:45, Michael Biebl <biebl@debian.org> wrote:
> Am 2015-03-04 01:13, schrieb Michael Biebl:
>>
>> Am 04.03.2015 um 01:34 schrieb Michael Biebl:
>>>
>>> Am 04.03.2015 um 01:07 schrieb Daurnimator:
>>> Did you dist-upgrade the VM and those failures are from before the
>>> upgrade?
>>> Can you attach your /var/log/dpkg.log
>>
>>
>> The reason why I'm asking is, that the fixed version 215-12 migrated to
>> testing on 2015-02-28.
>> The latest AMI according to [1] is from 20150213, so it can't have
>> 215-12 yet. So this looks like the VM was upgraded and the error
>> messages are from before the upgrade when systemd < 215-12 was installed.
>>
>> [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie
>
>
> Just double checked: The latest AMI provided by Debian ships 215-11.
> So, if you have 215-12 installed, this means the VM was upgraded after the
> VM was instantiated and booted and the error messages you see are most
> likely from 215-11, which does not ship the fix yet.

Ah ha!
It appears something along the way upgraded systemd without me knowing.
I just rebooted the system and everything seems to be fine now :)

dpkg.log contains:

2015-03-03 20:57:32 upgrade libsystemd0:amd64 215-11 215-12
2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-11
2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-11
2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11
2015-03-03 20:57:32 status half-installed libsystemd0:amd64 215-11
2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12
2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12
2015-03-03 20:57:32 configure libsystemd0:amd64 215-12 <none>
2015-03-03 20:57:32 status unpacked libsystemd0:amd64 215-12
2015-03-03 20:57:32 status half-configured libsystemd0:amd64 215-12
2015-03-03 20:57:32 status installed libsystemd0:amd64 215-12
2015-03-03 20:57:32 upgrade systemd:amd64 215-11 215-12
2015-03-03 20:57:32 status half-configured systemd:amd64 215-11
2015-03-03 20:57:32 status unpacked systemd:amd64 215-11
2015-03-03 20:57:32 status half-installed systemd:amd64 215-11
2015-03-03 20:57:33 status half-installed systemd:amd64 215-11
2015-03-03 20:57:33 status unpacked systemd:amd64 215-12
2015-03-03 20:57:33 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 configure systemd:amd64 215-12 <none>
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd:amd64 215-12
2015-03-03 20:57:34 status half-configured systemd:amd64 215-12
2015-03-03 20:57:34 status installed systemd:amd64 215-12
2015-03-03 20:57:34 upgrade systemd-sysv:amd64 215-11 215-12
2015-03-03 20:57:34 status half-configured systemd-sysv:amd64 215-11
2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-11
2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11
2015-03-03 20:57:34 status half-installed systemd-sysv:amd64 215-11
2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12
2015-03-03 20:57:34 status unpacked systemd-sysv:amd64 215-12
2015-03-03 20:57:35 configure systemd-sysv:amd64 215-12 <none>
2015-03-03 20:57:35 status unpacked systemd-sysv:amd64 215-12
2015-03-03 20:57:35 status half-configured systemd-sysv:amd64 215-12
2015-03-03 20:57:35 status installed systemd-sysv:amd64 215-12

Send a report that this bug log contains spam.