| Bug ID |
11448
|
| Summary |
Qt Wireshark - After enabled/disabling RTCP in Enable Protocols dialog Wireshark mouse and Menu options are unusable
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
Mac OS X 10.10
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13801 [details]
Sample trace file with some rtp packets dissected as rtcp
Build Information:
Wireshark 1.99.9-230-g821ea20 (v1.99.9rc0-230-g821ea20 from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
libz 1.2.3, with GLib 2.36.0, with SMI 0.4.8, without c-ares, without ADNS,
with
Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
without PortAudio, without AirPcap.
Running on Mac OS X 10.10.4, build 14E46 (Darwin 14.4.0), with locale C, with
libpcap version 1.5.3 - Apple version 47, with libz 1.2.5, with GnuTLS 2.12.19,
with Gcrypt 1.5.0.
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (with SSE4.2)
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
While testing possible workarounds for Bug 11446 I stumbled into an Qt UI issue
when a trace file is open and one disables or enables a protocol and then
closes the Enabled Protocols window with [Ok]. Once the Enabled Protocols
dialog disappears, Wireshark's Qt UI will generally no longer respond to mouse
events. But it will respond to a limited number of keystroke events (TAB key,
UP-arrow and DOWN-arrow, ENTER and some action key like Command-W (for close
file on OS X.))
On OS X one can open the various menus but virtually all items will be greyed
out. Wireshark can not be shutdown gracefully; one must kill the Wireshark
process. If NO trace file is opened when one changes a protocol's enabled
state from the Enabled Protocols dialogs then once the change is applied Qt
Wireshark will respond normally.
I have only tested/verified this behavior on OS X.
Steps to reproduce issue:
1 - Start Qt Wireshark
2 - Open the attached trace file rtp_decoded_as_rtcp.pcap (this is one of the
two trace files from bug 11446).
3 - Open the "Enabled Protocols" window by: A - selecting the Analyze / Enable
Protocols...[1] menu item, B - by selecting the "Disable Protocol" menu item
from the Right-mouse click from the packet-list item Context Menu (this second
option is new with the Qt UI) or C - Using the action key sequence
Command-Shift-E.
4 - Within the Enabled Protocols dialog click in the "Search" text entry field
and enter "rtc" in the filter field to quickly navigate to relevant protocols.
5 - Click on the "RTCP" checkbox to enable or disable the RTCP protocol.
6 - Click on [Ok] to apply the change and close the window.
7 - Try to click on different elements in the Qt Wireshark window; the Qt UI
will respond with a sound but will not select the clicked on item. But
pressing up/down arrow will move cursor in Packet List. Pressing TAB will
allow one to move to the Packet Details and Hex pane sections etc.
8 - Trace file can be closed with command-W and new trace file opened by
scrolling up/down from the list of previously open trace file using the
keyboard and then pressing ENTER.
9 - Kill the Wireshark process from CLI of via OS X's Force Quit menu item.
[1] NOTE: The menu item in Qt Ui is named "Enable Protocols..." whereas as in
the GTK+ UI it is named "Enabled Protocols...". Arguably the menu item name in
the Qt UI should be consistent with the dialog name of "Enabled Protocols".
You are receiving this mail because:
- You are watching all bug changes.