Cannot store network settings

Our Neighbors Asahi Linux Ask Asahi
1

Hi,
I have installed both KdePlasma and Hyprland profiles (with two distinct users) on my Fedora Asahi, and everytime I login&out I need to reconfigure networks. I found something similar may concern to other variables ( Reddit - Dive into anything ), but I am not sure.

Is there anyone experienced this issue?

thanks,

2

I once had the same problem and solved it by hand work.

There should be a file under /etc/NetworkManager/system-connections/{YOURNETWORKID}.nmconnection. Open and edit the contents you want to save.

For example, I had to type a password every time I connected to the wifi, so I saved the password in it:

[connection]
id=YOURNETWORKID
uuid=xxxxx
type=wifi
interface-name=wlp1s0f0
permissions=user:YOURUSERNAME:;

[wifi]
mode=infrastructure
ssid=YOURNETWORKID

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
leap-password-flags=1
psk-flags=1
wep-key-flags=1
psk=YOURPASSWORD

[ipv4]
method=auto

[ipv6]
addr-gen-mode=default
method=auto

Restart your NetworkManager and everything should be fine.

BTW, if you have trouble with Enterprise WIFI, that is another story, do:

nmcli c a type wifi con-name YOURNETWORKID ifname wlp1s0f0 ssid YOURNETWORKID -- wifi-sec.key-mgmt wpa-eap 802-1x.eap peap 802-1x.phase2-auth mschapv2 802-1x.identity YOURACCOUNTID 802-1x.password YOURPASSWORD

to solve it.

As for the system-wide authentication service you mentioned, polkit-kde-agent-1 above, you should execute it at the start of Hyprland. You don’t need to worry about this while at KDE

cat <<EOF >>~/.config/hypr/hyprland.conf
# Authentication Agent
exec-once = /usr/libexec/kf5/polkit-kde-authentication-agent-1
EOF # This makes sure the agent runs only once on the startup.

It takes effect when I utilize 1Password for GPG commit and ssh-agent

1 Like
3

That may also be a kwallet problem. In systemsettings you can check if you have a default wallet (has to be Blowfish encrypted and use your user/login password)

1 Like
4

Thank you both. Actually I did not have time to explore the topic. I tried to check the kwallet but I think the problem is not there. I tried to start from the beginning with a new configuration:

I logged in with the KDE-plasma profile, and I created a brand new connection associated with a WIFI (where I set to store password for all the users (not encrypted)) , the connection is set and work. But what appears in /etc/NetworkManager/system-connection is the new connection but “root-PROTECTED”.

5

Hi guys,
I come back here, because actually I did not solved my problem, as it appears not depending on network configuration, but much more on ID-account’s permissions. In short:

  1. switch on, dual boot (macOS, fedora-asahi)
  2. I log in KDE’s account, I set my “network1”. Even if I set “network1” as open to all users, in “/etc/NetworkManager/system-connections” it results as “locked”, then I unlock it.
  3. I log out from KDE, and log in in Hyprland’s account
  4. in Hyprland “network1” is not visible (even if is in “/etc/NetworkManager/system-connections” folder). I set new “network2”: same problem, it appears locked.
  5. I unlock and edit both configurations adding permissions=user:MYKDENAME:MYHYPRLANDNAME;
  6. I log out from Hyprland.
  7. then if I log in either in KDE and Hyprland, wifi connection is found!

BUT

  1. If I shutdown the computer and boot again, everytning is lost! I must create a brand new configuration from scratch (step 2)). Even if in “/etc/NetworkManager/system-connections” folder both previous configurations “network1” and “network2” are there! (But they are not recognized from the network manager.

As you can see, it is a multiple problem (the fact that it creates a “locked” configuration, that is not recognized across KDE-HyprLand, and that is lost upon rebooting!), a multiple problem that is generated from the same issue, I guess.

PS: Both profiles are as administrator.

any suggestion?

many thanks
T

6

That’s wrong, the correct syntax is:

permissions=user:foo:;user:bar:;

Or better remove this property to make it available to all users.

Be sure to restart the service to apply the changes:

sudo systemctl restart NetworkManager.service
1 Like
7

Thank you Vladislav. Actually the problem is exactly there!

I set the configuration (again it creates a “locked” file in /etc/NetworkManager/system-connections), I removed the line of permissions (as you suggested), then when I restarted NetworkManager.service the network connection, I just created, disappeared completely in the list (still there in the folder, but not available in the list of connections).

It disappears when I restart the service.

8

ok. Sorry guys. My mistake. I solved the problem.

The problem was mine: when I “unlocked” the permission of

/etc/NetworkManager/system-connections/MYCONNECTION

allowing the full operation from everyone (chmod 777), the file automatically turned to be “not usable” for NetworkManager.service which is a root service. All the problems came from this operation. I try to create the connection and I kept it like it was created, and everythings was fine!

Sorry for the confusion, the error was mine!, but at least I understood the origin of the problem.

thnx
R