Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=542319.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-11-29T09:51:33+00:00 Didier 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... Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/449401/comments/1 ------------------------------------------------------------------------ On 2009-12-21T11:46:15+00:00 Didier 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/449401/comments/3 ------------------------------------------------------------------------ On 2010-01-23T15:30:00+00:00 Johan 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/449401/comments/4 ------------------------------------------------------------------------ On 2010-06-26T00:19:35+00:00 Dan 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/449401/comments/5 ** Changed in: network-manager (Fedora) Status: Confirmed => Fix Released ** Changed in: network-manager (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/449401 Title: nm 0.8 lacks feature to unlock SIM by PUK Status in Network Manager Applet: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager package in Fedora: Fix Released 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. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/449401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
