systemd-logind crashed with SIGSEGV in strlen()

[mfmj_linux]

happen after login

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 14 01:24:37 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2013-11-15 (698 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Vostro1310
ProcCmdline: /lib/systemd/systemd-logind
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=c508c4ae-ef50-4989-b330-f175b5df7b5d ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f9b5af296fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f9b5af296fa) ok
 source "(%rax)" (0x558c8a000000) not located in a known VMA region (needed readable region)!
 destination "%xmm12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __GI___strdup (s=0x558c8a000000 <error: Cannot access memory at address 0x558c8a000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UpgradeStatus: Upgraded to wily on 2015-10-05 (9 days ago)
UserGroups:

dmi.bios.date: 03/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0H528C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1310:pvrNull:rvnDellInc.:rn0H528C:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1310
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.

[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 #1495178, 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.