3.6 does not work in Linux Mint 20
Opens fine, loads scores fine, but the menu is completely inactive and you cannot do anything. You can't even exit the program. (Clicking on the close-window "x" also does nothing.) Massive FAIL. This is still an alpha version, clearly.
Comments
Appimage?
In reply to Appimage? by Shoichi
Yes, AppImage, which is the only option for Linux.
Any chance that there is a model dialog open that your missing (such as the telemetry dialog on first run)? If so, try pressing Escape once after launching and see if that works out.
In reply to Any chance that there is a… by jeetee
That occurred to me, too. But there wasn't one, alas.
When you say it loads scores fine, what do you mean? You were able to go to File / Open and select a score, but upon loading it, then the menus became inactive? Was this a score created pre-3.6? If so, did you see a dialog asking if you wanted to update the fonts etc? If not, probably the dialog opened offscreen for some reason, and hitting Esc should close it. Otherwise, we'd need more information to understand the problem that appears unique to your particular system.
In reply to When you say it loads scores… by Marc Sabatella
Ah, sorry. It successfully loads my previous session from version 3.2.3 (from the repo), so there are scores to see upon startup. The update-fonts dialog did pop up, and that window operated normally. But the main MuseScore window is inert. Using the keyboard (e.g., Alt-F for the Files menu) also did not work. It seems like MuseScore is functioning normally, from what little I can tell, except that the main window is failing to interact with mouse or keyboard.
I'm running Linux Mint 20.1, kernel 5.4.0-64-generic x86_64, Cinnamon 4.8.6. The AppImage file name is MuseScore-3.6.0.487916429-x86_64.AppImage.
When I try starting it from the command line in a terminal, it hangs on "restoring session". In the terminal appears the line "QWidget::insertAction: Attempt to insert null action". I don't know what that means, if anything. When I run it from the command line, the following gets added to /var/log/syslog:
Jan 20 12:11:10 hypatia dbus-daemon[23246]: [session uid=0 pid=23244] AppArmor D-Bus mediation is enabled
Jan 20 12:11:14 hypatia systemd[2564]: tmp-.mount_mscorees66NN.mount: Succeeded.
Jan 20 12:11:14 hypatia systemd[1]: tmp-.mount_mscorees66NN.mount: Succeeded.
which seems to indicate things are happy at that point. But when I double-click on the AppImage (and it successfully restores the previous session), this appears in /var/log/syslog:
Jan 20 12:12:17 hypatia systemd-resolved[1370]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
I don't know what else to try at this point.
In reply to Ah, sorry. It successfully… by murison
Have you tried to delete/rename the old default settings in home/Documents/Musescore3?
In reply to Have you tried to delete… by Ralof
Thanks for the tip. I tried it and the behavior is still the same.
In reply to Thanks for the tip. I tried… by murison
WHat if you start by double-clicking a score rather than from the command line or using the program icon?
This will bypass the start center and restoring the previous session. If that doesn't help, what about -F option to revert to factory settings?
In reply to WHat if you start by double… by Marc Sabatella
Re clicking on a score: interesting. The toolbars are now almost fully functional, and I can edit successfully. However, anything eliciting a dropdown menu does not work, still. Also, cannot exit the program at all, other than to kill the process.
Re -F option: I get this error message:
/tmp/.mount_MuseSckuK7Ld/bin/mscore-portable: symbol lookup error: /tmp/.mount_MuseSckuK7Ld/bin/mscore-portable: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev, version Qt_5
If instead I use sudo,
sudo -E ./MuseScore-3.6.0.487916429-x86_64.AppImage
we're back to the same behavior as clicking on a score.
If I do s straight sudo (no -E option) with -F, the whole window goes gray and nonresponsive as soon as I close the start center window.
If I do sudo -E with the factory reset flag -F, I get the grayed-out screen again as soon as I try to load a score.
In reply to Re clicking on a score:… by murison
Do you have the app image somewhere in your home directory?
In reply to Do you have the app image… by Ralof
Does that matter? How could that matter?
Exactly the same happens after I downloaded and installed the latest version 3.6, other versions I have had no problems with. I have Mac OSX Catalina 10.15.7 and a high end Macbook Pro 16"
So Disappointing
In reply to Exactly the same happens… by allen1
To summarise I open the 3.6 musescore3, all the windows appear as normal, All the Musescore options on the Top Options menu are all greyed out. Clicking anything anywhere just give a Mac bing sound. Even the red close window button doesn't work. Only option is to CMD-OPTION-ESC and kill the app. Or locate the PID and kill -9 it from a terminal.
My processor is a 2.4Ghz 8-Core Intel Core i9
Memory is 64GB 2667 MHz DDR4
1TB Flash Storage Hard Drive
2 x GPUs
In reply to To summarise I open the 3.6… by allen1
All that behavior does seem to indicate that there is a(n offscreen?) popup modal window open, or perhaps hidden behind the main window?
You can always try a reset to factory defaults which should restore all window positions as well.
In reply to All that behavior does seem… by jeetee
You are right, there was a pop up window, but it was hidden behind other apps. Thanks for your answer
In reply to All that behavior does seem… by jeetee
Definitely have version 3.6 now, but a lot of the new features don't appear to be working, for instance typing a number during keyboard entry doesn't change the note duration?
In reply to Definitely have version 3.6… by allen1
on num-pad?
In reply to Definitely have version 3.6… by allen1
Typing a number to set note duration isn't exactly a new feature though..
If you hover over the duration buttons in the toolbar, a tooltip will show you which shortcut is configured on your system.
In reply to All that behavior does seem… by jeetee
There is no hidden or offscreen window for me — the first thing I checked.
Seems to me that differences in the QT5 compilations can be causing the problems described above.
This might be worth a try:
https://wiki.qt.io/Install_Qt_5_on_Ubuntu
I assume the steps for Mint are very similar if not identical.
In reply to Seems to me that differences… by Ralof
I'm having the same problem. After I upgraded from Linux Mint Cinnamon 19.3 to 20.3, "musescore" no longer starts. See attached screenshot.
I'm wondering why the AppImage doesn't embed all the shared libraries that it needs (or perform a statically-linked build).
Any ideas how to fix this?
In reply to I'm having the same problem… by gmlewis
I'm wondering whether qt5-default results in a too new 5.x version to be compatible with the AppImage (keeping in mind that was built over a year ago).
Bundling the whole of Qt would blow up the AppImage size by several GB
In reply to I'm having the same problem… by gmlewis
Maybe the answer is to actually install whatever version of MuseScore your distribution provides so that can pull in the missing dependencies, then simply not use that and use the AppImage, which should then be able to use these.
As far as I know, the philosophy with AppImage builds is to include libraries that are are known not be present in all distributions, but for space reasons, to leave out the libraries that all known distributions do include. Of course, distributions that didn't exist back in early 2021 wouldn't have been considered, nor was it probably expected that newer distributions would not include compatible versions of Qt, since it's so widely used. But I'm not really an expert on any of this, juts kind of speculating based on what little I do know.
In reply to Maybe the answer is to… by Marc Sabatella
Ah, thank you, Marc! That solved it.
For Linux Mint 19.3, I had to use the AppImage version, but now that I'm on Linux Mint 20.3, "sudo apt-get install musescore3" actually works... so I've switched to that.
In reply to Ah, thank you, Marc! That… by gmlewis
Which version did you end up with then? (Help > About)
In reply to Ah, thank you, Marc! That… by gmlewis
What version does it give you? If not 3.6.2, its still better to use the AppImage. Even if it is 3.6.2, do be aware that the repositories versions are not built or tested by us, and if you find strange errors (which is unfortunately common), it's also best to use the AppImage - that's the only version we keep up to date and build and support ourselves.
In reply to What version does it give… by Marc Sabatella
OS: Linux Mint 20.3, Arch.: x86_64, MuseScore version (64-bit): 3.2.3+dfsg1-4build1 (Ubuntu focal/amd64), MuseScore build number not set, revision: d2d863f
OK, then maybe I'll try to download the Qt5 libs manually since I have no clue which ones the AppImage version is missing.
In reply to OS: Linux Mint 20.3, Arch.:… by gmlewis
Seems to me like you already have the Qt libraries now if that old version of MuseScore is working. So why not just run the AppImage now?
In reply to Seems to me like you already… by Marc Sabatella
Unfortunately, it still isn't working... Searching for that missing symbol on Google, I'm finding all sorts of references to libstdc++-6 and gcc-5 and I've tried all the workarounds and still can't get it to work. However I'm no longer convinced that it is missing a Qt5 lib... but something lower in the C++ libs.
Maybe I'll just try building from source. :-D
In reply to Unfortunately, it still isn… by gmlewis
The good news is I can build MuseScore 4.0.0 preview and it runs.
The bad news is I couldn't build MuseScore 3.6.2... I got stuck in the freetype compilation.
In reply to OS: Linux Mint 20.3, Arch.:… by gmlewis
I have been through every possible permutation and wasted countless hours trying to get >3.2 versions to run on Linux Mint. It should not take a Ph.D. (and I have a Ph.D.!) to get the appimage to run. There is something wrong about the appimage files. That has to be fixed or we'll never be able to run a musescore appimage.
In reply to I have been through every… by murison
There won't be any further changes to 3.x
In reply to I have been through every… by murison
That's what I was thinking too, so I tried adding this to the CMakeLists.txt:
target_link_libraries(mscore ${LINK_LIB} -static)but it had problems with a Qt5 library (shock, surprise :-) ).
Note (to others listening in) that static linking is a very common practice and does not bundle every possible (Qt5) library into the final executable, and will not (in general) make a GB-large executable... That's what compilers (actually linkers) are for... to include only the parts that you are actually using. :-D
Oh, and I don't have a Ph.D., so caveat emptor. :-)
In reply to OS: Linux Mint 20.3, Arch.:… by gmlewis
I'm wondering, I'm on Minte 20.3 Mate 64 bit and MuseScore-3.6.2.548021370-x86_64.AppImage is working very well (there are still bugs though) and I cannot reproduce your problem. Do you use Cinemon or Xfce edition instead btw? If I could help in any way by comparing e.g. installed packages or anything else please give me a note.
In reply to I'm wondering, I'm on Minte… by gerb1857
Wow, that's really weird! Yes, I'm using Cinnamon. I'll try Xfce and see if there is a difference.
Thanks for the info and the offer, @gerb1857, I appreciate it.