Comment # 4
on bug 11911
from Pierre Fortin
(In reply to Peter Wu from comment #2)
> Actually, "wireshark -i usbmon2 -k" is only broken on master, 2.0 seems
> unaffected.
Never reported anything about usbmon...
> What do you mean by "only [possible] from the main screen"?
That it only works when starting from the main screen, not the dialog.
> At some point I
> managed to have the Options / Stop / Start buttons disabled, but I cannot
> reproduce that anymore (maybe related to preference since I wiped those for
> testing). Another issue I had in the past was related to selection of the
> "eth0" device by default, but I have not seen that today.
>
> Could you clarify your steps, including possible other factors that could
> influence it?
>From my original report with clarifications:
Examples:
1. Start a capture. Get a successful capture. Stop. Start ==> I get "No
interface selected"
This should remember the interface previously used. i.e., why is the interface
used successfully just before trying to restart a capture not maintained?
2. Start a capture. Get a successful capture. Stop. Capture Options. Start. ==>
I get a "dry capture" -- IOW, capture appears to be running; but nothing is
captured.
This requires that for each capture attempt, I have to wait to see some packets
being captured before I can be sure wireshark is actually capturing before
proceeding to my next step, such as triggering a download.
3. Start a capture. Get a successful capture. Stop. Getting a successful
capture requires these steps:
Capture Options->Select interface->Start.
Stop. ==> I get No packets captured.
This stop gets me to the main scree from which I can start a live capture.
Example 3 is the only way to be sure I have a working capture.
Not sure how I can make it clearer without a video...
HTH
You are receiving this mail because:
- You are watching all bug changes.