Wireshark-bugs: [Wireshark-bugs] [Bug 10313] Qt Wireshark, when run directly from the command li
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 27 Jul 2014 22:47:50 +0000

changed bug 10313

What Removed Added
Summary Menu not showing Qt Wireshark, when run directly from the command line, leaves the input focus in a weird state
OS Mac OS X 10.4 Mac OS X 10.9

Comment # 3 on bug 10313 from 
I've confirmed this on 10.9; if I run ./wireshark-qt, or "open ./wireshark-qt",
or double-click wireshark-qt from the Finder, Terminal's menu is displayed, but
it doesn't work.  If I click on the Dock icon for wireshark-qt (a "generic
executable" icon), that doesn't fix it; if I click on the Desktop, the input
focus goes fully to the Finder, and if I click on the wireshark-qt window, it
gets the full input focus.

If I run the executable from, for example, TextEdit from the command line
(/Applications/TextEdit.app/Contents/MacOS/TextEdit), Terminal's menu remains,
but it is, at least, functional.  Clicking on it in the Dock gives TextEdit the
full input focus.

This does not happen on 10.8.

If I build a Wireshark app bundle on 10.9, and open that, it works correctly.

This could be a Qt issue - it might be doing something that happened to work
prior to 10.9 but that fails to work on 10.9 and later.  It might also be that
we're doing something with Qt that we shouldn't be.

A quick search didn't find any immediately obvious bugs concerning this in the
Qt bug database.

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