Musescore Does Not Work In Karmic

Using Jack as my sound output works as a workaround for now.

"bt_audio_service_open: connect() failed" suggests something is happening with bluetooth. If you disable bluetooth sound output, what effect does that have?

Also, though this is unrelated, it seems swiftfox is causing a lot of X errors for you; see ~/.xsession-errors. You might like to check that out (but here is obviously not the best forum for that).

Do I have a bluetooth service enabled? I have bluetooth manager unchecked in the startup applications. I don't even have bluetooth.

How would I go about disabling it entirely, then?

Hmm; I suspect it has something to do with pulseaudio, but it's just a guess, and a couple of quick Google searches were fruitless. I don't have much time left tonight to do more research, so I suggest you poke around and see if there are any bluetooth services running at all, and if pulseaudio has any bluetooth modules loaded; something like "pactl list | grep blue" should do the trick. Also, check what's using your sound card with (sudo, if you want to see root processes) "lsof /dev/snd/*". Sorry I can't be more helpful at the moment; I'll try and return to this at the weekend or next week some time.

I removed Bluez and other bluetooth software.

I also commented out everything on this little section here in /etc/pulse/default.pa:

### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif

and I removed pulseaudio-module-bluetooth.

No dice. The bluetooth error message is relieved, but I still get the 'sequencer init failed' message.

The processes using the sound card are:

timidity 2388 timidity 3u CHR 116,3 0t0 4157 /dev/snd/seq
pulseaudi 14601 cornwall mem CHR 116,10 5055 /dev/snd/pcmC0D0p
pulseaudi 14601 cornwall 19u CHR 116,17 0t0 6563 /dev/snd/controlC1
pulseaudi 14601 cornwall 25u CHR 116,12 0t0 5086 /dev/snd/controlC0
pulseaudi 14601 cornwall 26u CHR 116,10 0t0 5055 /dev/snd/pcmC0D0p
pulseaudi 14601 cornwall 27u CHR 116,12 0t0 5086 /dev/snd/controlC0
pulseaudi 14601 cornwall 32u CHR 116,12 0t0 5086 /dev/snd/controlC0

I have tried killing timidity, but that also does not work. I will post anything if I find or think of something, but I think that's all I can think of now. Also, my friend also uses Karmic and she is in the same spot I am. She's a fresh install, too, so I don't believe this is a user configuration problem (for the record)

and on an unrelated note, the swiftfox errors are actually a firefox bug. I have a mild case of it, lots of people are getting their log size up to many megabytes.

Right. Could you just make sure that pasuspender is doing its job (though I see no reason why it shouldn't..) by running `speaker-test >/dev/null & pasuspender lsof /dev/snd/*; pkill speaker-test` and posting the output? This will cause your system to output a brief burst of noise. Also, please attach your ~/.config/MusE/MuseScore.ini file; I may see if there are any tweaks to be made (say, disabling all outputs apart from portaudio, which seems to work in conjunction with pulseaudio at least in wine these days), and then make them globally.

Thanks.

cornwall@cornwall-desktop:~$ speaker-test >/dev/null & pasuspender lsof /dev/snd/*; pkill speaker-test
[1] 13720
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 14601 cornwall 19u CHR 116,17 0t0 6563 /dev/snd/controlC1
pulseaudi 14601 cornwall 27u CHR 116,12 0t0 5086 /dev/snd/controlC0
pulseaudi 14601 cornwall 32u CHR 116,12 0t0 5086 /dev/snd/controlC0

I was not aware that portaudio even worked with alsa/pulseaudio. here's the file.

Please try running `mscore.real -d` with the ~/.config/MusE/MuseScore.ini file replaced with the one attached, and attach the output given, and information as to whether or not audio works.

Sound worked when following the prescribed inststructions. I also saw some sort of debug information on the notes (if that's at all relevant). I also had a very long terminal output (also seems like debug) which I attached.

I just realized like a moron the reason you had me do mscore -d >.>. Forgive the slow mind, it's been on overclock.

2009/12/4 Chauncellor <email address hidden>:
> Sound worked when following the prescribed inststructions.

Now, this is very interesting. You see, running "mscore.real" skips
out pasuspender. I've just updated the mscore.sh script (which wraps
mscore.real) so that it checks for a PulseAudio version greater than
or equal to 0.9.19, and in that case it skips running pasuspender.
Obviously, this is good news; and it works for 0.9.4 as well. This
update will be in the 0.9.5 package that should be in Debian shortly,
and I'll update the stable and prerelease PPAs accordingly. If you
can't wait, then copy the attached mscore.sh script to
"/usr/bin/mscore" and mark it executable. If you wish, advise your
friend to do the same; she may also need to remove the MuseScore.ini
file, or enable PortAudio output in the I/O preferences.

Best wishes,

--
Toby Smithe :: http://fulltinreality.com

Fantastic news. Thanks very much :)

My pleasure.

Was the recent update for Karmic supposed to be the fix? I updated my friend's mscore and the problem is still there. I do notice it is in fix-committed status, but I want to be sure.

The update for mscore in the PPAs should contain the fix, but it may be required to remove the configuration file. If that does not work, please re-open the bug (with the usual information attached; I'll probably end up writing an apport hook at this rate!).

Ah, deleting the configuration files did it. I had assumed that apt-get purge would have done that for me, otherwise I would have checked.

Sorry for the noise. It works brilliantly now!

(Fix Released is supposed to be reserved for when the fix hits Ubuntu)

Also, no apt/dpkg action should ever touch your user files or configuration (because those are the user's responsibility, and it would be impossible to distinguish between {deliberate settings} and {those that should be changed because a bug that has been fixed in the defaults may still manifest itself with the current user settings}), so don't rely on that!

Happy composing :)

My apologies! I'm sorry, I forgot I had a PPA!

When will this be included in the standard updates? This seems to be a bit of a blocker for freshly installed mscore.

2010/1/30 Chauncellor <email address hidden>:
> When will this be included in the standard updates? This seems to be a
> bit of a blocker for freshly installed mscore.

You're right. I'll be spending some time working on MuseScore
tomorrow, and I'll look into this then.

--
Toby Smithe