Am Dienstag 29 August 2006 12:40 schrieb Michael Biebl: > I can not reproduce this bug here. It works as expected, meaning that > after starting knetwormanager, it tries to open the wallet, kwallet > prompts me for the password, and after that k-n-m is able to retrieve > the key. > I just a uploaded a new revision [1] which fixes some kwallet related > issues, e.g. it only access kwallet on demand and not directly on > startup. Let me know if this revision also fixes your problem. > If not, please create a new test account, so that you don't have any > possible side effect and try again.
I installed the new version and strange things happened: * On the first tries, it could not find the PSK at all. Then I created a testuser and added that user to groups plugdev and netdev. However, that was not enough. I also had to add the user to group "dialout" or a DBUS error appeared (startup from console) and no network devices were visible. Most strange is that removing that user from group dialout did not make that error reappear. After that, it kind of worked except that it didn't use the kwallet at all. At least that what it looks like because connecting to the network did not succeed at all (wpa_cli showed some PSK errors). I added the testuser to all other groups that my normal user has and suddenly, it worked and the PSK was stored in the wallet. Somewhat strange behaviour because again, removing all those previously added groups (except plugdev and netdev) did not have any effect anymore. Back to my own user, it still had the same problem. I probably got the clue, then, to note that I have _two_ wallets: my standard one for this system and a manually added old one from my old system. Knetworkmanager could not handle that, probably, because removing the old, second one (that was alphabetically before the standard one) solved the problem. After that, adding the old one again did not confuse knetworkmanager anymore, maybe the standard one was not first in list but now is. Conclusion: The wallet code in knetworkmanager needs to be more robust, it fails in quite some situations. Also, failure to connect to the DBUS is only visible in the konsole, no error message pops up! If wpasupplicant fails to use the PSK, network-manager tries on forever with absolutely no status report that something failed :-( And I leave out the errors that two running network-manager clients caused. After all, it's beta level software. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
