fix: lockup if first run message is up and a client connects - #8601

How do I reproduce the bug that this fixes? What are the steps? I solved #8599 with my PR.

On master:

1. Have working config (server with clients connected)
2. Clear settings
3. Start server
4. See 'Server is running' and fingerprint dialogs at the same time (fingerprint dialog appears in front and no freeze)

I was unable to get the GUI to freeze on master. I guess if it's a race condition then maybe I'm just not being unlucky enough. Have you seen a GUI freeze since my PR landed?

My rationale: I don't want to land a "just in case" PR unless I can prove it solves a bug.

added steps above

6. If the new server dialog is open still the app will freeze.

I don't see this freeze. Instead, I see:

The 'New client' dialog in front of the 'Server is running' dialog.

Please send me a screenshot of the crash on latest master so I know what I'm looking for.

you need to accept the client dialog and add the screen to see the freeze.

you need to accept the client dialog and add the screen to see the freeze.

Still not seeing it. I left the 'Server is running' dialog there, added the client to the grid, and all I see now is...

Are you sure you're still able to repro this on master?

100% of the time ( video below is current master )

Deskflow: 1.21.2.240 (34f61869)
Qt: 6.9.0
System: Arch Linux
Session: KDE (wayland)

Thanks for the video.

I don't know what I missed yesterday, but yeah, managed to repro. Finally!

Edit: I also cleared the client settings. Perhaps that made the difference.

Deskflow: 1.21.2.240 (34f61869)
Qt: 6.8.2
System: Fedora Linux 41 (Workstation Edition)
Session: GNOME (wayland)