Package Details: rambox-bin 0.5.13-1

Git Clone URL: (read-only)
Package Base: rambox-bin
Description: Free and Open Source messaging and emailing app that combines common web applications into one.
Upstream URL:
Keywords: chat franz messenger skype slack whatsapp
Licenses: GPL3
Provides: rambox
Submitter: jbbr
Maintainer: jbbr
Last Packager: jbbr
Votes: 59
Popularity: 3.779755
First Submitted: 2016-07-02 10:51
Last Updated: 2017-10-05 02:02

Latest Comments

Malganis commented on 2017-09-29 18:50

I've tried to reinstall several times, but for some reason it worked n the 6th try.

Before the last try, I did sudo pacman -Rs rambox
Between the dependencies listed after this, electron was one of them, curious...

Thank you for your attention.

jbbr commented on 2017-09-29 13:35

@Malganis: Can you try reinstalling this package? What is the content of /usr/bin/rambox?

This package does not depend on the electron package and there shouldn't be any references to /usr/bin/electron.

I was unable to reproduce your problem.

Malganis commented on 2017-09-26 16:13

Hi I'm getting this error:

/usr/bin/rambox: /usr/bin/electron: Broken interpreter: File or directory not found

Obviously, electron is not there.

I hope that this doesn't have anything to do with my npm config, for I have changed the default path directory of npm /usr to ~/.npm-global.

jbbr commented on 2017-07-05 11:45

@meister1337: done

meister1337 commented on 2017-07-05 10:59

Please update to 0.5.10

Hering commented on 2017-06-03 08:46

@emphire: Kinda, but I dont even see the icon, only the process in htop.

emphire commented on 2017-05-26 08:22

After installing, when I run rambox, the icon appears in my toolbar but the window is not visible. I can bring the app to the foreground but there is no window to interact with (I did try toggling the "Show/Hide window" option).

Has anyone else had this issue?

jbbr commented on 2017-05-20 23:18

0.5.8 has been released but is marked as "Pre-release".
Because of this and a memory leak (see ) I did not yet updated this package.

If you feel adventurous: Updating to 0.5.8 is straightforward - just change pkgver and shasums in the PKGBUILD.



jbbr commented on 2017-04-20 16:48


Thanks for the advice. I wasn't aware of this possibility although I really disliked the fact of unnecessary rebuilds due to changed of metadata.

I incorrectly thought that the AUR service would reject pushes without incremented pkgrel.

EDIT: I reverted the pkgrel to 1. Hopefully this prevents some unnecessary "upgrades"

chmercesmoreira commented on 2017-04-20 16:23


Thank you for maintaining this package, I'd like to give you an advice:
Don't change the pkgrel on the PKGBUILD file when making changes that do not change the package itself (you just changed some metadata information).

From Arch Wiki (
The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1. In exceptional cases other formats can be found in use, such as major.minor.

All comments