Package Details: viber 27.3.0.2-5

Git Clone URL: https://aur.archlinux.org/viber.git (read-only, click to copy)
Package Base: viber
Description: Free and secure calls and messages to anyone, anywhere, on any device and network, in any country!
Upstream URL: https://www.viber.com
Licenses: LicenseRef-Viber-TOS
Conflicts: viber
Submitter: MohammadR
Maintainer: jasongodev
Last Packager: jasongodev
Votes: 261
Popularity: 0.152614
First Submitted: 2013-08-20 17:20 (UTC)
Last Updated: 2026-04-10 18:44 (UTC)

Dependencies (17)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 50 Next › Last »

maros commented on 2022-08-31 06:09 (UTC)

@CyberOto manythanks! :)

This resolved the issue for me. (on manjaro)

dr_pedja commented on 2022-08-30 17:09 (UTC)

@CyberOto, thanks! This resolved the issue for me!

CyberOto commented on 2022-08-30 14:53 (UTC)

@karcher,

I was able to override the kvantum error:

QQmlApplicationEngine failed to load component
qrc:/Resources/QML/MainWindow.qml: module "kvantum" is not installed
[1]    237585 segmentation fault (core dumped)  viber

by starting it with QT_STYLE_OVERRIDE="" viber.

karcher commented on 2022-08-29 10:02 (UTC)

Hi,

I'm getting similar error as @dr_pedja. Viber doesn't start after OS reinstallation. I tried with the a fresh ".ViberPC" folder as well as with the argument QT_QPA_PLATFORM=xcb, but the issue persists. The "kvantum" package is already installed. Any other ideas how to fix it?

Warning: Ignoring WAYLAND_DISPLAY on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
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)

strshr commented on 2022-08-28 16:07 (UTC)

@kristijanhusak, thanks a lot, had exactly the same issue on Fedora with a secondary phonetic keyboard, your solution fixed it for me.

bobolin commented on 2022-08-25 20:22 (UTC)

Same here.

xkbcommon: ERROR: Couldn't process include statement for 'us(phonetic)'
xkbcommon: ERROR: Abandoning symbols file "(unnamed)"
xkbcommon: ERROR: Failed to compile xkb_symbols
xkbcommon: ERROR: Failed to compile keymap
[72982:73009:0825/232011.344564:FATAL:xkb_keyboard_layout_engine.cc(640)] 
Keymap file failed to load: us-phonetic
Trace/breakpoint trap (core dumped)

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?

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 50 Next › Last »