Wireshark-bugs: [Wireshark-bugs] [Bug 1188] New: Automatic Scrolling not showing most recent pac

Date: Sun, 29 Oct 2006 03:05:28 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1188

           Summary: Automatic Scrolling not showing most recent packets
           Product: Wireshark
           Version: 0.99.3
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: Minor
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: crsacer@xxxxxxxxx


Build Information:
wireshark 0.99.3a
Compiled with GTK+ 2.10.6, with GLib 2.12.4, with libpcap 0.9.1,
with libz 1.2.2, with libpcre 6.7, with Net-SNMP 5.2.3, with ADNS, without Lua.
Running with libpcap version 0.9.1 on FreeBSD 6.0-SECURITY.
--
Problem occurs when "Automatic scrolling in live capture" set.

Once the Packet List pane is full, Auto Scroll should scroll to the bottom of
the packet list when new packets appear.

During a live capture, problem can be observed by capturing a "burst" of
packets (e.g. ping -f -c5 192.168.1.7).

When a burst of packets is received, the packets are appended to the bottom of
the packet list, however Auto Scroll does not scroll the list down, so the
packets remain out of view.  When the next burst of packets arrives, the packet
list is first scrolled to the bottom, then the new packets are appended to the
bottom list (out of view).  The result is that you must manually scroll the
list down to view the most recent packets.

It seems that Auto Scroll is getting ahead of itself and scrolling to the
bottom of the packet list before the new packets are displayed.

- Also occurs on
ethereal 0.10.14
Compiled with GTK+ 2.8.12, with GLib 2.8.6, with libpcap 0.9.1, with libz
1.2.2,
with libpcre 6.6, with Net-SNMP 5.2.2, with ADNS.
Running with libpcap version 0.9.1 on FreeBSD 6.1-RELEASE.

- Similar to BUG 632 (fixed)


-- 
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.