| Bug ID |
12519
|
| Summary |
Qt: pkt_comment used as custom column or as coloring rule not applied to updated frames.
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
Mac OS X 10.10
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.1.1-61-ge2e8456 (v2.1.1rc0-61-ge2e8456 from unknown)
Copyright 1998-2016 Gerald Combs <[email protected]> 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.3.2, with libpcap, without POSIX capabilities, with
GLib 2.36.0, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2,
with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with
QtMultimedia, without AirPcap.
Running on Mac OS X 10.10.5, build 14F1808 (Darwin 14.5.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with GnuTLS 2.12.19, with Gcrypt
1.5.0, with zlib 1.2.5.
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Added both a custom column and a coloring rule for pkt_comment. When a capture
with packet comments is opened the Packet Comment column will display “Yes” and
display the expected color for any packets with comments.
But if a packet comment is added or deleted from a frame, neither the custom
column not the coloring rule will be updated to reflect the new packet comment
state.
Partial workaround: reload capture
When capture file is reloaded the if any packet comments have been updated you
must select [Save] to preserve the updated comments before the reload will
commence.
You are receiving this mail because:
- You are watching all bug changes.
