monitor.py crashed with TypeError in call_blocking()
Bug #628432 reported by
Rodolfo Augusto Manzoli
This bug affects 17 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wicd |
Fix Released
|
Medium
|
Michael Terry | ||
| wicd (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: wicd
monitor.py crashed with TypeError in call_blocking()
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: wicd-daemon 1.7.0+ds1-5
ProcVersionSign
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Wed Sep 1 19:14:17 2010
ExecutablePath: /usr/share/
InstallationMedia:
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python -O /usr/share/
ProcEnviron: PATH=(custom, no user)
PythonArgs: ['/usr/
SourcePackage: wicd
Title: monitor.py crashed with TypeError in call_blocking()
UserGroups:
Related branches
lp:~mterry/wicd/no-none-in-update-state
- David Paleino: Pending requested
-
Diff: 22 lines (+5/-3)1 file modifiedwicd/monitor.py (+5/-3)
Revision history for this message
| Rodolfo Augusto Manzoli (rmanzoli88) wrote | #1 |
| 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 |
| visibility: | private → public |
Revision history for this message
| Michael Terry (mterry) wrote | #2 |
Revision history for this message
| David Paleino (dpaleino) wrote | #3 |
| 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 |
| Changed in wicd: | |
| status: | Confirmed → Fix Committed |
| Changed in wicd: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.