https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4000
Chris Maynard <christopher.maynard@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #3 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2010-11-29 17:59:52 PST ---
(In reply to comment #2)
> I have a completely different system now, so I am unable to determine if the
> original problem still exists or not.
OK, well I'm closing the bug as invalid, since it's almost certainly not a
Wireshark bug. If you experience this again, you might want to contact the
WinPcap developers about it first to hear what they have to say. Here's the
link to their contact page: http://www.winpcap.org/contact.htm. And if it does
prove to be a Wireshark bug after all, then you can either reopen this bug or
open a new one.
> I find it remarkable that you took more than 14 months to respond to my bug
> report!
There are hundreds of bugs filed in the Wireshark database with varying degrees
of difficulty in solving. Although anyone in the Wireshark community can post
comments, ask questions, make suggestions, or submit patches to fix bugs, there
are really only a limited number of developers who actually do. Those core
developers keep very busy with their day jobs - you know, the ones that pay the
bills - as well as devoting a significant amount of their free time on the
Wireshark project, which includes much more than just fixing the bugs that are
filed in the database. Developers come and go as their free time permits.
Developers also have their own interests and priorities, and that includes many
things completely separate from Wireshark altogether. We are a community of
volunteers and well, sometimes bugs just get missed or forgotten. Anyway, if
you keep some of that in mind, maybe you won't think it's really all that
remarkable.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
