Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12510] New: Qt: Coloring Rules in Custom Column not update

Date: Sat, 11 Jun 2016 11:43:05 +0000
Bug ID 12510
Summary Qt: Coloring Rules in Custom Column not updated after change
Product Wireshark
Version Git
Hardware All
OS All
Status UNCONFIRMED
Severity Minor
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 2.1.1-21-gc755c88 (v2.1.1rc0-21-gc755c88 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.
--
Created custom columns to display the contents of the frame.coloring_rule.name
and frame.coloring_rule.string.  After changing the coloring rules that affect
coloring of the roes, the contents of the coloring rules custom columns are not
updated to refekcet the new rules.

Steps to reproduce:

1 - Open QT based Wireshark.

2 - Open an existing capture file.

3 - Create custom columns for displaying frame.coloring_rule.name and/or
frame.coloring_rule.string in the packet list.

4 - With colorization enabled the custom columns should now reflect the new
coloring rule.

5 - Open the Coloring Rules dialog and disable or enable some coloring rules
that will impact how some rows should be colored (for example if the trace
contains some ping packets disable the "ICMP" rule).

6 - Click [Ok] to close and apply the updated Coloring Rules.

7 - At this point the colorization of some rows will change, but the contents
of the coloring rules reported in the custom columns for the re-colorized rows
will contain the values from the previous rule.

Workaround:  Reload the capture file.


You are receiving this mail because:
  • You are watching all bug changes.