Wireshark-bugs: [Wireshark-bugs] [Bug 4569] Trying to Run Wireshark as "root" causes system to completely lockup (requires hard reset)

From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 12 Mar 2010 15:05:01 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4569

--- Comment #9 from Gary <gajimmy@xxxxxxxxxxx> 2010-03-12 15:04:59 PST ---
Here's the output for "tcpdump":
1.eth0
2.vmnet1
3.vmnet8
4.any (Pseudo-device that captures on all interfaces)
5.lo

I was not able to run the two "dumpcap" commands. Either of the those ("dumpcap
-D" or "dumpcap -S") causes the lockup problem.  Therefore, I do not have any
output, per se, though I imagine the complete computer freeze is a clue.

Next, as for which of the "Running Wireshark as You", I ran "the good way".  

Finally, sorry to do this to you, but this computer is being returned, probably
tomorrow.  I've now also discovered a similar freeze-up problem when running
VMWare, and that's not even using anything to do with "root".  However, if it
will help you, that problem occurs when dealing with the USB connections
between the host (this AMD box) and the various guest systems I've created
(mainly Windows XP and Win7 systems).  I need a system that will work now, and
I need both Wireshark and VMware to work.  So, this system will be traded for
an Intel-based CPU system.

If there's anything else you'd like me to do, please let me know and I'll do it
if I've not yet returned this computer.

Thanks again.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.