supplicant fails due to issues speaking to dbus (max pending requests)

Bug #1033600 reported by Stéphane Graber on 2012-08-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Critical
Mathieu Trudel-Lapierre

Bug Description

Manually reporting this bug as apport doesn't seem to like me today. I'll try to get apport to attach all the needed information.

This bug happened while using my laptop as usual on my home network, happened a few days in a row lately but I couldn't track down what package introduced it (if any).
---
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
CheckboxSubmission: 12108b8b8b67d760cdd84f1b9574e7f3
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
DistroRelease: Ubuntu 12.04
Package: wpasupplicant 0.7.3-6ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Tags: precise running-unity
Uname: Linux 3.2.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin pcscd plugdev sambashare

apport information

tags: added: apport-collected precise running-unity
description: updated
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :
Stéphane Graber (stgraber) wrote :

Attached all the data I have and that doen't contain anything confidential.

There's too little in the stack traces to be able to do much with this. Would you be able to manually retrace it (using apport-retrace on the .crash file) or running it into a debugger to provide a more complete trace?

Thanks.

Changed in wpasupplicant (Ubuntu):
status: New → Incomplete
Stéphane Graber (stgraber) wrote :

Well, what I attached is the output of apport-retrace using it to download the required symbols from the internet, so I'm not sure why I didn't get a full traceback...

Anyway, I no longer have the original .crash so I can't attempt a new retrace... I'll do so when the bug happens again and will try and get more details attached to this bug report.

This was in fact due to NetworkManager hogging the dbus queue:

Aug 6 17:48:21 castiana NetworkManager[7344]: <warn> Couldn't disconnect supplicant interface: The maximum number of pending replies per connection has been reached.
Aug 6 17:48:21 castiana NetworkManager[7344]: <warn> Couldn't send AP scan mode to the supplicant interface: The maximum number of pending replies per connection has been reached.
Aug 6 17:48:21 castiana NetworkManager[7344]: <info> Activation (wlan0/wireless): association request to the supplicant failed: (null) - The maximum number of pending replies per connection has been reached
Aug 6 17:48:21 castiana NetworkManager[7344]: <info> (wlan0): device state change: config -> failed (reason 'supplicant-failed') [50 120 10]
Aug 6 17:48:21 castiana NetworkManager[7344]: <warn> Activation (wlan0) failed for access point (799-lan-gn)
Aug 6 17:48:21 castiana NetworkManager[7344]: <info> Marking connection '799-lan-gn' invalid.
Aug 6 17:48:21 castiana NetworkManager[7344]: <warn> Activation (wlan0) failed.
Aug 6 17:48:21 castiana NetworkManager[7344]: <warn> Couldn't disconnect supplicant interface: The maximum number of pending replies per connection has been reached.
Aug 6 17:48:21 castiana NetworkManager[7344]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Aug 6 17:48:21 castiana NetworkManager[7344]: <info> (wlan0): deactivating device (reason 'none') [0]

Changed in wpasupplicant (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
importance: Undecided → Critical
status: Incomplete → In Progress
summary: - wpa_supplicant crashed with SIGSEGV in X509_verify_cert()
+ supplicant fails due to issues speaking to dbus (max pending requests)

This bug was fixed in the package network-manager - 0.9.6.0-0ubuntu3

---------------
network-manager (0.9.6.0-0ubuntu3) quantal; urgency=low

  * debian/patches/dnsmasq-dbus-updates.patch: make sure the no_reply flag is
    set for the SetServers message we send to dnsmasq -- we're not expecting a
    reply and the messages otherwise stick around in the queue as pending.
    (LP: #1033600)
  * debian/patches/lp990011_use_tempaddr_sysctl_default.patch: properly query
    both /etc/sysctl.d/10-ipv6-privacy.conf and /etc/sysctl.conf for the value
    of use_tempaddr. (LP: #998223)
  * debian/patches/dnsmasq-dbus-updates.patch: fail DNS caching updates (so as
    to not write 127.0.0.1 to resolv.conf) if the lists of device configs were
    empty (no nameservers or domains). (LP: #1023486)
 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 16 Aug 2012 00:46:06 -0400

affects: wpasupplicant (Ubuntu) → network-manager (Ubuntu)
Changed in network-manager (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers