is this during the installation of the live image?

if so would be an issue of the distro, as they are curating the installation procedure

Setting status, since we're waiting on a reply

(In reply to Marco Martin from comment #1)
> is this during the installation of the live image?
> 
> if so would be an issue of the distro, as they are curating the installation
> procedure

This is aarch64. A flashed ssd for a Rpi 4 using the Fedora Rawhide 44 KDE image. Upon first boot plasma setup starts asking for user name and so on. On the screen where it asks for a network connection, I selected my wifi router and entered the password. A check mark then shows confirming connection. When plasma setup is complete it then restarts the system. I can log in using the account I just created but it didnt save or remember the network connection I had already made during plasma setup. I then need to reconnect to my wifi router and it then works as expected. 

Hope this helps.

> Its like it didn't save my network connection settings.
Did it? Or didn't it?

IIRC plasma-setup relies on the assumption that network credentials are now stored globally, rather than per-user in KWallet (which is a Plasma 6.6 change). Look in /var/lib/NetworkManager/ and see if the network credentials are there.

(In reply to Nate Graham from comment #4)
> > Its like it didn't save my network connection settings.
> Did it? Or didn't it?
> 
> IIRC plasma-setup relies on the assumption that network credentials are now
> stored globally, rather than per-user in KWallet (which is a Plasma 6.6
> change). Look in /var/lib/NetworkManager/ and see if the network credentials
> are there.

Well I was trying to say it did not. Thus, after reboot I had to select my wifi and enter my password again and it works as expected.  So, when plasma setup asks for network credentials, select wifi, enter password, I see a check noting the good connection. It did not remember this info after the initial re boot. It remembered the login info fine. When I can ill re-flash another image for the Rpi 4 and run the setup again. 

Ill see if I can look at Network Manager after the initial setup before the reboot.

The network credentials should be under /etc/NetworkManager/system-connections/ and likely named $SSID.nmconnection

If you do run another install, pasting the contents (before manually re-connecting it) of that here would be helpful (just remove your network password from the pasted output).

(In reply to Kristen McWilliam from comment #6)
> The network credentials should be under
> /etc/NetworkManager/system-connections/ and likely named $SSID.nmconnection
> 
> If you do run another install, pasting the contents (before manually
> re-connecting it) of that here would be helpful (just remove your network
> password from the pasted output).

Ok thank you!

Created attachment 189151 [details]
Network Manager SSID

Repro'd on Fedora Rawhide (x86), it seems like something in the Fedora config has changed things.

When connecting to wifi it first shows the password dialog from plasma-setup, but after submitting it there is a password dialog from plasma-nm, which doesn't happen on other systems I have tested.

The end result is that the connection config gets the permissions line inside the [connection] block that it isn't supposed to get anymore by default, e.g.:

```
[connection]
id=$SSID
uuid=...
type=wifi
interface-name=$INTERFACENAME
permissions=user:plasma-setup:;
```

I have a feeling this is an issue specific to the Fedora configuration rather than plasma-setup.

(In reply to Kristen McWilliam from comment #9)
> Repro'd on Fedora Rawhide (x86), it seems like something in the Fedora
> config has changed things.
> 
> When connecting to wifi it first shows the password dialog from
> plasma-setup, but after submitting it there is a password dialog from
> plasma-nm, which doesn't happen on other systems I have tested.
> 
> The end result is that the connection config gets the permissions line
> inside the [connection] block that it isn't supposed to get anymore by
> default, e.g.:
> 
> ```
> [connection]
> id=$SSID
> uuid=...
> type=wifi
> interface-name=$INTERFACENAME
> permissions=user:plasma-setup:;
> ```
> 
> I have a feeling this is an issue specific to the Fedora configuration
> rather than plasma-setup.

Ok yes can confirm. The second dialog seem to be a new one. The passwords work and the initial step to connect to network seem fine. When plasma setup is complete and the system restarts, the initial step to connect to the network is not remembered. I can log in fine but im disconnected from the network. Can re-connect and enter password fine. Still want to confirm some things with the new Beta 2 out.

Ok so on our latest build for Fedora 44 Beta 1.1 this issue persists.  Again this is on bare metal Rpi 4. Ive only come across this issue on the Rpi4. During Plasma Setup its the only time I see a screen asking to connect to a network.

If this is a Fedora thing, can we  transfer this to Bugzilla?

Thanks

I don't know how it is a Fedora bug, because we don't have any particular modifications that would cause this.

The only changes we make to Plasma Setup was to use the Fedora look and feel package instead of the normal Plasma one.

(In reply to Neal Gompa from comment #12)
> I don't know how it is a Fedora bug, because we don't have any particular
> modifications that would cause this.
> 
> The only changes we make to Plasma Setup was to use the Fedora look and feel
> package instead of the normal Plasma one.

Thank you for clarifying. Had to reopen this. Ive only seen this on the Rpi 4. Hmmmm

Something has changed for Fedora's config of plasma-nm between F43 and F44… I can confirm this is an issue in a regular user session (not specific to raspberry pi) after initial setup, not specific to plasma-setup.

This works as expected on my F43 system & on KDE Linux:

*Correct Behaviour*

Connect to wifi network `Merritt` -> config is created at `/etc/NetworkManager/system-connections/Merritt.nmconnection` and the `[connection]` group has no `permissions` key.

Then on F44 Rawhide:

*Incorrect behaviour*

Connect to wifi network `Merritt` -> config is created at `/etc/NetworkManager/system-connections/Merritt-74033867-13bd-4541-94b3-923c57841384.nmconnection` and the `[connection]` group _does have_ the `permissions` key.

When setup with plasma-setup it is `permissions=user:plasma-setup:;` and when setup from a regular session it is `permissions=user:merritt:;` (`merritt` being whatever the username is). So when plasma-setup does it, the new user doesn't have access because the connection has been set for only the plasma-setup user. When the new user sets the connection, that is overwritten with that user's permission — but it still isn't a global connection like it should be.

Fedora 43 has NetworkManager 1.54, while Fedora 44 and Rawhide have NetworkManager 1.56. So perhaps the difference is there?

Possibly — it works as expected on KDE Linux and it is still using NetworkManager 1.54.3

Then perhaps this is a NetworkManager bug, because plasma-nm and plasma-setup are just talking to NetworkManager via its API, as far as I know.

This has been reproduced on standard x86_64 Fedora 44 now: https://bugzilla.redhat.com/show_bug.cgi?id=2455469

Hmm. So these are the commits with 'permission' in them between 1.54.0 and 1.56.0:

[adamw@toolbx fedora-toolbox-43 NetworkManager (main)]$ git log -S 'permission' --oneline --name-status 1.54.0..1.56.0
3d85bace3d libnm: add function to copy a certificate or key as user
M       NEWS
M       src/libnm-core-impl/nm-utils.c
8437e14758 vpn: add nm_vpn_plugin_info_supports_safe_private_file_access()
M       src/libnm-core-impl/nm-vpn-plugin-info.c
aac5b80fca core: pass certificates as blobs to supplicant for private connections
M       NEWS
M       src/core/devices/nm-device-ethernet.c
M       src/core/devices/nm-device-macsec.c
M       src/core/devices/wifi/nm-device-wifi.c
M       src/core/supplicant/tests/test-supplicant-config.c
a417df3484 device: read private files in stage2
M       src/core/devices/nm-device.c
2fc662cc71 libnm-core, core: add permission helpers
M       src/core/nm-core-utils.c
M       src/core/nm-core-utils.h
M       src/libnm-core-impl/nm-setting-connection.c
M       src/libnm-core-intern/nm-core-internal.h
0530af60b3 Squashed 'src/n-acd/' changes from a600afc870..6ac6f7e105
M       src/n-acd.c
```
I had a poke through but none of them is a screamingly obvious culprit at first glance. But they're mostly by Beniamino Galvani, so I'll get in touch and see if he can shed any light here.

OK so I've traced this out a ways. I think this is the important bit:

https://invent.kde.org/plasma/plasma-nm/-/blob/5ec60ac4699621706dfc7cd08351028f005fd793/libs/editor/uiutils.cpp#L687

UiUtils::setConnectionDefaultPermissions() . Note how it does different things depending on whether the calling user has "org.freedesktop.NetworkManager.settings.modify.system" set to "yes". If it's yes, it creates a system-wide connection. Otherwise, it creates a user-specific connection (one with the 'permissions=' string that lets only that user use the connection).

The way we get here is that plasma-setup modules/wifi/contents/ui/ConnectDialog.qml and/or modules/wifi/contents/ui/main.qml calls PlasmaNM.Handler.addAndActivateConnection() , which - at least for wifi connections? it seems like it does nothing for non-wifi connections, which is a little odd - calls UiUtils::setConnectionDefaultPermissions(settings); .

Note that plasma-setup has this rather odd commit: https://invent.kde.org/plasma/plasma-setup/-/commit/f8018622e3d27c9133a56def8f7c58be16b9c178

The message is "wifi: Store password for everyone", which sounds like it's meant to fix this bug, but what it actually *does* is change the call in ConnectDialog.qml from:

addAndActivateConnection(devicePath, specificPath, passwordField.text);

to:

addAndActivateConnection(devicePath, specificPath, passwordField.text, PlasmaNM.Handler.StoreForAllUsers);

unless I'm missing something, this is pure nonsense. plasma-nm Handler::addAndActivateConnection - https://invent.kde.org/plasma/plasma-nm/-/blob/5ec60ac4699621706dfc7cd08351028f005fd793/libs/handler.cpp#L270 - takes three args. I can't find any other case of anything attempting to call anything called `addAndActivateConnection` this way, with a fourth arg that somehow indicates whether this should be a system-wide connection. It also doesn't look to me like PlasmaNM.Handler.StoreForAllUsers is actually a thing that exists. I don't know what the story is there. I'm somewhat surprised it doesn't blow up? Maybe we never actually reach this line for some reason?

Aha, OK, I've got the smoking gun in Fedora:

https://src.fedoraproject.org/rpms/NetworkManager/c/3c4f1bab8f65b330b3759fa75a2e66a50c3b96d2?branch=f44

Note that removes the -Dmodify_system=true build arg, i.e. we no longer give regular users the org.freedesktop.NetworkManager.settings.modify.system permission. That was changed between F43 and F44, so it lines up exactly with what we're seeing here.

I suspect the easiest/best short-term fix would be to have plasma-setup (not sure if upstream or downstream...) ship a polkit policy that grants it that permission. I'm not sure what the best long-term, cross-distro / cross-OS approach is.

Note for the non-plasma-setup case: this will depend on how your distro has that polkit permission setup, which depends on its NetworkManager build most likely. It will likely also matter whether your user is an admin or not.

If your user has that permission non-interactively, creating a connection will likely create a system-wide connection by default. If you have it interactively you'll likely see a password prompt when you try to create a connection. If you don't have that permission, creating a connection will give you one owned by your user.

A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-setup/-/merge_requests/98

Git commit 28f742ca4337850de1f5f450b9eb5a5d500f540e by Adam Williamson.
Committed on 15/04/2026 at 15:09.
Pushed by ngompa into branch 'master'.

fix: give us permission to create system-wide network connections

We need the org.freedesktop.NetworkManager.settings.modify.system
polkit action in order for any network connections we create to
be system-wide. Without this, they will be created tied to the
plasma-setup user, which is useless.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

M  +1    -0    files/plasma-setup-polkit.rules

https://invent.kde.org/plasma/plasma-setup/-/commit/28f742ca4337850de1f5f450b9eb5a5d500f540e

Git commit 98e207aee2d6d35ea9b0f64af0ae576e7f9cdde6 by Neal Gompa, on behalf of Adam Williamson.
Committed on 17/04/2026 at 19:36.
Pushed by ngompa into branch 'Plasma/6.6'.

fix: give us permission to create system-wide network connections

We need the org.freedesktop.NetworkManager.settings.modify.system
polkit action in order for any network connections we create to
be system-wide. Without this, they will be created tied to the
plasma-setup user, which is useless.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

(cherry picked from commit 28f742ca4337850de1f5f450b9eb5a5d500f540e)

M  +1    -0    files/plasma-setup-polkit.rules

https://invent.kde.org/plasma/plasma-setup/-/commit/98e207aee2d6d35ea9b0f64af0ae576e7f9cdde6