From 0589fbf8171901812f4e9df14d4572e9d578be98 Mon Sep 17 00:00:00 2001 From: SulfurNitride Date: Mon, 6 Apr 2026 14:42:30 -0500 Subject: Fix misleading "No Wine Prefix" error when launch binary not found MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ENOENT from process execution was always shown as "No Wine Prefix" when useProton was set, even when the prefix was properly configured. Now checks FluorineConfig::isSetup() first — if the prefix exists, falls through to the generic spawnFailed dialog which shows the actual missing binary path. Co-Authored-By: Claude Opus 4.6 (1M context) --- src/src/spawn.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/src/spawn.cpp b/src/src/spawn.cpp index d94fbae..6cb925e 100644 --- a/src/src/spawn.cpp +++ b/src/src/spawn.cpp @@ -1026,7 +1026,7 @@ pid_t startBinary(QWidget *parent, const SpawnParameters &sp) { const auto e = spawn::spawn(sp, pid); if (e != 0) { - if (e == ENOENT && sp.useProton) { + if (e == ENOENT && sp.useProton && !FluorineConfig::isSetup()) { QMessageBox::critical( parent, QObject::tr("No Wine Prefix"), QObject::tr("No Wine prefix has been configured for this instance.\n\n" -- cgit v1.3.1