start application, start packet capture, allow time to pass to capture
some packets, stop capture, click save, enter a filename to be used as
the save file (preexisting state does not seem to matter), click the
OK button in the save-file dialog.
ethereal will immediately exit, printing the following in the process:
Gdk-ERROR **: BadWindow (invalid Window parameter)
serial 13968 error_code 3 request_code 15 minor_code 0
exit code is '1':
.live.[root@i386-3es:~]# echo $?
The save file will exist, and can be read by ethereal without problem.
It seems to contain the full contents of the file, but I've not
conducted exhaustive comparisons on large sets of live-captured
packets. I'm open to suggestions for test strategies, if any might be
Seems to happen with total reliability, I have found no workaround
using the steps listed above.
Expected behavior is for the application to silently continue running.
I'm seeing this too using FC3. not 100% repeatable from saving, but
This is really weird as I haven't seen this happening on any of my
machines and I'm using ethereal quite often. I guess you can't send me
strace when this bug happens only occasionally :( Anyway new version
of ethereal is avaliable now in development tree - ethereal-0.10.7. I
don't see anything in changelog mentioning that file saving was fixed
but it would be great if you try it out.
Fixed in ethereal-0.10.8