https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067
Christopher Maynard <christopher.mayn...@igt.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|CONFIRMED |RESOLVED
--- Comment #20 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to Christopher Maynard from comment #19)
> Is there any update on this bug? Wireshark 2.0.x is end of life as of
> November 18, 2017 and Wireshark 2.2.x is end of life as of September 7,
> 2018. Does the bug still exist even with the latest stable version of
> Wireshark? If so, please provide updated build and other relevant
> information.
There hasn't been any additional feedback, so I'm going to close this bug. If
the problem can be reproduced using the lates stable version of Wireshark, then
feel free to reopen the bug and update the relevant information.
--
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
