ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 4748] New: Wireshark stops receiving packets soon after st

Date: Thu, 6 May 2010 03:26:11 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4748

           Summary: Wireshark stops receiving packets soon after start
                    capturing
           Product: Wireshark
           Version: 1.2.8
          Platform: Other
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Critical
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: yiyu.inbox@xxxxxxxxx


Build Information:
Compiled with GTK+ 2.18.8, (64-bit) with GLib 2.22.5, with libpcap 1.0.0, with
libz 1.2.5, without POSIX capabilities, with libpcre 7.9, without SMI, without
c-ares, without ADNS, without Lua, with GnuTLS 2.8.6, with Gcrypt 1.4.4, with
MIT Kerberos, without GeoIP, without PortAudio, without AirPcap.

Running on Darwin 10.3.0 (MacOS 10.6.3), with libpcap version 1.0.0, GnuTLS
2.8.6, Gcrypt 1.4.4.

Built using gcc 4.2.1 (Apple Inc. build 5659).

--
When I view the interface list, the packet counts go up as expected. As soon as
I start capturing on an interface, either ethernet or loopback, only "first
burst" of packets are received and displayed, then wireshark stops receiving
(as I observed with network traffic monitor) or displaying more packets.

When I open preferences, I get many many repeats of:
--BEGIN--
(wireshark:55381): Gtk-CRITICAL **: gtk_widget_has_screen: assertion
`GTK_IS_WIDGET (widget)' failed
--END--

in terminal. The number (55381) varies at different runs.


I have exactly same issue on a MacBook and an iMac. Both of them use Intel CPU,
run 10.6.3.

On the other hand, wireshark compiles and runs fine on a PC with Ubuntu 10.04
32-bit.

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