Hi !
I installed OpenSUSE 42.1 KDE
in installation, I passed network phase
when I finished I clicked on wifi icon to connect
I saw available networks but when I choose one to connect with, Kwallet was opened, after enter password nothing happened and I can’t connect
see screenshots:
http://i.imgur.com/piwC4gE.png
I just ignore wallet window then wifi password window appeared, I entered the password and connect normally
sorry for this thread :shame: !
now kwalletmanager open crashed 
so I can’t disable it
You shouldn’t ignore the kwallet window.
You have to configure kwallet when it is first started. (you can select classic method and enter an empty password to not be bothered with having to enter a password on login to open your wallet)
KDE’s NetworkManager applet (plasma-nm) uses kwallet to store the password, if kwallet isn’t running/configured, you’ll have to re-enter it every time you want to connect.
Unless you set up the connection as “system connection” (enable option “Allow other users to connect” or similar in the connection settings), the wifi password is stored system-wide by NetworkManager itself then.
now kwalletmanager open crashed
so I can’t disable it
kwalletmanager won’t help you anyway, as it is a KDE4 application and can only access/configure KDE4’s wallet.
A KF5 version has not been released yet, but will be part of the KDE Applications 15.08 release in less than 2 weeks.
And again, if you disable kwallet(5), you have to enter your wifi password every time you connect.
If kwallet isn’t working and you need an immediate alternative,
It’s likely you can just enter the password into your wpa_supplicant.conf file.
I’ve only entered the password in plain text (years ago).
The following archwiki forum thread suggests you can store the password’s hash (see last post). If you do this, there is a special wpa hashing utility to create your string.
https://bbs.archlinux.org/viewtopic.php?id=144471
I haven’t looked at this for many years… but IIRC
It’s easiest to first try to create a connection using a connection manager like NM, the attempt creates most of the connection properties so you don’t have to create from scratch because NM is just a frontend for wpa_supplicant. IIRC in those days even if you stored your password in kwallet it was also written to wpa_supplicant.conf but I doubt that is still the case today (verify for yourself).
Once your password is in your network connection described in wpa_supplicant.conf, you should be able to activate your connection using NM, or if that doesn’t work by invoking your connection using the wpa_supplicant utility (in a console).
Note of course that this is just another way to launch a wireless connection (specifically WPA/WPA2 with password).
If you are connecting to an open access point or WEP, you should use the “iw” utility.
And, any possible kwallet issue isn’t addressed, just avoided.
TSU