Wireshark-bugs: [Wireshark-bugs] [Bug 11766] New: USBPcap prevents mouse and keyboard from worki
Date: Tue, 24 Nov 2015 18:05:59 +0000
Bug ID 11766
Summary USBPcap prevents mouse and keyboard from working
Product Wireshark
Version unspecified
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Blocker
Priority Low
Component Extras
Assignee bugzilla-admin@wireshark.org
Reporter nicolas.calderon.asselin@gmail.com

Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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) Xeon(R) CPU           X5690  @ 3.47GHz (with SSE4.2), with 12285MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 31101

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information
--
Wireshark 2.0.0 installer offers installing the USBPcap plugin. This plugin has
a fairly major bug open since 2013
(https://github.com/desowin/usbpcap/issues/3). After installing Wireshark (with
teh USBPcap option selected) and rebooting, my keyboard and mouse were not
recognized (usb keyboard and mouse). Safe mode didn't help. I had to get a PS/2
keyboard to uninstall USBPcap (and all of Wireshark, just to be sure) so that
my usb and mouse would be functional again.


You are receiving this mail because:
  • You are watching all bug changes.