After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 687855 - Ask for PIN when enabling "Mobile Broadband"
Ask for PIN when enabling "Mobile Broadband"
Status: RESOLVED DUPLICATE of bug 685331
Product: gnome-shell
Classification: Core
Component: network-indicator
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on: 687908
Blocks:
 
 
Reported: 2012-11-07 15:37 UTC by Aleksander Morgado
Modified: 2012-12-12 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Aleksander Morgado 2012-11-07 15:37:53 UTC 
Currently the switch to enable "Mobile Broadband" just triggers enabling of wwan in NetworkManager. When wwan gets enabled in NM it will request to enable each modem found in ModemManager, but this enabling may fail if the modem is locked. So, before even enabling wwan in NM, gnome-shell should probably check the lock status of each modem and request PIN for them if they are locked.

For some reason, if I'm not mistaken, the current behaviour is that PIN is requested for a modem whenever it is found locked, even if we didn't ask to enable "Mobile Broadband", which I don't think it's ok.

PINs should get asked to the user only when "Mobile Broadband" gets enabled (either by just clicking on the global switch or as part of the connection request to a given settings profile).
Comment 1 Giovanni Campagna 2012-11-07 16:54:17 UTC 
Current behavior is that PIN is asked when NM says so.
I honestly have no idea of what this means in practice, because I don't have a modem to test, but I'd rather have NM do the right thing and only ask for PIN when need.
Comment 2 Aleksander Morgado 2012-11-07 22:09:53 UTC 
You're truly right; I think I'm mixing the behaviour of n-m-a and the shell indicator applet. For some reason I think the network-manager-applet does some extra logic regarding PIN unlocking that the shell indicator doesn't. I'll try to check this tomorrow.
Comment 3 Aleksander Morgado 2012-11-08 06:35:05 UTC 
Just checked the sources of network-manager-applet and realized that it was the one trying to unlock the modem as soon as it was detected; I filed bug 687897 for that. Now, I guess I'll need to see how NetworkManager is supposed to request PIN secrets during Mobile Broadband enabling, as in that case we're not launching a connection profile.
Comment 4 Aleksander Morgado 2012-12-12 12:48:24 UTC 

*** This bug has been marked as a duplicate of bug 685331 ***