| Bug ID |
12378
|
| Summary |
Qt: At start of live capture frame 1 will not be selected until the arrival of second packet burst
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14516 [details]
Couple of window snapshots showing before and after arrival of second packet
Build Information:
Version 2.1.0-1030-g4b6d9a7 (v2.1.0rc0-1030-g4b6d9a7 from unknown)
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 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
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 14F1713 (Darwin 14.5.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
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.
--
At start of live capture frame 1 will not be selected until the arrival of a
second packet burst.
When a frame is selected in the packet list pane its contents will be displayed
in the packet details and packet bytes panes. After the start of a new packet
capture frame 1 normally is automatically selected.
But when capturing on a quiet network or when certain types of capture filters
are in use there could be a considerable amount of time between the arrival of
the first burst of packets and the second burst of packets. In this case while
the packet list pane will have one or more entries from the initial packet
burst, the packet details and packet bytes panes will be empty because no
packet has been selected. Frame 1 will not be automatically selected until the
arrival of the second burst of packets.
This behavior occurs whether or not "Automatically scroll to the last packet
during a live capture" is enabled.
This behavior was replicated on both OS X and Windows using buildbot images.
One method to replicate:
1 - Start Wireshark.
2 - Select a capture interface and prepare a capture filter for a pingable
target address of your choice (in this case the pingable target is 8.8.8.8):
> Capture filter: icmp and dst 8.8.8.8
3 - Start capturing.
4 - Send a single icmp ping packet to target address:
Note: The example below assumes OS X's ping command. On Windows and Linux
adjust the command to use appropriate ping options to send a single icmp ping
packet.
> $ ping -c 1 8.8.8.8
At this point Wireshark will have captured a single packet which will be
displayed ---but not selected --- in the packet list pane; because no packet is
selected the packet details and packet bytes panes will remain empty.
5 - Send a second single icmp ping packet to target address:
> $ ping -c 1 8.8.8.8
At this point Wireshark will have captured two packets. Frame 1 will now be
selected and its contents displayed in the packet details and packet byte
panes.
Workaround:
Click on a packet in the packet list.
You are receiving this mail because:
- You are watching all bug changes.