Package Details: vibrantlinux-git 2.1.7.r0.ga75092b-1

Git Clone URL: (read-only, click to copy)
Package Base: vibrantlinux-git
Description: vibranceGUI replacement for Linux
Upstream URL:
Keywords: digital vibrance vibrancegui vibrantLinux
Licenses: MIT
Conflicts: vibrantlinux
Provides: vibrantlinux
Submitter: gbr
Maintainer: gbr
Last Packager: gbr
Votes: 2
Popularity: 0.000005
First Submitted: 2019-02-06 22:37
Last Updated: 2022-01-02 00:32

Required by (0)

Sources (1)

Pinned Comments

gbr commented on 2019-10-20 09:13

Kind reminder: This is a git-based package, so unless the building process fails for you, there's no need to flag it out-of-date.

Additionally, if you're using an AUR helper such as yay, you might encounter the following error when building the package:

/home/user/.cache/yay/vibrantlinux-git/vibrantlinux is not a clone of

That's because the URL of the repository has changed. To fix it, just delete the cache directory and re-build: ~/.cache/yay/vibrantlinux-git/vibrantlinux

Latest Comments

1 2 Next › Last »

Scrumplex commented on 2020-05-31 10:21

vibrantlinux is now not depending on libxnvctrl, and now needs "libvibrant" as a dependency (instead of just vibrant).

depends=('qt5-base' 'libvibrant')

is all you need

gbr commented on 2020-05-21 15:21

Just did it, thanks guys.

Scrumplex commented on 2020-05-21 14:40

Can you please add "provides=(vibrantlinux)" and "confilcts=(vibrantlinux)"?

zee commented on 2020-05-21 13:00

hey! Just updated this recently, the build requirements have changed and v2 is out now with support for any gpu driver that implements the CTM proprerty.

gbr commented on 2020-02-22 14:48

Thanks for the heads up! I'll update the package soon.

zee commented on 2020-02-22 00:32

the program is pretty solid right now so I probably won't be updating it anytime soon but I've moved all my projects to github.

zee commented on 2019-11-21 19:27

@gbr I see I'm very sorry about that, I just realized what my mistake was. I was using the canonicalPath function instead of canonicalFilePath, thank you very much for pointing this out, and finding the error yourself, this has been fixed and pushed as v1.2.4

gbr commented on 2019-11-21 17:45

@zee: I believe I found out what the problem is, I've sent a pull request on your repository, please check once you got time. Basically, the algorithm to detect if the program was already running, compares the directory path of each running process, whilst it should be comparing the executable path. That's why this error message will not show up as easily if you run Vibrant Linux from the build directory, for example. But once you move the binary to /usr/bin (where other multiple binaries are also running from), the error message pops up.

zee commented on 2019-11-20 17:05

@gbr that's strange, I'm not using the package but on my end if I follow the arch install instructions (git clone, cd, ./ then I can run it with no problem (v1.2.3). Are you sure it's up to date? That issue was there for like a second before I realized what I did wrong and fixed it. If your version is up to date and the problem persists please open an issue so I can try to sort it out, I imagine that would fit more than the package comments.

gbr commented on 2019-11-20 16:13

@zee: No worries, that's what package maintainers are for. :p However, in the last update, vibrantLinux doesn't seem to start anymore. If you try to launch if from the terminal, this error will show: Vibrant Linux is already running.