Workspaces Don't Save on Exit (ArchLinux)

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

A workspace will be created, but remain identical to the "default" workspace if
1. The UI is changed by dragging panels around.
2. A workspace is created from the modified layout using either the "Create New Workspace" or "Save Layout as New Workspace" button.
3. The file is saved and then exited.
Upon re-entering any file, the workspace will load as if it was the default workspace.

A workspace will be temporarily created, and deleted upon reload if
1. The UI is changed by dragging panels around.
2. A workspace is created from the modified layout using either the "Create New Workspace" or "Save Layout as New Workspace" button.
3. The file is not saved, and the user exits the software.
Upon entering any file, the created workspace will no longer be listed.

I notice aspects of the workspace do actually save, such as modifications to what is listed on the top toolbar, but I can't exactly imagine this feature is working as intended if that's the only thing that workspaces affect.

Supporting files, videos and screenshots

A 2 minute video showing a few variations of the bugged behavior.

In which versions of MuseScore Studio is this issue present?

4.7.2

Regression

I was unable to check

Operating system

Arch Linux (SteamOS)

Additional context

I have gotten a workspace to save exactly once. It was at least a few versions ago, perhaps 4.5.x
During my attempts at filming this bug in action, I have killed that workspace. Rest in peace, I guess...
I chose not to mark this bug as a regression because I remember getting it to save even back then was a miracle.

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

No source file or test is named. First reproduce the workspace creation, save, exit, and reload flows on Arch Linux, then trace the workspace persistence and loading entry points. Done means layouts created after dragging panels survive both saved and unsaved exits and remain available after reopening a file.