Bug 205319 - knetworkmanager asks for kwallet password for unencrypted network
Summary: knetworkmanager asks for kwallet password for unencrypted network
Status: RESOLVED DUPLICATE of bug 243792
Alias: None
Product: Network Management
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-27 12:10 UTC by Martin Schlander
Modified: 2011-03-17 07:03 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schlander 2009-08-27 12:10:56 UTC 
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

When starting KDE in an environment with a known unencrypted wireless network, the KDE4 KNetworkManager will autoconnect to this which is fine.

However KNM will ask for the KWallet password nevertheless. This seems a bit annoying an unnecessary.

Expected behaviour: KNM only asks for KWallet access when a passphrase is needed.
Comment 1 Will Stephenson 2009-08-30 10:48:19 UTC 
This is because the wallet is opened for any connection write (eg updating seen-bssids), not just ones that need to change stuff in the wallet.
Comment 2 Martin Schlander 2009-09-01 12:57:23 UTC 
Btw. I also noticed when I startup with a cable connected and a wireless network also available, knm will connect to the wireless too and ask for kwallet access.

I think this will probably annoy most people, and that they'd prefer if it only connected the wired by default, and without the need to enter kwallet password.
Comment 3 Luiz Angelo De Luca 2009-09-15 05:34:26 UTC 
Still in kde 4.3.1

I disabled wireless (physical switch) and plugged on an ethernet cable. Netowkr manager also asked for kwallet.
Comment 4 Lamarque V. Souza 2011-03-15 17:07:31 UTC 
Is this problem still happening?
Comment 5 Lamarque V. Souza 2011-03-17 07:03:43 UTC 

*** This bug has been marked as a duplicate of bug 243792 ***