Hi, I think the Linux file manager fix from #34 only covers one of the current open-target execution paths.
Symptom
On Linux/KDE, all "Open in File Manager" actions are still shown in the UI, but clicking them does not open the folder.
Examples:
- The toolbar dropdown shows "Open in File Manager"
- The workspace/file context menu also shows "Open in File Manager"
The action fails with this error in the logs:
Unknown open target "fileManager"
What I found
I inspected the generated app.asar.
The main bundle appears to be patched correctly. In .vite/build/main-*.js, the fileManager target has a Linux implementation using shell.openPath(), so the #34 patch seems to apply to the main-process bundle.
However, the current app also has a separate open-target registry in:
That worker bundle has its own target map and lookup function. The lookup throws when a target id is missing:
function W9(e) {
let t = ale.get(e);
if (t == null) throw Error(`Unknown open target "${e}"`);
return t;
}
The worker-side fileManager target only defines darwin and win32 platforms, but no linux platform. Because the worker target map is built from e.platforms[process.platform], fileManager is not registered on Linux in that path.
darwin: {...},
win32: {...}
This would explain why #34 fixed the main bundle path but the action still fails in the current build: the same Linux fileManager implementation also needs to be injected into the worker bundle, or the worker should reuse a registry that already includes the patched Linux target.
Version details
From codex-app/resources/codex-linux-build-info.json:
- Upstream Codex.app version:
26.616.51431
- Upstream DMG sha256:
e0d07909bd047d897db544e366103d4f14c06c1e038e8443aa97dc90405fcacf
- Electron version:
42.1.0
- codex-desktop-linux version:
0.8.4
- codex-desktop-linux commit:
c868dcd19f3a176d833ac9f1d35873f6a21e8921
- Target:
manjaro/pacman:kde
- Session: Wayland
- Relevant enabled feature:
open-target-discovery
The generated app.asar sha256 is:
58c152953655980b2dc83717afbb35d12d37871fa35dae92f9382e757b7f113d codex-app/resources/app.asar
Hi, I think the Linux file manager fix from #34 only covers one of the current open-target execution paths.
Symptom
On Linux/KDE, all "Open in File Manager" actions are still shown in the UI, but clicking them does not open the folder.
Examples:
The action fails with this error in the logs:
What I found
I inspected the generated
app.asar.The main bundle appears to be patched correctly. In
.vite/build/main-*.js, thefileManagertarget has a Linux implementation usingshell.openPath(), so the #34 patch seems to apply to the main-process bundle.However, the current app also has a separate open-target registry in:
That worker bundle has its own target map and lookup function. The lookup throws when a target id is missing:
The worker-side
fileManagertarget only definesdarwinandwin32platforms, but nolinuxplatform. Because the worker target map is built frome.platforms[process.platform],fileManageris not registered on Linux in that path.This would explain why #34 fixed the main bundle path but the action still fails in the current build: the same Linux
fileManagerimplementation also needs to be injected into the worker bundle, or the worker should reuse a registry that already includes the patched Linux target.Version details
From
codex-app/resources/codex-linux-build-info.json:26.616.51431e0d07909bd047d897db544e366103d4f14c06c1e038e8443aa97dc90405fcacf42.1.00.8.4c868dcd19f3a176d833ac9f1d35873f6a21e8921manjaro/pacman:kdeopen-target-discoveryThe generated
app.asarsha256 is: