On Sun, Dec 18, 2016 at 05:58:13PM +0100, Elimar Riesebieter wrote: > > On Sun, Dec 18, 2016 at 05:02:01PM +0100, Elimar Riesebieter wrote: > > > > I even removed the .moc directory, to make sure there is nothing in it > > > > that might be incompatible now, but it didn't help. > > > > I also tried it with and without the moc-ffmpeg-plugin package. > > > > I have to correct this statement a bit: > > With an empty/removed .moc directory it's starting up again. > > It wasn't working on my first attempt, because I tried it with a > > different user with a different (non-working) asoundrc. > > > > But with my old config it's not starting. The breaking change seems to > > be a custom AlsaDevice that I have also configured in my .asoundrc. > > So it is not moc's fault. I can see in the debug server logs that > there are no mixers or sound devices available. Could be caused by > your .asoundrc. > > What custom sound device do you have configured? Does sound work > with other apps like aplay some_file.wav?
I have a bluetooth speaker configured: $ cat ~/.asoundrc defaults.ctl.card 1 defaults.pcm.card 1 defaults.timer.card 1 defaults.bluealsa.interface "hci0" defaults.bluealsa.device "xx:xx:xx:xx:xx:xx" defaults.bluealsa.profile "a2dp" And yes, sound is working with other apps. It's even working with moc 1:2.6.0~svn-r2848-1, which is why I think it's a regression in moc. As already mentioned, after upgrading moc (and changing nothing else) it no longer starts.
signature.asc
Description: Digital signature
