Describe the bug
On master, IPv6 addresses are no longer visible. Connecting via IPv6 still works, but the addresses are not visible in the user interface. IPv6 addresses are visible in 1.3.0.
Steps to Reproduce
Hover over a server with IPv6 support in Mumble Server Connect or while connected to a server look at an IPv6 connected user's Connection Information IP Address.
Screenshots


Notice how the IPv6 address is not visible but the port is.
IPv4 address whited out for privacy.
Desktop:
Additional context
This issue is present on the current master, but I am unsure what commit introduced the issue.
Do you have the address of a server using IPv6 at hand so I can try it out for myself? :)
If you run a server on localhost (I assume that you do since you work on Murmur), then it will support IPv6 and IPv4.
I assume that you do since you work on Murmur
I do indeed.
it will support IPv6 and IPv4.
But I'm still shown the IPv4 address. Do you happen to know a way to force it to only use/show IPv6?
Do you happen to know a way to force it to only use/show IPv6?
You can set the host to '[::1]' which is the ipv6 version of 127.0.0.1.
Okay thanks. Will try that :)
Hovering over the server in Mumble Server Connect shows both IPv6 and IPv4, but you will only be able to see the port portion of the IPv6. Here is a better image of what it looks like in 1.3.0.

To clarify even further, in 1.3.0 it correctly shows Addresses 127.0.0.1:64738, [0::1]:64738 but in recent versions incorrectly shows Addresses 127.0.0.1:64738, :64738.
I just bisected the commits between the state of 1.3.0 and current master and b263b91340fb8b359e34626de880f606cfd9c116 turned out to be the cause of this.
Okay I messed that commit up. This is what you get for blindly replacing deprecated functions without checking the docs for the replacement :man_facepalming:
QString::asprintf is a static function and thus it only works if I assign its return value to a variable. Which I didn't...