Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 1137] Wireshark will not start capture

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 5 Jan 2007 12:53:50 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1137


elittos@xxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED




------- Comment #10 from elittos@xxxxxxxxx  2007-01-05 12:53 GMT -------
this should have been closed.  The problem was a hardware issue with my old
laptop.  New laptop, no problems !!!


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

  • Prev by Date: [Wireshark-bugs] [Bug 1233] packet-ntp.c : fix bug in switch { }
  • Next by Date: [Wireshark-bugs] [Bug 964] Win98SE: Can't get pathname of Ethereal: GetModuleFileName failed
  • Previous by thread: [Wireshark-bugs] [Bug 1137] Wireshark will not start capture
  • Next by thread: [Wireshark-bugs] [Bug 1292] New: Win32: confusing setup target warning if cl.exe is not in path
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation