Cannot change Chord Symbol durations settings from default on STYLE PAGE

[PV000001]

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Musecore 4.7.4 on OS Ubuntu 24.04.4 LTS downloaded from https://musescore.org/en/download/musescore-x86_64.AppImage
Result: MuseScore-Studio-4.7.4.260706075-x86_64.AppImage

1. Create a guitar line using slashes to create various rhythm and note/chord durations including rests.
2. Above the slashes add chord symbols.
3. Play the test line.
   RESULT: All chords sustain until the next chord. (DEFAULT BEHAVIOR.)

CASE:
I want the chord durations to match the slash notations including rests.

5. Right click on a chord symbol and select STYLE.
6. Style page displays.
7. Scroll to bottom and in the section PLAYBACK attempt to change the default behavior from "Until Next Chord Symbol" to "Chord/Rest Duration."
   RESULT: No attempts at clicking the desired third selection at the bottom will change the option list selection.
8. Click OK.
9. Play the test line again to verify behavior has not changed.
10. Test the other option lists on the style page.
    RESULT: No option lists can be changed from default.
    SEE CLOUD URL RECORDING of FAILED UI INTERACTIONS.

Attempted Solution.
On the same Styles page I clicked Reset All Styles to default. RESULT = No Change
At main menu Help Revert to Factory. RESULT = No Change

Other Diagnostics:
Launched Audacity and the EDIT SETTINGS screen which also has option drop down list widgets and they worked correctly.

Supporting files, videos and screenshots

https://mega.nz/file/25RnEQja#9mp7T7FREp0Bz9rN4vMQZMBmA5oWnmw16F7-F9KiK2Y

In which versions of MuseScore Studio is this issue present?

TESTED same behavior on Musecore 4.7.4 and 4.7.3

Regression

I was unable to check

Operating system

Ubuntu 24.04.4 LTS

Additional context

Running MuseScore AppImage as executable "Run as Program." For many past versions and current version no attempted procedure (many tried) will "install" the appimage. NOTE: Exept for this UI feature all other features of the program I use appear to function without any known issues.

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

[MarcSabatella]

Are you saying you are trying to operate the dropdowns normally - by clicking to open the menu, then clicking the desired item - and the item you are clicking does not actually select? It's working fine for me. Are by chance attempting to force MuseScore to use Wayland using the undocument/experiment environment variable for this? It's not supported and basically known not to work. Are other dropdowns working for you in MuseScore?

If you are having trouble that is not due to forcing Wayland, please attach the specific score with the problem, in case it turns out to somehow be specific to something about it.

BTW, to install the AppImage, simply run it from the command line with the "install" option. If you experience some sort of issue with that, please ask for help in the official Support forum at musescore.org and give more details on what goes wrong.

[PV000001]

I don't know what you mean "Force Wayland." I'm not doing this intentionally. I click on the selections as they are highlighted in the drop-down moving the mouse as you see in the demo and the highlighted item does not select when I click. Also as you can see from the recording none of the dropdowns on that Style page are working for me. Also mentioned in my initial report drop downs in another program are working. I'm performing the same action in both programs. I tested another MuseScore drop-down option in the Staff Properties -> Transposition and as I have used that in the past successfully verified that option still works properly. I'm not doing anything different to select that tool than the ones which do not work.

As far as installing I have asked more than once in the forum for several years and have attempted to apply all the suggestions. Techniques which used to work no longer work. That however is the least of my concerns.

Link to TEST score used in issue recording from the initial report:
https://mega.nz/file/DkQVSJ7C#ejLPJLlX_Yj2QUE8ob1ttN-w9kbXmRf3TK4jrqV_fzE

[MarcSabatella]

There is an environment variable you can use - MU_QT_QPA_PLATFORM that you can use to force MuseScore to use Wayland instead of X11. Please be sure this variable is not set in your environment.

When I asked about other dropdowns, I meant, other than in the Style dialog. How about dropdowns in Preferences, or Properties? Also does it work if you use the cursor keys to select the elements, and Enter to confirm?

[PV000001]

You realize twice in this initial report I specified I'm running MuseScore on Ubuntu Linux? I assume "Wayland" is a Windows thing which I'm not using. I'm assuming at this point the reason others are not reproducing the issue is they are using Windows to test. This error might be Linux specific.

In answer to:
" How about dropdowns in Preferences, or Properties? Also does it work if you use the cursor keys to select the elements, and Enter to confirm?"
I will echo what I already posted above:
" I tested another MuseScore drop-down option in the Staff Properties -> Transposition and as I have used that in the past successfully verified that option still works properly. I'm not doing anything different to select that tool than the ones which do not work."

As far as using cursor keys to select and enter... Those do not work at all.
Cursor keys completely unresponsive on the Style Page in question. If I tap ENTER while the mouse is highlighting a selection ENTER has no effect.

[MarcSabatella]

