GNOME Bugzilla – Bug 631904
ModemManager asks for PIN code, ruins automatic connection attempt
Last modified: 2011-09-30 05:28:29 UTC
Created attachment 172115 [details] ModemManager log NetworkManager 0.8.1 (Ubuntu 10.10) In my mobile-broadband connection settings, I have enabled "Connect automatically", and I have entered the modem's PIN code, in order not to have to enter it manually every time I connect. However, that doesn't stop ModemManager from asking for the PIN code anyway when I plug in the modem, probably as it is probing the device. Before I have time to enter the PIN code, an automatic connection attempt kicks in, and I get an error response saying "Cannot perform this operation while connected". Then I get a notification about the connection attempt having failed. Some time after that, I get another chance to enter the PIN, and after that I can successfully connect manually. If I ignore the PIN code request, the automatic connection attempt will fail anyway, probably because the device hasn't been fully probed yet.
Created attachment 172117 [details] NetworkManager log
Even when I have disabled networking in nm-applet, I am prompted for the PIN code on inserting the modem.
I have exactly this problem with the same nm version in Ubuntu 10.10 with what lsusb reports as Huawei E220/E270
I thought that this might be a duplicate of #633362, but for me difference is that if I ignore the SIM PIN dialog, it disappears after a couple of seconds, but the connection is not automatically made in the background. Whilst the dialog is visible, nm-applet reports the modem as connected, although it isn't, and the dialog disappears after a couple of seconds. Even if I enter the correct PIN, it is ignored, and after a few more seconds, the whole thing is repeated. After a varying number (2-7) of cycles, the PIN dialog doesn't disappear, nm-applet reports the modem as "available", rather than "connected", the PIN is accepted, and the connection made.
It's still likely the PIN not being sent to the modem; if we got that fixed finally this problem would go away. *** This bug has been marked as a duplicate of bug 618532 ***