Package Details: viber 21.8.0.11-1

Git Clone URL: https://aur.archlinux.org/viber.git (read-only, click to copy)
Package Base: viber
Description: Proprietary cross-platform IM and VoIP software
Upstream URL: https://www.viber.com
Licenses: custom
Submitter: MohammadR
Maintainer: nslxndr
Last Packager: nslxndr
Votes: 262
Popularity: 0.51
First Submitted: 2013-08-20 17:20 (UTC)
Last Updated: 2024-01-16 09:41 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 40 Next › Last »

firewalker commented on 2020-05-28 11:48 (UTC)

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!

firewalker commented on 2020-05-10 11:48 (UTC)

Does anyone knows the offending commit of glibc?

iamkaant commented on 2020-05-03 17:23 (UTC)

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?

jacp commented on 2020-04-23 05:12 (UTC)

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

rapurapu commented on 2020-04-17 16:39 (UTC)

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

dpp commented on 2020-04-17 16:18 (UTC)

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

vs220 commented on 2020-04-11 09:48 (UTC)

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

ssk commented on 2020-04-10 03:49 (UTC) (edited on 2020-04-10 03:49 (UTC) by ssk)

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

rapurapu commented on 2020-04-08 13:18 (UTC)

Call is not working somehow.

vs220 commented on 2020-03-25 18:03 (UTC) (edited on 2020-03-25 18:20 (UTC) by vs220)

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