KDE requests password for network it already knows the password for

I’ve just moved house, and haven’t setup my AP yet

so I’m connecting directly to the gateway, which has poor signal where I’m connecting to it from. This has caused some strange behaviour to arise:

Despite

kcmshell kcm_networkmanagement

knowing what the password to the network is

  1. image

I’m ocasionally prompted for the password to it when the connection becomes poor

image

yet the dialog disappears whenever I re-invoke the aforementioned configuration page.

Am I doing something wrong? That is, is this a symptom of misconfiguration that I’m luckily only just now experiencing, or should I file a bug?

I also experience this behavior. I think it is something to do with Network Manager not trusting that it already has the password if you get a few quick disconnect/reconnect cycles.

Another option - that people on the internet are talking about - is that Network Manager will prompt for the password if it can’t talk to the FreeDesktop.org secrets manager. This could be either KDE’s KWallet, or GNOME keyring. See if you have either of them running: the GNOME keyring process should be called gnome-keyring-daemon and the KWallet process should be called kwalletd5.

1 Like
PS /home/rokejulianlockhart> Get-Process gnome-keyring-daemon  
Get-Process: Cannot find a process with the name "gnome-keyring-daemon". Verify the process name and call the cmdlet again.
PS /home/rokejulianlockhart> Get-Process kwalletd5           

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
      0     0.00     114.43       5.26    3595 …19 kwalletd5

PS /home/rokejulianlockhart>

Wow. PowerShell on Linux. Just… Wow.

Yea, that more or less my setup (I mean - except PowerShell…). Can you please check what version of kwalletd5 is installed? It needs to be at least 5.97 to have org.freedesktop.secrets support. Also, if you can - see if you have that D-Bus API available on your system - for example by running qdbus org.freedesktop.secrets

1 Like

@guss77,

qdbus6 org.freedesktop.secrets
PS /home/rokejulianlockhart> qdbus6 org.freedesktop.secrets                                                   /
/MainApplication
/modules
/modules/kwalletd5
/org
/org/freedesktop
/org/freedesktop/secrets
/org/freedesktop/secrets/aliases
/org/freedesktop/secrets/aliases/default
/org/freedesktop/secrets/collection
/org/freedesktop/secrets/collection/kdewallet
/org/freedesktop/secrets/collection/kdewallet/0
/org/freedesktop/secrets/collection/kdewallet/1
/org/freedesktop/secrets/collection/kdewallet/10
/org/freedesktop/secrets/collection/kdewallet/11
/org/freedesktop/secrets/collection/kdewallet/12
/org/freedesktop/secrets/collection/kdewallet/13
/org/freedesktop/secrets/collection/kdewallet/14
/org/freedesktop/secrets/collection/kdewallet/15
/org/freedesktop/secrets/collection/kdewallet/16
/org/freedesktop/secrets/collection/kdewallet/17
/org/freedesktop/secrets/collection/kdewallet/18
/org/freedesktop/secrets/collection/kdewallet/19
/org/freedesktop/secrets/collection/kdewallet/2
/org/freedesktop/secrets/collection/kdewallet/20
/org/freedesktop/secrets/collection/kdewallet/21
/org/freedesktop/secrets/collection/kdewallet/3
/org/freedesktop/secrets/collection/kdewallet/4
/org/freedesktop/secrets/collection/kdewallet/5
/org/freedesktop/secrets/collection/kdewallet/6
/org/freedesktop/secrets/collection/kdewallet/7
/org/freedesktop/secrets/collection/kdewallet/8
/org/freedesktop/secrets/collection/kdewallet/9
/org/freedesktop/secrets/session
/org/freedesktop/secrets/session/482
/org/freedesktop/secrets/session/483
/org/kde
/org/kde/kwalletd5
PS /home/rokejulianlockhart>
zypper info kwalletd5
PS /home/rokejulianlockhart> zypper info kwalletd5                                                            Repository 'KDE:Unstable:Extra' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...
Reading installed packages...


Information for package kwalletd5:
----------------------------------
Repository     : KDE:Unstable:Frameworks
Name           : kwalletd5
Version        : 5.110.0git.20230818T171113~e452dae-ku.1.1
Arch           : x86_64
Vendor         : obs://build.opensuse.org/KDE:Unstable
Installed Size : 458.0 KiB
Installed      : Yes
Status         : out-of-date (version 5.109.0git.20230807T020122~d3aa686-ku.8.3 installed)
Source package : kwallet-5.110.0git.20230818T171113~e452dae-ku.1.1.src
Upstream URL   : https://www.kde.org
Summary        : Safe desktop-wide storage for passwords
Description    : 
    This framework contains two main components:
    * Interface to KWallet, the safe desktop-wide storage for passwords on KDE workspaces.
    * The kwalletd used to safely store the passwords on KDE work spaces.

PS /home/rokejulianlockhart>

Hahaha. Once I even chsh -s’d it, and it was actually wonderful. There’s no other battle-hardened object-oriented shell like it for Linux.

Yea… that looks fine. I would further check that KDE Wallet has your network password by opening the KDE Wallet Manager (don’t use the application launcher - that shortcut will not work, open it from the system tray icon) and check under “Network Management” → “maps” - there’ll be lots of UUID style keys, where one should just have your password next to “psk” (you may need to check “show values”).

One possibility of the issue is that the KDE wallet service has crashed - next time you get the password prompt, see if the secrets D-Bus service is still available.

There’s no other object-oriented shell on Linux (or any OS) :person_shrugging:

Personally I can’t get my head around the Verb-Object-Subject syntax that it uses - I much prefer my shell syntax “object verb subject”. It could be that I’m not a native English speaker, or the fact that Verb-Object is terrible for TAB completion. Either or, I’m not sure. The second I stopped needing to write shell scripts for Windows systems, I stopped using PowerShell and I haven’t looked back. I mean - it is great that PowerShell is available on Linux (and open source, or some such), but it isn’t for me.

1 Like

Also, I have to point that I had encountered this issue a lot, but I never bothered to investigate. Thanks for kicking my butt into looking into that :smiley:

1 Like

Yeah, the key is there.

1 Like