wireshark 0.99.7 - X Window System error while capturing

[be.public@…]

I'm using Mac OS X 10.5, and Port Version 1.6.0.

Wireshark 0.99.7 always crashes after capturing approx. 5 seconds with this error:

beninb:~ beni$ sudo 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 11374 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.)

I know, running it as root is not good. but wireshark can't access my network-cards when running as standard user.

This bug always occurs, on interface 'en0' and 'lo0'. i couldn't test it with the other interface 'en1', as i have no Wireless LAN here.

Please contact me, if you need more information about my system.

benedikt k.

[ulrich.clara@…]

Hi,

i have the same behaviour ... with or without sudo starting. I testet even with WLAN on en1 and got this message after a few seconds:

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 30812 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.)

Ulli

[ryandesign (Ryan Carsten Schmidt)]

Cc wireshark maintainer.

[ryandesign (Ryan Carsten Schmidt)]

Greg Hauptmann ​reported the same problem on the macports-users mailing list.

[ghosthound]

This is a known issue w/ Leopard's X11, ideally we'll see a (n Apple) fix shortly.

[ghosthound]

Also, this is a duplicate of 13012 (initial problem)