Multi-display doesn't work about ashirt HOT 8 CLOSED

I can't seem to reproduce this on my macbook. Are you using a particular release or more than 2 monitors (counting the macbook display itself)? Or does this only happen if you add a display after the application is started?

from ashirt.

Have seen it occur with two monitors (including macbook display) when the second display is not setup to mirror. In mirror mode is definitely works. Running a pretty standard macos 10.15.6 with no weird extensions or software installed that may effect the layout or anything. This behavior has been reported by others on the team as well. Have verified that it occurs if both monitors are connected and setup when the application starts or if the second monitor is attached after the application starts.

from ashirt.

Confirmed that this appears to either be related to using Qt 5.15 or the version that is distributed by homebrew. Testing a build from @JoelAtDeluxe using the officially distributed Qt 5.14 this issue went away. Going to install the official 5.15 distribution and check if the issue still occurs. If so, will report the bug upstream. If not, we can switch over to the official distribution for now and file a bug with homebrew.

from ashirt.

Tested this again on qt 5.15.1 from homebrew on macos and it still seems broken. This appears to maybe be an issue with the specific distribution from homebrew. Going to check if we can easily build with official versions from Qt in github actions.

from ashirt.

After more testing we've finally identified the conditions that cause it to break. It's been replicated on official Qt releases as well. This seems to explicitly only happen in a multi-monitor environment when the primary monitor is arranged below the secondary monitor. Searching the bug tracker for Qt doesn't show any known issues, working to figure out how to get this reported and figure out how to get it fixed.

from ashirt.

The bug has been reported upstream to Qt https://bugreports.qt.io/browse/QTBUG-87177. Waiting to see what they say.

from ashirt.

Need to check whether this is still present in Qt 6. If not, we can close this as we no longer support Qt 5.

from ashirt.

Confirmed this is fixed on Qt 6.3 using the most recent continuous build. Since we don't support Qt 5 anymore, we can close this.

from ashirt.