Arch Linux User Repository

@Max77 The link works just fine for me, so it's likely an issue with your system. Check your HTTP proxy settings or if you're on a VPN.

Error while loading 'https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb'

Viber keeps creating the directory "~/Documents" even if I've set the downloads directory for both media and documents to "~/downloads". Can some one help me out with this?

Hey everyone. I have had a similar problem on a debian buster system...even the appImage failed. However, when I installed the .deb file there, it added in libxcb-xinput0, after which it worked again. Not sure if this is helpful, but maybe someone can figure out what the relevance is, and adjust whatever is required to fix it in general.

@Stelian Thank you very much!!!

@mozo, @MarsSeed I have tried the latest RPM version of Viber from their site and it can't make or receive a call.

The long story short - after many hours of testing and debugging I think that the problem is related to the signal SIGSYS and Seccomp. We need help from people who know more in this area. Maybe the solution will be the developers of Viber /or someone who knows how/ to update QtWebEngine with a more recent version. As a temporary solution for now we can set the QTWEBENGINE_DISABLE_SANDBOX environment variable to 1.

$ QTWEBENGINE_DISABLE_SANDBOX=1 viber

After setting the variable Viber can make and receive calls again. I don't know what the security implications would be.

@MarsSeed, I'm using Telegram too but I need both - Telegram and Viber. Let's hope the maintainer will try with rpm.

@Stelian, I don't think Viber was ever supported on Arch Linux.

@mozo I think the we could try out the Viber for Fedora RPM. In theory that should be linked to newer libraries, more in line with Arch.

Btw I've managed to convince my friends and family to come over to Telegram. :)

That one has a native Linux client, works better than Viber and doesn't show ads or monitor our activities for monetization purposes.

@Stelian, it's working fine on Ubuntu, I just tried it...

Unfortunately I don't have Ubuntu to try but I can install it tommorrow to test it.

I have tried the viber.AppImage version from their site and it has the same problem. Do we know for sure that Viber can make and receive a call for the supported linux distributions - Ubuntu and Fedora? Could someone confirm it? Maybe Viber for linux has a bug in general that is not related to the linux distribution?

I don't know what the difference is but this is really bad news... Can we try to use the rpm package? Will it make any difference?

I have received an official response from the viber support:

Hello,

Viber is no longer supported on Arch Linux.

For a full list of supported devices and platforms, please follow the link: https://vb.me/5d739e20

We apologize for the inconvenience.

Best regards, Tina L Viber Support Team Quick question? Tweet to @ViberHelp

Could someone tell us what is the difference between the supported linux distributions and Arch Linux?

