Mscore won't open files

Bug #526516 reported by Christopher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
musescore (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mscore

The screenshot shows what happens when trying to open a file. If I have a recent score in good shape to open I can open other scores afterwards, but that's not a viable solution.

Revision history for this message
Christopher (soft-kristal) wrote :
Revision history for this message
Toby Smithe (tsmithe) wrote :

That screenshot is not what you describe. What Ubuntu release are you on?

Revision history for this message
Christopher (soft-kristal) wrote :

I'm using both Karmic (9.10) and Lucid (10.04). I'll try to be a bit clearer.

When I open the program and either select 'Open' from the File menu or click on the icon, the screenshot is what I see.
If, on the other hand I open a recent document from the File menu, it becomes possible to open some other scores.
Others seem to be irretrievably corrupted somehow.

Opening MuseScore from the source file rarely works. It appears in the panel, then quits.

Revision history for this message
Christopher (soft-kristal) wrote :

Here's a screenshot of opening a corrupted file. I can see it in the navigator, but it won't display on the canvas.

Revision history for this message
Toby Smithe (tsmithe) wrote :

Weird stuff. Could you wait until the new version of musescore[1] is published in lucid and then see if you can reproduce?

[1] https://launchpad.net/ubuntu/+source/musescore/0.9.6~beta1+dfsg-0ubuntu1

Thanks!

Revision history for this message
Christopher (soft-kristal) wrote :

I'm eagerly awaiting its release.

Revision history for this message
Christopher (soft-kristal) wrote :

I was able update mscore to musescore (Beta), but there were a few hoops to jump through. The Beta is considered as a downgrade and must be forced with Synaptics. It will result in an error message, and one needs to use the Computer Janitor to get rid of mscore-common and the sound fonts.

Afterwards, using Synaptics again to install musecore-common can be accomplised.

Revision history for this message
Toby Smithe (tsmithe) wrote :

Damn, that's probably due to the way dpkg deals with versioning. I had thought that the version I gave for the 0.9.6 beta was "higher".. I'll open another bug against musescore to remind me.

As for this one, is it still reproducible?

Revision history for this message
Toby Smithe (tsmithe) wrote :

Also, what's the output of `apt-cache madison mscore`?

Revision history for this message
Christopher (soft-kristal) wrote :

That I can give you right away.

 mscore | 0.9.6~beta1+dfsg-0ubuntu1 | http://archive.ubuntu.com lucid/universe Packages
    mscore | 0.9.5+dfsg-1 | http://archive.ubuntu.com lucid/universe Sources
 musescore | 0.9.6~beta1+dfsg-0ubuntu1 | http://archive.ubuntu.com lucid/universe Sources
    mscore | 0.9.6b2438+dfsg-0ubuntu~lucid1 | http://ppa.launchpad.net lucid/main Sources

As to the rest, we're in luck. I have Lucid running on the desktop as well. I also have Karmic on both the laptop and the desktop so it can be tested on both. It'll take a while to report on that.

Revision history for this message
Christopher (soft-kristal) wrote :

Bad news - I didn't have mscore installed on the desktop so it went right to a clean install of the beta. Reproducing the error will have to wait until Lucid is officially released and I update my Karmic partition. I don't risk files on Alphas.

For what it's worth, the beta just finished installing on the desktop with no errors.

Revision history for this message
Toby Smithe (tsmithe) wrote :

Erm, could you clarify which 0.9.6 beta package you installed, from where, and onto which system? I assumed that you meant the installation/upgrade on Lucid had revealed the packaging bug, if not, then I'm uncertain as to where it arises, and thus what needs fixing.

Also, could you clarify, when you write "with no errors", does that mean that this bug - about file opening - no longer persists? Or was that statement limited to the upgrade packaging bug? (This is why it's good to have separate bug reports! But, don't worry yet- I want to confirm that there really is a packaging bug before opening one.)

Revision history for this message
Christopher (soft-kristal) wrote :

I have two computers - a laptop and a desktop with Lucid partitions, where the Beta is available for installation. The laptop had 0.9.6 prerelease (2438?) installed while the desktop had none at all.

The desktop installation proceeded smoothly, which is to be expected with a clean install. The laptop was another matter; requiring forced 'downgrading' to beta with Synaptics and removing mscore-common with either autoremove or Computer Janitor afterwards before being able install musescore and musescore-common; again with Synaptics.

Revision history for this message
Toby Smithe (tsmithe) wrote :

Right, thanks. I'll be sure to fix that by uploading a newer version to the PPA (so that this case doesn't arise- I don't see any other solution, sadly, until the final 0.9.6 release is made). Seems you reported the other bug about needing to remove mscore-common, but marked it as invalid? See bug 527349, which I've confirmed :)

Can I mark *this* bug fixed, though? Or does it persist in the beta?

Changed in mscore (Ubuntu):
status: New → Incomplete
affects: mscore (Ubuntu) → musescore (Ubuntu)
Revision history for this message
Christopher (soft-kristal) wrote :

So far, so good in the beta. If you want to mark it fixed, it's fine by me.

Changed in musescore (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Confirmed
Revision history for this message
Toby Smithe (tsmithe) wrote :

Wicked.

Changed in musescore (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.