Since nearly one year connecting to my WPA/TKIP wifi network is a nightmare. It was russian roulette to get it connected until i discovered the issue. The NetworkManager applet in combination with KWalllet / pam is unreliable. For some reason it's not able to pick the password associated with the connection, and keep requesting password to me. If I enter it again and again it's worse - Multiple connections are created in the network connections editor, still unable to pick the wallet password. The only reliable workaround i have is to disable wifi, delete all passwords in NetworkManager entry in the wallet, enable wifi, request conenction, fill password.. tada it works.
There is not enough information in this bug report to triage the issue. Please read https://community.kde.org/Get_Involved/Bug_Reporting and add the missing information, particularly Steps To Reproduce, your distro, and the version of the distro and KDE Software that you're using.
Reproduction steps: 1/ Click a ssid being wpa 2/ enter password 3/ Wait it connect (or not, the bug) 4/ if it works fine, reboot the machine go to 1/ 5/ NM ask password again 6/ enter password again 7/ repeat 5/ and 6/ multiple times 8/ Open you kwallet in the NM section, see multiple entries for the same ssid 9/ Disable wifi 10/ Delete all NM passwords 11/ Enable wifi 12/ Go to 1/ Distribution: KaOS, up to date (no version, rolling release) KDE Software: 18.08.1-1 KDE Frameworks 5.50.0 Qt: 5.11.2, but does not matter, got the issues since more than a year (Qt 5.9 at least).
Thanks, that helps!
And if it matter, this is a mac book machine (mid 2014).
I installed KaOS and couldn't reproduce the issue. What is you KWallet configuration? Do you use password for your wallet? Do you get asked to open the wallet? DOes killing kded5 and starting it again help?
(Please respond with the requested information)
There is no master password set on teh wallet so no password is being asked for that. The distribution comes with a pam wallet configuration, so i guess the wallet is being opened upon login. I did not tried to kill kded, but i can try to have a look at it in the next days. The work around i used previously no longer works, was just working by chance. The thing that just works reliably is to bypass kwallet entirely by using the network connection preference and create the connection on my own, using a non encrypted password for all users, not using auto connection.
Also, as noted, i'm using a mac book machine, the wifi driver does not seems in a very good shape, so maybe it does not help as well. I was not having the issue as well on a non apple machine.
Created attachment 115576 [details] wifi log Some more info to add today. The usage of non encrypted (non wallet) passwords works far better, still it sometimes have the same issue. Sometimes the first manual click to connect the wifi don't works and desktop request a password, like it does for kwallet. I just ignore the dialog, and try to manually connect again - works. This mean that kwallet may not be the problem (but is much more impacted by the issue) but something other (the driver ?). Here is a small attached log file, not sure it can help though.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Requested information was provided.
From the log I can see it fails on missing secret agent, which it shouldn't in case your password is stored to all users (unencrypted). Can you attach here output from "nmcli -f all connection show SoDream"?
Forgot to change the status. Please provide requested information.
connection.id: SoDream connection.uuid: 18d4861f-a18f-4655-9425-e77824706fc6 connection.stable-id: -- connection.type: 802-11-wireless connection.interface-name: -- connection.autoconnect: non connection.autoconnect-priority: 0 connection.autoconnect-retries: -1 (default) connection.multi-connect: 0 (default) connection.auth-retries: -1 connection.timestamp: 1543349014 connection.read-only: non connection.permissions: -- connection.zone: -- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout: 0 connection.metered: inconnu connection.lldp: default connection.mdns: -1 (default) connection.llmnr: -1 (default) 802-11-wireless.ssid: SoDream 802-11-wireless.mode: infrastructure 802-11-wireless.band: -- 802-11-wireless.channel: 0 802-11-wireless.bssid: -- 802-11-wireless.rate: 0 802-11-wireless.tx-power: 0 802-11-wireless.mac-address: 60:03:08:A9:F5:E0 802-11-wireless.cloned-mac-address: -- 802-11-wireless.generate-mac-address-mask:-- 802-11-wireless.mac-address-blacklist: -- 802-11-wireless.mac-address-randomization:default 802-11-wireless.mtu: auto 802-11-wireless.seen-bssids: 58:90:43:13:EB:87 802-11-wireless.hidden: non 802-11-wireless.powersave: 0 (default) 802-11-wireless.wake-on-wlan: 0x1 (default) 802-11-wireless-security.key-mgmt: wpa-psk 802-11-wireless-security.wep-tx-keyidx: 0 802-11-wireless-security.auth-alg: -- 802-11-wireless-security.proto: -- 802-11-wireless-security.pairwise: -- 802-11-wireless-security.group: -- 802-11-wireless-security.pmf: 0 (default) 802-11-wireless-security.leap-username: -- 802-11-wireless-security.wep-key0: <hidden> 802-11-wireless-security.wep-key1: <hidden> 802-11-wireless-security.wep-key2: <hidden> 802-11-wireless-security.wep-key3: <hidden> 802-11-wireless-security.wep-key-flags: 0 (aucun) 802-11-wireless-security.wep-key-type: unknown 802-11-wireless-security.psk: <hidden> 802-11-wireless-security.psk-flags: 0 (aucun) 802-11-wireless-security.leap-password: <hidden> 802-11-wireless-security.leap-password-flags:0 (aucun) 802-11-wireless-security.wps-method: 0 (default) 802-11-wireless-security.fils: 0 (default) ipv4.method: auto ipv4.dns: -- ipv4.dns-search: -- ipv4.dns-options: "" ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes: -- ipv4.route-metric: -1 ipv4.route-table: 0 (unspec) ipv4.ignore-auto-routes: non ipv4.ignore-auto-dns: non ipv4.dhcp-client-id: -- ipv4.dhcp-timeout: 0 (default) ipv4.dhcp-send-hostname: oui ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.never-default: non ipv4.may-fail: non ipv4.dad-timeout: -1 (default) ipv6.method: auto ipv6.dns: -- ipv6.dns-search: -- ipv6.dns-options: "" ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes: -- ipv6.route-metric: -1 ipv6.route-table: 0 (unspec) ipv6.ignore-auto-routes: non ipv6.ignore-auto-dns: non ipv6.never-default: non ipv6.may-fail: non ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: stable-privacy ipv6.dhcp-duid: -- ipv6.dhcp-send-hostname: oui ipv6.dhcp-hostname: -- ipv6.token: -- proxy.method: none proxy.browser-only: non proxy.pac-url: -- proxy.pac-script: --
All wireless passwords have secret-flag set to 0, which means that the password is saved into NetworkManager. I would blame NetworkManager for this broken behaviour. There was a related bug in NetworkManager, but I don't remember in which version it was and in which version it was fixed. Please report your problem to NetworkManager as there is nothing we can do from plasma-nm side.
Well, i have no idea of what to report because i have no idea what you mean with secret-flags to 0. Can you details or just open the bug yourself ? Also, my distribution is very cutting edge, if the fix would be resolved upstream already and released then most likely i would already have this patch.
Bulk transfer as requested in T17796