Bug#952742: mumble: start locks sound for all application (even the client itself)
tags 952742 - unreproducible moreinfo tags 952742 + fixed-upstream patch thanks This has been fixed upstream in a one-line patch here: https://github.com/mumble- voip/mumble/pull/3990/commits/0780d93aab3eec9796e1cb8606c5f3c089d64eca Ubuntu users are also running into the problem https://bugs.launchpad.net/bugs/1874231 I'm going to do an upload with a patch to fix this. Upstream has a release snapshot up for 1.3.1 so a bugfix release should be available soon. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
lemmel: > Well done ! > > I was stupid: jackd was in the ouput, but as Pulse was selected I totally > ignored it ; and jackd doesn't even figure in the Mumble UI ! > > I'm really sorry: I filled a bug, and waste your time. I consider this bug to be worthwhile and important and I'm glad you opened it. I'm very thankful to Sébastien for figuring out that this relates to Jack and I didn't realize that could have been the cause. The Jack support in Mumble is rather new and there have been some other issues with it (7-second startup delay for Mumble on Sid without Jack installed, for instance): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941455 > Le mardi 31 mars 2020, 19:58:06 CEST Sébastien Leblanc a écrit : >>> ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 >> >> I see you have Jack installed, have you checked if Mumble started it? >> Unfortunately, while Mumble supports Jack, it does not play nicely with >> it in this release, as there are no options in the GUI pertaining to >> disabling automatic connections or automatic startup of the Jack server. >> By default, it will attempt to start Jack if it is installed on the >> system, even if you set the output module to ALSA or PulseAudio. >> >> >> In `~/.config/Mumble/Mumble.conf`, you can add the following : >> >> >> % >> >> [jack] >> startserver=false >> >> % >> >> >> Please see if this does anything. Thank you for figuring out the above setting; I didn't know that was possible. And as you mentioned there's no options in the GUI pertaining to Jack. :-/ I'll see if I can discuss this issue with upstream. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
On 20-03-31 14 h 42, lemmel wrote: > Well done ! > > I was stupid: jackd was in the ouput, but as Pulse was selected I totally > ignored it ; and jackd doesn't even figure in the Mumble UI ! > > I'm really sorry: I filled a bug, and waste your time. It is actually a manifestation of an underlying bug: Mumble provides no control in the GUI for Jack parameters, and by default starts it if it is installed, whether you are actually using it or not. -- Sébastien Leblanc pEpkey.asc Description: application/pgp-keys
Bug#952742: mumble: start locks sound for all application (even the client itself)
Well done ! I was stupid: jackd was in the ouput, but as Pulse was selected I totally ignored it ; and jackd doesn't even figure in the Mumble UI ! I'm really sorry: I filled a bug, and waste your time. Le mardi 31 mars 2020, 19:58:06 CEST Sébastien Leblanc a écrit : > > ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 > > I see you have Jack installed, have you checked if Mumble started it? > Unfortunately, while Mumble supports Jack, it does not play nicely with > it in this release, as there are no options in the GUI pertaining to > disabling automatic connections or automatic startup of the Jack server. > By default, it will attempt to start Jack if it is installed on the > system, even if you set the output module to ALSA or PulseAudio. > > > In `~/.config/Mumble/Mumble.conf`, you can add the following : > > > % > > [jack] > startserver=false > > % > > > Please see if this does anything. > > -- > Sébastien Leblanc > >
Bug#952742: mumble: start locks sound for all application (even the client itself)
> ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 I see you have Jack installed, have you checked if Mumble started it? Unfortunately, while Mumble supports Jack, it does not play nicely with it in this release, as there are no options in the GUI pertaining to disabling automatic connections or automatic startup of the Jack server. By default, it will attempt to start Jack if it is installed on the system, even if you set the output module to ALSA or PulseAudio. In `~/.config/Mumble/Mumble.conf`, you can add the following : % [jack] startserver=false % Please see if this does anything. -- Sébastien Leblanc pEpkey.asc Description: application/pgp-keys
Bug#952742: mumble: start locks sound for all application (even the client itself)
lemmel: > I too tested in a VM (with KDE) but to no avail: I wasn't able to reproduce > the problem with it. > > I will test this week-end an update, then a full reset of my Mumble prefs, > and will tell you the results. > > PS: thx for your invest Thanks for taking the time to try reproducing the problem; I'm glad to have verification that the issue is not as serious as it first appeared. I'd like to think that there would be a comparable difference between the KDE test VM and the Debian Sid/Testing instance that is having Mumble audio issues. A logical possibility would be something related to the PulseAudio settings / installation or perhaps AppArmor security settings related to audio, if those have been customized. I find these types of investigations can be worthwhile, as they can be good learning experiences. I'll try to think of whether there's another way I can help. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
I too tested in a VM (with KDE) but to no avail: I wasn't able to reproduce the problem with it. I will test this week-end an update, then a full reset of my Mumble prefs, and will tell you the results. PS: thx for your invest Le jeudi 5 mars 2020, 00:29:19 CET Chris Knadle a écrit : > Chris Knadle: > [...] > > Concerning Debian Sid/Unstable, my understanding is that it is not a > > complete > > distribution, and so Unstable is meant to be run as Unstable + Stable, i.e. > > Sid > > + Buster. Looking at the distributions you're currently using I see it's > > Unstable + Testing, i.e. Sid + Bullseye. I'm not sure if that may explain > > this > > bug or not; I may try to take a VM snapshot and upgrade to Sid + Bullseye > > and > > see if I can get the audio in Mumble to crap out. > > Okay I made a VM snapshot and upgraded the VM to Sid + Testing and Mumble > audio > (using PulseAudio) still worked, and audio for the rest of the system worked > as > well with and without Mumble running. I used MATE as the GUI for the testing. > > I've also enabled AppArmor in the same VM and audio works within and outside > of > Mumble, regardless of whether it's running or not. > > I am not able to reproduce this bug, and I think I've run out of options to > try > to do so. > > -- Chris > >
Bug#952742: mumble: start locks sound for all application (even the client itself)
[sent this on 3/4 to the bug reporter and forgot to send it to the bug report] Chris Knadle: [...] > Concerning Debian Sid/Unstable, my understanding is that it is not a complete > distribution, and so Unstable is meant to be run as Unstable + Stable, i.e. > Sid > + Buster. Looking at the distributions you're currently using I see it's > Unstable + Testing, i.e. Sid + Bullseye. I'm not sure if that may explain > this > bug or not; I may try to take a VM snapshot and upgrade to Sid + Bullseye and > see if I can get the audio in Mumble to crap out. Okay I made a VM snapshot and upgraded the VM to Sid + Testing and Mumble audio (using PulseAudio) still worked, and audio for the rest of the system worked as well with and without Mumble running. I used MATE as the GUI for the testing. I've also enabled AppArmor in the same VM and audio works within and outside of Mumble, regardless of whether it's running or not. I am not able to reproduce this bug, and I think I've run out of options to try to do so. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
severity 952742 important tags 952742 + moreinfo unreproducible thanks lemmel: > Package: mumble > Version: 1.3.0+dfsg-1+b1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > fresh dist-upgrade (this day 02/28/20) brought up a mumble that lock all sound > on the host, the mumble client itself producing no sound. > > I did all kind of setup with the mumble client (OSS, ALSA, etc), but it did > nothing. I upgraded a VM running native Sid + Buster and did a full upgrade, and found audio with Mumble 1.3.0+dfsg-1+b1 via pulseaudio worked fine. I tried using ALSA with Mumble, and was not able to get that to work with the "[default] Playback/recording through the PulseAudio sound server" setting, and haven't tried further settings (yet). I tried OSS with Mumble and was not able to get that to work, but that didn't surprise me. Concerning Debian Sid/Unstable, my understanding is that it is not a complete distribution, and so Unstable is meant to be run as Unstable + Stable, i.e. Sid + Buster. Looking at the distributions you're currently using I see it's Unstable + Testing, i.e. Sid + Bullseye. I'm not sure if that may explain this bug or not; I may try to take a VM snapshot and upgrade to Sid + Bullseye and see if I can get the audio in Mumble to crap out. But for now I'm marking the severity of this bug as "important" rather than "grave" because as best I can tell it's broken on your system but not others. [If other users hit this bug when running Sid + Buster, please report that to this bug.] It's also possible this might be AppArmor related, because Mumble doesn't ship an AppArmor profile at the moment, and I see you've got AppArmor enabled. [...] > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr > (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled The best place I know to get more helpful advice in tracking down the audio difficulty is the #mumble IRC channel on irc.freenode.net. There are users in the IRC channel that regularly help with PulseAudio issues. Similar to your experience, for me PulseAudio is mostly a "magic" thing which I tweak a bunch to get what I need if I find I need something specific. I'll try to be more help if I can. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
Greetings, lemmel. lemmel: > Package: mumble > Version: 1.3.0+dfsg-1+b1 > Severity: grave1.3.0+dfsg-1 > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > fresh dist-upgrade (this day 02/28/20) brought up a mumble that lock all sound > on the host, the mumble client itself producing no sound. > > I did all kind of setup with the mumble client (OSS, ALSA, etc), but it did > nothing. > > Don't really know the reason as pulseaudo is kind of a magic thing to me, but > I > did retrieve several versions of the mumble client and saw that the current > git > code work correctly. > > Here is the summary of my builds (all extracted from the Git repository) and > tests : > - git clone https://github.com/mumble-voip/mumble.git mumble > cd mumble > git checkout tags/1.3.0 > git submodule init > git submodule update > ===> FAILED > > - git clone --single-branch --branch 1.3.x https://github.com/mumble- > voip/mumble.git > cd mumble > git submodule init > git submodule update > ===> FAILED > > - git clone https://github.com/mumble-voip/mumble.git > cd mumble > git submodule init > git submodule update > ===> SUCCESS > > So it may suggest that the current devel version fixes something about its > sound management. I normally upload mumble when there's a release snapshot available; I don't upload development versions from Git unless upstream specifically directs doing that. (Which only happened once because there was no 1.3.0 snapshot available for release at the time.) I don't know why upstream is taking so long to make another release snapshot. :-/ > PS : system informations > - 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux > - libc6 : amd64 2.29-10 > - mumble : 1.3.0+dfsg-1+b1 > - gcc -v : gcc version 9.2.1 20200224 (Debian 9.2.1-30) > - Qt : 5.12.5 > - pulseaudio : 13.0-5 I'm glad this specific section was added because I had tested Mumble in a Sid VM and the audio worked fine, but the version of pulseaudio in that VM ended up being held back to 12.2-4+deb10u1 and can't be upgraded due to package conflicts. I would like to test this with a more "pure" Sid VM to see what I find. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#952742: mumble: start locks sound for all application (even the client itself)
Package: mumble Version: 1.3.0+dfsg-1+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, fresh dist-upgrade (this day 02/28/20) brought up a mumble that lock all sound on the host, the mumble client itself producing no sound. I did all kind of setup with the mumble client (OSS, ALSA, etc), but it did nothing. Don't really know the reason as pulseaudo is kind of a magic thing to me, but I did retrieve several versions of the mumble client and saw that the current git code work correctly. Here is the summary of my builds (all extracted from the Git repository) and tests : - git clone https://github.com/mumble-voip/mumble.git mumble cd mumble git checkout tags/1.3.0 git submodule init git submodule update ===> FAILED - git clone --single-branch --branch 1.3.x https://github.com/mumble- voip/mumble.git cd mumble git submodule init git submodule update ===> FAILED - git clone https://github.com/mumble-voip/mumble.git cd mumble git submodule init git submodule update ===> SUCCESS So it may suggest that the current devel version fixes something about its sound management. PS : system informations - 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux - libc6 : amd64 2.29-10 - mumble : 1.3.0+dfsg-1+b1 - gcc -v : gcc version 9.2.1 20200224 (Debian 9.2.1-30) - Qt : 5.12.5 - pulseaudio : 13.0-5 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mumble depends on: ii libasound21.2.1.2-2 ii libavahi-compat-libdnssd1 0.7-5 ii libc6 2.29-10 ii libgcc-s1 [libgcc1] 10-20200222-1 ii libgcc1 1:10-20200222-1 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 ii libprotobuf17 3.6.1.3-2+b2 ii libpulse0 13.0-5 ii libqt5core5a 5.12.5+dfsg-9 ii libqt5dbus5 5.12.5+dfsg-9 ii libqt5gui55.12.5+dfsg-9 ii libqt5network55.12.5+dfsg-9 ii libqt5sql55.12.5+dfsg-9 ii libqt5sql5-sqlite 5.12.5+dfsg-9 ii libqt5svg55.12.5-2 ii libqt5widgets55.12.5+dfsg-9 ii libqt5xml55.12.5+dfsg-9 ii libsndfile1 1.0.28-7 ii libspeechd2 0.9.1-4 ii libspeex1 1.2~rc1.2-1.1 ii libspeexdsp1 1.2~rc1.2-1.1 ii libssl1.1 1.1.1d-2 ii libstdc++610-20200222-1 ii libx11-6 2:1.6.9-2 ii libxi62:1.7.9-1 ii lsb-release 11.1.0 mumble recommends no packages. Versions of packages mumble suggests: pn mumble-server ii speech-dispatcher 0.9.1-4 -- no debconf information
