On 14/11/18 8:14 am, Ed Greshko wrote:
On 11/14/18 5:03 AM, Stephen Morris wrote:
> It's possible it is environmental, but if it is how do I identify what is causing
> given that this was not always the functionality with nm on my system, and from my
> perspective it surfaced on a cold boot after putting on system maintenance.
Well, the first thing I would do is to create a new user account and see if that account
acts the same as the one you are using now. That should narrow it down to user space or
I tried an existing user account that hasn't been used for over 3 years
and it had the same issue.
I also created a new user and it behaved similarly but slightly
differently. When I logged in with the new user I made the mistake of
not changing the default so it logged into Gnome, and when Gnome started
Networkmanager had a definition for ethernet and my wifi even though
they had not been explicitly set up, and the wifi definition had the
correct password for my router as the network was connected.
I logged out of Gnome and logged into KDE, and went into the
networkmanager wifi definition and deliberately set the wifi password to
an incorrect entry from the correct entry that the definition had. The
incorrect entry was not retained and neither was the correct entry
blanked out like in the original issue, or something was overwriting the
incorrect entry with the correct one.
Having gotten this issue with the new user account I checked
kwalletmanager5 on that account and kwalletmanager5 was completely
empty, as it is if I run kwalletmanager5 under root. I installed
pam-kwallet after getting the issue, which stopped the prompt for the
kwallet password when it was being accessed, so I don't know if that is
impacting what is occurring relative to the correct wifi password being