Package Details: rambox-os-bin 0.5.18-10

Git Clone URL: (read-only)
Package Base: rambox-os-bin
Description: Forked Free and Open Source messaging and emailing app that combines common web applications into one
Upstream URL:
Licenses: GPL3
Conflicts: ramboxrambox-os-gitrambox-binramboxpro-bin
Provides: rambox-os
Submitter: bjo
Maintainer: freaknils
Last Packager: bjo
Votes: 3
Popularity: 0.104340
First Submitted: 2018-12-13 22:34
Last Updated: 2019-05-21 19:27

Latest Comments

rjt commented on 2019-07-27 05:01

Hey, just a heads-up that Rambox-OS has been renamed to Hamsket, and the upstream URL is now:

bjo commented on 2019-05-21 19:25

Yep, you're right.

neXyon commented on 2019-05-21 16:05

Almost fixed, it should be

chmod 4755 ${pkgdir}/opt/${_pkgname}/chrome-sandbox

instead of

chmod 4755 /opt/rambox-os/chrome-sandbox

bjo commented on 2019-05-20 20:13

Thanks, fixed.

travelskid commented on 2019-05-20 11:30

if have this problem: "[3022:0520/] 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 /opt/rambox-os/chrome-sandbox is owned by root and has mode 4755."

Do :

sudo chmod 4755 /opt/rambox-os/chrome-sandbox

bjo commented on 2019-01-31 14:21

Any reason this doesn't install the latest (stable) release from github?

Yes, the "stable" builds e.g. have issues with Whatsapp etc.

thisischrys commented on 2019-01-31 06:31

It's invalid again. AppVeyor is an automated build system, it could rebuild any number of times depending on how it's setup.

I see this is called "Latest unstable build artifacts" on the github. Any reason this doesn't install the latest (stable) release from github?

Should also conflict with rambox-bin, rambox-os-git and probably ramboxpro-bin

bjo commented on 2019-01-18 13:56

@diddyonlinux strange, I assaume TheGoddessInari did a rebuild.

diddyonlinux commented on 2019-01-18 13:45

ERROR: One or more files did not pass the validity check! When I try to install.

nvllsvm commented on 2018-12-17 19:20

Please link the rambox executable to /usr/bin. This is especially important for folks who don't use the *.desktop files to launch their apps.