Package Details: viber

Git Clone URL: (read-only, click to copy)
Package Base: viber
Description: Proprietary cross-platform IM and VoIP software
Upstream URL:
Licenses: custom
Submitter: MohammadR
Maintainer: nslxndr
Last Packager: nslxndr
Votes: 252
Popularity: 2.21
First Submitted: 2013-08-20 17:20
Last Updated: 2020-08-15 20:42

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

stathisq commented on 2019-03-18 12:00

@setevoy There are not only visual updates but also functionality updates too. Now you can edit/pin posts, view polls, and in general, you got the same functionality as Windows client. It seems like Viber is developed in qt in both Windows and Linux, and if they wanted they could always give an updated version of Viber. Even the EOL email response we get from them, it seems to me more like an automated response, rather than a real EOL response.

ugis commented on 2019-03-18 10:04

Trying to install from scratch, have the same Issue as madjoe (==> ERROR: One or more files did not pass the validity check!).

Any suggestions?

setevoy commented on 2019-03-17 18:02

Upgraded it yesterday - can't see any issues at all. And yes - it looks a bit different than a previous one (but I may be wrong although - didn't pay to much attention on it).

[2019-03-16 23:00] [PACMAN] Running 'pacman --color auto -U --noconfirm /tmp/yaourt-tmp-setevoy/PKGDEST.AsD/viber-'

[2019-03-16 23:00] [ALPM] transaction started

[2019-03-16 23:00] [ALPM] upgraded viber ( ->

7314776 commented on 2019-03-17 16:16

Blocked Viber update for now as it seems to be an injection. [sorry, wrong link] .... I tried to learn about any Viber development process for Linux, any updated version different from 7 point something: no data at all! And Viber support continues replying “stopped development and updates in Linux...”. Viber distribution model to be blamed, viber.deb was always viber.deb whether it was about version 6 or version 7. Probably, someone somehow was able to hack this outdated developed stuff replacing it with “new” version 10. In absence of other news or reliable info, I’d prefer NOT to update Viber. Please, correct if I’m wrong.

madjoe commented on 2019-03-17 12:27

Synchronizing package databases...

Starting full system upgrade...

Cloning viber build files...

Checking viber dependencies...

Building viber...

==> Making package: viber (Sunday, March 17, 2019. 13:25:49 CET)

==> Checking runtime dependencies...

==> Checking buildtime dependencies...

==> Retrieving sources...

-> Found viber.deb

-> Found eula.html

-> Found viber

==> Validating source files with md5sums...

viber.deb ... FAILED

eula.html ... Passed

viber ... Passed

==> ERROR: One or more files did not pass the validity check!

notuxius commented on 2019-03-01 14:45

sleep for 1 sec didn't do the trick for me - the delay wasn't enough for 'wmctrl -i -c "$wid"' command to minimize Viber window - increasing to 4 sec works. Also there is some scale window and tray icon issues for me with ext monitor - setting 'QT_AUTO_SCREEN_SCALE_FACTOR=0' resolves them. So i ended up with next code:


if [ "$1" = "StartMinimized" ]; then { sleep 4; while ! pid=$(pidof /opt/viber/Viber); do sleep 1; done; [ -n "$pid" ] && wid=$(wmctrl -p -l | grep Viber | grep " $pid " | awk '{print $1}') && wmctrl -i -c "$wid"; } & fi exec env QT_AUTO_SCREEN_SCALE_FACTOR=0 /opt/viber/Viber "$@"

duzun commented on 2019-02-24 13:33

There is a small issue: viber doesn't start minimizer with viber StartMinimized command. That's because /usr/bin/viber doesn't pass arguments to /opt/viber/Viber.

Please, append "$@" to /usr/bin/viber like so:

!/bin/sh exec /opt/viber/Viber "$@"

It would also be great to have an option to start Viber in the system tray, not just minimized, maybe with wmctrl:


if [ "$1" = "StartMinimized" ]; then { sleep 1;
while ! pid=$(pidof /opt/viber/Viber); do sleep 1; done; [ -n "$pid" ] && \ wid=$(wmctrl -p -l | grep Viber | grep " $pid " | awk '{print $1}') && \ wmctrl -i -c "$wid"; } & fi exec /opt/viber/Viber "$@"


setevoy commented on 2019-02-18 10:26

+1 for the solution with removing the ~/.cache/qtshadercache directory.

tarkal commented on 2019-02-12 09:26

+1 removing ~/.cache/qtshadercache solved issue

OSKiller commented on 2019-02-12 07:06

I've deleted ~/.cache/qtshadercache/*... After that I've got an error: '/opt/viber/Viber: error while loading shared libraries: cannot open shared object file: No such file or directory'... So, I've copied in in /usr/lib & /usr/lib32 directories... Now everything works perfectly...

There was no such issue on my home PC with Nvidia GeForce and proprietary drivers...