Bug ID |
12222
|
Summary |
Output of `dumpcap -D` causes startup hangs when udev debug is enabled
|
Product |
Wireshark
|
Version |
unspecified
|
Hardware |
x86-64
|
OS |
Linux (other)
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
GTK+ UI
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
$ wireshark -v
Wireshark 2.0.1
Copyright 1998-2015 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.5.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.8, with GLib 2.46.2, without SMI, without c-ares,
without ADNS, with Lua 5.2, with GnuTLS 3.4.7, with Gcrypt 1.6.4, with MIT
Kerberos, without GeoIP, without QtMultimedia, without AirPcap.
Running on Linux 4.4.1-2-ARCH, with locale C, with libpcap version 1.7.4, with
libz 1.2.8, with GnuTLS 3.4.9, with Gcrypt 1.6.5.
Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz (with SSE4.2)
Built using gcc 5.3.0.
--
When udev debug output is enabled, either via kernel parameter or in
`/etc/udev/udev.conf`, the stderr of `dumpcap -D` contains a few lines, which
none of the frontents is unable to parse properly. As a result, tshark,
wireshark-qt and wireshark-gtk are unable to enumerate interfaces and don't
work.
To reproduce:
* edit `/etc/udev/udev.conf` on your system, add:
udev_log="debug"
* restart wireshark
You are receiving this mail because:
- You are watching all bug changes.