Repository navigation
Conversation
…-recording-resume-fix Improve app presence and preview/export fidelity
…r-visual-polish Polish editor preview and motion blur
…ws-hud-passthrough fix windows passthrough
…ase-cleanup Clean up codebase formatting, dependencies, extension system removal
Use practical bitrate targets across export backends and add dithering when converting full-range canvas frames to BT.709 video range.
Record captured frames with BT.709 conversion and explicit limited-range metadata. Share the Windows conversion code between capture engines and apply matching colour metadata on macOS and FFmpeg fallbacks.
…ncement-popups Add announcements and polish recording motion
…imental-update-modal Fix experimental update channel and toast
…ware-decode-retry Recover Lightning decoding and add voluntary export error reports
…rt-preferences-separation Keep export preferences separate from project edits
…arding-email-sign-in Add first-launch onboarding and email sign-in
…ed-sharing-ownership Add account-scoped hosted sharing with bounded uploads
…-loading-autosave Improve Home loading, thumbnails, and automatic project saves
…d-publish-ui Add Link and Local publishing and a shared cloud library
…back-access-hardening Tighten feedback table access and add rollback verification
Drag any corner of the floating webcam preview to resize it (120-480px per side, kept inside the HUD viewport). The chosen size is saved and restored the next time the HUD opens. Fixes webadderallorg#1103 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ting-preview-resizability Make the floating webcam preview resizable
The README adds an Ubuntu AppImage section that identifies this setuid_sandbox_host.cc abort and distinguishes it from a missing FUSE dependency. It documents starting a trusted release build with --no-sandbox, notes that the flag must be passed on every launch and that it disables Chromium's sandbox, and says a system-wide user-namespace change is not required for the workaround. Refs webadderallorg#888
Contributor
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes.
 |
| Layer / File(s) | Summary |
|---|---|
Document the sandbox workaround README.md |
The README distinguishes the chrome-sandbox startup error from missing FUSE. It documents using --no-sandbox for trusted release AppImages with this error and notes the flag must be supplied at each launch. It warns that the flag disables Chromium’s sandbox. |
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other · Severity of issue fixed: Medium
Merge Risk: 
55abd
-
The documented workaround matches the project’s AppImage and Electron behavior, and the README clearly warns that it disables Chromium’s sandbox. No actionable merge risk remains.
🚥 Pre-merge checks | ✅ 5
-
✅ Passed checks (5 passed)
-
Check name Status Explanation Title check The title clearly and concisely describes the main documentation change: explaining Ubuntu AppImage sandbox launch failures. Description check The description includes all required template sections and provides relevant context, motivation, change type, issue reference, testing guidance, and explanations for omitted screenshots and tests. T… Linked Issues check Issue #888allows documentation as an alternative to changing AppImage behavior, adding an AppArmor profile, or adding a wrapper. README.md adds a focused Ubuntu AppImage section. It identifies the `s…Out of Scope Changes check The diff adds only the README.md troubleshooting section. The content directly supports issue #888by explaining the reported launch failure and its documented workaround. No unrelated source, build, …Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
The main branch history no longer shares recent commits with this branch. Take the tree of main and keep only the README section this PR adds.
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.
Pull Request Template
The README adds an Ubuntu AppImage section that identifies this setuid_sandbox_host.cc abort and distinguishes it from a missing FUSE dependency. It documents starting a trusted release build with --no-sandbox, notes that the flag must be passed on every launch and that it disables Chromium's sandbox, and says a system-wide user-namespace change is not required for the workaround.
On Ubuntu 24.04 and later, and on TUXEDO OS, Recordly-linux-x64.AppImage aborts as soon as it starts. Chromium reports that the SUID sandbox helper was found but chrome-sandbox is not configured correctly, then the process hits a trace/breakpoint trap and dumps core. AppArmor can block unprivileged user namespaces, so Chromium cannot set up its user-namespace sandbox and falls back to the chrome-sandbox helper. That helper inside an AppImage is not setuid root, so Chromium exits instead of continuing. Installing FUSE or building Recordly from source does not lift the restriction.
Description
The README adds an Ubuntu AppImage section that identifies this setuid_sandbox_host.cc abort and distinguishes it from a missing FUSE dependency. It documents starting a trusted release build with --no-sandbox, notes that the flag must be passed on every launch and that it disables Chromium's sandbox, and says a system-wide user-namespace change is not required for the workaround.
Motivation
Covered in the summary above.
Type of Change
Related Issue(s)
Fixes #888
Screenshots / Video
No user-visible surface changes in this PR, so there is nothing to show.
Testing Guide
This change touches documentation only, so there is no test to run.
Checklist
Not claimed: no review round ran on this change before submission.
Not verified: this needs a person on the named hardware or environment.
Not claimed: this diff changes no changelog or release-note file.
Thank you for contributing!
Summary by CodeRabbit
chrome-sandboxstartup failure, including how it differs from a missing FUSE issue.