https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16774
Bug ID: 16774
Summary: Packet Bytes window is not showing hex and bytes
correctly (because the UI misinterprets the screen
scale level information provided by the OS)
Product: Wireshark
Version: 3.2.6
Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
Severity: Normal
Priority: Low
Component: Qt UI
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Build Information:
Version 3.2.6 (v3.2.6-0-g4f9257fb8ccc)
Copyright 1998-2020 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<https://www.gnu.org/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.12.8, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.3, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.15.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.39.2, with brotli, with LZ4, with
Zstandard, with Snappy, with libxml2 2.9.9, with QtMultimedia, with automatic
updates using WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled
resampler), with SBC, with SpanDSP, with bcg729.
Running on 64-bit Windows 10 (2004), build 19041, with Intel(R) Core(TM)
i7-9850H CPU @ 2.60GHz (with SSE4.2), with 16166 MB of physical memory, with
locale Swedish_Sweden.1252, with light display mode, without HiDPI, with Npcap
version 0.9994, based on libpcap version 1.9.1, with GnuTLS 3.6.3, with Gcrypt
1.8.3, with brotli 1.0.2, without AirPcap, binary plugins supported (19
loaded). Built using Microsoft Visual Studio 2019 (VC++ 14.27, build 29111).
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and https://www.wireshark.org for more information.
--
Packet Bytes pane places it's columns wrong if Wireshark UI is active on a
monitor with a different Scale and Layout setting than the primary monitor.
(as far as I can tell, all the other window panes look alright.)
To reproduce,
a. You need a system with at least two monitors.
1. Press [win]+[I] to start Windows Settings.
2. Pick the settings pane System.
3. Under Scale and Layout, pick a new scale for your primary monitor that has a
higher number than the secondary monitor. (How about 125%?)
4. Ensure that the scale setting for the secondary monitor is set to a lower
number than the setting on the primary monitor. (How about 100%?)
5. Run Wireshark.
(Wireshark cannot be active when the scale settings are altered. Start the
application AFTER altering the scale settings.)
6. Activate the Packet Byte pane.
7. Drag the UI window back and forth between the two monitors and compare the
looks on the Packet Byte window.
Conclusion,
- If the two monitors has the same scale settings, the Packet Byte pane looks
like it should.
- If the scale differs, it only looks decent on the primary monitor. (to the
extent where it's possible to render the Packet Byte pane useless on a
secondary monitor.)
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <[email protected]>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:[email protected]?subject=unsubscribe
