[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2019-09-17 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582

Gerald Combs  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2019-09-17 Thread bugzilla-daemon
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] activateIgnoringOtherApps:YES]

at application startup (which indicates that our wrapper script may no longer
be necessary).

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-31 Thread bugzilla-daemon
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 Services to open the application bundle
instead of simply forking+execing Wireshark.app/Contents/MacOS/Wireshark:

workq_kernreturn(0x20, 0x0, 0x1) = 0 0

  libsystem_kernel.dylib`__workq_kernreturn+0xa
  libdispatch.dylib`_dispatch_queue_wakeup_global_slow+0x3c
  libdispatch.dylib`_dispatch_queue_wakeup_with_qos_slow+0x7e
  libxpc.dylib`xpc_connection_resume+0x98
  SharedFileList`-[SFLListManager _connection]+0x1d8
  SharedFileList`__37-[SFLListManager
listWithIdentifier:]_block_invoke+0x175
  libdispatch.dylib`_dispatch_client_callout+0x8
  libdispatch.dylib`_dispatch_barrier_sync_f_invoke+0x4a
  SharedFileList`-[SFLListManager listWithIdentifier:]+0x108
  SharedFileList`LSSharedFileListCreate+0xf7
  LaunchServices`_LSGetRecentItemsSharedList(short, unsigned
int**)+0x57
  LaunchServices`_LSGetRecentItemCount+0x19
  LaunchServices`_LSOpenItemsWithHandler_CFDictionaryApplier(void
const*, void const*, void*)+0x1748
  CoreFoundation`__CFDictionaryApplyFunction_block_invoke+0x16
  CoreFoundation`CFBasicHashApply+0x80
  CoreFoundation`CFDictionaryApplyFunction+0xba
  LaunchServices`_LSOpenStuffCallLocal+0x163c
  LaunchServices`_LSOpenStuff+0x7e
  LaunchServices`_LSOpenURLsWithRole_Common(__CFArray const*,
unsigned int, AEKeyDesc const*, LSApplicationParameters_V1 const*,
ProcessSerialNumber*, long, __CFURL const**)+0x183
  LaunchServices`LSOpenURLsWithRole+0x20

It would be nice to know what LSOpenURLsWithRole does that fork+exec doesn't.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-31 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12582

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com,
   ||eapa...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-30 Thread bugzilla-daemon
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 raise()
> as well.

I tried that with wireshark 2.0.5 (see diff below), but it didn't help -- the
original menu problem persists. As far as I can tell, adding these calls had no
effect on anything.

--- wireshark-qt.cpp.orig2016-07-27 12:26:43.0 -0600
+++ wireshark-qt.cpp2016-07-30 15:59:31.0 -0600
@@ -769,6 +769,8 @@
 // Init the main window (and splash)
 main_w = new(MainWindow);
 main_w->show();
+main_w->activateWindow();
+main_w->raise();
 // We may not need a queued connection here but it would seem to make
sense
 // to force the issue.
 main_w->connect(&ws_app, SIGNAL(openCaptureFile(QString,QString,unsigned
int)),

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-27 Thread bugzilla-daemon
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 this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-26 Thread bugzilla-daemon
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
> application bundle)?

Ah, yes, I was directly running the /usr/local/bin/wireshark executable created
by Homebrew. I didn't know that things like menus could be broken when I did
that... interesting!

And indeed, when I run the application bundle that Homebrew builds, the menus
work fine.

Specifically, this works:

1) brew install --with-qt5 wireshark
2) brew linkapps wireshark
3) open /Applications/Wireshark.app

Therefore, I'll alias `wireshark` to open the application bundle from now on.
Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12582] (Qt5) app menus won't pull down

2016-07-03 Thread bugzilla-daemon
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 homebrew creates an application bundle)?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe