https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
Gerald Combs changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #6 from Gerald Combs ---
Closing. We work around this for development via the "run/wireshark" wrapper
script and newer versions of Qt appear to handle this by calling
[[NSApplication sharedApplication]
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #5 from Gerald Combs ---
If I copy the "open" command to /tmp (so as to avoid System Integrity
Protection) and run
sudo dtruss -s /tmp/open run/Wireshark.app
It looks like "open" uses Launch
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
Alexis La Goutte changed:
What|Removed |Added
CC|
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #4 from Matt Day ---
(In reply to Gerald Combs from comment #3)
> We currently call the main window's show() function at line 503 in
> wireshark-qt.cpp. We might need to add calls to activateWindow() and
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #3 from Gerald Combs ---
We currently call the main window's show() function at line 503 in
wireshark-qt.cpp. We might need to add calls to activateWindow() and raise() as
well.
--
You are receiving
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #2 from Matt Day ---
(In reply to Gerald Combs from comment #1)
> Are you doing this by running the Wireshark executable directory or by
> opening its application bundle (assuming that homebrew creates an
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582
--- Comment #1 from Gerald Combs ---
(In reply to Matt Day from comment #0)
> 2. start Wireshark
Are you doing this by running the Wireshark executable directory or by opening
its application bundle (assuming that