Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.