Unable to search in Palettes under Wayland
As per the title, I am unable to search through Palettes. When I type in the search box, characters are not displayed. Attached, you can find the output of a launch with debug option enabled. Although there are a lot of lines, nothing seems to be related to the input box.
OS: Arch Linux, Arch.: x86_64, MuseScore version (64-bit): 3.6.2, revision: github-musescore-musescore-
I'm using Sway (a Wayland compositor).
Attachment | Size |
---|---|
musescore.txt | 113.53 KB |
Comments
What are you searching for? If I enter e.g. "piz" into the search box, it does show "pizz." from the text palette and the Bartok Pizzicato symbols from the Articulations palette. MuseScoore 3.6.2, Windows 10.
In reply to What are you searching for?… by Jojo-Schmitz
I cannot search for anything, it's impossible to write in the input box. I tried also to delete the cache and start with a clean configuration, but it's always the same problem. I suspect it's a matter of integration between Musescore, Qt and Wayland.
In reply to I cannot search for anything… by tigerjack89
Or between Wayland and... and...
unknown:unknown: MuseScore::cmd
unknown:unknown: Wayland does not support QWindow::requestActivate()
In reply to Or between Wayland and… by underquark
The requestActivate message is quite common for applications based on Qt running under Wayland. I don't think it's the culprit here.
Indeed when I click on the input box no message is produced in the logs.
It appears from the log you posted that you might be using a third-party build rather than the AppImage we provide and support ourselves. Try that instead., Works fine for me, and I'm also running a system that uses Wayland.
In reply to It appears from the log you… by Marc Sabatella
I tried that and it failed to start saying
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".
Available platform plugins are: xcb.
I have indeed as environment variable "QT_QPA_PLATFORM=wayland-egl" to enable wayland support for QT applications.
If I launch the AppImage with
QT_QPA_PLATFORM=xcb ./MuseScore*.AppImage
everything works fine. However, the application will not use Wayland anymore, but XWayland. You can test that this is the case using the xeyes utility.
In reply to I tried that and it failed… by tigerjack89
OK, but then it, is that a problem?
In reply to OK, but then it, is that a… by Marc Sabatella
Well, Wayland is the official replacement for X11, so yes, I would expect that an application using QT would be fully compatible with Wayland. From what I saw, the application runs smoothly under Wayland. The only issue I had is with the search palette, which maybe has some X11 specific code. So it would be nice and in the long run better to make it totally compatible with Wayland.
In reply to Well, Wayland is the… by tigerjack89
MuseScore 4 will use a different version of Qt, so it's possible they've since supported it more fully - I'm not up on all of those technical details. i mean, if there an actual problem running MuseScore 3.6.2 this way today, or if the issue basically solved in terms of actually using the problem? I don't know if using XWayland introduces some sort of other problem I'm not aware of. It doesn't for me.
In reply to MuseScore 4 will use a… by Marc Sabatella
I tried latest nightly of MuseScore and the Wayland support is still missing, meaning that QT_QPA_PLATFORM=wayland (or wayland-egl) cannot be used.
XWayland is just a temporary compatibility layer for applications not fully supporting Wayland, so it will use an additional layer of overhead. Also, there are some other problems like DPI scaling not working. But anyway, I think the main point here is that it's a pity to not have Wayland support, since all major Linux distros switched to it.
In reply to I tried latest nightly of… by tigerjack89
Hmm.. I was under the impression the nightlies are on 5.15, which AFAIK should support native Weston.
Then again it could be that the AppImage packaging does not include qtwayland..
In reply to Hmm.. I was under the… by jeetee
I don't know. I tried to extract the files from the AppImage and the lib directory has a lot of libQt5* files.
In reply to Well, Wayland is the… by tigerjack89
Then again Wayland is still fairly new and the Qt version used in 3.6 relatively old..