09:47:07 <dEBRUYNE> Seems to be an issue on Windows where the GUI does not start, concerns .2 and higher
09:47:31 <dEBRUYNE> https://www.reddit.com/r/Monero/comments/mqoc3q/monero_wallet_gui_support_01720_oxygen_orion/
09:47:45 <dEBRUYNE> https://www.reddit.com/r/monerosupport/comments/mqmunn/gui_wallet_not_appearing_on_launch/
09:47:54 <dEBRUYNE> xiphon, selsta ^^
10:52:36 <selsta> can't think of any change that would cause this
11:24:22 <selsta> .merge- 3397
11:24:22 <xmr-pr> Removed
11:37:01 <dEBRUYNE> Two users isn't a coincidence though
11:56:44 <selsta> dEBRUYNE: can you ask them to run a specific binary?
11:56:52 * selsta still compiling
12:03:45 <dEBRUYNE> Suppose I could, if they agree with that
12:53:16 <selsta> .merge+ 3401
12:53:16 <xmr-pr> Added
18:34:00 <xiphon> dEBRUYNE: "Seems to be an issue on Windows where the GUI does not start, concerns .2 and higher" -> yeah, we didn't touch anything related
18:35:24 <selsta> xiphon: quite sure it is https://github.com/monero-project/monero-gui/pull/3302
18:35:41 <selsta> Screen.desktopAvailableWidth reporting 0 on their systems for whatever reason
18:36:31 <selsta> "I can see the process running in task manager, the GUI Wallet icon appears in my taskbar but I can't view or open the GUI Wallet window" <-- hints at a 0x0 size window
18:47:30 <selsta> .merge+ 3397
18:47:30 <xmr-pr> Added
18:51:31 <xiphon> selsta: "quite sure it is" -> yep, maybe (i was thinking about OpenGL rendering and related stuff)
18:51:55 <xiphon> .merges
18:51:55 -xmr-pr- 3392 3394 3395 3397 3401
18:52:12 <selsta> will try to find a solution
18:53:19 <selsta> either with clamp(available, min, max) or some other Qt function
18:56:53 <xiphon> i'm already on it
18:58:29 <selsta> ok
19:05:18 <selsta> .merge+ 3404
19:05:18 <xmr-pr> Added
19:12:40 <selsta> xiphon: https://doc.qt.io/qt-5/qml-qtquick-window-screen.html
19:12:47 <selsta> "Note that the Screen type is not valid at Component.onCompleted, because the Item or Window has not been displayed on a screen by this time."
19:12:56 <selsta> we use screen inside Note that the Screen type is not valid at Component.onCompleted, because the Item or Window has not been displayed on a screen by this time.
19:13:07 <selsta> we use screen inside  Component.onCompleted*
19:13:45 <selsta> main.qml line 1288
19:15:06 <xiphon> yes, we do, will handle that as well
19:15:12 <xiphon> will update the PR shortly
19:16:38 <selsta> the question is if the bug is Component.onCompleted being 0 or if screen being used in invalid way resulted in negative x / y coordinates
19:16:56 <selsta> Screen.desktopAvailableWidth being 0*
19:17:03 <selsta> my copy paste does not work today lol
19:36:02 <xiphon> will omit QML Screen type usage
19:50:48 <xiphon> btw, selsta, could you test dropping "x =" and "y =" lines in Component.onCompleted on MacOS?
19:51:10 <xiphon> The window is centered by default on Win
19:54:15 <selsta> ok
19:57:23 <selsta> xiphon: on mac it also centers automatically
20:01:54 <xiphon> thanks
20:02:21 <selsta> ApplicationWindow also has screen property
20:02:27 <selsta> which can be used instead of Screen
20:03:09 <selsta> don't know what is best solution
20:38:53 <selsta> .merges
20:38:53 -xmr-pr- 3392 3394 3395 3397 3401 3404