Wireshark-bugs: [Wireshark-bugs] [Bug 12582] New: (Qt5) app menus won't pull down
Date: Sat, 02 Jul 2016 23:06:49 +0000
Bug ID 12582
Summary (Qt5) app menus won't pull down
Product Wireshark
Version 2.0.4
Hardware x86-64
OS Mac OS X 10.11
Status UNCONFIRMED
Severity Major
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter fjarlq@gmail.com

Build Information:
Wireshark with Qt 5 was installed via Homebrew by running:
brew install --with-qt5 wireshark

Wireshark 2.0.4 (Git Rev Unknown from unknown)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> 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.6.1, with libpcap, without POSIX capabilities, with
libz 1.2.5, with GLib 2.48.1, without SMI, with c-ares 1.11.0, without Lua,
with
GnuTLS 3.4.13, with Gcrypt 1.7.1, with MIT Kerberos, with GeoIP, with
QtMultimedia, without AirPcap.

Running on Mac OS X 10.11.5, build 15F34 (Darwin 15.5.0), with locale C, with
libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 3.4.13,
with Gcrypt 1.7.1.
Intel(R) Xeon(R) CPU           E5462  @ 2.80GHz

Built using clang 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31).

--
In order to avoid the problem of bug 12067 (can't resize packet trace panes
when built with Qt4), I'm building Wireshark with Qt 5 on my OS X systems.

But, after starting Wireshark, the app menus do not pull down when selected by
the mouse. To reproduce:

1. brew install --with-qt5 wireshark
2. start Wireshark
3. use the mouse to try to open any of the app menus (the pull-down menus on
the OS X menu bar)
4. observe that none of the app menus will pull down or react to the mouse in
any way

Workaround: The app menus function properly after switching focus to another
app and then switching focus back to Wireshark.


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