systemd-logind crashed with SIGABRT

[wolf hesse]

rogera@ubi64:~$ lsb_release -rd
Description: Ubuntu Wily Werewolf (development branch)
Release: 15.10

rogera@ubi64:~$ apt-cache policy systemd
systemd:
  Installed: 225-1ubuntu4
  Candidate: 225-1ubuntu4
  Version table:
 *** 225-1ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
Date: Fri Sep 25 12:45:30 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2014-06-30 (454 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 1709CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /lib/systemd/systemd-logind
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=4cbe9c84-d808-45ed-9e3e-b24c44ee3e24 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGABRT
UpgradeStatus: Upgraded to wily on 2015-08-05 (54 days ago)
UserGroups:

dmi.bios.date: 10/04/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 7BETD3WW (2.14 )
dmi.board.name: 1709CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7BETD3WW(2.14):bd10/04/2007:svnLENOVO:pn1709CTO:pvrThinkPadX60:rvnLENOVO:rn1709CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1709CTO
dmi.product.version: ThinkPad X60
dmi.sys.vendor: LENOVO

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1429544, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.