wpa_supplicant crashed with SIGSEGV in _dbus_object_tree_dispatch_and_unlock()

[Eric Riese]

encountered after resuming from suspend

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: wpasupplicant 2.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Mon Sep 14 20:50:29 2015
EcryptfsInUse: Yes
ExecutablePath: /sbin/wpa_supplicant
ExecutableTimestamp: 1439920046
InstallationDate: Installed on 2015-09-12 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150911)
ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
ProcCwd: /
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f79131d8cba <__strcmp_sse2_unaligned+26>: movdqu (%rdi),%xmm1
 PC (0x7f79131d8cba) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: wpa
StacktraceTop:
 ?? ()
 ?? ()
 _dbus_object_tree_dispatch_and_unlock (tree=0x55817697eaa0, message=message@entry=0x5581769814c0, found_object=found_object@entry=0x7fff1a711c38) at ../../dbus/dbus-object-tree.c:1020
 dbus_connection_dispatch (connection=0x55817697ee40) at ../../dbus/dbus-connection.c:4744
 ?? ()
Title: wpa_supplicant crashed with SIGSEGV in _dbus_object_tree_dispatch_and_unlock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Launchpad Janitor (janitor)]

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

[Mathieu Marquer (slasher-fun)]

Inverting duplicate status so we can have a retrace of the trace with debug symbols.

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