Thanks for your suggestion but we want the native version :(

@mozo As a temporary solution you can install viber for windows under wine. I tested it and it works, but it uses too much CPU and memory compared to native linux viber.

It's a big problem. I hope for a solution badly.

@Badabum, @mozo Thank you. Perhaps the problem is global. I haven't found a workaround yet. I am using Xfce if it matters.

@Stelian Same problem here.

@Stelian, I have the same problem. I can't make any calls from desktop, or redirect a call to PC. A week or two ago everything worked fine.

Could someone confirm this problem: Viber Linux can not start or receive calls (on laptop). Other users do not receive notifications when I am calling. When someone calls me there is only a notification sound, but not a way to accept the call.

Some of the colored emojis render as black and white. When I first installed viber some emoticons would show up black and white emojis and some would just show up as squares. So, I installed the noto-fonts-emoji package. The effect was that the squares were converted into colored emojis just the way I wanted them to be but the original black and white emojis remained as they are. How to get the black and white emojis to be colored?

Does anyone know how to get notifications to work on plasma? On any other GTK-based DE they work just fine but not in plasma...

God this version is quite buggy, Viber scrolls super fast with touchpad and it freezes when I move it to second monitor. Hopefully they will release new bugfix version soon.

@teras run LD_LIBRARY_PATH=/opt/viber/lib /usr/bin/viber

@teras ldd for viber on my machine shows it uses bundled libraries

ldd /opt/viber/Viber | grep qt
libQt5Sql.so.5 => /opt/viber/lib/libQt5Sql.so.5 (0x00007f610e0a8000)

After the latest QT update (which might be the reason @wooque has this issue -- I have it too), Viber became obviously slower. After discussions with people who use Viber under Ubuntu, I found out that, although my Viber version links on system wide QT libraries, when checked with ld, on my friend's it uses the private folder under /opt/viber/lib instead.

For example, for me ldd shows this entry libQt5Sql.so.5 => /usr/lib/libQt5Sql.so.5 (0x00007f795f6ec000) while for my friend on Ubuntu this libQt5Sql.so.5 => /opt/viber/lib/libQt5Sql.so.5 (0x00007f905eb4f000)

I believe the authors of Viber would like the second behavior, otherwise they wouldn't distribute the QT libraries. Any idea how to fix this on Arch?

On Plasma when I start Viber it shows generic X icon instead of Viber icon in taskbar, is there a fix for this?

@radio_rogal run

killall viber
QT_QPA_PLATFORM=xcb viber

@MKharaba, same to me:

==> Validating source files with sha256sums... viber-13.3.1.22.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build viber

==> Validating source files with sha256sums...
    viber-13.3.1.22.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
error downloading sources: viber

qt.qpa.wayland: Failed to load client buffer integration: "wayland-egl"
qt.qpa.wayland: Available client buffer integrations: ()

Works Fine

On KDE Plasma new viber 13.3.1 is completely broken! It doesn't show pop-ups. Without that feature it is very uncomfortable. And this problem is not arch related, or plasma version related. I tried on VM with old plasma and ubuntu 18.04 and I got the same result.

Anyone can test pop-ups on different DE, please?

Hmm, today double click works fine...

Hey thanks for the package. Everything seems to be working fine - except that clicking (single or double) on the tray icon does not open the app. I need to right click and select open viber.

Nice porting. I have a problem. Viber freezes xfwm4. My pc is HP 2600 with Quadro FX 1800 with nvidia-340xx I think the freeze is linked to nvidia acceleration. Have you experience in with this?

PS: I'm using Artix

Icon doesn't show up in launcher like rofi until I changed Icon in /usr/share/applications/viber.desktop to /usr/share/icons/hicolor/32x32/apps/viber.png

@vs220 seems yes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GL_AMD_draw_buffers_blend, GL_AMD_multi_draw_indirect, 
    GL_ARB_derivative_control, GL_ARB_direct_state_access, 
    GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect,
    GL_ARB_half_float_vertex, GL_ARB_indirect_parameters, 
    GL_ARB_multi_draw_indirect, GL_ARB_occlusion_query2, 
    GL_AMD_draw_buffers_blend, GL_AMD_multi_draw_indirect
    GL_ARB_draw_indirect, GL_ARB_draw_instanced, 
    GL_ARB_indirect_parameters, GL_ARB_instanced_arrays, 
    GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, 
    GL_EXT_direct_state_access, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, 

@iamkaant OpenGL works? glxinfo |grep -e glx -e direct

I have reinstalled my system and now launching Viber I get

QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled

Cannot mix incompatible Qt library (5.14.2) with this library (5.15.1)

Aborted (core dumped)

Can anyone suggest a solution?

Sandor please update the package

Could please someone change sha256 to 1037a48d74caef33d123b166da2bfb1fe8fa67590b8669ecf25b314f41374267 ?

Thanks!

needed this pkg to work so old relatives can simply have it working in linux, so i updated it and addapted dependencies avoiding missing qt5 libs:

pkgver=13.3.1
depends=('libxss' 'xcb-util-image' 'xcb-util-keysyms' 'xcb-util-renderutil'  'xcb-util-wm' 'libxss' 'nss' 'libxcomposite' 'gst-plugins-base' 'gst-plugins-good' 'gst-plugins-ugly' 'gst-libav' 'libxslt' 'openssl-1.0' 'icu55' 'qrencode' 'libpng12' 'qt5-webengine' 'qt5-3d' 'qt5-remoteobjects' 'qt5-multimedia' 'qt5-websockets' 'qt5-virtualkeyboard')
md5sums=('d85f509804d5b83d602eafe5dc22dead')

Congratulation! Calls work in new version! Change a SHA in PKGBUILD and then install.

@Sirius, a new version came out, thus SHA of the package changed.

Currently it's: 1037a48d74caef33d123b166da2bfb1fe8fa67590b8669ecf25b314f41374267

So, until the maintainer verifies and alters the build, your temporary workaround would be to edit the PKGBUILD SHA on line 19.

I got this error when I tried to install viber: ==> Making package: viber 12.0.0.7-1 (Sat Jul 18 23:22:27 2020) ... ==> Validating source files with sha256sums... viber-12.0.0.7.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!

At the first start, the program displayed an error:

"qt.qpa.plugin: Could not load the Qt platform plugin" xcb "in" "even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. "

After installing the qt5-base package, everything worked. You need to add this package depending.

@everyone

Call is working in the snap version but version is outdated

Calls don' t work. Does anybody solve this problem?

[1:14:0529/143436.591733:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

syscall 0230: "Assuming 0230 is decimal, this corresponds to clock_nanosleep. Presumably, the existing seccomp filters in chromium only allow nanosleep, but not clock_nanosleep. They need to be adjusted."[1]

Bug report in [1] also states "There are fixes upstream at Qt based on the Chromium fixes" so unless they do a rebuild, I'm thinking I'll uninstall Viber instead of "enjoying it on their other platforms".

I opened a ticket for the issue with glibc. The response:

We have decided to put any updates for Linux on hold until further notice. There are no version releases planned in the foreseeable future. I apologize for any inconvenience. We hope that you can still enjoy Viber on our other platforms!

Does anyone knows the offending commit of glibc?

Like others, I have the issue with calls. Outgoing calls never reach anyone. When I make outgoing call, I get systemd-coredump[12749]: Process 12732 (QtWebEngineProc) of user 1000 dumped core. Anyone aware how to fix?

@nslxndr, I had to add the libxkbcommon-x11 library as a runtime dependency to be able to run the program on a fresh system installation. Could you please update PKBBUILD?

@dpp I think @vs220 explained the issue below. I don't know how to patch or downgrade glibc.

I have the same issue like rapurapu - calls don't work anymore

@ssk This has affected many programs

Comment by grayarcher (grayarcher) - Saturday, 21 March 2020, 17:44 GMT+2 "The root cause here is a change in glibc, as noted by the 2.31 release notes:

• System call wrappers for time system calls now use the new time64 system calls when available. On 32-bit targets, these wrappers attempt to call the new system calls first and fall back to the older 32-bit time system calls if they are not present. This may cause issues in environments that cannot handle unsupported system calls gracefully by returning -ENOSYS. Seccomp sandboxes are affected by this issue.

Since it's the individual applications like Discord, or any other electron/CEF based/like app that apply the seccomp filter, they will have to adjust their filters. Until that happens, the options are: - Patch the individual binaries to allow clock_gettime64, similary to how the source code changed in upstream chromium for a previous issue: https://github.com/chromium/chromium/commit/54407b422a9cbf775a68c1d57603c0ecac8ce0d7#diff-76dd4327967fba9837d93a944eeb1165

(A similar change was commited to OpenSSH https://github.com/openssh/openssh-portable/commit/ccd3b247d59d3bde16c3bef0ea888213fbd6da86#diff-5039537cc0e0b50db6f66642be1248fa ) - Downgrade glibc/revert that specific change in glibc"

After update error is shown:
qrc:/QML/DebugMenu.qml:262: TypeError: Cannot call method 'isWasabiEnabled' of undefined qrc:/QML/DebugMenu.qml:289: TypeError: Cannot call method 'isSearchInCommunitiesForceEnabled' of undefined qrc:/QML/DebugMenu.qml:296: TypeError: Cannot call method 'isOOABURISpamCheckerForceEnabled' of undefined qrc:/QML/DebugMenu.qml:304: TypeError: Cannot call method 'isRateCallQualityForceEnabled' of undefined [1:14:0410/092611.970084:ERROR:adm_helpers.cc(73)] Failed to query stereo recording. ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:seccomp-bpf failure in syscall 0230

Call is not working somehow.

@nik123true It works without qt5-base

Check out

LD_LIBRARY_PATH=/opt/viber/lib /usr/bin/viber

LD_LIBRARY_PATH=/opt/viber/lib ldd /usr/bin/viber |grep Qt5 ??

Please include qt5-base as a dependency because viber doesn't work without it.

Symlink /usr/bin/viber starting with lowercase letter. This causes firejail profile https://github.com/netblue30/firejail/blob/master/etc/Viber.profile to fail. Minor inconvenience, not sure if should be fixed.

I updated the package, sorry for the delay. @vyachkonovalov I applied the most of your changes, thanks for your work.

Oops, I made a mistake and removed PKGBUILD before making a git diff :D
Here is my patch, without unnecessary eula.html and viber (shell script) files, proper LICENSE, also fixed sed replacement for viber.desktop.
https://gist.github.com/vyachkonovalov/81a9ad265f437f9f40f7a3393aefc65b

@bbolgradov I manually added a new line at the end of your downloaded patch and I was able to successfully proceed with viber installation. Thank you

Should be fixed now. Github gists seem to get their last newline stripped.

@iraklisg Same for me. Just use bbolgradov's patch as a reference and update the version and hash manually, worked nicely for me :)

@bbolgradov @vyachkonovalov Thank you for your reply.

Interestingly, running git apply viber-12.0.0.7-1.patch gives me the following error:

error: corrupt patch at line 2

The same applies to vyachkonovalov's solution were I get:

error: corrupt patch at line 176

Am I missing something? Can I provide you some extra information?

@vyachkonovalov, that's a strange patch you've got there.

Here's a working one that simply bumps the version.

yay -G viber
cd viber
wget https://gist.githubusercontent.com/bbolgradov/0f34f525d001746e6addf8e790633563/raw/8448bc7ad3ec68a38f9b7694d7e2f6b73af5fcc5/viber-12.0.0.7-1.patch
git apply viber-12.0.0.7-1.patch
makepkg -sci

Wow, this version is so outdated.

@iraklisg Current is 12.0.0.7, here is the patch

How to apply the patch:

yay -G viber # not sure about this one, I don't use yay
cd viber
curl -O 'https://gist.githubusercontent.com/vyachkonovalov/c82390fb3d2fda95be89c8d21f657a26/raw/53f1ba9c4f44e2feae20155f506fdf5b6988f9a3/PKGBUILD.diff'
git apply PKGBUILD.diff
makepkg -si

Installing via yay:

Validating source files with md5sums...
    viber-10.3.0.37.tar.gz ... FAILED
    eula.html ... Passed
    viber ... Passed
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: viber

Choosing the package to be Clean builded did not do the trick for me:

Hello,

Please remove libcurl-compat from dependencies, Viber works OK without it, but presence libcurl-compat in the system breaks a lot of AUR packages with following configure errors:

configure:8766: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c -lalpm   >&5
/usr/bin/ld: /usr/lib/libcurl.so.4: undefined reference to `OpenSSL_version_num@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libssh2.so.1: undefined reference to `EVP_des_ede3_cbc@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libcurl.so.4: undefined reference to `SSL_CTX_set_srp_password@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libssh2.so.1: undefined reference to `EC_KEY_get0_group@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libarchive.so.13: undefined reference to `EVP_aes_128_ecb@OPENSSL_1_1_0'
/usr/bin/ld: /usr/lib/libcurl.so.4: undefined reference to `SSL_CTX_use_certificate_chain_file@OPENSSL_1_1_0'

Hello. Please change source to https.

I get the following CLI error:

~ >>> viber                                                                                                                                                   
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method

Hi, @nslxndr ! Please, add the "openssl-1.0" package to the dependencies section. Viber don't want to work without it.

Is there any reason for cdparanoia as dependency? I didn't see CD in years.

Please give the downloaded file an unique filename, as per https://wiki.archlinux.org/index.php/PKGBUILD#source (see the "Warning" box). This will fix checksum errors due to old viber.deb copies.

I remove viber 'pacman -Rsn viber', install it again and now it works.

@vs220, openssl-1.0 is installed

please add depending openssl-1.0

@pavelchavyr install openssl-1.0 pacman -Suy openssl-1.0

Choosing the package to be Clean builded did the trick for me:

  1 viber                                    (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 1

I have some problem. After updating 7->10 viber not starting.

qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave Received signal 11 <unknown> 000000000000

0 0x7f047a079993 <unknown>

1 0x7f047f3b03c0 <unknown>

2 0x7f0476913ce7 qHash()

3 0x0000005e1773 <unknown>

4 0x0000005e7d19 <unknown>

5 0x0000005e6767 <unknown>

6 0x0000005e47d6 <unknown>

7 0x00000080b86c <unknown>

8 0x0000008043c3 <unknown>

9 0x0000007ffe82 <unknown>

10 0x00000083d2cf <unknown>

11 0x00000083c6d0 <unknown>

12 0x7f0476b03ae5 QStateMachinePrivate::enterStates()

13 0x7f0476b069a1 QStateMachinePrivate::_q_start()

14 0x7f0476aa478e QObject::event()

15 0x7f0476b0a85f QStateMachine::event()

16 0x7f047752938e QApplicationPrivate::notify_helper()

17 0x7f047752a785 QApplication::notify()

18 0x7f0476a7b794 QCoreApplication::notifyInternal2()

19 0x7f0476a7c465 QCoreApplicationPrivate::sendPostedEvents()

20 0x7f0476acd373 postEventSourceDispatch()

21 0x7f047554c7bf g_main_context_dispatch

22 0x7f047554e739 <unknown>

23 0x7f047554e77e g_main_context_iteration

24 0x7f0476acce1b QEventDispatcherGlib::processEvents()

25 0x7f046e85858e <unknown>

26 0x7f0476a7717f QEventLoop::exec()

27 0x7f0476a7bd81 QCoreApplication::exec()

28 0x00000082f69b <unknown>

29 0x0000007fef5c <unknown>

30 0x7f04761e0223 __libc_start_main

31 0x0000005d3ee9 _start

r8: 6976656400001f40 r9: 0000000000000004 r10: 6976656404ece686 r11: 0000000000000202 r12: 00007ffdd4a66340 r13: 0000000004eb5650 r14: 00007ffdd4a66330 r15: 00007ffdd4a66348 di: 00000000ad169c10 si: 00000000269da1f0 bp: 0000000000000011 bx: 0000000004f16d20 dx: 0000000000000000 ax: 0000000004ecc740 cx: 0000000000000002 sp: 00007ffdd4a662f8 ip: 00007f0476913ce7 efl: 0000000000010282 cgf: 002b000000000033 erf: 0000000000000000 trp: 000000000000000d msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.

File checksum is outdated again.

Edit: curiously, the .deb still says 10.3.0.37.

Same as others, viber.deb does not pass validity check

@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.

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

Any suggestions?

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-10.3.0.37-1-x86_64.pkg.tar.xz'

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

[2019-03-16 23:00] [ALPM] upgraded viber (7.0.0.1035-1 -> 10.3.0.37-1)

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.

Synchronizing package databases...

Starting full system upgrade...

Cloning viber build files...

Checking viber dependencies...

Building viber...

==> Making package: viber 10.3.0.37-1 (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!

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:

!/bin/bash

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

LD_PRELOAD=libcurl.so.3 exec env QT_AUTO_SCREEN_SCALE_FACTOR=0 /opt/viber/Viber "$@"

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

LD_PRELOAD=libcurl.so.3 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:

!/bin/bash

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

LD_PRELOAD=libcurl.so.3 exec /opt/viber/Viber "$@"

Thanks!

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

+1 removing ~/.cache/qtshadercache solved issue

I've deleted ~/.cache/qtshadercache/*... After that I've got an error: '/opt/viber/Viber: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory'... So, I've copied libidn2.so in libidn2.so.4 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...

Solved by deleting ~/.cache/qtshadercache directory

SOLVED! mv ~/.cache ~/cache-old I've tried delete only Viber cache - doesnt help but mv all is OK from here

https://www.reddit.com/r/SolusProject/comments/9d4a5q/viber_white_screen_after_latest_update/ in link U may see QT cache causin' problem

It works, but the font is displayed in the color of the current background even when the text is highlighted...

It works perfect when started as sudo...

Same issue, but I did downgrade to all Qt5 updates and still not working.

The same issue.

Same issue after the QT update as DmitrySkibitsky commented.

After the update Qt stopped working. The application opens, but there is nothing in the application window, and the mouse cursor changes its state when you move around the application window area, even perhaps the event of clicks catches and performs an action, but nothing is displayed in the window itself.

Installed this package on an up-to-date Arch system today, but I can't get Viber to launch. Both /usr/bin/viber and /opt/viber/Viber exit immediately with no errors and status code 0. I have tried prepending LD_LIBRARY_PATH=/opt/viber/lib but it changed nothing. I have openssl and pulseaudio installed.

Any ideas?

http://www.reddit.com/r/linux/comments/9m16iz/til_viber_is_eol_on_gnulinux/

https://forum.manjaro.org/t/no-more-new-viber-on-linux/58927

As it looks, Rakuten will not release any new version of Viber for Linux.

Please! new version is neaded!

The package is flagged as out-of-date but I don't see any new version of Viber.

Hello, i have two problems using viber with KDE. First one I can not shutdow the machine. There is a notification poput that sayes, Viber preventing KDE from shutdown. Second I cannont uncheck the "Start viber on system startup" option from inside the Options menu. Can someone help me with those issues?

Install openssl-1.0 and pulseaudio and reboot.Worked for me.

Error:

Cannot mix incompatible Qt library (version 0x50901) with this library (version 0x50a01)

Can be fixed with command:

LD_LIBRARY_PATH=/opt/viber/lib/ viber

Viber starts fine but when I enter my phone it says "No Connection".

I don't know if this will help but I'm pasting the output when I run it from terminal:

Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...

Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...

Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...

Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback

qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings

qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup

qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init

qt.network.ssl: QSslSocket: cannot resolve sk_new_null

qt.network.ssl: QSslSocket: cannot resolve sk_push

qt.network.ssl: QSslSocket: cannot resolve sk_free

qt.network.ssl: QSslSocket: cannot resolve sk_num

qt.network.ssl: QSslSocket: cannot resolve sk_pop_free

qt.network.ssl: QSslSocket: cannot resolve sk_value

qt.network.ssl: QSslSocket: cannot resolve SSL_library_init

qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings

qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index

qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method

qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method

qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method

qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method

qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain

qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf

qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf

qt.network.ssl: QSslSocket: cannot resolve SSLeay

qt.network.ssl: QSslSocket: cannot resolve SSLeay_version

qt.network.ssl: Incompatible version of OpenSSL

qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method

qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init

QQuickItem: Cannot set activeFocusOnTab to false once item is the active focus item.

QQuickItem: Cannot set activeFocusOnTab to false once item is the active focus item.

qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method

qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init

It works on latest Antergos

Can't start Viber anymore:

$ viber /opt/viber/Viber: error while loading shared libraries: libpsl.so.5: cannot open shared object file: No such file or directory

Looks like libpsl was updated in the meantime.

$ ls -la libpsl* lrwxrwxrwx 1 root root 15 25. Feb 23:54 libpsl.so -> libpsl.so.6.2.0 lrwxrwxrwx 1 root root 15 25. Feb 23:54 libpsl.so.6 -> libpsl.so.6.2.0 -rwxr-xr-x 1 root root 64352 25. Feb 23:54 libpsl.so.6.2.0

All work so good. Thanks.

$ viber Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory... Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory... qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave PulseAudioService: pa_context_connect() failed PulseAudioService: pa_context_connect() failed Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.

Viber failed after qt5 and Viber update

strange, viber doesn't work just exits with 0 exit code. [tarasko@archlinux ~]$ LD_PRELOAD=libcurl.so.3 /opt/viber/Viber [tarasko@archlinux ~]$ echo $? 0

How can we use this without pulseaudio now? I use ALSA.