[maverick] 3G: doesn't connect when SIM is PIN-protected

Bug #644752 reported by alleluia20
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
plasma-widget-networkmanagement (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Maverick by alleluia20

Bug Description

Binary package hint: plasma-widget-networkmanagement

I use a modem huawei e1550 in kubuntu maverick, and (unsuccessfully) try to connect using the Network Manager plasma widget. The SIM card is PIN-protected. Then, the widget connects, prompts "obtaining network address", and then disconnects prompting "not managed". After that, the notifier of peripherals prompts again the disk integrated in the huawei modem, then I try to connect, and back to be beginning, like this forever and ever.

Nevertheless, if I connect in Windows with Mobile Partner (after unlocking the PIN, of course), and reboot into kubuntu, then the plasma widget connects at the first time. The same if I connect in Ubuntu via umtsmon (after unlocking the PIN, of course) and reboot. Here we have an (inconvenient) workaround: connect in Windows or via umtsmon (but umtsmon is not reliable, the connection is often lost), reboot without disconnecting the modem, and connect with Network Manager plasma widget.

The second (and more convenient) workaround is to use nm-applet, after having removed the instance of networkmanager used by kde. nm-applet first asks for the PIN before opening in the panel, and then we can connect without problems. Also, while nm-applet is connecting, the Network Manager plasma widget displays as though it were connecting itself, and finally displays a successful connection (what a cheek it's got :-) ).

Here the shell output:

$ nm-applet
An instance of nm-applet is already running

$ qdbus org.kde.kded /kded unloadModule networkmanagement
true

$ nm-applet
** Message: applet now removed from the notification area
** (nm-applet:2571): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:2571): DEBUG: old state indicates that this was not a disconnect 0
** (nm-applet:2571): DEBUG: old state indicates that this was not a disconnect 0
** Message: applet now embedded in the notification area
** (nm-applet:2571): DEBUG: foo_client_state_changed_cb

** (nm-applet:2571): WARNING **: handle_property_changed: property 'ip-interface' changed but wasn't defined by object type NMGsmDevice.
** (nm-applet:2571): DEBUG: foo_client_state_changed_cb

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plasma-widget-networkmanagement 0.9~svn1176084-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Sep 21 23:34:46 2010
EcryptfsInUse: Yes
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
ProcEnviron:
 LANGUAGE=fr_FR
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SourcePackage: plasma-widget-networkmanagement

Tags: 3g maverick pin
Revision history for this message
alleluia20 (david-maillists) wrote :
Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
Revision history for this message
bjorn fahller (bubuntu-fahller) wrote :

Same on Samsung NC10 with built in 3G-modem. This is a regression from Lucid, where it worked flawlessly. Will probably downgrade, since the function is needed.

Revision history for this message
Andras Bibok (biboka) wrote :

I confirm this with a Huawei E620 modem (T-Mobile HU).

Workaround: take the SIM into a handy and remove the PIN.

Revision history for this message
s0undt3ch (ufs) wrote :

This was working perfectly in lucid. It even allows you to enter the pin, why doesn't it just use it!? Maverick is becoming pain, first the bluetooth mouse, now this.....

Revision history for this message
aexl (aexl) wrote :

huawei e161 here too

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.