AUR (en) - viber

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.035179
First Submitted:	2013-08-20 17:20 (UTC)
Last Updated:	2024-07-31 20:30 (UTC)

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 43 Next › Last »

jordanoff83 commented on 2019-03-26 22:34 (UTC)

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

pavelchavyr commented on 2019-03-26 09:51 (UTC) (edited on 2019-03-26 09:51 (UTC) by pavelchavyr)

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.

CyberShadow commented on 2019-03-21 08:47 (UTC) (edited on 2019-03-21 08:48 (UTC) by CyberShadow)

File checksum is outdated again.

Edit: curiously, the .deb still says 10.3.0.37.

StratosL commented on 2019-03-20 18:42 (UTC)

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

stathisq commented on 2019-03-18 12:00 (UTC)

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

ugis commented on 2019-03-18 10:04 (UTC) (edited on 2019-03-18 10:05 (UTC) by ugis)

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

Any suggestions?

setevoy commented on 2019-03-17 18:02 (UTC) (edited on 2019-03-17 18:17 (UTC) by setevoy)

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)

7314776 commented on 2019-03-17 16:16 (UTC) (edited on 2019-03-17 16:56 (UTC) by 7314776)

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.

madjoe commented on 2019-03-17 12:27 (UTC) (edited on 2019-03-17 12:28 (UTC) by madjoe)

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!

notuxius commented on 2019-03-01 14:45 (UTC)

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