Search Criteria
Package Details: viber 23.2.0.3-2
Package Actions
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.023869 |
First Submitted: | 2013-08-20 17:20 (UTC) |
Last Updated: | 2024-07-31 20:30 (UTC) |
Dependencies (23)
- alsa-lib
- gst-libav (gst-libav-gitAUR)
- gst-plugins-bad (gst-plugins-bad-gitAUR)
- gst-plugins-base (gst-plugins-base-gitAUR)
- gst-plugins-good (gst-plugins-good-gitAUR)
- gst-plugins-ugly (gst-plugins-ugly-gitAUR)
- libjpeg (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR, libjpeg-turbo)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libxcomposite
- libxcursor
- libxdamage
- libxslt (libxslt-gitAUR)
- libxss
- nss (nss-hgAUR)
- numactl (numactl-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- openssl-1.1
- snappy (snappy-gitAUR)
- xcb-util-cursor (xcb-util-cursor-gitAUR)
- xcb-util-image
- Show 3 more dependencies...
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 44 Next › Last »
layger commented on 2022-09-29 06:58 (UTC) (edited on 2022-09-29 07:33 (UTC) by layger)
i m using Artix cinnamon, and after latest update i cannot use viber. Nothing works- flatpak and appimage version. Its been over a month and still they havent fixed it- F viber.....
when entering com.viber.Viber
Qt: Session management error: None of the authentication protocols specified are supported
QApplication: invalid style override 'gtk' passed, ignoring it. Available styles: Windows, Fusion
sh: line 1: xdg-mime: command not found
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 /app/extra/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 "gtk" is not installed
qt.core.qobject.connect: QObject::connect(QWindow, ApplicationEngine): invalid nullptr parameter
waldauf commented on 2022-09-13 09:42 (UTC)
I found out that I can run Viber from the KRunner when I switch the keyboard to the second one (I have two layouts). After Viber is started I return back the previous layout.
It also works when you want to run Viber from the command line.
zagorsk commented on 2022-09-08 12:32 (UTC) (edited on 2022-09-08 12:33 (UTC) by zagorsk)
I managed to launch viber with the ability to make calls via flatpack. First I installed it with the command: flatpak install flathub com.viber.Viber
and then launched: flatpack run com.viber.Viber
Link to the source - https://flathub.org/apps/details/com.viber.Viber
srki_82 commented on 2022-09-03 10:57 (UTC)
I just installed fresh KDE without Wayland, and with full Pipewire. Viber works out of the box without any modifications.
gorhat commented on 2022-09-03 04:55 (UTC)
Doesn't work on KDE + Nvidia + Wayland, QT_QPA_PLATFORM=xcb viber launches it with black app screen.
zagorsk commented on 2022-09-02 12:27 (UTC)
Since Viber version 18.02 I can't make voice calls no matter what I try QTWEBENGINE_DISABLE_SANDBOX=1 and QT_QPA_PLATFORM=xcp don't work. There is no crash, error, nothing, but the call menu is not displayed when there is a call, and if I make a call, it is not received at all.
karcher commented on 2022-08-31 08:28 (UTC)
@CyberOto, many thanks! That did the trick!
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!
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 44 Next › Last »