| Bug ID |
12737
|
| Summary |
Wireshark 2 Configuration Persistence
|
| Product |
Wireshark
|
| Version |
2.0.5
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)
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.11.0, 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
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, with AirPcap 4.1.1 build 1800.
Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz (with SSE4.2), with 16323MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
The settings in the "View" menu do not persist when using Wireshark 2. Here are
the steps I am performing:
1. From the View menu, deselect the Main Toolbar so it isn't shown
2. Close Wireshark
3. Open Wireshark - the Main Toolbar is back to visible. I expect the setting
to persist!
I looked at the "recent" file in ...\AppData\Roaming\Wireshark\, and the
gui.toolbar_main_show: gets written to the proper value (according to the view
menu setting) when Wireshark is closed. However, when opened again, Wireshark
ignores this setting. The view menu shows the main toolbar as checked
(enabled), regardless of the contents of the "recent" file when launching the
app.
I have also tried creating a custom profile, and it behaves the same way;
Wireshark ignores the "recent" file when launching, and consequently the
settings are not persistent.
The Wireshark Legacy performs like I think it should. It respects the settings
in the "recent" file when opening.
This issue isn't limited to the view settings. The filters, status bar, and
probably more items, are similarly affected.
You are receiving this mail because:
- You are watching all bug changes.