Linux: app stays in tray (no window) + missing lucide-react dependency

[uriva]

I ran into two setup/startup issues on Linux that seem related to current repo state.

1) Missing dependency: lucide-react

After cloning and running npm install, the app failed until I manually installed lucide-react.

lucide-react is imported in source files (for example: src/components/video-editor/TutorialHelp.tsx) but is not listed in package.json dependencies/devDependencies.

Expected

npm install should install everything required to run the app.

Actual

Manual npm i lucide-react is required.

---

2) Linux startup: app only appears in tray, window does not show

When launching the app, I can see Recordly in the system tray, but no main window appears.

I also see this log line:

[45527:0418/122231.948021:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1631] vaInitialize failed: unknown libva error

Expected

Main UI window should appear on launch (or when clicking tray icon).

Actual

Only tray icon appears; no visible window.

Notes

This may be Linux Wayland/VAAPI/GPU related. It could help to test startup behavior with:

• X11 (ELECTRON_OZONE_PLATFORM_HINT=x11)
• GPU disabled (ELECTRON_DISABLE_GPU=1)

Thanks for looking into this — happy to provide more env details/logs if needed.

[uriva]

Additional findings from local AppImage testing on Linux:

• AppImage in is executable and valid ELF.

• Launching normally fails immediately with Chromium sandbox error:

• Launching with starts the process and keeps it running, but no visible window appears (tray only behavior).
• Logs with show VAAPI warning and repeated GPU/network-service issues on Wayland.

This suggests two Linux problems:

1. packaged AppImage sandbox configuration, and
2. startup/windowing behavior under Linux (likely Wayland/GPU path).

[uriva]

Adding clean repro notes (previous comment had shell-escaped text issues):

Additional findings from local AppImage testing on Linux:

• AppImage at ~/Downloads/Recordly-linux-x64.AppImage is executable and valid ELF.
• Launching normally fails immediately with Chromium sandbox error:
  • The SUID sandbox helper binary was found, but is not configured correctly ... chrome-sandbox ... mode 4755
• Launching with --no-sandbox starts the process and keeps it running, but no visible window appears (tray-only behavior).
• Logs with --no-sandbox show VAAPI warning and repeated GPU/network-service issues on Wayland.

This suggests two Linux problems:

1. packaged AppImage sandbox configuration, and
2. startup/windowing behavior under Linux (likely Wayland/GPU path).

[uriva]

More diagnostics from source run (Linux, Wayland):

• Repo path: /home/uri/uriva/recordly
• Running npm run dev still crashes on GPU init with:
  • GPU process launch failed: error_code=1002
  • FATAL: GPU process isn't usable. Goodbye.
• This occurs even after avoiding Linux-only forced GPU acceleration switches.
• Forcing in-process-gpu avoids the immediate fatal crash in my test run, but app behavior is still unstable.

Given mic works in Chrome on the same machine, this still points to Recordly Linux Electron startup/GPU path rather than system mic config.

[uriva]

Another reproducible symptom on Linux/Wayland:

• Running npm run dev shows:
  • vaInitialize failed: unknown libva error
• App appears in taskbar/tray, but the HUD overlay does not become visible, so recording controls are inaccessible.

Local experiment indicates transparent always-on-top HUD behavior is a likely part of this on Linux Wayland (non-transparent fallback improves visibility behavior in testing).

[uriva]

Another concrete runtime issue found:

Invalid lucide-react export causes renderer crash

• File: src/components/video-editor/TutorialHelp.tsx
• Current import includes Twitter from lucide-react.
• On current lucide-react, this export is not available, causing runtime error:

Uncaught SyntaxError: The requested module '/node_modules/.vite/deps/lucide-react.js?...' does not provide an export named 'Twitter'

This can lead to a blank/black UI because the renderer fails during module load.

Suggested fix

Replace Twitter with an icon that exists in the installed lucide version (or use an existing icon already imported in that file, e.g. ExternalLink).