Users can hear me, but I can't hear them [debian] #735

Closed
opened 2026-02-20 19:35:37 -05:00 by deekerman · 9 comments
Owner

Originally created by @chrismp on GitHub (Dec 21, 2015).

My OS: Debian 8.2 (Jessie)
My desktop manager: MATE

I can listen to audio/video files, hear sound on YouTube and other sources.

I ran sudo apt-get install mumble and went through the audio setup wizard. I could hear myself during the setup.

Once setup, I opened MATE terminal. I ran mumble mumble://MyUserName@someserver.mumbleboxes.com:PORT_NUMBER_HERE to connect to a friend's server.

They could hear me, but I couldn't hear them. In the "Configuration" menu, I went thru each audio output device, but nothing worked. In fact, when a friend spoke, the mouth icon next to their username did not turn red to indicate they were speaking.

How do I fix this?

Originally created by @chrismp on GitHub (Dec 21, 2015). My OS: Debian 8.2 (Jessie) My desktop manager: [MATE](https://en.wikipedia.org/wiki/MATE_%28software%29) I can listen to audio/video files, hear sound on YouTube and other sources. I ran `sudo apt-get install mumble` and went through the audio setup wizard. I could hear myself during the setup. Once setup, I opened MATE terminal. I ran `mumble mumble://MyUserName@someserver.mumbleboxes.com:PORT_NUMBER_HERE` to connect to a friend's server. They could hear me, but I couldn't hear them. In the "Configuration" menu, I went thru each audio output device, but nothing worked. In fact, when a friend spoke, the mouth icon next to their username did not turn red to indicate they were speaking. How do I fix this?
Author
Owner

@MagiX13 commented on GitHub (Dec 21, 2015):

I have the same issue for a few days now, and am on jessie as well.
It worked fine ~ a week ago and I didn't change anything in my mumble settings. People can still hear me but I can't hear them
I tried

  • different settings regarding the output
  • different servers. I found one person that I could talk with on a lot of public servers, but that's about all
  • compiling mumble from source
  • server loopback

My guess would be that this is related to the recent kernel update to 3.16.7-ckt20-1+deb8u1. This is the only "big" update that I remember and might be related.
@chrismp which kernel are you using? (uname -a)

@MagiX13 commented on GitHub (Dec 21, 2015): I have the same issue for a few days now, and am on jessie as well. It worked fine ~ a week ago and I didn't change anything in my mumble settings. People can still hear me but I can't hear them I tried - different settings regarding the output - different servers. I found one person that I could talk with on a lot of public servers, but that's about all - compiling mumble from source - server loopback My guess would be that this is related to the recent kernel update to 3.16.7-ckt20-1+deb8u1. This is the only "big" update that I remember and might be related. @chrismp which kernel are you using? (uname -a)
Author
Owner

@hacst commented on GitHub (Dec 21, 2015):

Try if forcing TCP (With advanced checked go to Network -> Force TCP Mode) helps. If so this is likely caused by a Qt bug which randomly prevents us from receiving UDP.

Once https://github.com/mumble-voip/mumble/issues/1968 is resolved we should at least get automatic fallback to TCP if this issue occurs.

@hacst commented on GitHub (Dec 21, 2015): Try if forcing TCP (With advanced checked go to Network -> Force TCP Mode) helps. If so this is likely caused by a Qt bug which randomly prevents us from receiving UDP. Once https://github.com/mumble-voip/mumble/issues/1968 is resolved we should at least get automatic fallback to TCP if this issue occurs.
Author
Owner

@chrismp commented on GitHub (Dec 21, 2015):

@MagiX13 3.16.7-ckt20-1+deb8u1

@hacst That worked

@chrismp commented on GitHub (Dec 21, 2015): @MagiX13 3.16.7-ckt20-1+deb8u1 @hacst That worked
Author
Owner

@chrismp commented on GitHub (Dec 21, 2015):

@hacst Is there a way to start Mumble with the box checked? So I don't have to go to the sub-menu and check it each time I start it up?

@chrismp commented on GitHub (Dec 21, 2015): @hacst Is there a way to start Mumble with the box checked? So I don't have to go to the sub-menu and check it each time I start it up?
Author
Owner

@hacst commented on GitHub (Dec 21, 2015):

Hm. That setting should be stored like any other setting.

@hacst commented on GitHub (Dec 21, 2015): Hm. That setting should be stored like any other setting.
Author
Owner

@sharkwouter commented on GitHub (Jan 6, 2016):

@hacst I've been having the exact problem and have tried the same troubleshooting steps @MagiX13 used. I also use Debian Jessie and I stopped being able to hear people at about the time this issue was created. I use the Gnome desktop (version 3.14).

I've found out that I can only hear people who transfer no more that 72 kb/s. If people put down their quality settings I can hear them. Changing the maximum transfer on the server does not fix this and other users can hear each other (they are on Windows). I can hear myself with high transfer with server loopback.

If I check transfer from a person which I can't hear, I see transfer happening, but the lips don't light up.

It might have something to do with a kernel update, since https://www.debian.org/security/2015/dsa-3426 but I can't test the older kernel anymore, because I don't have the linux headers for it anymore (which means no xorg for me).

I posted on the forum as well: http://forums.mumble.info/viewtopic.php?f=4&t=2878#p7684

I haven't tested using TCP yet, will try that, but even if it works that is not a real solution to this problem.

I hope this helps.

@sharkwouter commented on GitHub (Jan 6, 2016): @hacst I've been having the exact problem and have tried the same troubleshooting steps @MagiX13 used. I also use Debian Jessie and I stopped being able to hear people at about the time this issue was created. I use the Gnome desktop (version 3.14). I've found out that I can only hear people who transfer no more that 72 kb/s. If people put down their quality settings I can hear them. Changing the maximum transfer on the server does not fix this and other users can hear each other (they are on Windows). I can hear myself with high transfer with server loopback. If I check transfer from a person which I can't hear, I see transfer happening, but the lips don't light up. It might have something to do with a kernel update, since https://www.debian.org/security/2015/dsa-3426 but I can't test the older kernel anymore, because I don't have the linux headers for it anymore (which means no xorg for me). I posted on the forum as well: http://forums.mumble.info/viewtopic.php?f=4&t=2878#p7684 I haven't tested using TCP yet, will try that, but even if it works that is not a real solution to this problem. I hope this helps.
Author
Owner

@philip-bl commented on GitHub (Nov 17, 2017):

I have this on Debian Stretch. After some time (1 to 15 minutes) I stop hearing people.

mumble 1.2.18-1
Linux 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

@philip-bl commented on GitHub (Nov 17, 2017): I have this on Debian Stretch. After some time (1 to 15 minutes) I stop hearing people. mumble 1.2.18-1 Linux 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
Author
Owner

@zeflap commented on GitHub (Mar 13, 2018):

@philip-bl Try 894ade2, available via adding the PPA at https://launchpad.net/~mumble/+archive/ubuntu/snapshot to your sources.list and using
apt-get source --build
This fixed the issue for me.

@zeflap commented on GitHub (Mar 13, 2018): @philip-bl Try 894ade2, available via adding the PPA at https://launchpad.net/~mumble/+archive/ubuntu/snapshot to your sources.list and using apt-get source --build This fixed the issue for me.
Author
Owner

@koudaiNEW commented on GitHub (May 30, 2025):

Configure -> compression -> quality, adjusting to below 50kb/s.
It worked.

@koudaiNEW commented on GitHub (May 30, 2025): Configure -> compression -> quality, adjusting to below 50kb/s. It worked.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mumble-mumble-voip#735
No description provided.