nextcloud / nextcloud/whiteboard

Add option to disable recordings

Open
#1,070 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
215
Forks
39
Avg merge
1d 3h
Merged PRs (30d)
32

Description

I get the following error

Chromium failed to start (Failed to launch the browser process:  Code: null

stderr:
[0302/084326.344920:ERROR:third_party/crashpad/crashpad/util/file/filesystem_posix.cc:63] mkdir /tmp/chrome-crashpad/new: Permission denied (13)
[0302/084326.345434:ERROR:third_party/crashpad/crashpad/util/linux/socket.cc:120] recvmsg: Connection reset by peer (104)
[0302/084326.345520:ERROR:third_party/crashpad/crashpad/util/file/filesystem_posix.cc:63] mkdir /tmp/chrome-crashpad/new: Permission denied (13)
[936:936:0302/084326.346325:ERROR:third_party/crashpad/crashpad/util/linux/socket.cc:120] recvmsg: Connection reset by peer (104)

TROUBLESHOOTING: https://pptr.dev/troubleshooting
). Install the required browser dependencies and restart the collaboration server.

This is because I am running the container as non root.

As I don't need recordings and don't want to see the error all the time, I think its best to be able to disable the feature

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the recording startup path and the server configuration used when the collaboration server runs in a non-root container. Check how Chromium is launched and where its failure is reported. Done means users can configure recordings off, the recording process is not started, and the repeated Chromium error is absent.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.