answered 2020-06-25 00:26:20 +0000
This is a known issue, reported in Bug 16281 and fixed in Wireshark version 3.2.3. I would recommend upgrading to the latest version of Wireshark, currently version 3.2.4 as of this writing.
