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: 264
Popularity: 0.67
First Submitted: 2013-08-20 17:20 (UTC)
Last Updated: 2024-01-16 09:41 (UTC)

Latest Comments

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

Stelian commented on 2022-08-25 00:32 (UTC)

With the latest version of Viber I cannot make or receive a call no matter what i try. QTWEBENGINE_DISABLE_SANDBOX=1 and QT_QPA_PLATFORM=xcb don´t work for me. There is no crash, error, nothing, but the call menu doesn´t show when there is a call and if i make a call it is not received at all.

wooque commented on 2022-08-24 17:24 (UTC)

For those who experience crashes when calling or receiving calls, it happens if Viber is started as Wayland native, QT_QPA_PLATFORM=xcb will force Viber to run under Xwayland and calls works as before.

kristijanhusak commented on 2022-08-24 08:50 (UTC)

I got same error as 4582:

xkbcommon: ERROR: Couldn't process include statement for 'us(latin)'
xkbcommon: ERROR: Abandoning symbols file "(unnamed)"
xkbcommon: ERROR: Failed to compile xkb_symbols
xkbcommon: ERROR: Failed to compile keymap
[6850:6894:0824/104801.341066:FATAL:xkb_keyboard_layout_engine.cc(640)] Keymap file failed to load: us-latin
[1]    6850 trace trap (core dumped)  viber

This happens because of multiple layouts. I initially had this:

setxkbmap -layout 'us,rs' -variant ',latin' -option 'grp:lctrl_lwin_toggle'

But that didn't work. I just needed to add a space before a comma in variant:

setxkbmap -layout 'us,rs' -variant ' ,latin' -option 'grp:lctrl_lwin_toggle'

That made it work.

zagorsk commented on 2022-08-23 13:58 (UTC)

since version 18.0.0.2, the voice call has stopped working. The QTWEBENGINE_DISABLE_SANDBOX=1 viber command does not help... At the same time, the log says "DBusMenu disabled for this application". It's unclear where to dig... Maybe someone still has viber 17 version in which the voice call worked?

mozo commented on 2022-08-21 21:58 (UTC)

@jordanoff83 Is this with the newest version? It's working fine on my end with the previous version and I don't want to upgrade because of the recent problems with the newest version.

jordanoff83 commented on 2022-08-21 19:12 (UTC)

@Stelian QTWEBENGINE_DISABLE_SANDBOX=1 viber works for me - succesfully started videocall.

dr_pedja commented on 2022-08-21 17:28 (UTC)

QApplication: invalid style override 'kvantum' passed, ignoring it. Available styles: Windows, Fusion qt.webenginecontext:

GLImplementation: desktop Surface Type: OpenGL Surface Profile: CompatibilityProfile Surface Version: 4.6 Using Default SG Backend: yes Using Software Dynamic GL: no Using Angle: no

Init Parameters: * allow-loopback-in-peer-connection
* application-name ViberPC * autoplay-policy no-user-gesture-required * browser-subprocess-path /opt/viber/libexec/QtWebEngineProcess * create-default-gl-context
* disable-features DnsOverHttpsUpgrade,ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture,AudioServiceOutOfProcess * disable-setuid-sandbox
* disable-speech-api
* enable-features NetworkServiceInProcess,TracingServiceInProcess,NetworkServiceInProcess * enable-threaded-compositing
* enable-usermedia-screen-capture
* in-process-gpu
* use-gl desktop

QQmlApplicationEngine failed to load component qrc:/Resources/QML/MainWindow.qml: module "kvantum" is not installed qt.core.qobject.connect: QObject::connect(QWindow, ApplicationEngine): invalid nullptr parameter Segmentation fault (core dumped)

Stelian commented on 2022-08-20 00:11 (UTC)

Could someone confirm that he is able/unable to make or receive a call?

hohmik commented on 2022-08-16 13:53 (UTC) (edited on 2022-08-16 13:54 (UTC) by hohmik)

US(macintosh) as first keyboard layout fix "Keymap file failed to load:" error. PS Any first keyboard layout with any option fix it.

In ~/.config/kxkbrc LayoutList=us,ru,il should be: VariantList=mac,phonetic, But if it is like this: VariantList=,phonetic, There will be: Keymap file failed to load: us-phonetic

ur5wkm commented on 2022-08-16 09:08 (UTC)

Got the same issue as firewalker and 4582:

xkbcommon: ERROR: Couldn't process include statement for 'us(winkeys)' xkbcommon: ERROR: Abandoning symbols file "(unnamed)" xkbcommon: ERROR: Failed to compile xkb_symbols xkbcommon: ERROR: Failed to compile keymap [21235:21257:0816/120454.717474:FATAL:xkb_keyboard_layout_engine.cc(640)] Keymap file failed to load: us-winkeys

My UI language is Ukrainian, the keyboard has two layouts - "ua" and "us". Also, I found that Viber starts without issues when the keyboard layout is set to "ua" instead of us. Looks like the issue appear only if you have two or more layouts set and the current one differs from the UI language.

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