Users and Groups assigned to shares changes after logout / restart

[Jesse-Dur]

Users and Groups assigned to shares changes after logout / restart

[adams13x13]

I can confirm, cockpit-file-sharing 3.3.4-1focal under Proxmox virtual environment 7.4-17 server, Google Chrome under Linux client.

To better reproduce:

Create 4 shares with different user assignments in the following order: "Share_4", "Share_3", "Share_2", "Share_1".
After "page reload" in web browser the user assignments are exchanged.

Share_1 gets users from Share_4,
Share_2 gets users from Share_3,
Share_3 gets users from Share_2,
Share_4 gets users from Share_1.

The same happens if I export configuration to a file on my computer and import it ("page reload" is required to be able to export, see #86).

User assignments in the exported file (cockpit-file-sharing_samba_exported_....conf) are correct, however in the reverse order (4-3-2-1).

User assignments in the system (as seen with 'sudo testparm') are correct, however in the reverse order like in the exported file.

If I edit any share and close it with "confirm" without any change, the (wrong) user assignment that was on the screen is saved in the export file and in the result of 'sudo testparm'.

It looks the problem is only that the GUI elements are initialized in the wrong order and than they keep this wrong information. The first share item in the alphabetically sorted list gets the users of the first created share item and so on.

[ofotache]

I can confirm, experiencing it on Raspberry Pi OS bookworm arm64.
It can be reproduced by refreshing the page.
I've discovered that the user assigned persists, even if it doesn't show up anymore, this can be tested by exporting the config the user is still in conf.

3.3.4-1focal_all.deb