nm 0.8 lacks feature to unlock SIM by PUK

Bug #449401 reported by Alexander Sack
24
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.

Revision history for this message
In , Didier (didier-redhat-bugs) wrote :

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'
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_prepare_done(): GSM modem connection failed: SIM PUK required
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...

Revision history for this message
karlrt (karlrt) wrote :

can reproduce this bug with karmic and lucid:

After blocking your sim (e.g. 3 times wrong pin) everytime you try to connect, nm fails to connect instantly without giving you any error.

So Modem is no longer usable until you unblock it with windows or another linux distro where it works (like jaunty) Thats why i think this bug is quite serious, it can lead to a lot of trouble.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager (Fedora):
status: Unknown → Confirmed
Revision history for this message
In , Didier (didier-redhat-bugs) wrote :

My previous entry above is incomplete.

When I get message

<< NetworkManager: <WARN> stage1_prepare_done(): GSM modem connection failed: SIM PUK required >>

the only solution with current version of NetworkManager is to boot on Windows or to remove SIM from USB stick and insert it in mobile phone to unlock it with the PUK code.

With previous versions of NetworkManager who accepted PUK code during configuration, behavior was different and NetworkManager was able to unlock the SIM so current behavior is a regression.

Revision history for this message
In , Johan (johan-redhat-bugs) wrote :

I just updated to Fedora-rawhide my kernel, ModemManager, NetworManager... but have the same problem.
I found another solution to unlock the sim, using wvdial to send:
AT+CPIN="puk","pin"

One thing to try may be to use the PIN field of the NetworkManager to send
puk,pin and not just the pin.

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

Recent versions of NM & ModemManager from updates will request the PUK when the card is plugged in, if the card is locked enough to require the PUK.

Revision history for this message
marco (schlickspringer) wrote :

Is there any workaround to reenable the SIM when using an internal SIM card and no windows is installed ? When will this be patched and is this targetted for Maverick ?

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
Revision history for this message
Thomas Hood (jdthood) wrote :

Supposedly fixed upstream.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
Changed in network-manager (Fedora):
importance: Unknown → Medium
status: Confirmed → 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.