Communication with the local password server failed [unsolved]

ralvez · 2024-04-28 03:18:41

Brand new install in my also new laptop, Dell Inspiron.
Installation was fine. I decided to go with Xorg and Plasma.
When I try to connect to a network resource (in my local LAN) dolphin errors with "Communication with the local password server failed".
If I do a regular ssh connection it works fine.

Any ideas to troubleshoot this issue? I noticed that some users reported a similar error but they are OLD like 2020/21 and also seems they were using wayland and I am using xorg.

Thanks

Last edited by ralvez (2024-04-29 19:04:40)

seth · 2024-04-28 06:58:08

https://wiki.archlinux.org/title/KDE_Wa … assphrases , https://wiki.archlinux.org/title/SSH_keys#SSH_agents or https://wiki.archlinux.org/title/Polkit … ion_agents related?

ralvez · 2024-04-28 16:13:11

Thanks seth,

I have been using i3 with sddm to login for about +/- 5 years.
When I installed Arch on this laptop I decided to give Plasma a try because I used to run KDE in all my systems back then.
But this time the experience was not as good as it use to be
I played with KWallet and may be I'm OK now. I'll have to see.

I also noticed that dolphin fails to connect to the local LAN but if I SSH into the servers using the CLI it works fine.
I'm investigating now. What can I say. Not the same KDE experience I expected.

Thanks for your help.

R.

seth · 2024-04-28 16:30:39

I'd say you probably lack https://archlinux.org/packages/extra/x86_64/kio-extras/ but dolphin has that as dependency - how exactly does it fail to connect the LAN?

Not the same KDE experience I expected.

It's unfortunately exactly what I expect

Last edited by seth (2024-04-28 16:30:51)

ralvez · 2024-04-28 16:41:54

When I do sftp://192.168.1.x to access an endpoint it responds: "Communication with the local password server failed"
However, if I ssh it works just fine.

BTW, I also wonder if this is related to KWallet. The wifi continues to disconnect and I have to manually type the password for the wifi as if KWallet does not know it. And I think that since it quotes the "local password server" these events may be related.

Last edited by ralvez (2024-04-28 16:44:14)

seth · 2024-04-28 16:48:49

Yes, that's still the original error and most likely kwallet or rather polkit related.
Do you have kwallet and https://archlinux.org/packages/extra/x8 … shaskpass/ installed and are they running?
And do you have these environment variables, https://wiki.archlinux.org/title/KDE_Wa … assphrases ?

ralvez · 2024-04-28 17:26:52

Yup. Definitely something is up with KWallet.
I've set it up using things like:
- Unlock KDE Wallet automatically on login,
- Using the KDE Wallet to store ssh key passphrases
- Store GPG key passphrases
- Automatic D-Bus activation

Then I rebooted and now when I try to log into the wallet it does not recognize my password. Grrr!

ralvez · 2024-04-28 17:46:34

Well ... I ended up deleting the wallet and starting all over.
We'll see.

ralvez · 2024-04-28 18:06:59

Well ... kdewallet has the WiFI password because I can see it.
Yet, after a few mins. it disconnected and I had to use the wifi password to re-connect because it does not re-try by itself. Frustrating.
And the same issue persist with dolphin.

I'm beginning to think that installing Plasma was a mistake.

seth · 2024-04-28 21:33:54

Yet, after a few mins. it disconnected and I had to use the wifi password to re-connect because it does not re-try by itself. Frustrating.

I'll assume you're using networkmanager which is decently chatty.

=> Check/post the system journal covering the incident.
For the current boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

ralvez · 2024-04-28 21:55:45

Hey seth,

I had some progress.
I can log into the local LAN services using sftp. Yay!!
The one thing that is a total bummer and a constant pain is the wifi.

It connects fine, but if it disconnects for whatever reason it will not reconnect automatically and I have to re-enter the password 2 or 3 times.

I tried using netctl and dhcpcd and disabled kdewallet but it was not a solution either.

I've been at this for over 6 hours now and getting to be pretty frustrated as you can imagine.

