Is KDEWallet working correctly in factory?

I normally disable KDEWallet since I use wicked (formally ifup) on my desktop, but I’ve left it enabled so far in factory and I just click cancel when the window pops up. And I can’t get wicked to work anyway so I’m using NM. After a recent update, I can no longer close the KDEWallet setup window. I disabled KDEWallet in system settings but then I was asked for my network password every time I logged in. So I re-enabled KDEWallet and went through the set up steps, but now it asks me for the wallet password every time I log in.

Is this the way KDEWallet is supposed to work?

Is there a way to have NetworkManager remember the password so I don’t have to use the wallet? (I hate that wallet.)

don’t use a password just leave blank then Wallet will stop bugging you

That did the trick. But is it a bug that I can’t cancel the setup window for KDEWallet or is that intentional?

Always been that way as far as I know I don’t use it LOL

It wasn’t that way for me until the latest updates and I know the KDE version in factory is beta, so I thought it might be a bug.

Are you saying you’re using NM without the wallet or are you using wicked?

I couldn’t get wicked to work with wireless and there’s been no response so far to the bug at bugzilla.

Well, I would find it normal that KWallet asks for the setup again the next time it is opened by some application, if you cancel it the first time.
But I haven’t tried that at all yet.
AFAIR there’s also the option to not setup kwallet in this initial dialog though.

And yes it is also normal that it asks for the wallet password if you set a (non-empty) password for the wallet. That’s the point of a password, isn’t it? :wink:
There is a way to open it automatically on login with the login password via PAM (similar to GNOME’s keyring), but I haven’t tried that yet either.
I’m using an empty password since I first installed/used KDE(3) in 2003.

Are you saying you’re using NM without the wallet or are you using wicked?

For “system connections” (called “Allow to share with other users” or similar in Factory) NetworkManager saves the password itself (in /etc/NetworkManager), kwallet is not used at all then.
That’s how I have setup my wireless connection. The connection is established then during boot already, not when the user logs in, and is available in text mode even without having KDE running.

KDEWallet seems to be working normally for me.

The differences that I notice: there’s now an option to use gpg encryption and your gpg key (if you already have one). But I think that’s only an option on first time setup.

KDEWallet no longer shows up in the system tray, even when it is open. I set it to never close, so it is always open after I have used it once. But it does not appear in the tray.

I haven’t tried factory on my laptop, so I have not tested this. In previous versions, there was an option for NetworkManager to save network keys in unencrypted files. If that option is still available, it should avoid the incessant demand for KDEWallet. Or, if you can set a wifi connection to be a system connection (available to all users), then the key is saved in a root-readable file under “/etc/NetworkManager”, so you should not be prompted for KDEWallet except when initially setting up the connection.

Right, this was changed for KDE 4.14, I think: kwalletmanager is not started automatically any more. But you should still be able to run it manually (I cannot check at the moment though).

I haven’t tried factory on my laptop, so I have not tested this. In previous versions, there was an option for NetworkManager to save network keys in unencrypted files. If that option is still available, it should avoid the incessant demand for KDEWallet. Or, if you can set a wifi connection to be a system connection (available to all users), then the key is saved in a root-readable file under “/etc/NetworkManager”, so you should not be prompted for KDEWallet except when initially setting up the connection.

Yes, that’s true.
But AFAIK the networkmanagement plasmoid would still try to open the KWallet and ask for your password, unless you disable the use of KWallet. No idea if that still applies to the new plasma-nm in Factory though.

I’m saying that I used to be able to cancel the setup window before and still use my network. Now it won’t let me use the network until I set up KDEWallet and I can’t close the setup window until I do.

I have /etc/NetworkManager/system-connections in factory. How do I use it like you did to save the network password?

Well, if the password is to be stored in KWallet, it obviously won’t work without KWallet setup/enabled.
Probably plasma-nm does not support storing the password unencrypted in the config file any more because of the obvious security issues.

Somewhere this rings a bell in the back of my head, I think I read about such a change (plasma-nm is totally rewritten from scratch anyway, it has nothing in common with the old plasmoid).
It might be that I confuse it with KMail/Akonadi now though, they decided to only support saving the passwords in KWallet a while ago (after 4.4)… :wink:

I have /etc/NetworkManager/system-connections in factory. How do I use it like you did to save the network password?

Mark your connection as “system connection” in the connection setup dialog. On Factory with plasma-nm you’d have to enable “Share this connection with other users” or similar in the connection settings.

I didn’t find a way to “mark my connection as system connection” but I did find a box to check that said, “All users may connect to this network.” I then disabled KDEWallet and logged out/in and I wasn’t asked for a password.

Thanks for the help.

That’s probably the new way that it is worded in factory. That should solve your problem.

Yes. I didn’t remember the exact wording, and wasn’t able to take a look either.

Btw, that’s not really a change introduced by the plasma-nm applet.
The option was renamed in NetworkManager itself quite some time ago, and is called this way in GNOME in 13.1 at least, but I think 12.3 as well.

It’s just that the old networkmanagement plasmoid was never adapted to this name change (which would have caused new translations as well e.g.)…