[Guy Harris <gharris@xxxxxxxxxxxx>]

> I've tried version 0.8.3, using binary package from Henri Gomez, and the
> filters seems to not work. They always say
> Unable to parse filter string (parse error)
> 
> This happens even with filters the program makes automatically when I double
> click over a captured package, such
> as
> 
> (ip.addr eq 192.168.2.1 and .......)

Double-click?  The filter in question looks like a "Follow TCP Stream"
filter, but I didn't think you could get that simply by double-clicking.

So are you saying that when you do a "Follow TCP Stream", you get a

	Unable to parse filter string (parse error)

error?

> Is this a documented bug?

No - "Follow TCP Stream", and other display filters (typed in the text
field in the middle of the row at the bottom of the window) work for me,
at least, and I haven't heard any other reports of them completely
failing to work.

You're not using that sort of filter as a capture filter - i.e., in the
"Filter:" text field in the window popped up by the "Start" item in the
"Capture" menu - are you?  If so, that won't work, unfortunately -
capture filters have a different syntax from display filters.