MuseScore 2.0 beta 1 crashes in Win7 & Win 8.1 Virtualbox VM

• Aug 27, 2014 - 20:35

I tried to take a look at MuseScore 2.0 beta 1 in Windows 7 and Windows 8.1 which I have installed as Virtual Machines in VirtualBox 4.3.14, running on Xubuntu 14.04 (64bit).

After installation, when I start MuseScore, it always crashes, see

https://twitter.com/mpopp75/status/504709308647739392


Comments

I ran beta1 on windows 7 and windows 8 in VirtualBox on mac without any issue. Do you have sound in your VM? can you try to start MuseScore from the command line in Windows, with the -s option which deactivate the sound engine. So open cmd, navigate to the installation direction, cd bin, mscore -s.

In reply to by Jojo-Schmitz

So PEBKAC that is?

I am the problem for reporting a crash in an application? What pathetic arrogant asshole are you?

(And your smiley doesn't help, because calling somebody a PEBKAC for genuinely reporting a bug is an inexcusable offense, if you are in any way related to this project rather than just a random user in which case you should be banned from the forum anyway.)

There are legitimate reasons for starting an application on a device with no sound available (like the reason I had) and if this application crashes, the PEBKAC is somewhere else! Maybe it's you.

No idea who this "Jojo-Schmitz" is, but it's better if you (the people behind Musescore) get rid of this kind of arrogant assholes.

In reply to by Jojo-Schmitz

Naming somebody PEBKAC who has filed a genuine, well meant and legitimate bug report is an offense. There is nothing more to say about this.

If I'm considered the offender now, then this was my last bug report here.

I can also keep issues which I find in Musescore to myself if the "thank you" that I get in return is something like "you are an idiot" (which is what a PEBKAC is generally considered to be).

In reply to by mpopp75

Imagine for a moment we'd sue each other for libel and slander, what do you think a judge would say about this?
"PEBCAK" with a smile vs. "pathetic arrogant asshole", twice and obvioulsy with a frown.
Tough decision? I don't think so.
The Wikipedia entry for PEBKAC redirects to 'user error', another good hint, isn't it?

Also there is a difference bewteen 'naming somthing' and 'naming someone', between "you are an idiot" (which I never said and never would, not in public at least, but you apparently understood) and "you made a mistake" (which I meant), don't you think?

You very clearly 'named someone' and clearly meant what you said, no doubt about that, I in turn, maybe not quite so clearly, 'named something' (an "user error" that is), and stated that it wasn't meant as an offence.

Don't you see that your reaction was way over the top? And makes an apology virtually impossible?

Enough of that, BTT: I do acknowledge that this crash is a bug, as does lasconic. And apparently pretty easy to work around too, just enable sound on the VM. Whether it is as easy to reproduce for the developers to be able to see and fix it remains to be seen.

In reply to by Jojo-Schmitz

The point is that my offense was only a reaction to your offense. To name somebody who files a genuine bug report PEBKAC is not acceptable under any circumstance.

PEBKAC means "problem exists between keyboard and chair", so clearly referring to the person being a/the "problem".

The outcome which I like to see is that there is a policy implemented (unless one already exists, in which case you would be in violation to this policy) that offending genuine bug reporters or other constructive forum contributors in any way (PEBKAC included) is not acceptable and may lead to the suspension of the user.

This particular incident can't be undone but there is a chance to learn from it and make sure other users don't get the "nice welcome" here which I received.

In reply to by Jojo-Schmitz

I spend a considerable amount of time and energy on a daily basis to invite people like mpopp75 to post questions, feedback, problems on the MuseScore forum. I often state that the MuseScore community is friendly and welcoming new users. Unfortunately this conversation is not an example of that and I find it rather painful to see this happen. We can do better.

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