Piano split into two staffs looses most of piano base clef notes.

Specific instructions: (With live midi instrument attached via USB port through active midi to usb device)
1. Use midi file (recorded with pianoteq) as an input file. Set to 1/16 notes.
2. Put cursor just after time signature an left mouse click. A blue box appears over first measure.
3. Put the cursor point on the edge of the blue box (left side of box, within staff lines) and left click. The fourth item from top is "Split Staff"
4. Select split staff. The midi keyboard will raplidly execute a series of notes.
5. The split staff will appear. Many notes in the original notation base cleff are now missing.
6. Undo the action. All the missing data reappears.

I have provided three MuseScore files:
1. Before conversion
2. After conversion
3. After undo.

Regards the Libre Office (Version 3): The main menu appears and covers the musescore. It has document highlighted. I either open the document (which is blank) or close the window w/o opening it. MuesScore works as if nothing happened. I have the "Play Panel" open automatically. The sequence of appearance is MuseScore, Play Panel, Libre Office.
I also provide the original midi file. The problem is not unique to this file, it is just an example that I used most recently.

Last, I provide the command line responses to these actions.

BTW: The play thru to midi instrument has never actually been set up to work (I do not know how) so I was surprised to hear anything from the midi keyboard.

I read the documentation which said to down load and tar/gunzip the package. I did this. I made the file execuitable with sudo chmod per the instructions.

michael1204@mike314159:~/Downloads/MuseScore$ ls -l
total 467568
-rwxr-xr-x 1 michael1204 michael1204 339022725 Jul 20 05:49 mscore
-rw-rw-r-- 1 michael1204 michael1204 139751637 Jul 31 18:20 mscore.64bits-2014-07-23-10-09-ade25ad.tar.bz2

I executed in the download/tar/gunzip directory via command line. (see below)

michael1204@mike314159:~/Downloads/MuseScore$ mscore

This (it seems) executes version 1.3 and you have the results.

I then used the ./ convention used for execuitable script files (see below)

I get:

michael1204@mike314159:~/Downloads/MuseScore$ ./mscore &
[1] 4017
michael1204@mike314159:~/Downloads/MuseScore$ ./mscore: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

[1]+ Exit 127 ./mscore
michael1204@mike314159:~/Downloads/MuseScore$

I expect an execuitable in the current directory to execute via its' name via command line. This should not be prempted by a PATH search. It seems that I was wrong. That said, doesn't a nightly build provide for the support libs complained about or point to the locations where they are from version 1.3 ?

PS: The log file has .mscz at the end by mistake. It should be .txt (Plz rename)

Since I did this wrong, I need better instructions to do it right.

Thanks