proper way in linux to open a file in an already-running musescore process without causing Segmentation Fault?

• Aug 3, 2015 - 11:14

Sorry for the verbose title. A little preface: I frequency open midi files in musescore, and to save myself trouble of manually opening every file, I've created a bash script using inotify that scans a particular directory for new or changed *.mid files and opens then in musescore automatically from commandline via mscore $filename. It works fine, in that the files open in my previously running musescore process, expect I notice that the terminal that I invoke mscore $filename on produces an error message "Segmentation fault (core dumped)". I verified that this message is not due to my script, since it happens anytime I open any .mscz or .mid via a terminal whenever a musescore process is already running. Opening a file via command line when there are no other musescore processes running executes just fine without producing any seg fault. This seg fault happens on my arch linux x86-64 machine running git 2.0.2 build and arch linux i686 machine running official 2.0.2. Windows 8.1 doesn't produce this seg fault error message when open a file via command line when an already-running musescore process exists.

I don't have time at the moment to look into whether other linuxes produce the same segmentation fault message, but if anyone can verify, that would be nice. Could be something to do with my setup or library versions. I'll try running with debugger later today to nail down exactly what's happening, even though it seems benign.

Do you still have an unanswered question? Please log in first to post your question.