Wireshark-bugs: [Wireshark-bugs] [Bug 2967] New: During packet capture Wireshark "blinked" and s
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2967
Summary: During packet capture Wireshark "blinked" and started
capturing anew
Product: Wireshark
Version: 1.0.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jmclean@xxxxxxxxx
Build Information:
Version 1.0.1 (SVN Rev 25639)
Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.8,
with ADNS, with Lua 5.1, with GnuTLS 2.3.8, with Gcrypt 1.4.1, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
While t/s a problem I was having with a printer I was using Wireshark to
capture packets to/from the printer's ip address to see if I could recognize
any issues. I asked the girl to send the printjob that was giving her problems
and while the capture was in process I noticed the Wireshark screen "blink" and
it cleared the capture window and started anew begining with a new packet # 1.
This happened twice. I subsequently attempted to recreate the odd event adding
a continuous ping of the ip address which I thought would act as a keepalive
and not have the same strange happenings. It didn't make any difference. I'm
not sure if something in her print has caused the strange phenomenon but
coincidently the trouble print job worked fine. I noticed, while looking for
the captured data that under the "open recent" (see attachment #2)there were
multiple capture files that were created with an appended suffix. Never saw
this before.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
