nm 0.8 lacks feature to unlock SIM by PUK
Bug #449401 reported by
Alexander Sack
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Manager Applet |
Fix Released
|
Medium
|
|||
network-manager (Fedora) |
Fix Released
|
Medium
|
|||
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
atm NM lacks error handling about the SIM PUK failure and nm-applet does not show the previously used UI because of that.
Changed in network-manager (Fedora): | |
status: | Unknown → Confirmed |
Changed in network-manager-applet: | |
importance: | Unknown → High |
Changed in network-manager-applet: | |
status: | Unknown → Invalid |
Changed in network-manager-applet: | |
importance: | High → Unknown |
status: | Invalid → Unknown |
Changed in network-manager-applet: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in network-manager (Fedora): | |
importance: | Unknown → Medium |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Description of problem:
NetworkMananger configuration screen for large band connections does not longer display field to specify PUK code for 3G modem
Version-Release number of selected component (if applicable):
NetworkManager- 0.7.996- 7.git20091113. fc12.rpm
How reproducible:
n/a
Steps to Reproduce:
1. n/a
2.
3.
Actual results:
NetworkMananger does not longer display field to specify PUK code for 3G modem
Expected results:
NetworkManager should dispaly field to specify PUK code for 3G modem when configuring large band connection
Additional info:
Log of a case where PUK is needed :
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) starting connection 'SFR Par défaut 1' prepare_ done(): GSM modem connection failed: SIM PUK required
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): device state change: 4 -> 6 (reason 0)
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): device state change: 6 -> 4 (reason 0)
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) opening serial device...
Nov 29 01:31:36 localhost NetworkManager: <WARN> stage1_
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9 (reason 1)
Nov 29 01:31:36 localhost NetworkManager: <info> Marking connection 'SFR Par défaut 1' invalid.
Nov 29 01:31:36 localhost NetworkManager: <info> Activation (ttyUSB0) failed.
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0)
Nov 29 01:31:36 localhost NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Nov 29 01:31:36 localhost NetworkManager: flush_routes: assertion `iface_idx >= 0' failed
Nov 29 01:31:36 localhost NetworkManager: flush_addresses: assertion `iface_idx >= 0' failed
Nov 29 01:31:36 localhost modem-manager: (ttyUSB0) closing serial device...