wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

Bug #1492144 reported by Martin Pitt
206
This bug affects 45 people
Affects Status Importance Assigned to Milestone
wpa (Ubuntu)
Confirmed
High
Unassigned

Bug Description

This happens when running the NetworkManager autopkgtests

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-0ubuntu9
Architecture: amd64
Date: Fri Sep 4 09:00:38 2015
ExecutablePath: /sbin/wpa_supplicant
ExecutableTimestamp: 1439920046
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: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1
 PC (0x7f66fb181cc6) 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:
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? ()
Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Martin Pitt (pitti) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /tmp/apport_sandbox_3HEGxn/lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /tmp/apport_sandbox_3HEGxn/lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in wpa (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libdbus-1-3
no debug symbol package found for libgpg-error0
no debug symbol package found for liblzma5
no debug symbol package found for libnl-genl-3-200
no debug symbol package found for wpasupplicant

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

For me it happens every time after wake up from sleep mode.

Revision history for this message
Eric Riese (jebuswankel) wrote :

I installed what debug packages I could find and filed another bug here: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1495743

I marked that as a duplicate of this. Dunno if that was the right thing to do.

I also created this bug: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1495741 before I realized I didn't have any better information than the original.

Eric Riese (jebuswankel)
Changed in wpa (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in wpa (Ubuntu):
status: New → Confirmed
Changed in wpa (Ubuntu):
status: Confirmed → In Progress
status: In Progress → New
status: New → Confirmed
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

During normal use of Wily on a Lenovo Yoga laptop convertible, I'm getting this issue upon resuming from suspend.

Changed in wpa (Ubuntu):
importance: Undecided → High
Revision history for this message
Sean Smith (stoc2528) wrote :

Occasionally get this issue when resuming from suspend or hibernation- when hibernation works.

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Happens to me when disabling/enabling wifi in Network-Manager applet (nm-gnome)

Revision history for this message
Andreas (andreas-rabus) wrote :

Happens on wake up after hibernate, that is closing laptop,. (With cryptswap if that's of interest...)

Revision history for this message
Vincent Fortier (th0ma7) wrote :

same as comment #12 for me. disabling wifi caused this bug in my case.

Revision history for this message
Léon Hagenaars-Keus (hagenaarsdotnu) wrote :

Happens for me when disabling and re-enabling wifi through hardware switch.
I did this because the network manager wouldn't reconnect to my wifi after some idle time.
Directly afterwards, wifi automatically reconnects without issue.

Revision history for this message
Rich Johnson (nixternal) wrote :

Happens when just booting up, as well as just sitting there.
Xubuntu 15.10

Revision history for this message
Daniel Moerner (dmoerner) wrote :

Confirmed, fresh install of Ubuntu 15.10 Beta 2. Error recurs on every suspend from resume and on every startup.

Revision history for this message
Sean Smith (stoc2528) wrote :

Fresh install Ubuntu 15.10b2 with updates, occurs when resume from suspend on Latitude E5250

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.