|
Bugzilla – Full Text Bug Listing |
| Summary: | kNetworkManager does not connect if KDE Wallet Manager is not used | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Forgotten User OvlPd7Jcli <forgotten_OvlPd7Jcli> |
| Component: | KDE4 Workspace | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | crmafra, forgotten_--EoyBps8f, forgotten_vrBbBW-brJ, publio.escipion.el.africano, rens.groenewegen |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User OvlPd7Jcli
2010-12-26 15:55:25 UTC
I can assure that this bug persists. If I rejected to open KWallet the wireless connection will be not reached, although KNetworkManager had the key. If I create a new user account or tried to connect to a new wireless network, and I rejected that my key were stored by KWallet, the connection will be not reached. But If after that I chosen the newly setup connection I will be able to confirm that KNetworkManager has the key in the "key" field. Checking "Show the key" will show it, and, also, the key will be fine. But KNetworkManager wil not be able to use it. That seems like KWallet intermediates/interferes the process of connecting itself, and I think it is not all right. "(changed during the 2011-02-20 Open-Bugs-Day about bugs for obsolete versions of openSUSE)" dom feb 20 16:50:15 UTC 2011 Another thing: i after all that i choose to let KWallet amange my key, the key that was in KNetworkManager will be erased, and I have to re-introduce it. I probably had the same issue when installing 11.4RC1. What I have not tried yet: What if I open the connection manager, go to `Other' and choose not to use KWallet there before trying to connect to any wireless network? If that works, this is likely to be some kind of "forking" problem, or lack of concurrency: After having entered the key, KNetworkManager tries to save it to the wallet and waits for that to return successfully rather than passing the key to wpa_supplicant (or wherever it is suppoed to go) concurrently and ignoring the "save status". Might be an upstream issue. Interesting. I'll test my self it later also. I have already tested it in 11.4 RC 2, and this issue is still present, and also is not worked around by the suggestion of Fieseler (comment 3). (>I probably had the same issue when installing 11.4RC1. What I have not tried >yet: What if I open the connection manager, go to `Other' and choose not to use >KWallet there before trying to connect to any wireless network? [...] ) If the KDE user decided to not connect to the network that he previously configured to connect always when he login but later, and canceled the KWallet's password dialog launched, he will have no further opportunity to connect that network in the current session. The user must to re-login. In 11.4 Final x86_64 + Updates I have found that if the user refuses to introduce his password when logins, due to KNetworkManager finds the wireless network the user previously indicated to connect to always, KNetworkManager further will not be able to connect to the network (even after launching KWallet, which seldom does not run). The user has to restart the session (or relogin) and in this second time should introduce the password and connect then. *** Bug 687676 has been marked as a duplicate of this bug. *** knetworkmanager is unmaintained and hence will not receive any non-security updates anymore. If the issue persists with 12.1, i.e. the plasmoid-networkmanagement, please report it upstream since it is not opensuse-specific. http://en.opensuse.org/openSUSE:Bugreport_KDE#Before_you_report_bugs |