Crash With Figured Bass

• Aug 30, 2015 - 04:24
Reported version
2.1
Priority
P2 - Medium
Type
Functional
Severity
S1 - Blocker
Reproducibility
Once
Status
active
Regression
No
Workaround
Yes
Project
MuseScore

When entering a figured bass, musescore crashes if the length value is changed, i. e.; by pressing CTRL+6, then, whilst holding CTRL, 7. I replicated this several times.

I've not filed a bug report here before, so I hope that I've done it correctly.

GIT commit: 3543170

Comments

• Aug 30, 2015 - 08:00
Status (old) active ⇒ needs info

Plese post the specific score you are having problems with and precise step by step instructions to reproduce the crash. I tried it just now and had no problems, so it must be something particular to your exact situation.

Reply

• Aug 30, 2015 - 08:23

Ah, the bug is on my system: the keypad produces the bug, but the numbers above the letters produces the expected result.

I've noticed that my keypad isn't working very well in other programmes, including musescore: pressing CTRL-3 on the keypad, for example, doesn't work, whereas it does if I use the three above the keys. I can post the score if you'd like, but I think this bug can be closed.

Reply

• Aug 30, 2015 - 15:45

Well crashes are bad. If we can prevent them, we should. So score & steps wpuld still be useful. But I don't have a numeric keypad myself to test with; hopefully someone else will be able to look.

Reply

• Aug 31, 2015 - 01:18

Right. I have uploaded the score to Dropbox: https://www.dropbox.com/s/l0uiyq6im26dv4z/%C2%ABPues%20yo%20solo%20me%2…

I can no longer reproduce the bug every time: I just tried the method I used yester-day, namely selecting a note, entering CTRL+g, then CTRL+6, then, whilst holding CTRL, pushing seven on the numpad. This did not result in an instant crash: I had to continue pushing a few random numbers on the numpad until the crash occurred. Having restarted musescore, I can not get it to crash.

Interestingly, using CTRL+numpad results in various characters and symbols being produced, such as the pound sing, an up-bow sign and a greater-than-or-equal-to sign. I had noticed this yester-day as well, but dismissed it as some peculiarity of musescore's. Here's a link to a snapshot: http://imgur.com/aMw4VMQ.

Let me know what else I can provide. If nothing else, triaging this bug might make my numpad more useable: as I indicated earlier, various programmes don't register its presses correctly. I suspect it has some thing to do with qt5 or KDE5, as I recently "upgraded" my system and broke many things: debian unstable seems to be very much so lately.

Reply