| Bug ID |
11977
|
| Summary |
Wireshark hangs with a profile directory with no recent file
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
CONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14211 [details]
Capture file downloaded from the wireshark website. Any capture file should
show the problem with a new profile.
Build Information:
Version 2.0.1 (v2.0.1-0-g59ea380 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.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 10, build 10586, 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-3770K CPU @ 3.50GHz (with SSE4.2), with 32660MB of
physical memory.
--
The current Wireshark 101 book uses a downloaded zip file to create the
"HTTP-DNS_Errors" profile.
The process has apparently changed in Wireshark 2.0. Looks like you have to use
the "Profile Copy" icon next to the "+" and "-" symbols at the bottom of the
Wireshark Configuration Profiles window to create a profile from the Default
profile.
(Right click on "Profile" on the right side of the Task Bar and then left-click
on "Manage Profiles".) This will provide a "recent" file in the user profile
folder. You can then manually copy the 3 unzipped book configuration files into
the new user profile.
Without a valid "recent" file in the new folder, Wireshark goes in to a
"Not-responding" mode and hangs forever. The same is true if you try to create
a "Troubleshooting" or "wireshark101" profile in the user profile directory.
I'm guessing you have to do the same thing for any other new profile that you
want to create from the Default profile.
If you simply create a new profile, without the recent file, Wireshark will
"Not Respond" regardless of the capture file you try to use.
I have attached the zip file with the capture file from the Wiresharkbook.
But any capture file should show the same issue.
You are receiving this mail because:
- You are watching all bug changes.