On Thu, Jan 24, 2008 at 02:18:39PM -0500, Rob Heilman wrote:
> Ever since the upgrade to Leopard/10.5 Wireshark has been fairly
> unstable. Errors like below seems to happen at random. I am currently
> running 10.5.1 and installed from ports (more info below) Is anyone
> else seeing this? If you have it running stable, did you install 10.5
> as an upgrade from 10.4 or as a clean install? I completely rebuilt
> ports from scratch and would like to avoid a clean install of the OS if
> possible. X11 was installed from the Leopard DVD. I also installed the
> new Xcode as required but don't remember if the 10.5 upgrade deleted the
> previous version or if my install was actually considered upgrading.
>
> -Rob Heilman
>
> =============================================================================
>
> Ares:~ rheilman$ wireshark
> The program 'wireshark' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
> (Details: serial 753345 error_code 8 request_code 152 minor_code 4)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error() function.)
This is a known issue, and I hear that the latest Xquartz (available
at http://trac.macosforge.org/projects/xquartz) resolves this issue.
If you're not interested in trying out (essentially) third party
software, you may have to wait until Apple rolls this fix into a Software Update.
See also:
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1953
-eric