crashed with TypeError in call_blocking()

Bug #628432 reported by Rodolfo Augusto Manzoli
This bug affects 17 people
Affects Status Importance Assigned to Milestone
Fix Released
Michael Terry
wicd (Ubuntu)
Fix Released

Bug Description

Binary package hint: wicd crashed with TypeError in call_blocking()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: wicd-daemon 1.7.0+ds1-5
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Wed Sep 1 19:14:17 2010
ExecutablePath: /usr/share/wicd/daemon/

InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/share/wicd/daemon/
ProcEnviron: PATH=(custom, no user)
PythonArgs: ['/usr/share/wicd/daemon/']
SourcePackage: wicd
Title: crashed with TypeError in call_blocking()

Related branches

Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :
tags: removed: need-duplicate-check
Changed in wicd (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
tags: added: precise
Changed in wicd (Ubuntu):
importance: Undecided → Medium
Michael Terry (mterry)
visibility: private → public
Revision history for this message
Michael Terry (mterry) wrote :

This could happen if either GetCurrentNetwork or GetCurrentBitrate fail to return strings, which will occur if either of them fail to match their regular expression against the current iwconfig output. (as happens in bug 1042290)

It seems like update_state() should safeguard against that possibilty.

Revision history for this message
David Paleino (dpaleino) wrote :

Fixed in revision 818, thanks to Michael Terry!

Changed in wicd:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Michael Terry (mterry)
milestone: none → 1.7.3
Changed in wicd (Ubuntu):
status: Confirmed → Fix Released
Changed in wicd:
status: Fix Committed → Confirmed
David Paleino (dpaleino)
Changed in wicd:
status: Confirmed → Fix Committed
merck (merckmoon)
Changed in wicd:
status: Fix Committed → Fix Released
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.