You are not logged in.
I'm using KDE Plasma 5, and trying to get NetworkManager working. It can currently connect to non-password-protected networks just fine, but when I try to log on to my home network with a password, it fails to connect (after waiting for some time) with the error "no secrets were provided". Any ideas?
Last edited by TheGuyWithTheFace (2015-07-28 13:32:18)
Offline
You need to install wpa_supplicant.
Last edited by remy18 (2015-06-13 17:39:58)
Offline
wpa_supplicant is already installed, according to pacman.
Offline
Yes i said a mistake you don't need wpa_supplicant for nm sorry...
edit: Finnaly you need it try systemctl start wpa_supplicant and check if there is no other network services activated for example wicd.
Last edited by remy18 (2015-06-13 17:56:48)
Offline
edit: Finnaly you need it try systemctl start wpa_supplicant
Don't do that, it will conflict with NetworkManager.service
@OP: How did you install Plasma 5?
Do you have a polkit agent installed?
https://wiki.archlinux.org/index.php/Polkit
Jin, Jiyan, Azadî
Online
For me it work and if i stop wpa_supplicant then networkmanager don't work
Last edited by remy18 (2015-06-13 18:04:16)
Offline
For me it work and if i stop wpa_supplicant then networkmanager don't work
That's because NetworkManager.service starts wpa_supplicant.service -- it should be left to do this by itself (and indeed it already is because the OP says it *will* connect to unsecured access points).
Jin, Jiyan, Azadî
Online
@OP: How did you install Plasma 5?
I just installed plasma from the arch repos as described here: https://wiki.archlinux.org/index.php/Plasma
Do you have a polkit agent installed?
Yes, I have polkit, polkit-kde-agent, polkit-qt4, and polkit-qt5 installed.
Offline
I just installed plasma from the arch repos as described here: https://wiki.archlinux.org/index.php/Plasma
There is more than one method on that page.
Please explicitly list the command(s) you used.
It's probably a good idea to add "Plasma 5" to the thread title to attract the attention of fellow Plasma users (not me).
Jin, Jiyan, Azadî
Online
Do you have dhcpcd service activated as well as the NetworkManager - these two don't mix well, disable dhcpcd and just use NetworkManager.service & have you followed this https://wiki.archlinux.org/index.php/Ne … figuration - if not using *wired* then follow this https://wiki.archlinux.org/index.php/Wi … figuration
Our enemies are your enemies, Nick. Disorder, war. It's just a matter of time before a dirty bomb goes off in Moscow, or an EMP fries Chicago. --- Alexander Pierce, Captain America: Winter Soldier
Access Denied! De-cryption failed, override denied all files sealed! --- Triskelion, Shield OS
-----
How to ask questions the smart way
Offline
It's probably a good idea to add "Plasma 5" to the thread title to attract the attention of fellow Plasma users (not me).
Good idea, post title updated.
Please explicitly list the command(s) you used.
According to my pacman.log, I installed kde by running
pacman -S plasma
.
Do you have dhcpcd service activated as well as the NetworkManager
I've made that mistake before, but according to systemctl dhcpd is loaded, but disabled. To be able to connect to my home network I've been using netctl and wifi-menu, but I've made sure to keep netctl disabled and manually start it after manually stopping NetworkManager after booting, just to be sure.
Offline
When you logged in to plasma desktop for the first time, did you set up a kde wallet and perhaps store the network password in there and have then since disabled it? NetworkManager may be looking there but the wallet is disabled and so can't find the stored password. Its a long shot because even if this is the case, I think it should allow you to enter the password again anyway and connect even when displaying the error you describe.
Offline
If I recall, I opted to not use KWallet.
Offline
Hm, so I just tried to start KWalletManager, and it clearly isn't working. I can start it, but the window is blank save for the file/settings/help menu at the top of the window, and those buttons appear unresponsive. A few seconds later I get an error that the window is unresponsive, and I just terminate the window. Is there a log somewhere I can check to see what's up with KWallet? Or is that maybe a completely separate issue?
Offline
Try removing .config/kwalletrc and .local/share/kwalletd/. Back them up first if you use kwallet.
Offline
Just tried that, no dice.
Last edited by TheGuyWithTheFace (2015-06-19 22:21:59)
Offline
I still think DarkCerberus was on the correct tack. That is the output of systemctl ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Here is the full output of systemctl:
The width of each line makes it hard to read, you might want to download it, sorry.
Offline
Please post the output of:
ls -l /etc/systemd/system/multi-user.target.wants
Post the output here (using code tags), do not use pastebin.com (it's rubbish).
Jin, Jiyan, Azadî
Online
lrwxrwxrwx 1 root root 39 Jun 3 23:56 dhcpcd@wlp3s0.service -> /usr/lib/systemd/system/dhcpcd@.service
lrwxrwxrwx 1 root root 46 Jun 13 11:37 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 40 Jun 3 23:45 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
Offline
# systemctl disable dhcpcd@wlp3s0.service
Then reboot.
Jin, Jiyan, Azadî
Online
Still no luck. Here's the output of `ls -l /etc/systemd/system/multi-user.target.wants` again:
lrwxrwxrwx 1 root root 46 Jun 13 11:37 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 40 Jun 3 23:45 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
Offline
Could you try deleting your home network in the networkmanager connection editor and then connecting again?
Offline
It looks like that might have solved it! I'll monitor it for a few more days to make sure, but I think that fixed the issue.
Offline
I think there had been a couple of issues. Main one with multiple network services running and a problem with kwallet storing info on the connection and not being able to access it as its broken. I think you needed to fix both issues. Glad it's working!
Offline