Startup issues in Linux
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 88
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
After updating to Cozy-Drive-3.16.0.AppImage on my Debian sid system, the app refuses to start.
As user:
$ cd /home/mithat/opt/CozyDrive/
$ ./Cozy-Drive-3.16.0.AppImage
[5194:1027/124812.829468:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_Cozy-<looks-like-a-random-string>/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap
There is no /tmp/.mount_Cozy-<looks-like-a-random-string> directory on the system.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the reported ./Cozy-Drive-3.16.0.AppImage command on Debian sid and start from the setuid_sandbox_host error. Investigate why the extracted chrome-sandbox is not configured as required; done means the AppImage starts successfully without the reported abort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100