You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start Agama Live CD locally (this client is for changing the settings)
Setup network
Connect also remotely (this client is for checking the state), stay on the main page and see what happens
Some settings are updated when changed, some not. These were done with the local client and observed at the remote one:
Change software selection - NOT changed in the other client's screen
Localization - language - Changes after accepting the new lang, also updates the Software from the previous change
Changing storage - Changes even while still playing with storage inside the Storage screen
Changing user - When the root password is set, the second client shows some kind of busy progress, but does not finish updating the section
After changing the language, User progress stops, but still does not update the screen (if I then use the second client to see the user settings and back, it's updated properly)
The same behavior can be seen when local client and remote client exchange their positions. It's easy to reproduce, so I can attach any logs you tell me when needed.
The text was updated successfully, but these errors were encountered:
@jreidinger wanted to know if changing the Product refreshes the info. Yes, it changes the Product, Storage and Software on the other client. So this part works as expected IMO.
@jreidinger wanted to know if changing the Product refreshes the info. Yes, it changes the Product, Storage and Software on the other client. So this part works as expected IMO.
I mean different one. When you see initial screen with product selection on both browsers and select product on one of them. I have feeling that I see no refresh when I set it using CLI.
Simple scenario:
Some settings are updated when changed, some not. These were done with the local client and observed at the remote one:
The same behavior can be seen when local client and remote client exchange their positions. It's easy to reproduce, so I can attach any logs you tell me when needed.
The text was updated successfully, but these errors were encountered: