If you mark (or unmark) the currently-selected frame, the packet details still say it's not marked (or it is marked)

Guy Harris said:

Build Information: Version 2.5.0 (v2.5.0rc0-2328-g72edf4e2)

Copyright 1998-2018 Gerald Combs <gerald@‍wireshark.org> and contributors. License GPLv2+: GNU GPL version 2 or later <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.5.0, with libpcap (including remote capture support), without POSIX capabilities, with GLib 2.36.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with GeoIP, with nghttp2 1.21.0, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with SBC, with SpanDSP, with bcg729.

Running on Mac OS X 10.12.6, build 16G1036 (Darwin 16.7.0), with Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (with SSE4.2), with 16384 MB of physical memory, with locale en_US.UTF-8, with libpcap version 1.9.0-PRE-GIT, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with zlib 1.2.8, binary plugins supported (13 loaded).

Built using clang 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2).

If you mark or unmark the currently-selected frame, it doesn't get redissected, so the packet details pane continues to reflect its state before it was marked or unmarked.

added uiqt versiondev labels

mentioned in merge request !9546 (merged)

closed with commit 199ecf29

mentioned in commit 1e584d55

mentioned in merge request !9547 (merged)

mentioned in commit 2662f55b

mentioned in merge request !9548 (merged)

mentioned in commit 4312130d

mentioned in commit 6acfae62

mentioned in issue #17743 (closed)

If you mark (or unmark) the currently-selected frame, the packet details still say it's not marked (or it is marked)

Child items 0

Activity