Wireshark-bugs: [Wireshark-bugs] [Bug 10073] New: adding capture options doesn't make wireshark
Date: Sun, 04 May 2014 10:20:01 +0000
Bug ID 10073
Summary adding capture options doesn't make wireshark start capturing
Classification Unclassified
Product Wireshark
Version 1.11.x (Experimental)
Hardware x86
OS Mac OS X 10.9
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter rols@rols.org

Build Information:
QMetaObject::connectSlotsByName: No matching signal for on_bStart_clicked()
QMetaObject::connectSlotsByName: No matching signal for on_bStop_clicked()
FIX: packet list heading menu sensitivity 
wireshark 1.11.4-54-g9496733 (v1.11.4-rc1-54-g9496733 from unknown)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
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.2.1 with GLib 2.36.0, with libpcap, with libz
1.2.3,
without POSIX capabilities, with SMI 0.4.8, without c-ares, without ADNS, with
Lua 5.1, without Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT
Kerberos, with GeoIP, without PortAudio, with AirPcap.

Running on Mac OS X 10.9.3, build 13D55 (Darwin 13.2.0), without locale, with
libpcap version 1.3.0 - Apple version 41, with libz 1.2.5, GnuTLS 2.12.19,
Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).

--
running wireshark from the command line with options to request it starts
capturing immediately have no effect, it just brings up the usual gui asking me
to 'capture', 'open a file' or 'learn about wireshark'. 

I've tried

wireshark -i lo0 -k

as a basic command. Replaced lo0 with en0 or '0', '1' and left the -i option
out completely. Tried with and without the -k, tried -S, -p and a few other
options. I just get the normal wireshark gui and no capture starts, I have to
select the interface and any filter I want manually in wireshark. 

tshark -i lo0 works fine.


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