Hello, Sascha. Sorry for the delay in reponse, I wanted to look into the bug and find some useful info before replying.
Sascha Silbe: > Package: mumble > Version: 1.2.8-2 > Severity: normal > > Dear Maintainer, > > on all the ARM based systems that I've tried (OLPC XO-1.75 (*), Wandboard > Quad, OpenRD Base) mumble spams stdout or stderr with these lines: > > === Begin === > warning: Unknown speex_preprocess_ctl request: 26 > warning: Unknown speex_preprocess_ctl request: 35 > === End === There's another report of this (#1834) which again was on an ARM: https://github.com/mumble-voip/mumble/issues/1834 The fix in that case was to rebuild mumble with CONFIG+="bundled-speex". (That would go into the "rules" file for the Debian source package.) Let me know if you occasionally rebuild Debian packages for ARM; if not then I can build a Mumble package for ARM on an amd64 system via qemu for you with this fix. > It's producing them at such a high rate that sshd consumes considerable > CPU time when I run mumble over SSH. If I understand correctly, this would involve using 'ssh -X' to do X forwarding over ssh to be able to see the GUI, and presumably rerouting the audio with something similar? (Or using something like x2go, which is possible to do on ARM but a bit more difficult.) Running the mumble client GUI over ssh is a bit unusual, I haven't heard of that before... I'm a bit curious as to hear how well that works and what situation that would be fitting for. > At least on the Wandboard Quad it happens both with on-board audio and > with a USB headset (Microsoft LifeChat LX-6000); OpenRD Base doesn't > have on-board audio so I only tried the USB headset. Yeah that's not surprising; this seems speex library related, which would be independent of the audio device. > On XO-1.75 it > crashes before it can output more than a few of these lines; see my > other bug report (which apparently ended up on > [email protected] because I had the backports version > installed when I reported the bug). Yes and that's correct -- for backports bugs are supposed to be reported to the backports mailing list (that's the policy for backports, listed in the FAQ: : https://backports.debian.org/FAQ/ ) and there's a somewhat obscure option that can be found in the manpages for deb-control(5), deb-src-control(5), and deb-origin(5): Bugs: url The url of the bug tracking system for this package. The current used format is bts-type://bts-address, like debbugs://bugs.debian.org. and the maintainer for the mumble backport set that (at my request) to: Bugs: mailto:[email protected] The 'reportbug' program respects this control header, so that's why your bug report for the backport went (correctly) to the backports mailing list. ('reportbug-ng' does not respect this header and the maintainer stated he won't be supporting it.) -- Chris -- Chris Knadle [email protected]
