Wireshark-bugs: [Wireshark-bugs] [Bug 4811] New: popup error window won't go away when underlyin
Date: Sun, 30 May 2010 16:13:36 -0700 (PDT)

           Summary: popup error window won't go away when underlying trace
                    file becomes unavailable
           Product: Wireshark
           Version: 1.2.7
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]

Created an attachment (id=4710)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=4710)
Windows "Clipboard" file showing (hopefully) the error dialog box

Build Information:
Version 1.2.7 (SVN Rev 32341)

Copyright 1998-2010 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO

Compiled with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, without libpcre, with SMI 0.4.8,
with c-ares 1.7.0, with Lua 5.1, with GnuTLS 2.8.5, with Gcrypt 1.4.5, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 31 2010), with

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version, based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public

Check the man page and http://www.wireshark.org for more information.
This situation is as follows:

I opened Wireshark to view a trace and left it running, while it displays the
main packet list page.  Some time later the underlying trace file become
unavailable (actually due to the file being touched while on an SMB share).

Then this happens:

When clicking on one of the particular packets, a dialog box with the following
error arises:

An error occured while reading from the file [blah blah]:  Less data was read
than was expected.

The box contains an "ok" button and the normal Windows controls in the upper
right corner.

Problems:  The ok button doesn't do anything.  Neither do any of the window
controls in the upper right of the window border.  The Wireshark app itself is
waiting for some action to happen on the dialog box.  So basically, the entire
application is stuck until the window is killed in some other way.  This can be
done using "close" from task bar, but isn't convenient.

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