[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	12910
Summary	Display jumps when opening packet in a new window on a dual-monitor system
Product	Wireshark
Version	2.2.0
Hardware	x86
OS	Windows 7
Status	UNCONFIRMED
Severity	Normal
Priority	Low
Component	Qt UI
Assignee	bugzilla-admin@wireshark.org
Reporter	Jim@agdatasystems.com

Build Information:
Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)

Copyright 1998-2016 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.3.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 16300MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
When you double-click a packet to open the packet in a new window, Wireshark's
Packet List will jump down by twenty or thirty packets and the selected packet
will change.

This only seems to happen when the new packet window opens on the same monitor
that Wireshark is running on, and only a two-monitor system.

To Reproduce:

1. Run Wireshark on a two-monitor system and leave it running on the primary
monitor.

2. Open a trace file, or capture traffic, so that there are more packets than
can be displayed on one screen.

3. Select one of the packets on the first screen.

4. Double-click any packet on that first screen to open it in a new window. The
new window will open on the first monitor and the display will jump.

5. Close the new packet window. Move Wireshark to the second monitor. Again,
double-click a packet to open in its own window. The new packet window will
open back on the first monitor, and the display will not jump.

6. Move the new packet window to the second monitor, where Wireshark is
running, and then close it.

7. Again, double-click a packet on the first screen to open in its own window.
This time the new packet window will open on the second monitor, where
Wireshark is running, and the display will jump.

This seems to stop happening after you scroll down a few screens. It doesn't
happen on a single-monitor system, and it doesn't happen when using the
right-click functionality and selecting "Show Packet in New Window"

---

      You are receiving this mail because:

• You are watching all bug changes.