Chromebook plus Acer, debian Linux container

After installing the official MuseScore 4.5.1 AppImage on a fresh Linux (Beta) environment on my Chromebook, the application opens but freezes when attempting to click certain icons or elements, specifically and reliably when clicking the "New Score" action.

Steps Taken to Troubleshoot:

Performed a clean start of the Linux (Beta) environment by removing and re-enabling it via Chrome OS settings.
Downloaded the official MuseScore 4.5.1 AppImage.
Installed necessary libraries including fuse, libnss3, libjack-dev, and libglvnd0 using sudo apt install.
Attempted to launch the AppImage directly and via the desktop icon; initially, the app would open but the UI was frozen. Terminal output showed libOpenGL.so.0 missing, QML "Binding loop detected" errors, MuseSampler errors, and file read errors.
Disabled the crostini-gpu-support flag in chrome://flags and fully restarted the Chromebook. This did not resolve the freezing or change the initial terminal errors.
Discovered that launching the application with the QT_GRAPHICSSYSTEM=raster or QT_GRAPHICSSYSTEM=software environment variable allowed the app to open and become partially responsive, enabling interaction with many UI elements. Example command: QT_GRAPHICSSYSTEM=raster "/home/martinecline/.local/bin/MuseScore-Studio-4.5.1.250800846-x86_64 (1).AppImage"
Tried reverting MuseScore to factory settings using the -F flag in combination with the QT_GRAPHICSSYSTEM variable. This did not resolve the specific freeze on "New Score".
Current Specific Issue:

With MuseScore launched using QT_GRAPHICSSYSTEM=raster (or software), the main application window appears and most buttons are interactive. However, clicking the "New Score" button/action causes the application UI to freeze completely.

Terminal Output When Clicking "New Score" (after initial launch messages):

The terminal shows the following specific output at the moment of clicking "New Score" and the freeze occurs:

[Paste the specific output lines you provided, starting from "ActionsDispatcher::doDispatch..." and including the QML errors like "QQmlComponent: Created graphical object...", "TypeError: Cannot read property 'iconColor'", and "Cannot assign to non-existent property 'sync']

Example lines:
14:52:06.842 | WARN | main_thread | Qt | QQmlComponent: Created graphical object was not placed in the graphics scene.
14:52:06.846 | ERROR | main_thread | GuiApp::perform | error: qrc:/qml/Muse/UiComponents/internal/StyledMenuItem.qml:205: TypeError: Cannot read property 'iconColor' of null
...
14:52:08.074 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: file-new
14:52:08.114 | WARN | main_thread | Qt | qrc:/qml/Muse/Ui/InteractiveProvider.qml:179: Error: Cannot assign to non-existent property "sync"
(Include any other lines that appeared concurrently)

Additional Information:

The initial startup terminal output (before clicking "New Score") consistently shows messages about missing libOpenGL.so.0, QML "Binding loop detected" errors, MuseSampler errors, and configuration file read errors, even when launched with QT_GRAPHICSSYSTEM and after disabling the Chrome OS GPU flag. (I can provide the full startup log if needed).

Request:

Could you please investigate this specific freezing issue when clicking "New Score" on Chromebook Linux using the AppImage? It appears to be related to QML rendering within the "New Score" workflow, possibly highlighting a compatibility issue with the platform's graphics stack despite attempted workarounds.