|
Bugzilla – Full Text Bug Listing |
| Summary: | NetworkManger: mobile broadband device requests PIN | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Klaus Singvogel <bugzilla> |
| Component: | Network | Assignee: | Vladimir Botka <vbotka> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bugzilla, suse |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 12.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Klaus Singvogel
2012-02-29 09:07:08 UTC
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. |