This bug should be fixed in Wireshark 3.2 and later as described at 
https://gitlab.com/wireshark/wireshark/-/issues/15865.

Reply via email to