Possible self-lock when Force Offline Mode is enabled

Description

When Bottles starts, it displays a dialog that cannot be closed until Bottles has finished downloading dependencies such as DXVK. (See attached screenshot.)

If the network is poor during the first launch and these dependencies fail to download, the dialog will close after a timeout. The user can then open Settings, enable Force Offline Mode, and close Bottles.

On the next launch, Bottles remains stuck on the dependency download dialog forever. Because this dialog blocks access to the main UI/Settings, the user cannot disable Force Offline Mode. This creates a self-lock/soft-lock.

Steps to reproduce

1. Launch Bottles for the first time on a poor or unstable network.
2. Let the dependency download (DXVK, etc.) fail. The startup dialog closes after a timeout.
3. Open Settings and enable Force Offline Mode.
4. Close Bottles.
5. Launch Bottles again.

Expected behavior

Bottles should not become permanently stuck in this state. For example:

• It should prevent enabling Force Offline Mode if required dependencies are missing, or
• It should detect missing dependencies and still allow the user to access Settings to disable Force Offline Mode, or
• The startup dialog should allow the user to cancel/skip and enter the app.

Actual behavior

Bottles is stuck on the dependency download dialog on every launch. The user cannot proceed or enter Settings to disable Force Offline Mode.

Environment

• Bottles version: 2:52.0-5.fc44
• Installation method:rpm pack
• OS/Distribution: Fedora 44
• Desktop environment: KDE Plasma 6.7.5

Additional context

Screenshot:

This is likely a deadlock: Force Offline Mode prevents the required downloads, but the startup flow requires those downloads to complete before the user can access Settings.