mirror of
https://github.com/open-webui/desktop.git
synced 2026-11-05 01:27:46 +00:00
[PR #272] fix(linux): stop appending no-sandbox to fix blank webviews #238
Labels
No labels
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/desktop#238
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/open-webui/desktop/pull/272
Author: @hirntot
Created: 9/18/2026
Status: 🔄 Open
Base:
main← Head:codex/fix-linux-webview-sandbox📝 Commits (1)
5f55f00fix(linux): stop appending no-sandbox during startup📊 Changes
1 file changed (+4 additions, -3 deletions)
View changed files
📝
src/main/index.ts(+4 -3)📄 Description
Description
On LMDE 7 (amd64), Open WebUI Desktop 0.0.20 displays its shell and connection sidebar but leaves the remote webview blank. Chromium repeatedly reports
Creating shared memory in /tmp/.org.chromium.Chromium.… failed: No such process (3)andUnable to access(W_OK|X_OK) /tmp: No such process (3). A run with--disable-gpustill failed and the webview exited with code 133. Both/tmpand/dev/shmhad mode 1777 and available space.Remove the unconditional
app.commandLine.appendSwitch('no-sandbox')from Linux startup and update the GPU-workaround comment. A separate copy of the installed 0.0.20 application with only this runtime line removed successfully displayed the remote login page without passing--no-sandbox; its log no longer contained the shared-memory errors. The initial test used a fresh, separate profile. Subsequently, the user installed the rebuilt DEB over the original installation and confirmed that the normal app now works with their existing profile, which had failed before the package update. The installed version (0.0.20+rlfix1) and patched application archive SHA-256 were independently verified. An explicit command-line--no-sandboxalso worked around the original failure, but is not needed by the patched copy.This leaves renderer sandbox selection to Electron and preserves the existing SwiftShader, shared-memory and GPU-sandbox workarounds. It does not enable sandboxing for every desktop window or claim to resolve all Linux rendering failures. The precise Chromium startup interaction has not been proven; the patch is based on the observed behavior above.
Validation
npm run build: passes, including TypeScript and Svelte checks (0 Svelte-check errors/warnings); Vite reports warnings in untouched components.src/main/index.ts: identical findings before and after the change (22 errors, 139 warnings); no new findings.git diff --check: passes.Related Issues
Related to #178 and #157. Overlaps the removal of the unconditional native-package
no-sandboxswitch in #269, but intentionally avoids that PR's broader security changes. This is a small independently reviewable fix for the reproduced DEB failure.Contributor License Agreement
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.