i upgraded opensuse 13.1 from kde 4.12.4 to 4.13.0 i created before the upgrade a wifi access point . this wifi access point works well but i discovered in the tag "wifi security" that the key field is empty ! i checked in /etc/NetworkManager/system-connections/Radio Wifi AP file that there is a key psk=ABC...23J another thing : the padlock is yellow i use wpa_supplicant 2.1git-48.3 because with the 2.0 we can't create any ap Reproducible: Always
I don't understand where the key field is empty?
Created attachment 86603 [details] field "password" is empty
Is that connection available for all users (whether the password is stored in NetworkManager or in KWallet)? Can you please check whether our kded deamon is running?
(In reply to comment #3) > Is that connection available for all users yes > (whether the password is stored in NetworkManager or in KWallet)? in NetworkManager Can you please check whether our kded > deamon is running? kded4 is running another info : my pc can connect to the wifi ap of my isp i created a connexion . the password is well displayed but it is not an hexadecimal number but something as "-Sd4 ...fm,qgL"
I didn't mean whether kded4 is running, I need to know whether "networkmanagement" kded module is loaded. You can check that on DBus or in System Settings → Startup and Shutdown → Service Manager → Startup Services and check whether "Plasma Networkmanagement module" is running.
Yes "Plasma Networkmanagement module" is running.
no more pb since opensuse has updated wpa_supplicant to 2.0-3.4.1
i reopen the bug report wpa personnal key is displayed only if the connection is "connected" no pb with another type of wifi connection as a simple hotspot connection
1) Is the password stored in KWallet? Open KWalletManager → Network Management → Maps and check whether is there your password stored under some UUID. 2) Can you please attach NetworkManager logs? 3) Is the issue reproducible with a new user?
4) Do you use Plasma Netbook UI?
opensuse 13.1 , kde 4.13.2 plasma nm 0.9.3.3-4.3 wpa_supplicant to 2.0-3.4.1 because of the new wpa_supplicant i delete the AP then i create again the access point then password key pb still there - nothing is stored in kwallet under "Network Manager" - as ssid it don't accept special symbol for example instead of "ma_connexion_partagée" we have "ma_connexion_partagée"
Created attachment 87736 [details] network manager log
i don't use plasma netbook ui
with another user same pb i can't see the password key i made an error : even if the ap is connected we can't see the password key
Git commit 5294e9f0087735abb801b24c8d7bc69a952a5848 by Jan Grulich. Committed on 18/07/2014 at 06:26. Pushed by grulich into branch '0.9.3'. Comment out code delaying initialization of our secret agent until we found a better solution Related: bug 337554, bug 335754 M +8 -8 kded/service.cpp http://commits.kde.org/plasma-nm/5294e9f0087735abb801b24c8d7bc69a952a5848
Git commit 9edd166c9abfbc7c834fba4fed1c730289580261 by Jan Grulich. Committed on 21/07/2014 at 11:22. Pushed by grulich into branch '0.9.3'. Properly delay initialization of our kded module and drop support for plaintext files REVIEW:119353 Related: bug 337554, bug 335754 M +0 -11 editor/connectioneditor.cpp M +11 -39 kded/secretagent.cpp M +4 -4 kded/secretagent.h M +25 -20 kded/service.cpp M +5 -3 kded/service.h M +3 -1 libs/editor/connectiondetaileditor.cpp M +2 -0 libs/handler.h http://commits.kde.org/plasma-nm/9edd166c9abfbc7c834fba4fed1c730289580261
i reopen the bug report opensuse 13.1 x86_64 kde 4.13.3 plasma nm 0.9.3.3-4.4 networkmanager 0.9.8.8-4.1 wpa_supplicant to 2.0-3.4.1 not only the wifi access point has this pb but my wifi lan access point has this pb ! i can't connect my pc to my wifi lan plasma-nm asks for the key when i click on "connect" i must use a wired connection in the file containing connection settings we have the key: [802-11-wireless-security] key-mgmt=wpa-psk )...............................................................^
Can you try to compile the latest version from git (specifically 0.9.3 branch)?
opensuse 13.1 x86_64 kde 4.14.0 plasma nm 0.9.3.4-1.2 networkmanager 0.9.8.8-10.1 wpa_supplicant to 2.0-3.4.1 i recently updated kde to 4.14.0 thus updated plasma-nm to 0.9.3.4-1.2 and networkmanager to 0.9.8.8-10.1 one pb disappeared : now i can connect to internet with wifi it remains one pb : in the connexion editor the "wpa & wpa2 personnel" key is not displayed
Try to remove and add your connection again.
(In reply to Jan Grulich from comment #20) > Try to remove and add your connection again. i created again the connexion => pb still there wpa key is not displayed and i discover another pb : - i must close and open my kde session to use the new wifi connexion if i don't do this then it does not appear in the list of wifi connexions even if i refresh the list - a second connexion with name <ssid of the re-created wifi connexion> appears in the list ! no corresponding file in /etc/NetworkManager/system-connections/ * the wifi connexion i created again a connexion to a hidden network
another pb . i wonder why the key pass is in a text file and not crypted instead of to be recorded in kwallet.
Are you sure you have enabled KWallet? It should be saved in KWallet only if KWallet is enabled and plasma-nm has access to it.
what do you mean by "you have enabled KWallet" ?
There is a checkbox for enabling KWallet in System Settings → Account details → KDE Wallet. Also in "Access Control" tab check whether plasma-nm has not denied permission to access to it.
yes kdewallet is enable . in "acess control" tab there are many apps but no "plasma-nm"
i discovered this : connexion to a not hidden wifi lan : - key is displayed - key recorded in kwallet connexion to a hidden wifi lan - key is not displayed - key is not recorded in kwallet but in in the conf file in /etc/NetworkManager/system-connections/
Looks like NetworkManager behaves differently in storing secrets for hidden networks. It is possible that this behavior has changed in newer NM version. Anyway, I don't see any problem in plasma-nm. Can I close this bug now?
where can i report abug about networkworkmanager ? thanks
I would try newer NetworkManager version first, your version is quite old. You can report NM issues here [1]. Before you report your issue, could you please enable plasma-nm debug in kdebugdialog and restart kded4 from terminal and post the output from it after you try to edit and save your connection? There should be entries like: plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint) plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/3" plasma-nm: Setting name: "802-11-wireless-security" plasma-nm: Hints: () plasma-nm: Flags: 4 [1] - https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
what is the console command to restart kded4 ? thanks
Just kill it with killall kded4.
in kdebugdialog i checked "plasma-nm" then in root console linux-b4lz:~ # killall kded4 linux-b4lz:~ # kded4 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KDE Daemon (kded) already running. then i created a wifi connexion to a hidden wifi ap then no messages displayed in the root console
another try linux-b4lz:~ # killall kded4 kded4: no process found linux-b4lz:~ # kded4 kdeinit4: Shutting down running client. klauncher: Exiting on signal 15 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KDE Daemon (kded) already running. klauncher: Exiting on signal 15 kded(29849): "KLauncher could not be reached via D-Bus. Error when calling kdeinit_exec_wait: The name org.kde.klauncher was not provided by any .service files " Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) KDE Daemon (kded) already running.
Any chance you could try Plasma 5? It's possible that the situation is fixed there and also there won't be any new KDE 4 release in future.
sorry but no . it's a pity we can't create wifi connection with virtualbox
Closing, there won't be any new release of plasma-nm for KDE 4. Switch please to Plasma 5 and re-open this bug if your problem persists.