Describe the bug
On systems where Chromium's GPU process cannot produce frames, Streambert opens but the main window stays completely blank forever — the app appears to hang. There is no crash and no error dialog.
Reproduction (tested on the affected hardware below):
- Install Streambert (or run
npm start) on a machine whose GPU/driver stack is unsupported by Chromium (e.g. NVIDIA with the open-source nouveau driver).
- Launch the app.
- The window opens, logs show the renderer loads (
[boot] renderer loaded: +560ms), but no frame is ever painted. The window is blank/black and unresponsive.
Root cause: Chromium starts the GPU process but it fails to produce frames (a silent hang, not a crash), so no error is surfaced and the user cannot fix it from inside the app.
Expected Behavior
The app window should render and be usable regardless of GPU hardware/driver support, or fall back automatically to software rendering (SwiftShader) when hardware acceleration is unavailable.
Environment
- Streambert version: v2.6.0 (also reproducible on the latest 2.x)
- Operating system: Linux — Pop!_OS 24.04 LTS, kernel 7.0.11, COSMIC (Wayland session, XWayland)
- GPU: NVIDIA GeForce GT 730 (Kepler GK208B), open-source
nouveau driver only (kernel log: Direct firmware load for nouveau/nv106_fuc084 failed)
- Installation method: other (run from source with
npm start)
Additional information
- Searched the issue tracker for similar reports (
gpu) before filing — no results.
- Diagnostics:
app.getGPUFeatureStatus() under the default config reports everything as disabled_software/unavailable_software, yet the window still never paints — feature status alone is insufficient because the failure is a hang, not a crash.
- For reference: launching with
--disable-gpu renders fine but disables WebGL; --use-angle=swiftshader renders fine and keeps software WebGL (OpenGL ES 2.0/3.0 via SwiftShader).
Describe the bug
On systems where Chromium's GPU process cannot produce frames, Streambert opens but the main window stays completely blank forever — the app appears to hang. There is no crash and no error dialog.
Reproduction (tested on the affected hardware below):
npm start) on a machine whose GPU/driver stack is unsupported by Chromium (e.g. NVIDIA with the open-sourcenouveaudriver).[boot] renderer loaded: +560ms), but no frame is ever painted. The window is blank/black and unresponsive.Root cause: Chromium starts the GPU process but it fails to produce frames (a silent hang, not a crash), so no error is surfaced and the user cannot fix it from inside the app.
Expected Behavior
The app window should render and be usable regardless of GPU hardware/driver support, or fall back automatically to software rendering (SwiftShader) when hardware acceleration is unavailable.
Environment
nouveaudriver only (kernel log:Direct firmware load for nouveau/nv106_fuc084 failed)npm start)Additional information
gpu) before filing — no results.app.getGPUFeatureStatus()under the default config reports everything asdisabled_software/unavailable_software, yet the window still never paints — feature status alone is insufficient because the failure is a hang, not a crash.--disable-gpurenders fine but disables WebGL;--use-angle=swiftshaderrenders fine and keeps software WebGL (OpenGL ES 2.0/3.0 via SwiftShader).