| Bug ID |
12845
|
| Summary |
First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"
|
| Product |
Wireshark
|
| Version |
2.2.0
|
| Hardware |
x86
|
| OS |
Windows 10
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)
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 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 10, build 10586, with locale Czech_Czech
Republic.1250, with Npcap version 0.07, based on 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) i5-3210M CPU @ 2.50GHz (with SSE4.2), with 8141MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
After installing 2.2.0, the first start hung at the "initializing tap
listeners". Up to Pascal's advice to the OP at
https://ask.wireshark.org/questions/55394/upgrade-to-wireshark-22-error , I've
removed USBPcapCMD.exe (and my test extcap binary) from my "C:\Program
Files\Wireshark\extcap" folder and tried again, this time Wireshark started
normally. After putting the two binaries back, Wireshark continued to start
normally, and the interfaces available through these binaries became available.
After reboot, the situation was the same, with the binaries in the extcap
folder, Wireshark did not start.
But I've tested it further and it is even more fuzzy. If I reboot and keep the
binaries in extcap directory, Wireshark hangs the same way, but the next start
succeeds even with the binaries in place. If I reboot and remove the binaries
before starting Wireshark, Wireshark starts OK, but the first start after I put
them back fails. Next start is fine again.
So the conclusion seems to be that only the first load of the extcap binaries
(actually, USBPcapCMD.exe alone is enough) after install or reboot causes a
problem.
Adding my extcaptest.exe after Wireshark "got used" to USBPcapCMD.exe did not
cause another hang.
My Lua plugins in profile\plugins directory may remain in place as they do not
prevent Wireshark from starting.
(Bonus question: how would I copy the build information as required above if
Wireshark would eventually not start at all?)
You are receiving this mail because:
- You are watching all bug changes.