| Bug ID |
12389
|
| Summary |
Wireshark no longer remembers what monitor it last ran on
|
| Product |
Wireshark
|
| Version |
2.0.3
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.3 (v2.0.3-0-geed34f0 from master-2.0)
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 WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, 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 C, 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
--
The GTK version of Wireshark remembers what monitor it was running on when it
was last shut down. If you drag Wireshark to the second monitor of a
dual-monitor system, and then shut down, Wireshark will start on the second
monitor on the next launch.
The QT version always launches on the first monitor, regardless of where it was
running at the last shut down. Having Wireshark remember where it was running
last is especially useful in virtual classes.
You are receiving this mail because:
- You are watching all bug changes.