Cannot open msc files

[LKRaider]

Binary package hint: mscore

After saving a score (in the msc format), the file cannot be opened by MuseScore, a parsing error is shown.

To make the file open correctly, the msc file must be edited on a text editor and the DOCTYPE tags must be removed. This allows MuseScore to correctly open the file again, but any successive saves will re-introduce the DOCTYPE tags again, making this a tedious process of manually removing them everytime.

[Toby Smithe (tsmithe)]

I have built a fixed version of the package, available for now in my PPA (please see [0]). As soon as mscore is uploaded to Debian, and is sync'ed into Intrepid, I can see about getting a fix in hardy-updates, or at least hardy-backports.

https://launchpad.net/~tsmithe/+archive

[LKRaider (paul-eipper)]

I tried your mscore (0.9.1d+dfsg-0ubuntu4.0tsmithe4), but I still get the error message here.

[Toby Smithe (tsmithe)]

On Sun, May 25, 2008 at 11:00 PM, LKRaider <email address hidden> wrote:
> I tried your mscore (0.9.1d+dfsg-0ubuntu4.0tsmithe4), but I still get
> the error message here.

That's peculiar. Does this happen with new scores, too? Could you post
a score that provokes the bug?

[LKRaider (paul-eipper)]

Seems to happen with new scores too.

Attached is a file that causes the error message to appear.

[LKRaider (paul-eipper)]

$ mscore -v
Connection failure: Connection refused
Suspending PulseAudio
Connection failure: Connection refused
/usr/bin/mscore.real: Linux Music Score Editor; Version 0.9.1 Build 646

$mscore morrowind_error.msc
Connection failure: Connection refused
Suspending PulseAudio
Connection failure: Connection refused
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
Couldn't resolve property: 2
Couldn't resolve property: 2
Couldn't resolve property: 2

[Toby Smithe (tsmithe)]

Very strange; clearly, the patch was not comprehensive. I have tested
with a similar patch against the latest upstream version (0.9.2), and
that seems to have resolved the problem.

Please test with the attached packages, assuming you're on i386, and
the attached (working, at least here) copy of your score.

[LKRaider (paul-eipper)]

Installed and cofirmed it opens the file you posted.

Tried to save the file as another name and open it again and it worked correctly. Now the DOCTYPE declaration is not included on the save anymore.

PS: Gdebi would not allow me to install the mscore_0.9.2+dfsg-1_i386.deb package, saying it was "corrupt or I had no permissions to open the file", which didn't happen to the mscore-common package (even if both were chmod 644 and chown'ed to my user).
dpgk -i on the terminal didn't complain tho...

[Launchpad Janitor (janitor)]

This bug was fixed in the package mscore - 0.9.2+dfsg-0ubuntu1

---------------
mscore (0.9.2+dfsg-0ubuntu1) intrepid; urgency=low

  * New upstream release (LP: #235731)
  * Patches dropped:
    + 03-build-desktop-file - incorporated upstream
    + 06-build-documentation - new online documentation system obsoletes this
  * Patches added:
    + 07-fix-xml-in-msc - Qt 4.4 updates break xml production thus
     creating files which do not open with mScore.
     (LP: #234681)

 -- Toby Smithe <email address hidden> Sun, 27 Apr 2008 12:33:00 +0100

[Toby Smithe (tsmithe)]

LKRaider, sorry to bother you again. I'm trying to prepare a patch
that works against the current Hardy version (ie, the version against
which you initially reported this bug), so that I can apply for a
Stable Release Update.

However, in doing so, I have once again tested the version of the
package 0.9.1d+dfsg-0ubuntu4.0tsmithe4, which apparently did not work
for you. It works for me here, and I cannot see in the source, any
further places where the code requires patching. Could you possibly
downgrade your installed version back to
0.9.1d+dfsg-0ubuntu4.0tsmithe4, and test with the test score I
attached on 2008-05-28? Thanks. I have attached here deb files for
that version.

Once again, my apologies for the hassle.

http://launchpadlibrarian.net/14643299/mscore-common_0.9.1d%2Bdfsg-0ubuntu4.0tsmithe4_all.deb
http://launchpadlibrarian.net/14643298/mscore_0.9.1d%2Bdfsg-0ubuntu4.0tsmithe4_i386.deb

[LKRaider (paul-eipper)]

I just tested it again with 0.9.1+dfsg-0ubuntu4 and it didn't work.
Here is the procedure I followed:

1) installed from the debs you posted above (with dpkg -i)
2) opened the msc file you posted, no error was shown, as expected
3) saved the file from the menu as a new filename
4) tried to open the file and the error appears

Can you reproduce this behaviour there?

PS: don't worry about the hassle :P I too want to see the package working 100%

[codeslinger (codeslinger)]

it's been two years. what does it take to get this deployed? I can not believe that there are only two musicians in this entire world who happen to be using ubuntu hardy and mscore and have auto-updates turned on.

also, was a bug report for qt 4.4 ever opened?? that's where the real bug is. this fix to mscore is just a work-around for a bug in the qt shared library. I can't find a bug report for that issue.

please see: http://musescore.org/node/4321
for more details.

[Toby Smithe (tsmithe)]

This is unlikely to ever be fixed in Hardy proper. Whilst Canonical provides guaranteed support for those packages that are in the main repository for the full lifetime of the LTS release, packages in the universe repository are only supported on a voluntary basis. If you can provide a patch to mscore 0.9.1 that fixes this bug, I will happily have it sponsored, if not, please don't be aggressive.

A far better solution for you (and for my scarce free time) would be to use the latest stable release, 0.9.5, which you can install from my PPA at https://launchpad.net/~mscore-ubuntu/+archive/mscore-stable - follow the instructions at that address to install the repository. If you want more recent packages, you can use the unstable prereleases at https://launchpad.net/~mscore-ubuntu/+archive/ppa but be warned, as these are much more likely to have bugs. The packages are also currently a little out of date- due to the complex nature of the software, I cannot blindly track upstream version changes. Updates take time to check over and validate, but I hope to be able to provide the recently released beta version of 0.9.6 soon.

LKRaider, I'm sorry that I never got back to you. I'm sure you can appreciate why, but I admit that that was far from desirable. If you wish, please use the updated packages described above.

[codeslinger (codeslinger)]

I was not able to locate a qt bug about this issue, but surely this must be a well known problem. So I have asked about it here:

https://answers.launchpad.net/qt/+question/99921