Wireshark-bugs: [Wireshark-bugs] [Bug 8324] New: VoIP Call Flow dialog does not fully update on
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 12 Feb 2013 22:53:14 +0000
Bug ID 8324
Summary VoIP Call Flow dialog does not fully update on interaction
Classification Unclassified
Product Wireshark
Version 1.8.5
Hardware x86-64
OS Windows 7
Status UNCONFIRMED
Severity Normal
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter tuba.terry@gmail.com 

Created attachment 9983 [details]
Screenshot of VoIP Call Flow Dialog

Build Information:
Stable build downloaded from site:
Windows 64-bit: 1.8.5 SVN Rev 47350 from /trunk-1.8
--
When interacting with the VoIP Call Graph Analysis tool, the tool's interface
does not fully refresh on mouse clicks or keyboard presses. (Accessed via the
Telephony -> VoIP Calls menu option, then selecting any number of calls and
clicking Flow - I tested 1, 2, 3 and 4 calls in the Flow.)

Clicking or arrow-keying through the first five packets in a flow works as
expected - the selected packet is highlighted in the Graph Analysis window and
also in the main Wireshark window.  

Clicking or arrow-keying to any packets after that will select the specified
packets in the main Wireshark window, but the Graph Analysis window shows no
change.  (Example in screenshot).  If the call flow is long enough to have a
scroll bar, scrolling down will only update the space where the first five
packets were.

Changing the size of the Graph Analysis window refreshes the entire window and
brings its appearance to match its current state.

Marked priority as Normal because this is not preventing use of the feature,
but it does make visual comparisons difficult


Problem experienced on an Intel system with Nvidia graphics (latest drivers)
and an AMD-based system, also with Nvidia graphics. (latest drivers)  No other
alternative hardware to test on.  I've seen this problem on earlier wireshark
revisions over time, but I don't have any data on that.

You are receiving this mail because:
  • You are watching all bug changes.