Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mumble Server 1.4.x: warning message about ChannelListener Feature #1817

Closed
cfdisk opened this issue Apr 28, 2022 · 6 comments
Closed

Mumble Server 1.4.x: warning message about ChannelListener Feature #1817

cfdisk opened this issue Apr 28, 2022 · 6 comments

Comments

@cfdisk
Copy link

cfdisk commented Apr 28, 2022

Is your feature request related to a problem? Please describe.
The following message appears when connecting to mumble server (since 1.4.x):

"[WARNING]: This server has the ChannelListener feature enabled but your client version does not support it. This means that users might be listening to what you are saying in your channel without you noticing! You can solve this issue by upgrading to Mumble 1.4.0 or newer."

Describe the solution you'd like
matterbridge should report itself as a version 1.4 Client to get rid of the warning.

@cfdisk cfdisk added the enhancement New feature or request label Apr 28, 2022
@42wim
Copy link
Owner

42wim commented May 1, 2022

cc: @s3lph is this something you can take a look at?

@s3lph
Copy link
Contributor

s3lph commented May 2, 2022

This needs to be resolved in gumble, see layeh/gumble#49. For the time being I'd say it's safe to ignore this warning.

@ghost
Copy link

ghost commented May 20, 2022

FYI for anyone reading, if you want a temporary workaround, you can add something like:

IgnoreMessages="^\\*\\*\\[WARNING]\\*\\*:"

to your mumble config section in your TOML. If you wanted to perfectly match the message, you could, of course, extend the regex even more, but this seemed adequate as a short-term1 solution to suppress the message.


1could end up long-term, but you know :P

@42wim 42wim closed this as completed Jan 28, 2023
@ghost
Copy link

ghost commented Jan 29, 2023

I suppose this is closed under the assumption 880586b resolves this?

@ghost
Copy link

ghost commented Jan 29, 2023

I just tested the latest build (right from master branch!; specifically: this build) and the warning still seems to come through.

Edit: Yeah...the upstream library hasn't had any updates in years, so not surprising.

@42wim
Copy link
Owner

42wim commented Jan 29, 2023

@xnaas it's closed because we can't fix it, depending on upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants