https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5932
--- Comment #13 from Jim Aragon <Jim@xxxxxxxxxxxxxxxxx> 2011-05-21 15:34:00 PDT ---
(In reply to comment #12)
> How do you start wireshark normally? Clicking or double clicking
> on an Icon?
Ok, you're on to something! I normally start Wireshark by double-clicking an
icon that executes the following command:
"C:\Program Files\Wireshark\wireshark.exe" -k -c 20000 -i 1
The "-k -c 20000 -i 1" parameters were added by me.
I also have an icon that launches Wireshark with no command-line parameters:
"C:\Program Files\Wireshark\wireshark.exe"
When I launch Wireshark from this icon, the capture filters work normally.
I took the command-line parameters out, and tried them individually.
"C:\Program Files\Wireshark\wireshark.exe" -k
Capture filters did not work properly.
"C:\Program Files\Wireshark\wireshark.exe" -c 20000
Capture filters did work properly.
"C:\Program Files\Wireshark\wireshark.exe" -i 1
Capture filters did not work properly.
> Can you edit the preferences file and change
> console.log.level: 18
> to
> console.log.level: 255
> Start wireshark from a shell. Then you should see the debug output in the shell
> (I think it is called cmd in Windows). Can you start capturing the traffic
> using
> the capture filter and provide the debug output?
I did this, but did not see any output in the cmd window.
The results of launching Wireshark from the command prompt duplicated the
results of launching it from the icons: With the command-line parameters,
capture filters did not work properly; without command-line parameters, capture
filters did work properly.
> Thanks for helping to debug the problem. I can't reproduce it on my machine...
Thanks for working on it.
Jim
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
