Wireshark-bugs: [Wireshark-bugs] [Bug 11468] New: Changing name resolution via View->Name Resolu

Date: Mon, 24 Aug 2015 20:37:00 +0000
Bug ID 11468
Summary Changing name resolution via View->Name Resolution menu does not update display of currently-shown frames
Product Wireshark
Version Git
Hardware x86
OS All
Status UNCONFIRMED
Severity Normal
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 1.99.9 (v1.99.9rc0-381-g5b961f5 from master)

Copyright 1998-2015 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 4.8.6, with libpcap, without POSIX capabilities,
without libnl, with libz 1.2.8, with GLib 2.42.2, without SMI, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 3.3.17, with Gcrypt 1.6.3, without Kerberos,
without GeoIP, without PortAudio, without AirPcap.

Running on Linux 4.1.5-100.fc21.x86_64, with locale C, with libpcap version
1.7.3, with libz 1.2.8, with GnuTLS 3.3.17, with Gcrypt 1.6.3.
        Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (with SSE4.2)

Built using gcc 4.9.2 20150212 (Red Hat 4.9.2-6).
--
I happened to enable Transport Resolution in the Qt UI by selecting it in the
View->Name Resolution menu.

It appeared to have no effect: I still saw unresolved transport ports in the
destination port column (which I had added) and the protocol-details pane
showed only unresolved port names.

But if I scrolled down so I could see some new frames the column and
packet-details show correctly resolved ports (in the newly displayed frames;
the previously-shown 25 frames never refresh to show the resolved port names).

Changing the preference via Edit->Preferences does not have the problem: the
already-displayed frames are redissected and the name resolution takes effect.


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