MuseScore 3.6 requires sudo to open on Ubuntu 20.04
I am a first time MuseScore user but fairly experienced linux user. For some reason that I can't figure out, MuseScore seems to require superuser level (sudo) permissions to open properly. This happens with the app-image before or after installing. Is this expected behavior?
Comments
For reference, when I run the program without sudo (from the command line), it just outputs
/lib/x86_64-linux-gnu/libjack.so.0
/lib/x86_64-linux-gnu/libnss3.so
and exits.
In reply to For reference, when I run… by oscardssmith
I've never heard of this. I assume you gave it full execute permission for the current user? Did you place the file in an unusual location? Did you install the AppImage or are you running it from the command line directly (the former usually better)?
In reply to I've never heard of this. I… by Marc Sabatella
I did chmod a+x the AppImage before running it from the command line in my Downloads folder. Without sudo, I see a splash screen that never does anything if I double click (or just the 2 lines of text if I run from command line. With sudo, everything works exactly as I would expect. I also tried installing which seems not to have changed the behavior at all.
In reply to I did chmod a+x the AppImage… by oscardssmith
Maybe a permissions problem in your home folder?
In reply to Maybe a permissions problem… by Marc Sabatella
My home folder has permissions drwxr-xr-x (I don't think I ever messed with it). Does it need to be something different?
Thanks for being so responsive on this!
In reply to My home folder has… by oscardssmith
Wouldn't hurt to make writable for group or other I guess although it sure doesn't seem like it should be necessary. Make sure also there are write permissions for .config etc, and don't already have a write-protected folder Documents since MuseScore wants to create one. But I'm not really that experienced with Linux. Really just grasping at straws here. Hopefully some else can help further if this doesn't get your sorted.
In reply to Wouldn't hurt to make… by Marc Sabatella
I think I figured it out. The first time I tried to open the program, I force quit it since it wasn't opening quickly. Doing so got a tmp folder into a corrupted state where it was unable to be deleted. Restarting my computer has solved this.
In reply to I think I figured it out… by oscardssmith
Excellent. I figured it was something along those lines, but since I've never encountered it or heard it reported, I couldn't say where to look more specifically.
In reply to I've never heard of this. I… by Marc Sabatella
I've also tried running it with --debug but that doesn't give any extra information.
In reply to I've also tried running it… by oscardssmith
@oscardssmith, I haven't mastered Linux (I use Mint) but I just download the Appimage, right click and from Properties/Permissions make it executable (forgive me if this is irrelevant to you).
I am using Ubuntu 20.04 too. But I do not need sudo.
Maybe some of your musescore folders got root ownership somehow?
In reply to I am using Ubuntu 20.04 too… by bmhm
I figured this out. The issue was that the first time I opened it, I force closed it because it felt like it was taking to long and I ended up with a folder in tmp that was undeleatable (even by root). Restarting fixed the issue.