Advertisement

10.27.2007 at 09:53AM PDT, ID: 22922143
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Running wireshark on mac os x 10.5

Asked by thomasbonham in Mac OS 10.5 (Leopard), Mac OS X, Mac OS 10.4 (Tiger)

Tags: , , ,

I just installed the new Mac OS X 10.5 and I'm having problems with WireShark running. The way I start it is by going to /usr/local/bin then run ./wireshark it opens and then when I start to caption it will working for up to 50 packets at most and then I get this error from the command line.

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

Now has the error says to do run it will a --sync and that doesn't help. It just gives back the same error.

Thanks,

ThomasStart Free Trial
[+][-]12.11.2007 at 03:24PM PST, ID: 20453853

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]12.11.2007 at 03:35PM PST, ID: 20453927

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Mac OS 10.5 (Leopard), Mac OS X, Mac OS 10.4 (Tiger)
Tags: wireshark, mac, x, os
Sign Up Now!
Solution Provided By: thomasbonham
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628