systemd-logind crashed with SIGSEGV in strlen()

[John Radley]

Linux u1510a 4.2.0-14-generic #16-Ubuntu SMP Fri Oct 2 05:14:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
15.10 Beta 2 upgraded yesterday 6th.
Virtualbox 5.06
Windows 10 host
Booted today 7th Oct and on logging in received the Internal Error dialogue, which had not occurred before.
Will add additional comment it repeats.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu7
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
Date: Wed Oct 7 00:23:04 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-10-01 (6 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5da0d2b6-e5c8-44dc-beab-78eb9e6678b8 ro quiet splash
SegvAnalysis:
 Segfault happened at: 0x7f6b90d7d6fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f6b90d7d6fa) ok
 source "(%rax)" (0x55720f000000) 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=0x55720f000000 <error: Cannot access memory at address 0x55720f000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #1495178. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Apport retracing service (apport)]

StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __GI___strdup (s=0x55720f000000 <error: Cannot access memory at address 0x55720f000000>) at strdup.c:41
 free_and_strdup (p=0x55720ffbb1b8, s=0x55720f000000 <error: Cannot access memory at address 0x55720f000000>) at ../src/basic/util.c:6023
 method_set_wall_message.lto_priv.423 (message=0x55720ffc3d80, userdata=0x55720ffbb060, error=0x7ffc1d6202d0) at ../src/login/logind-dbus.c:2323
 method_callbacks_run (found_object=0x7ffc1d620430, require_fallback=false, c=0x55720ffc15d0, m=0x55720ffc3d80, bus=0x55720ffbdba0) at ../src/libsystemd/sd-bus/bus-objects.c:410

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.