Wireshark-bugs: [Wireshark-bugs] [Bug 10405] Systematically can't close - must force close
Comment # 1
on bug 10405
from Guy Harris
(In reply to teo8976 from comment #0)
> By the way, I think you should unify the components "gtk-ui" and "Qt-UI"
> into one "UI" category in the bugtracker.
Other people, however, including Gerald Combs, thought we should split them, at
least back in June 2014:
https://www.wireshark.org/lists/wireshark-dev/201406/msg00143.html
> How is the reporter supposed to know?
By seeing whether the "About Wireshark" window, or the output of "wireshark -v"
at the command line, mentions GTK+ or Qt.
If you haven't looked at that information, you haven't properly filed the bug;
the "Build Information" part of the Bugzilla form says
Paste the COMPLETE build information from "Help->About Wireshark",
"wireshark -v", or "tshark -v".
so if you're filing a bug you're supposed to open that window, or run
"wireshark -v" from the command line, if that is at all possible, so you'll see
that output.
> Do you even use two UI frameworks in the same application?
In the same binary? No.
In the same application? Yes, in that you can build GTK+ (2.x or 3.x) and Qt
versions, and in that, for example, the 1.12 and earlier binary releases we
provide use GTK+ by default but the "bleeding-edge" binary releases we provide
use Qt by default.
> I have guessed Gtk just because all the error messages contain the work gtk
> but I have really no idea.
Yes, that's the case.
You are receiving this mail because:
- You are watching all bug changes.
