A huge and important question is IF you use a Wayland or X11 session. Because this remember me by some issues seen with the Wayland sessions on the past - I talk about something like Plasma 5.10.x when it was on KTown.

Possible that your particular application(s) to (still) interact badly with the Wayland sessions, and please note that contrary to Plasma5, the Plasma6 uses as default a Wayland session, while on SDDM login screen, the X11 sessions are named: Plasma (X11)

Which language setup you use?

I for one, I use ru_RU.UTF-8 - set on user side, after login, for my (own) desktop sessions and en_US.UTF-8 as system-wide setup and for the desktop sessions on cases when I want to show screenshots to English speaking people. Yet, even I use 2 full different character sets on a given computer, I did not observed on this Plasma6 build an issue like the one described by you.

However, IF what you describe is confirmed, probably this is something down to the Qt libraries, which both Qt6 and Qt5 are the ones shipped as is by Slackware-current. Anyway, I do not exclude your issues, but I need more information to reproduce them.

1 members found this post helpful.

I'm using the Plasma (Wayland) session launched from SDDM.

I use en_US.UTF-8 as my LANG variable.
The Plasma environment is set up with American English as basic languages but most regional settings are configured for Europe or my country (Paraguay). Sadly Plasma no longer allows a fine-grained tuning of regional settings. All text applications and also konsole/yakuake profiles are set to UTF-8 as in Plasma 5. I did not have these issues with Plasma 5.

The point is: my own language needs are rather simple; they are usually covered by the latin1 encoding (ISO 8859-1). The filenames which usually trigger this response are those with Turkish or Polish characters.

1 members found this post helpful.

You can be kind to test the same issue (both with the misplaced menus and text) while using a X11 session, by starting a Plasma (X11) session? This is important to see if the issues are generic or specific to Wayland sessions.

You can give me some examples of (downloadable) files with Turkish or Polish characters (i.e. images), which triggers these issues?

An additional note: As for the (detached and misplaced) menus, I'm citing MuseScore 4.1 as an example.

In Plasma 5 and compiled under qt5, MuseScore behaved correctly in this regard, although it never was very stable.

Now, it is as unstable as ever (not more), but I get those misplaced menus, no matter whether compiled against qt5 or qt6.

On Plasma5 you used to use a Wayland or X11 session?

And how about the MuseCore 4.2.1 bellow, for trying to test the menus issue. It have the issues, if I build it?

https://slackbuilds.org/repository/1...dia/MuseScore/

I now tried MuseScore 3.6.x, compiled against Qt5, and menus work OK even in Wayland session. Still I plan to test MuseScore 4.1 against the X11 session as you requested.

1 members found this post helpful.

Yes, all cases of displaced menus were from MuseScore 4.1 as posted in SlackBuilds.org against the Wayland Plasma 6 session.

BUT, I can assume that on X11 sessions it works OK?

Also, seems like on the SlackBuilds.org is MuseCore 4.2.1 , not 4.1

I will try to send you some links in private.

Many thanks!

Just an FYI there is a 4.3.0 MuseScore release which includes a patch for some misbehavior with qt5-declarative and menus. I’m building the 4.3.0 release as we speak, but I’m unsure if this is the fix you’re after. But the SBo package is outdated and i feel its generally a good idea to test on the latest release when using the latest environment as well. So that may be an option, or the 4.2.1 could be patched as well.

The Arch package has the patch commit info if one would like to go that route.

1 members found this post helpful.

1. I tried MuseScore 4.2.1 under Plasma6/X11 and menus work OK there.
2. I tried MuseScore 4.2.1 under Plasma5/Wayland and menus work OK.
3. I tried Musescore 4.2.1 under Plasma6/Wayland and menus appear out of place.
4. Thanks @jloco, I will try 4.3.0
5. @LuckyCyborg: about the filename and weird characters snafu, I sent you a link via private message.

Well, I built Musescore 4.3 and the menus issue still persists. In addition, I noticed that it won't build on Qt6 even after passing it all the Qt6 Cmake options from the KDE6 buldscript.

All other Qt5 apps behave normally. Oh well.

2 members found this post helpful.

Thanks @LuckyCyborg for the great effort!

Best regards
---
SlackwareCN: The Slackware Linux CN Community
slackwareCN：https://github.com/slackwarecn
slackwareCN：http://www.slackwarecn.cn
slackwareloong doc ：https://github.com/slackwarecn/slackbook_cn_loongarch64
slackwareloong web doc : https://slackwarecn.gitbook.io/slackbook_cn_loongarch64

2 members found this post helpful.

@sombragris

Regarding the issue with the characters, I am really sorry, but I cannot confirm it. My system insists to display properly the name of Michał Klauza, both on Konsole and Dolphin, also the files looks like being extracted properly. I believe that's either an issue with your language setup, either your system is really "dirty" and a clean install may be necessary. Please note that my -current installation used to experiment with Plasma6 is no longer than a month old. I have did a clean install for building "clean" the packages for the first build from this thread.

Regarding the MuseScore's menus issue on Wayland/Plasma6 sessions, I can confirm it, if it's about what you see in the attached screenshot. And this one is MuseScore 4.3.0

However, looks like even on latest version of 4.3.0 the MuseScore has NO support for Qt6 (but they work actively on porting it to) and to add insult to injury, they use a custom way on rendering the interface, which is clear that is not fully compatible with the latest support offered by the Wayland/Plasma6 sessions.

BUT, I for one I am not a C/C++ programmer, so my sincere suggestion is you to open an issue on their repository, along with the 2.5k other ones already present.

Meanwhile, I have experimented with a "special" package, which uses a script wrapper to force the XCB platform even on those Wayland sessions. This means that even on a Wayland session the MuseScore will use the X11 backend (via XWayland) and the menus will be properly rendered. For your convenience, I have uploaded a tarball containing both the package and the SlackBuild, and you can find it bellow:

https://easyupload.io/ixoxyd

The associated checksum is bellow:
Let's hope that they are aware by this issue with Wayland/Plasma6 and that they will fix it along with the porting to Qt6 which is now done on the "master" branch.

Attached Thumbnails

 

3 members found this post helpful.