No, Wayland is very much specific to Linux. And this all works just fine on other Linux systems, except those forcing MuseScore to run under Wayland. .so again, please check. Actually, try reporting the output of "env | grep QT".

And sorry, I see that you did indeed answer the question about other dropdowns within MuseScore.

I'm assuming there is something unusual about system configuration that is triggering this. If it's not Wayland, though, it isn't clear what. Maybe something specific to your mouse or display drivers...are things like clicking small items (staccato dots, say) working as they should?

[PV000001]

"env | grep QT"
Result:
QT_ACCESSIBILITY=1
QT_IM_MODULE=ibus

All other control features on all other configuration pages are working (as far as I have tested.)
Strange if Wayland is the fault why only broken on that style page?

[MarcSabatella]

Well, the style dialog is one of the few that is leftover from MU3 and not reimplemented using QML, so it definitely has behaviors the others don't (and vice versa). But on some systems running Wayland, some dropdowns in MuseScore don't open at all while others do (see for example #28775), and in other cases clicking is off by a few pixels through the app (see for example #31024). And that's why I asked if you can select staccato dots normally - that would be the most obvious symptom if this problem existed. Can you please test that?

Even though you don't have the environment variables set to force Wayland, it could be something else on your system is forcing it (like not having an alternative installed). Please try:

QT_QPA_PLATFORM=xcb mscore4portable

(after having installed MuseScore as explained above, or replace "mscore4portable" with the filename you normally use otherwise).

I'm not saying I know this is a Wayland issue; I'm saying it's the first thing that comes to mind that could explain this behavior and why I don't see it on my Linux systems.

But FWIW, there have also been reports of problems here and there using ibus, but that's usually having to do with keyboard, not mouse. And I tried setting QT_IM_MODULE=ibus and had no issues. There could still be something to this, but I doubt it.

Although I'm not able to reproduce this issue (and I can't test with Wayland because it crashes on startup for me), one thing I do see that might well be related it, the cursor keys do not appear to work on the dropdowns on this page of the dialog. That is, hitting Down after opening one of the dropdowns on the "Chord symbols" does not change which item appears highlighted, and there is no screenreader feedback. However, it does actually work - if I hit Down and then Enter, the item below originally-selected item is now selected. Other pages work as expected.

There is also a visible difference between these dropdowns and others. Compare this dropdown which works normally with the keyboard:

versus this one which doesn't:

I'm thinking this is unlikely to be a coincidence - whatever is breaking keyboard input on my system (Debian 12) might be the same thing breaking mouse input on others.

[PV000001]

I'm currently testing MuseScore as an INSTALLED application. Nothing has changed in the previously reported behavior.

The only place I could find dots lists in the UI is in the Add Pallets Sidebar. Those are all working. I believe I have noted NOT ALL dropdowns are affected. I found one other location in the STYLES pages which has a broken dropdown:
MEASURE NUMBERS -> TEXT STYLE frame -> Measure Number
All others I have tested in MuseScore seem to work normally.

I executed the command:
QT_QPA_PLATFORM=xcb mscore4portable

Result:
Nothing changed in the error behavior so far reported.

Are you still convinced my system is using Wayland? If it is, it's not something I would have installed on purpose.

ADDED (working solution):
I fiddled with the idea you suggested of tapping ENTER while the mouse was over a selection. Doing that I was able to get the selection to change but it was tricky. I never got the item I thought was selected and had to keep trying until the one I wanted worked.
As you noted the color selection of the mouseover seems to be broken and perhaps yet another error behind this on these affected dropdowns where the id/element in an array is scrambled.

Bottom line... Per your suggestion I have a working temporary solution and these dropdowns are items I'm not likely to change once I have them set. If it's a flaw in my system I would be interested in discovering what it is and why not all dropdowns in the program are affected.
It's suspicious that all dropdowns on this particular Style page are affected. These are symptomatic of copy/paste errors from my experience.

[MarcSabatella]

Again, I'm not convinced at all - it just seemed the most obvious candidate based on the symptoms. And no, Wayland is not something you'd have installed - it is a part of most Linux systems, along with X11, as one of the two main display servers available to programs to use in putting things on your screen. But I'm more and more seeing it's not likely to connected to Wayland.

When I aslked about clicking a staccato dot, I mean in your score. Sometimes issues like this happen because the mouse pointer is somehow out of sync with the display, such as due to confusion over high DPI scaling. When this happens, in order to select something, you may actually have to click a short distance to the side or above or below the item you are attempting to select. So I want to know if selecting a staccato dot in a score seems like this is the case. And if so, does clicking a similar distance away from the drodown change anything.

[PV000001]

Right Clicking a staccato dot brought up the Articulations style page as expected. Is this what you wanted?
Purposely clicking away from the dot selected the measure as expected.

RESOLUTION 1920*1080
I usually do not have trouble clicking score elements.