Version: 0.9 (using KDE 4.7.4) OS: Linux This issue affects version 0.9.0-rc4. It wasn't present in -rc2. When I connect to mobile broadband by clicking on the respective entry in the Network Management Plasma Widget, I often get a prompt to enter my SIM PIN (although the connection is set to store the PIN and it has been maintained correctly). Reproducible: Sometimes Steps to Reproduce: Click on Mobile Broadband entry in the Network Management Plasma Widget's connection list. Actual Results: I get a prompt for the SIM PIN (and other connection details). Expected Results: A connection is immediately attempted (w/o an extra dialog).
There is only one change in Plasma NM that could cause this behaviour change. In November 10th I fixed a bug in Plasma NM where it did not always prompted the user for secrets when NetworkManager requested them. Maybe that is why rc4 is asking them now. I cannot change that, the NM specification says we should always ask for secrets when NM requests them. Is your connection a system connection? If yes then storing the PIN is NetworkManager's reponsability, not ours. By the way, the password field in the gsm dialog is required even if the password is bogus. If the password field is empty the dialog asking for gsm secrets will appear even if the PIN is correctly stored and the modem already unlocked (in this situation the PIN was already used to unlock the modem). Again: NetworkManager's specification mandates that we ask for all missing secrets, even the ones that are not actually used.
On Thu, Feb 2, 2012 at 13:38, Lamarque V. Souza <lamarque@kde.org> wrote: > There is only one change in Plasma NM that could cause this behaviour change. > In November 10th I fixed a bug in Plasma NM where it did not always prompted > the user for secrets when NetworkManager requested them. Maybe that is why rc4 > is asking them now. I cannot change that, the NM specification says we should > always ask for secrets when NM requests them. > > Is your connection a system connection? If yes then storing the PIN is > NetworkManager's reponsability, not ours. Yep. The PIN is also stored correctly, but still requested sometimes. The connection in question was indeed a system connection. I changed this to a non-system connection for now, which will hopefully work around the issue. Would it make sense to file a NetworkManager bug? > By the way, the password field in the gsm dialog is required even if the > password is bogus. If the password field is empty the dialog asking for gsm > secrets will appear even if the PIN is correctly stored and the modem already > unlocked (in this situation the PIN was already used to unlock the modem). > Again: NetworkManager's specification mandates that we ask for all missing > secrets, even the ones that are not actually used. Makes sense, but does not apply to this case as all password/PIN fields are populated. Thanks for the speedy reply, BTW!
(In reply to comment #2) > Yep. The PIN is also stored correctly, but still requested sometimes. > The connection in question was indeed a system connection. I changed > this to a non-system connection for now, which will hopefully work > around the issue. Would it make sense to file a NetworkManager bug? It makes sense, NetworkManager should not ask for secrets it is responsable for storing. Unless NetworkManager actually does not store the PIN for the reason I mentioned above or it is one of the "secrets not saved" bugs I have seen people complaining about on the Internet. Some of those bugs happens with nm-applet too, which makes them likely to be bugs in NetworkManager itself. > Thanks for the speedy reply, BTW! You're welcome.
*** This bug has been marked as a duplicate of bug 293045 ***