Wireshark-bugs: [Wireshark-bugs] [Bug 10890] Qt Wireshark - On OS X Launching Wireshark from bas
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 23 Jul 2015 03:17:25 +0000

changed bug 10890


What Removed Added
CC   lukem-wireshark@mewburn.net

Comment # 11 on bug 10890 from 
(In reply to Jim Young from comment #10)
> Is this QTBUG-34160?  Perhaps. The messages are identical to QCocoaMenu
> message reported in QTBUG-34160; but there are no additional messages when
> exiting Wireshark.

I think they are still related to the QTBUG-34160 - see below.
This is still a problem with Qt5.4.2 (from homebrew) and Qt5.5.0 (from qt.io
upstream).


> There's no prefix to indicate if these messages are errors, warnings or are
> simply informational.

The items are warnings, as can be confirmed when running as:
   env QT_MESSAGE_PATTERN="[%{type}] %{appname} (%{file}:%{line}) - %{message}"
./wireshark

or (to force an abort on the first warning):
   env QT_FATAL_WARNINGS=1 ./wireshark

(Debug hints from http://doc.qt.io/qt-5/debug.html)


> I played around with the various Context menu items.  No additional
> occurrences of the QCocoaMenu messages appeared but the following
> QCocoaWindow message was generated each time the Packet List or Packet
> Details Context menu Copy > Bytes > item was highlighted:
> 
> > void QCocoaWindow::syncWindowState(Qt::WindowState) invalid window content view size, check your window geometry

I've seen this issue too, with the failure to display a sub sub menu for Copy >
Bytes.

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