https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12147
Christopher Maynard <christopher.mayn...@igt.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to Stig Bjørlykke from comment #1)
> I think this has been fixed in gf9e8a8ad or g9d4a676f in the upcoming 2.0.2
> release.
>
> Please try an automated build to see if the issue has been fixed for you:
> https://www.wireshark.org/download/automated/win64/
No feedback, so assuming it's been fixed. If the problem can still be
reproduced using the latest stable version of Wireshark and with the Qt UI
(since the GTK+ UI is no longer supported), then feel free to reopen the bug.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