ralvez · 2024-04-28 22:02:24

Here is the file you asked

seth · 2024-04-28 22:54:16

Apr 28 17:44:15 snake-eyes wpa_supplicant[522]: Delete '/run/wpa_supplicant/wlp2s0' manually if it is not used anymore
Apr 28 17:44:15 snake-eyes wpa_supplicant[522]: Failed to initialize control interface '/run/wpa_supplicant'.
                                                You may have another wpa_supplicant process already running or the file was
                                                left by an unclean termination of wpa_supplicant in which case you will need
                                                to manually remove this file before starting wpa_supplicant again.

You also run networkmanager and dhcpcd concurrently - disable the latter.

Your conky WAN IP script is incompatible w/ python 3.12

Apr 28 17:44:38 snake-eyes conky[2860]: Traceback (most recent call last):
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/urllib/request.py", line 1344, in do_open
Apr 28 17:44:38 snake-eyes conky[2860]:     h.request(req.get_method(), req.selector, req.data, headers,
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1336, in request
Apr 28 17:44:38 snake-eyes conky[2860]:     self._send_request(method, url, body, headers, encode_chunked)
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1382, in _send_request
Apr 28 17:44:38 snake-eyes conky[2860]:     self.endheaders(body, encode_chunked=encode_chunked)
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1331, in endheaders
Apr 28 17:44:38 snake-eyes conky[2860]:     self._send_output(message_body, encode_chunked=encode_chunked)
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1091, in _send_output
Apr 28 17:44:38 snake-eyes conky[2860]:     self.send(msg)
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1035, in send
Apr 28 17:44:38 snake-eyes conky[2860]:     self.connect()
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1470, in connect
Apr 28 17:44:38 snake-eyes conky[2860]:     super().connect()
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/http/client.py", line 1001, in connect
Apr 28 17:44:38 snake-eyes conky[2860]:     self.sock = self._create_connection(
Apr 28 17:44:38 snake-eyes conky[2860]:                 ^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/socket.py", line 828, in create_connection
Apr 28 17:44:38 snake-eyes conky[2860]:     for res in getaddrinfo(host, port, 0, SOCK_STREAM):
Apr 28 17:44:38 snake-eyes conky[2860]:                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/socket.py", line 963, in getaddrinfo
Apr 28 17:44:38 snake-eyes conky[2860]:     for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
Apr 28 17:44:38 snake-eyes conky[2860]:                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes conky[2860]: socket.gaierror: [Errno -3] Temporary failure in name resolution
Apr 28 17:44:38 snake-eyes conky[2860]: During handling of the above exception, another exception occurred:
Apr 28 17:44:38 snake-eyes conky[2860]: Traceback (most recent call last):
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/home/ralvez/.dotconfig/conky/wan-ip.py", line 9, in <module>
Apr 28 17:44:38 snake-eyes conky[2860]:     ip = urllib.request.urlopen('https://tnedi.me').read().decode('utf8')
Apr 28 17:44:38 snake-eyes conky[2860]:          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/urllib/request.py", line 215, in urlopen
Apr 28 17:44:38 snake-eyes conky[2860]:     return opener.open(url, data, timeout)
Apr 28 17:44:38 snake-eyes conky[2860]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes conky[2860]:   File "/usr/lib/python3.12/urllib/request.py", line 515, in open
Apr 28 17:44:38 snake-eyes conky[2860]:     response = self._open(req, data)
Apr 28 17:44:38 snake-eyes conky[2860]:                ^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes ksmserver[2858]:   File "/usr/lib/python3.12/urllib/request.py", line 532, in _open
Apr 28 17:44:38 snake-eyes ksmserver[2858]:     result = self._call_chain(self.handle_open, protocol, protocol +
Apr 28 17:44:38 snake-eyes ksmserver[2858]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes ksmserver[2858]:   File "/usr/lib/python3.12/urllib/request.py", line 492, in _call_chain
Apr 28 17:44:38 snake-eyes ksmserver[2858]:     result = func(*args)
Apr 28 17:44:38 snake-eyes ksmserver[2858]:              ^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes ksmserver[2858]:   File "/usr/lib/python3.12/urllib/request.py", line 1392, in https_open
Apr 28 17:44:38 snake-eyes ksmserver[2858]:     return self.do_open(http.client.HTTPSConnection, req,
Apr 28 17:44:38 snake-eyes ksmserver[2858]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 28 17:44:38 snake-eyes ksmserver[2858]:   File "/usr/lib/python3.12/urllib/request.py", line 1347, in do_open
Apr 28 17:44:38 snake-eyes ksmserver[2858]:     raise URLError(err)
Apr 28 17:44:38 snake-eyes ksmserver[2858]: urllib.error.URLError: <urlopen error [Errno -3] Temporary failure in name resolution>

But appaerntly NM didn't have to ask for a password?

Apr 28 17:44:39 snake-eyes NetworkManager[455]: <info>  [1714340679.5765] device (wlp2s0): Activation: (wifi) access point 'IT2Wifi' has security, but secrets are required.
Apr 28 17:44:39 snake-eyes NetworkManager[455]: <info>  [1714340679.8917] device (wlp2s0): Activation: (wifi) connection 'IT2Wifi' has security, and secrets exist.  No new secrets needed.

pam however fails to open kwallet

Apr 28 17:44:23 snake-eyes sddm-helper[857]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Apr 28 17:44:27 snake-eyes systemd[832]: Started Unlock kwallet from pam credentials.
Apr 28 17:44:27 snake-eyes pam_kwallet_init[1127]: 2024/04/28 17:44:27 socat[1127] W address is opened in read-write mode but only supports read-only
Apr 28 17:44:27 snake-eyes kwalletd6[858]: kf.wallet.kwalletd: Wallet failed to get opened by PAM, error code is -9

Doesn't look like you're auto-login'ing.
https://wiki.archlinux.org/title/KDE_Wa … figure_PAM
Different password or ("ended up deleting the wallet and starting all over") not using the (default) "kdewallet" wallet?

ralvez · 2024-04-28 23:32:53

Thanks for all the help.
I did not do anything originally for SDDM because the arch info says: "For SDDM no further edits should be needed because the lines are already present in /etc/pam.d/sddm."

However, I just added the "force_run" because it did not have that instruction in mine.

And I do have the ~/.config/environment.d/ssh_askpass.conf :

SSH_ASKPASS=/usr/bin/ksshaskpass
SSH_ASKPASS_REQUIRE=prefer

The thing I'm unclear though is which file I should edit to auto unlock KWallet.

NOTE: This code

exec --no-startup-id /usr/lib/pam_kwallet_init

Last edited by ralvez (2024-04-28 23:35:50)

ralvez · 2024-04-28 23:36:54

Oh! and I disabled dhcpcd.

seth · 2024-04-29 06:20:22

Is your default wallets name "kdewallet"? Is the kwallet password your login password?
What's the status quo on your network? The previous journal didn't show NM failing to obtain the wifi password (after a reconnect). Are you still being asked?
(Or only after login because your wallet doesn't open automatically)

ralvez · 2024-04-29 11:47:33

My default wallet was named "kdewalltet" and the password was my user login because the Arch instruction suggested I do so.
But if the wifi disconnects, it does not automatically re-connects.

Yesterday at the end of the day I decided to delete the wallet and create a new one I gave it a different name but the same user password.

I'm not sure it makes a difference BUT the connection did not drop or got disconnected. ( I guess we can say is a win? )

At this point I'm not sure if "auto login" is running but so far I have not been asked. Fingers crossed.

Last edited by ralvez (2024-04-29 11:48:43)

ralvez · 2024-04-29 12:42:40

Well ... I can confirm that I'm not auto-logged.
The wifi dropped and I had to enter the password like 5 times.
Then I decided to re-start NetworkManager and it connected. So frustrating!

ralvez · 2024-04-29 14:37:00

I'm trying something new.

I created /etc/sddm.conf.d/sddm.conf with a copy of /usr/lib/sddm.conf.d/default.conf

At the bottom I've added:

 exec --no-startup-id /usr/lib/pam_kwallet_init

I hope that will auto-login my user.

I also enabled

User=my_user
Session=plasma

Last edited by ralvez (2024-04-29 14:38:33)

ralvez · 2024-04-29 19:03:05

Well ... after much struggle and with heavy heart I installed Ubuntu (Dell default Linux distro for this laptop).
Aside from the issues with the wifi I noticed that the power consumption was ridiculous. After closing the laptop for the night in the morning it had only 2% battery but at the end of the day it was at 45%.

So ... I guess is not an Arch friendly laptop and I do not have enough time to play with it. May be I'll try again when I have more time using something else OTHER than KDE.

I'm disappointed because with Arch the laptop was supper responsive. Loved it. Also all my systems are Arch and I'm not versed in the world and Ubuntu but it will have to be for awhile.

Thanks for all the help. I appreciate it.

Last edited by ralvez (2024-04-29 19:08:45)

seth · 2024-04-29 22:51:44

Check (on ubuntu, this is rather not gonna change)

cat /sys/power/mem_sleep

You might be limited to s2idle and either did not conffigure the system for suspend-then-hibernate or the hibernation failed.

---

I'm not sure it makes a difference BUT the connection did not drop or got disconnected

The connection is not supposed to drop depending on kwallet, the latter will only impact whether you might have to re-enter teh wifi passsword in case that happens (though iirc NM can also just store the password on disk in plain text)

The wifi dropped and I had to enter the password like 5 times.
Then I decided to re-start NetworkManager and it connected. So frustrating!

For clarification, the NM restart did not require you to re-enter the wifi password?
(Where the previous reconnects did?)

Yesterday at the end of the day I decided to delete the wallet and create a new one I gave it a different name but the same user password.

According to the wiki only the default "kdewallet" gets unlocked by pam, everthing else will require you to enter the password into kwallet.

I hope that will auto-login my user.

Probably not, also that looks like an i3 "exec" stanza?

Arch Linux

#1 2024-04-28 03:18:41

Communication with the local password server failed [unsolved]

#2 2024-04-28 06:58:08

Re: Communication with the local password server failed [unsolved]

#3 2024-04-28 16:13:11

Re: Communication with the local password server failed [unsolved]

#4 2024-04-28 16:30:39

Re: Communication with the local password server failed [unsolved]

#5 2024-04-28 16:41:54

Re: Communication with the local password server failed [unsolved]

#6 2024-04-28 16:48:49

Re: Communication with the local password server failed [unsolved]

#7 2024-04-28 17:26:52

Re: Communication with the local password server failed [unsolved]

#8 2024-04-28 17:46:34

Re: Communication with the local password server failed [unsolved]

#9 2024-04-28 18:06:59

Re: Communication with the local password server failed [unsolved]

#10 2024-04-28 21:33:54

Re: Communication with the local password server failed [unsolved]

#11 2024-04-28 21:55:45

Re: Communication with the local password server failed [unsolved]

#12 2024-04-28 22:02:24

Re: Communication with the local password server failed [unsolved]

#13 2024-04-28 22:54:16

Re: Communication with the local password server failed [unsolved]

#14 2024-04-28 23:32:53

Re: Communication with the local password server failed [unsolved]

#15 2024-04-28 23:36:54

Re: Communication with the local password server failed [unsolved]

#16 2024-04-29 06:20:22

Re: Communication with the local password server failed [unsolved]

#17 2024-04-29 11:47:33

Re: Communication with the local password server failed [unsolved]

#18 2024-04-29 12:42:40

Re: Communication with the local password server failed [unsolved]

#19 2024-04-29 14:37:00

Re: Communication with the local password server failed [unsolved]

#20 2024-04-29 19:03:05

Re: Communication with the local password server failed [unsolved]

#21 2024-04-29 22:51:44

Re: Communication with the local password server failed [unsolved]

Board footer