Bugzilla – Bug 749537
NetworkManger: mobile broadband device requests PIN
Last modified: 2013-10-03 15:59:21 UTC
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 In my EeePC is a mobile broadband device built in. I've already configured it and stored PIN into my environment. - Means an additional request isn't necessary. But after every (!) wake up (from suspend-to-ram) and after every every boot, I get a requester, requesting for the PIN of the device. This requester doesn't make sense for two reasons: a) as the PIN is already present (stored) in the environment b) as the mobile broadband connection is disabled in NetworkManager, in contrary to WLAN or LAN - just click on NM widget in KDE. Reproducible: Always Steps to Reproduce: 1. Connect a mobile broadband device 2. Disable broadband connection 3. Configure your connection and store PIN in environment 4. Boot or resume from suspend Actual Results: Unnecessarily a requester for the PIN for the mobile broadband device is coming up. Expected Results: The requester shouldn't pop up just because of system start. The requester should only when starting mobile broadband connection. Please keep in mind it is built-in and cannot disconnect without modifying the motherboard (unsoldering the device). :-)
It looks like the behavior that you expect was implemented a month ago, see KDE Bug 292477 Comment #3 Comment #2 of the same bug explains why storing the PIN was not enough and, in addition, gives a workaround: change your connection to a system connection
For me, 12.2 RC 1 works: the SIM PIN is only requested when starting the WWAN connection. However, see Bug 765244 for a bug regarding the "Always Ask" mode dialog.
@Klaus: Does 12.2 work for you?
12.2 is not useable for me: - Akgregator and Suspend-To-RAM took too long on my Eee PC (compared with 12.1), - 12.2 consumed a lot more battery capacity in daily work compared with 12.1. - the movement of init.d scripts to systemd was another reason. - even the boot time seemed to take much more time than a 12.1. system, maybe because I have an atom processor in my netbook only, but never measured it. After 5 days of use 12.2., I went back on 12.1. @Jan: opensuse-12.2. works in general, but 12.2 is not useable for me, so can't test this in 12.2. But this is a 12.1 issue, so I think there's no need to ask for 12.2.
@Klaus: I seriously doubt anyone will fix this in 12.1. If you do not want to update your whole KDE (note that 4.9 is available for 12.1, too) you might try to update your NetworkManager from the UpdatedApps or even Unstable:Playground repository mentioned in http://en.opensuse.org/KDE_repositories
@Klaus: Did an KDE update help?
Resolving because of no response.