Search Criteria
Package Details: viber 16.1.0.37-1
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: | 265 |
Popularity: | 0.98 |
First Submitted: | 2013-08-20 17:20 (UTC) |
Last Updated: | 2021-10-13 14:00 (UTC) |
Dependencies (18)
- alsa-lib (alsa-lib-git, alsa-lib-minimal-git, alsa-lib-x205ta)
- gst-libav (gst-libav-git)
- gst-plugins-base (gst-plugins-base-git)
- gst-plugins-good (gst-plugins-good-git)
- gst-plugins-ugly (gst-plugins-ugly-git)
- libpulse (libpulse-bluedio, pulseaudio-pali, pulseaudio-dummy, libpulse-nosystemd-git, libpulse-nosystemd, libpulse-nosystemd-minimal-git, libpulse-airplay, pulseaudio-git)
- libxcomposite
- libxcursor (libxcursor-git)
- libxdamage
- libxslt (libxslt-git)
- libxss
- nss (nss-hg)
- openssl (libressl-git, openssl-static, openssl-hardened, quictls-openssl, openssl-git)
- openssl-1.0 (openssl-1.0-chacha20, openssl-1.0-hardened)
- xcb-util-image
- xcb-util-keysyms
- xcb-util-renderutil
- xcb-util-wm
Latest Comments
Hubro commented on 2022-06-14 12:40 (UTC)
@Max77 The link works just fine for me, so it's likely an issue with your system. Check your HTTP proxy settings or if you're on a VPN.
Max77 commented on 2022-06-14 11:48 (UTC)
Error while loading 'https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb'
nikinbaidar commented on 2022-05-06 15:10 (UTC)
Viber keeps creating the directory "~/Documents" even if I've set the downloads directory for both media and documents to "~/downloads". Can some one help me out with this?
trentmu commented on 2022-04-05 10:15 (UTC)
Hey everyone. I have had a similar problem on a debian buster system...even the appImage failed. However, when I installed the .deb file there, it added in libxcb-xinput0, after which it worked again. Not sure if this is helpful, but maybe someone can figure out what the relevance is, and adjust whatever is required to fix it in general.
mozo commented on 2022-03-09 08:45 (UTC)
@Stelian Thank you very much!!!
Stelian commented on 2022-03-09 02:22 (UTC) (edited on 2022-03-09 13:23 (UTC) by Stelian)
@mozo, @MarsSeed I have tried the latest RPM version of Viber from their site and it can't make or receive a call.
The long story short - after many hours of testing and debugging I think that the problem is related to the signal SIGSYS and Seccomp. We need help from people who know more in this area. Maybe the solution will be the developers of Viber /or someone who knows how/ to update QtWebEngine with a more recent version. As a temporary solution for now we can set the QTWEBENGINE_DISABLE_SANDBOX environment variable to 1.
$ QTWEBENGINE_DISABLE_SANDBOX=1 viber
After setting the variable Viber can make and receive calls again. I don't know what the security implications would be.
mozo commented on 2022-03-08 19:09 (UTC)
@MarsSeed, I'm using Telegram too but I need both - Telegram and Viber. Let's hope the maintainer will try with rpm.
MarsSeed commented on 2022-03-08 15:16 (UTC)
@Stelian, I don't think Viber was ever supported on Arch Linux.
@mozo I think the we could try out the Viber for Fedora RPM. In theory that should be linked to newer libraries, more in line with Arch.
Btw I've managed to convince my friends and family to come over to Telegram. :)
That one has a native Linux client, works better than Viber and doesn't show ads or monitor our activities for monetization purposes.
mozo commented on 2022-03-08 11:05 (UTC)
@Stelian, it's working fine on Ubuntu, I just tried it...
mozo commented on 2022-03-08 00:23 (UTC)
Unfortunately I don't have Ubuntu to try but I can install it tommorrow to test it.
Stelian commented on 2022-03-08 00:16 (UTC) (edited on 2022-03-08 00:17 (UTC) by Stelian)
I have tried the viber.AppImage version from their site and it has the same problem. Do we know for sure that Viber can make and receive a call for the supported linux distributions - Ubuntu and Fedora? Could someone confirm it? Maybe Viber for linux has a bug in general that is not related to the linux distribution?
mozo commented on 2022-03-07 20:35 (UTC) (edited on 2022-03-07 20:36 (UTC) by mozo)
I don't know what the difference is but this is really bad news... Can we try to use the rpm package? Will it make any difference?
Stelian commented on 2022-03-07 19:24 (UTC) (edited on 2022-03-07 19:31 (UTC) by Stelian)
I have received an official response from the viber support:
Hello,
Viber is no longer supported on Arch Linux.
For a full list of supported devices and platforms, please follow the link: https://vb.me/5d739e20
We apologize for the inconvenience.
Best regards, Tina L Viber Support Team Quick question? Tweet to @ViberHelp
Could someone tell us what is the difference between the supported linux distributions and Arch Linux?
mozo commented on 2022-02-28 23:15 (UTC)
Thanks for your suggestion but we want the native version :(
Stelian commented on 2022-02-28 22:08 (UTC) (edited on 2022-02-28 22:09 (UTC) by Stelian)
@mozo As a temporary solution you can install viber for windows under wine. I tested it and it works, but it uses too much CPU and memory compared to native linux viber.
mozo commented on 2022-02-28 21:21 (UTC)
It's a big problem. I hope for a solution badly.
Stelian commented on 2022-02-28 20:19 (UTC)
@Badabum, @mozo Thank you. Perhaps the problem is global. I haven't found a workaround yet. I am using Xfce if it matters.
mozo commented on 2022-02-28 12:55 (UTC)
@Stelian Same problem here.
Badabum commented on 2022-02-27 18:20 (UTC) (edited on 2022-02-27 18:26 (UTC) by Badabum)
@Stelian, I have the same problem. I can't make any calls from desktop, or redirect a call to PC. A week or two ago everything worked fine.
Stelian commented on 2022-02-23 19:54 (UTC)
Could someone confirm this problem: Viber Linux can not start or receive calls (on laptop). Other users do not receive notifications when I am calling. When someone calls me there is only a notification sound, but not a way to accept the call.
nikinbaidar commented on 2022-02-08 17:25 (UTC)
Some of the colored emojis render as black and white. When I first installed viber some emoticons would show up black and white emojis and some would just show up as squares. So, I installed the
noto-fonts-emoji
package. The effect was that the squares were converted into colored emojis just the way I wanted them to be but the original black and white emojis remained as they are. How to get the black and white emojis to be colored?zelimir commented on 2021-12-01 11:38 (UTC)
Does anyone know how to get notifications to work on plasma? On any other GTK-based DE they work just fine but not in plasma...
wooque commented on 2021-11-08 18:55 (UTC)
God this version is quite buggy, Viber scrolls super fast with touchpad and it freezes when I move it to second monitor. Hopefully they will release new bugfix version soon.
vs220 commented on 2021-10-18 15:14 (UTC)
@teras run LD_LIBRARY_PATH=/opt/viber/lib /usr/bin/viber
wooque commented on 2021-10-18 14:46 (UTC)
@teras ldd for viber on my machine shows it uses bundled libraries
teras commented on 2021-10-18 14:39 (UTC) (edited on 2021-10-18 14:39 (UTC) by teras)
After the latest QT update (which might be the reason @wooque has this issue -- I have it too), Viber became obviously slower. After discussions with people who use Viber under Ubuntu, I found out that, although my Viber version links on system wide QT libraries, when checked with ld, on my friend's it uses the private folder under /opt/viber/lib instead.
For example, for me ldd shows this entry
libQt5Sql.so.5 => /usr/lib/libQt5Sql.so.5 (0x00007f795f6ec000)
while for my friend on Ubuntu thislibQt5Sql.so.5 => /opt/viber/lib/libQt5Sql.so.5 (0x00007f905eb4f000)
I believe the authors of Viber would like the second behavior, otherwise they wouldn't distribute the QT libraries. Any idea how to fix this on Arch?
wooque commented on 2021-10-18 00:29 (UTC)
On Plasma when I start Viber it shows generic X icon instead of Viber icon in taskbar, is there a fix for this?
vs220 commented on 2021-10-13 18:05 (UTC) (edited on 2021-10-13 18:07 (UTC) by vs220)
@radio_rogal run
zelimir commented on 2021-10-13 10:37 (UTC)
@MKharaba, same to me:
==> Validating source files with sha256sums... viber-13.3.1.22.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build viber
MKharaba commented on 2021-10-13 07:52 (UTC) (edited on 2021-10-13 07:54 (UTC) by MKharaba)
radio_rogal commented on 2021-09-04 09:11 (UTC) (edited on 2021-09-04 09:11 (UTC) by radio_rogal)
Thenujan commented on 2021-08-16 01:35 (UTC)
Works Fine
no95typem commented on 2020-12-31 14:38 (UTC) (edited on 2020-12-31 14:40 (UTC) by no95typem)
On KDE Plasma new viber 13.3.1 is completely broken! It doesn't show pop-ups. Without that feature it is very uncomfortable. And this problem is not arch related, or plasma version related. I tried on VM with old plasma and ubuntu 18.04 and I got the same result.
Anyone can test pop-ups on different DE, please?
manjaro_loover commented on 2020-12-13 10:29 (UTC)
Hmm, today double click works fine...
manjaro_loover commented on 2020-12-08 22:24 (UTC)
Hey thanks for the package. Everything seems to be working fine - except that clicking (single or double) on the tray icon does not open the app. I need to right click and select open viber.
mauzil commented on 2020-11-18 08:29 (UTC)
Nice porting. I have a problem. Viber freezes xfwm4. My pc is HP 2600 with Quadro FX 1800 with nvidia-340xx I think the freeze is linked to nvidia acceleration. Have you experience in with this?
PS: I'm using Artix
wooque commented on 2020-11-17 10:42 (UTC) (edited on 2020-11-17 10:43 (UTC) by wooque)
Icon doesn't show up in launcher like rofi until I changed Icon in
/usr/share/applications/viber.desktop
to/usr/share/icons/hicolor/32x32/apps/viber.png
iamkaant commented on 2020-11-12 18:04 (UTC) (edited on 2020-11-12 18:07 (UTC) by iamkaant)
@vs220 seems yes
vs220 commented on 2020-11-12 17:23 (UTC)
@iamkaant OpenGL works? glxinfo |grep -e glx -e direct
iamkaant commented on 2020-11-12 12:35 (UTC) (edited on 2020-11-12 12:36 (UTC) by iamkaant)
I have reinstalled my system and now launching Viber I get
Can anyone suggest a solution?
dalu commented on 2020-08-15 11:35 (UTC)
Sandor please update the package
vblats commented on 2020-08-10 18:12 (UTC)
Could please someone change sha256 to 1037a48d74caef33d123b166da2bfb1fe8fa67590b8669ecf25b314f41374267 ?
Thanks!
damir commented on 2020-08-08 22:18 (UTC) (edited on 2020-08-08 22:19 (UTC) by damir)
needed this pkg to work so old relatives can simply have it working in linux, so i updated it and addapted dependencies avoiding missing qt5 libs:
noobfromby commented on 2020-07-23 14:47 (UTC)
Congratulation! Calls work in new version! Change a SHA in PKGBUILD and then install.
kaynetik commented on 2020-07-20 06:40 (UTC)
@Sirius, a new version came out, thus SHA of the package changed.
Currently it's:
1037a48d74caef33d123b166da2bfb1fe8fa67590b8669ecf25b314f41374267
So, until the maintainer verifies and alters the build, your temporary workaround would be to edit the
PKGBUILD
SHA on line 19.Sirius commented on 2020-07-18 21:05 (UTC)
I got this error when I tried to install viber: ==> Making package: viber 12.0.0.7-1 (Sat Jul 18 23:22:27 2020) ... ==> Validating source files with sha256sums... viber-12.0.0.7.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!
Rverkvn commented on 2020-07-04 13:13 (UTC) (edited on 2020-07-04 16:06 (UTC) by Rverkvn)
At the first start, the program displayed an error:
"qt.qpa.plugin: Could not load the Qt platform plugin" xcb "in" "even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. "
After installing the qt5-base package, everything worked. You need to add this package depending.
rapurapu commented on 2020-06-14 08:39 (UTC)
@everyone
Call is working in the snap version but version is outdated
noobfromby commented on 2020-06-14 08:35 (UTC)
Calls don' t work. Does anybody solve this problem?
Mel commented on 2020-05-29 12:48 (UTC)
syscall 0230: "Assuming 0230 is decimal, this corresponds to clock_nanosleep. Presumably, the existing seccomp filters in chromium only allow nanosleep, but not clock_nanosleep. They need to be adjusted."[1]
Bug report in [1] also states "There are fixes upstream at Qt based on the Chromium fixes" so unless they do a rebuild, I'm thinking I'll uninstall Viber instead of "enjoying it on their other platforms".
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
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 ??
nik123true commented on 2020-03-25 17:03 (UTC)
Please include qt5-base as a dependency because viber doesn't work without it.
hubcap commented on 2020-01-05 15:10 (UTC) (edited on 2020-01-05 15:14 (UTC) by hubcap)
Symlink /usr/bin/viber starting with lowercase letter. This causes firejail profile https://github.com/netblue30/firejail/blob/master/etc/Viber.profile to fail. Minor inconvenience, not sure if should be fixed.
nslxndr commented on 2019-12-07 13:52 (UTC)
I updated the package, sorry for the delay. @vyachkonovalov I applied the most of your changes, thanks for your work.
crabvk commented on 2019-12-03 10:06 (UTC) (edited on 2019-12-03 10:06 (UTC) by crabvk)
Oops, I made a mistake and removed PKGBUILD before making a
git diff
:DHere is my patch, without unnecessary eula.html and viber (shell script) files, proper LICENSE, also fixed
sed
replacement for viber.desktop.https://gist.github.com/vyachkonovalov/81a9ad265f437f9f40f7a3393aefc65b
iraklisg commented on 2019-12-02 18:13 (UTC)
@bbolgradov I manually added a new line at the end of your downloaded patch and I was able to successfully proceed with viber installation. Thank you
bbolgradov commented on 2019-12-02 18:02 (UTC)
Should be fixed now. Github gists seem to get their last newline stripped.
Hubro commented on 2019-12-02 17:40 (UTC)
@iraklisg Same for me. Just use bbolgradov's patch as a reference and update the version and hash manually, worked nicely for me :)
iraklisg commented on 2019-12-02 17:39 (UTC)
@bbolgradov @vyachkonovalov Thank you for your reply.
Interestingly, running
git apply viber-12.0.0.7-1.patch
gives me the following error:The same applies to vyachkonovalov's solution were I get:
Am I missing something? Can I provide you some extra information?
bbolgradov commented on 2019-12-02 15:00 (UTC) (edited on 2019-12-02 18:10 (UTC) by bbolgradov)
@vyachkonovalov, that's a strange patch you've got there.
Here's a working one that simply bumps the version.
crabvk commented on 2019-12-01 16:53 (UTC) (edited on 2019-12-01 16:55 (UTC) by crabvk)
Wow, this version is so outdated.
@iraklisg Current is 12.0.0.7, here is the patch
How to apply the patch:
iraklisg commented on 2019-11-30 17:15 (UTC)
Installing via
yay
:Choosing the package to be Clean builded did not do the trick for me:
al3xxx commented on 2019-11-06 15:58 (UTC) (edited on 2019-11-06 16:23 (UTC) by al3xxx)
Hello,
Please remove libcurl-compat from dependencies, Viber works OK without it, but presence libcurl-compat in the system breaks a lot of AUR packages with following configure errors:
crabvk commented on 2019-09-24 16:59 (UTC)
Hello. Please change source to https.
antonjo commented on 2019-09-03 14:26 (UTC)
I get the following CLI error:
zfkerr commented on 2019-07-11 19:52 (UTC) (edited on 2019-07-11 19:53 (UTC) by zfkerr)
Hi, @nslxndr ! Please, add the "openssl-1.0" package to the dependencies section. Viber don't want to work without it.
tomas.novoselic commented on 2019-06-06 17:51 (UTC)
Is there any reason for cdparanoia as dependency? I didn't see CD in years.
CyberShadow commented on 2019-06-05 07:46 (UTC)
Please give the downloaded file an unique filename, as per https://wiki.archlinux.org/index.php/PKGBUILD#source (see the "Warning" box). This will fix checksum errors due to old viber.deb copies.
pavelchavyr commented on 2019-05-04 13:00 (UTC)
I remove viber 'pacman -Rsn viber', install it again and now it works.
pavelchavyr commented on 2019-05-04 12:26 (UTC)
@vs220, openssl-1.0 is installed
vs220 commented on 2019-04-29 10:59 (UTC)
please add depending openssl-1.0
vs220 commented on 2019-04-29 10:56 (UTC)
@pavelchavyr install openssl-1.0 pacman -Suy openssl-1.0
jordanoff83 commented on 2019-03-26 22:34 (UTC)
Choosing the package to be Clean builded did the trick for me:
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...
==> 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 "$@"
duzun commented on 2019-02-24 13:33 (UTC)
There is a small issue: viber doesn't start minimizer with
viber StartMinimized
command. That's because /usr/bin/viber doesn't pass arguments to /opt/viber/Viber.Please, append "$@" to /usr/bin/viber like so:
!/bin/sh
LD_PRELOAD=libcurl.so.3 exec /opt/viber/Viber "$@"
It would also be great to have an option to start Viber in the system tray, not just minimized, maybe with wmctrl:
!/bin/bash
if [ "$1" = "StartMinimized" ]; then { sleep 1;
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 /opt/viber/Viber "$@"
Thanks!
setevoy commented on 2019-02-18 10:26 (UTC)
+1 for the solution with removing the ~/.cache/qtshadercache directory.
tarkal commented on 2019-02-12 09:26 (UTC)
+1 removing ~/.cache/qtshadercache solved issue
OSKiller commented on 2019-02-12 07:06 (UTC) (edited on 2019-02-12 07:07 (UTC) by OSKiller)
I've deleted ~/.cache/qtshadercache/*... After that I've got an error: '/opt/viber/Viber: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory'... So, I've copied libidn2.so in libidn2.so.4 in /usr/lib & /usr/lib32 directories... Now everything works perfectly...
There was no such issue on my home PC with Nvidia GeForce and proprietary drivers...
eduard commented on 2019-02-11 19:00 (UTC)
Solved by deleting ~/.cache/qtshadercache directory
Just-Punk commented on 2019-02-11 15:52 (UTC) (edited on 2019-02-11 15:59 (UTC) by Just-Punk)
SOLVED! mv ~/.cache ~/cache-old I've tried delete only Viber cache - doesnt help but mv all is OK from here
https://www.reddit.com/r/SolusProject/comments/9d4a5q/viber_white_screen_after_latest_update/ in link U may see QT cache causin' problem
OSKiller commented on 2019-02-11 12:44 (UTC)
It works, but the font is displayed in the color of the current background even when the text is highlighted...
It works perfect when started as sudo...
tarkal commented on 2019-02-11 07:58 (UTC)
Same issue, but I did downgrade to all Qt5 updates and still not working.
Just-Punk commented on 2019-02-11 01:00 (UTC)
The same issue.
cnotis commented on 2019-02-10 18:47 (UTC)
Same issue after the QT update as DmitrySkibitsky commented.
DmitrySkibitsky commented on 2019-02-09 14:05 (UTC)
After the update Qt stopped working. The application opens, but there is nothing in the application window, and the mouse cursor changes its state when you move around the application window area, even perhaps the event of clicks catches and performs an action, but nothing is displayed in the window itself.
Hubro commented on 2019-01-31 23:45 (UTC)
Installed this package on an up-to-date Arch system today, but I can't get Viber to launch. Both /usr/bin/viber and /opt/viber/Viber exit immediately with no errors and status code 0. I have tried prepending LD_LIBRARY_PATH=/opt/viber/lib but it changed nothing. I have openssl and pulseaudio installed.
Any ideas?
gorhat commented on 2018-10-21 16:07 (UTC) (edited on 2018-10-21 16:08 (UTC) by gorhat)
http://www.reddit.com/r/linux/comments/9m16iz/til_viber_is_eol_on_gnulinux/
https://forum.manjaro.org/t/no-more-new-viber-on-linux/58927
As it looks, Rakuten will not release any new version of Viber for Linux.
87dv commented on 2018-10-20 20:52 (UTC)
Please! new version is neaded!
stathisq commented on 2018-09-16 12:28 (UTC)
The package is flagged as out-of-date but I don't see any new version of Viber.
killvanrea commented on 2018-07-06 10:47 (UTC)
Hello, i have two problems using viber with KDE. First one I can not shutdow the machine. There is a notification poput that sayes, Viber preventing KDE from shutdown. Second I cannont uncheck the "Start viber on system startup" option from inside the Options menu. Can someone help me with those issues?
lazux commented on 2018-06-03 17:04 (UTC)
Install openssl-1.0 and pulseaudio and reboot.Worked for me.
Myrik93 commented on 2018-05-23 09:12 (UTC) (edited on 2018-05-23 09:13 (UTC) by Myrik93)
Error:
Cannot mix incompatible Qt library (version 0x50901) with this library (version 0x50a01)
Can be fixed with command:
LD_LIBRARY_PATH=/opt/viber/lib/ viber
dx4 commented on 2018-05-21 08:50 (UTC) (edited on 2018-05-21 08:51 (UTC) by dx4)
Viber starts fine but when I enter my phone it says "No Connection".
I don't know if this will help but I'm pasting the output when I run it from terminal:
Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...
Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...
Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory...
Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory...
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: Incompatible version of OpenSSL
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
QQuickItem: Cannot set activeFocusOnTab to false once item is the active focus item.
QQuickItem: Cannot set activeFocusOnTab to false once item is the active focus item.
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
jango commented on 2018-05-15 09:25 (UTC)
It works on latest Antergos
vladafirefly commented on 2018-03-09 11:51 (UTC)
Can't start Viber anymore:
$ viber /opt/viber/Viber: error while loading shared libraries: libpsl.so.5: cannot open shared object file: No such file or directory
Looks like libpsl was updated in the meantime.
$ ls -la libpsl* lrwxrwxrwx 1 root root 15 25. Feb 23:54 libpsl.so -> libpsl.so.6.2.0 lrwxrwxrwx 1 root root 15 25. Feb 23:54 libpsl.so.6 -> libpsl.so.6.2.0 -rwxr-xr-x 1 root root 64352 25. Feb 23:54 libpsl.so.6.2.0
Wladymyr commented on 2018-02-10 19:57 (UTC)
All work so good. Thanks.
Huan commented on 2017-12-31 14:50 (UTC)
$ viber Qt WebEngine ICU data not found at /opt/viber/resources. Trying parent directory... Qt WebEngine resources not found at /opt/viber/resources. Trying parent directory... qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave PulseAudioService: pa_context_connect() failed PulseAudioService: pa_context_connect() failed Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
Viber failed after qt5 and Viber update
cyberwoodman commented on 2017-12-12 10:18 (UTC)
strange, viber doesn't work just exits with 0 exit code. [tarasko@archlinux ~]$ LD_PRELOAD=libcurl.so.3 /opt/viber/Viber [tarasko@archlinux ~]$ echo $? 0
shillshocked commented on 2017-12-08 06:41 (UTC)
How can we use this without pulseaudio now? I use ALSA.
verni commented on 2017-11-03 18:55 (UTC) (edited on 2017-11-03 19:02 (UTC) by verni)
kamazee commented on 2017-11-03 07:55 (UTC)
beaux_monde commented on 2017-11-02 13:14 (UTC)
kamazee commented on 2017-11-01 07:34 (UTC)
romgvo commented on 2017-10-31 10:20 (UTC)
beaux_monde commented on 2017-10-31 08:22 (UTC)
mikes commented on 2017-10-30 10:52 (UTC) (edited on 2017-10-30 11:26 (UTC) by mikes)
ilovekorn commented on 2017-10-28 07:34 (UTC) (edited on 2017-10-28 07:34 (UTC) by ilovekorn)
thetotalchaos commented on 2017-10-25 19:51 (UTC)
hamsteri commented on 2017-10-20 15:01 (UTC) (edited on 2017-10-20 15:05 (UTC) by hamsteri)
firewalker commented on 2017-08-28 06:59 (UTC)
petsam commented on 2017-08-25 09:11 (UTC)
resetko commented on 2017-08-05 17:03 (UTC)
ZeroBit commented on 2017-06-04 15:37 (UTC)
nicman23 commented on 2017-06-04 13:10 (UTC)
ZeroBit commented on 2017-05-29 19:56 (UTC) (edited on 2017-05-31 07:42 (UTC) by ZeroBit)
Tedd88 commented on 2017-05-21 17:30 (UTC) (edited on 2017-05-21 17:31 (UTC) by Tedd88)
resetko commented on 2017-05-12 11:45 (UTC)
Mark1 commented on 2017-05-07 14:32 (UTC)
eduard commented on 2017-04-21 19:35 (UTC)
StratosL commented on 2017-04-06 16:08 (UTC)
eduard commented on 2017-04-03 07:02 (UTC)
eduard commented on 2017-04-03 06:56 (UTC)
Just-Punk commented on 2017-04-02 20:14 (UTC)
Krejzi commented on 2017-04-02 18:31 (UTC)
Just-Punk commented on 2017-04-01 10:17 (UTC)
Just-Punk commented on 2017-04-01 10:15 (UTC)
eduard commented on 2017-03-24 10:54 (UTC)
eduard commented on 2017-03-20 10:30 (UTC)
k0ste commented on 2017-03-18 07:13 (UTC)
07d7 commented on 2017-02-11 18:46 (UTC)
k0ste commented on 2017-02-07 15:10 (UTC)
07d7 commented on 2017-02-07 14:30 (UTC)
Guc24 commented on 2017-02-04 17:25 (UTC) (edited on 2017-02-04 17:32 (UTC) by Guc24)
aztec102 commented on 2017-01-25 11:05 (UTC)
aztec102 commented on 2017-01-25 11:00 (UTC)
flycal6 commented on 2017-01-24 04:59 (UTC)
spsf64 commented on 2017-01-21 20:14 (UTC)
smirky commented on 2017-01-20 10:48 (UTC)
notexistence commented on 2017-01-20 10:16 (UTC)
k0ste commented on 2016-12-29 07:39 (UTC)
jdevelop commented on 2016-12-29 01:17 (UTC)
sergey.orloff commented on 2016-12-13 07:31 (UTC)
sergey.orloff commented on 2016-12-02 15:29 (UTC)
idmistir commented on 2016-11-17 13:42 (UTC)
coxa commented on 2016-11-07 11:45 (UTC)
shtrih commented on 2016-10-18 06:12 (UTC) (edited on 2016-10-18 06:19 (UTC) by shtrih)
hawara commented on 2016-09-14 22:10 (UTC)
Forum_Liker commented on 2016-08-31 16:12 (UTC)
alex.theoto commented on 2016-08-31 14:15 (UTC)
Forum_Liker commented on 2016-08-28 17:53 (UTC)
commented on 2016-07-28 14:49 (UTC)
k0ste commented on 2016-07-01 12:21 (UTC)
Tido.com commented on 2016-06-09 08:15 (UTC)
Tido.com commented on 2016-06-08 16:08 (UTC)
Tido.com commented on 2016-06-08 15:44 (UTC)
commented on 2016-05-27 10:36 (UTC)
ZeroBit commented on 2016-05-25 19:32 (UTC)
nob_dy commented on 2016-05-24 10:02 (UTC)
itoffshore commented on 2016-05-19 18:43 (UTC)
commented on 2016-05-04 05:28 (UTC)
ahjolinna commented on 2016-05-01 15:00 (UTC)
shashurup commented on 2016-04-27 07:41 (UTC)
dripdrop commented on 2016-04-22 20:51 (UTC) (edited on 2016-04-22 23:32 (UTC) by dripdrop)
commented on 2016-04-21 10:14 (UTC)
k0ste commented on 2016-04-20 13:50 (UTC)
exec commented on 2016-04-20 13:40 (UTC) (edited on 2016-04-20 14:03 (UTC) by exec)
commented on 2016-04-20 05:58 (UTC)
ilusi0n commented on 2016-04-19 19:40 (UTC)
nslxndr commented on 2016-04-18 12:33 (UTC)
ahphaw5S commented on 2016-04-18 11:55 (UTC)
nslxndr commented on 2016-04-16 21:06 (UTC)
anarsoul commented on 2016-04-15 23:26 (UTC)
kosegr commented on 2016-04-15 09:29 (UTC) (edited on 2016-04-15 10:27 (UTC) by kosegr)
Tido.com commented on 2016-03-30 14:40 (UTC) (edited on 2016-03-30 14:43 (UTC) by Tido.com)
Maximka commented on 2016-03-28 19:03 (UTC)
Maximka commented on 2016-03-28 18:02 (UTC)
Genues commented on 2016-03-28 17:47 (UTC)
k0ste commented on 2016-03-28 13:25 (UTC)
iddqd21 commented on 2016-03-28 13:08 (UTC)
smirky commented on 2016-03-28 11:52 (UTC) (edited on 2016-03-28 11:53 (UTC) by smirky)
k0ste commented on 2016-03-28 01:59 (UTC)
mamantoha commented on 2016-03-27 18:43 (UTC)
emmerkar commented on 2016-03-23 16:42 (UTC) (edited on 2016-03-23 16:43 (UTC) by emmerkar)
nslxndr commented on 2016-03-17 22:18 (UTC)
jdevelop commented on 2016-03-17 18:51 (UTC)
TheChickenMan commented on 2015-12-10 14:10 (UTC)
TheChickenMan commented on 2015-12-10 14:08 (UTC)
isfeldt34 commented on 2015-11-30 11:24 (UTC)
smirky commented on 2015-09-09 17:57 (UTC)
realcnbs commented on 2015-08-26 12:58 (UTC)
luis6674 commented on 2015-08-14 18:24 (UTC)
dmgk commented on 2015-08-10 07:25 (UTC)
Shagabutdinov commented on 2015-07-31 15:03 (UTC)
topgun commented on 2015-06-24 18:12 (UTC)
tajidinabd commented on 2015-06-24 14:28 (UTC)
antijunak commented on 2015-06-22 16:26 (UTC)
daimonion commented on 2015-06-08 22:46 (UTC)
amenzhinsky commented on 2015-06-03 09:49 (UTC)
Genues commented on 2015-05-29 07:37 (UTC)
geomaster commented on 2015-05-29 06:59 (UTC)
geomaster commented on 2015-05-29 06:58 (UTC)
daimonion commented on 2015-05-25 13:05 (UTC)
baongoc124 commented on 2015-05-25 10:43 (UTC)
graczykr commented on 2015-05-15 14:33 (UTC)
alvinnex commented on 2015-04-29 20:30 (UTC)
logdog commented on 2015-04-16 08:31 (UTC)
kaptoxic commented on 2015-04-15 17:02 (UTC)
nagar commented on 2015-04-11 02:47 (UTC)
logdog commented on 2015-03-15 07:04 (UTC)
sorrat commented on 2015-03-10 20:30 (UTC)
artem.jackson commented on 2015-03-01 21:03 (UTC)
fheday commented on 2015-02-16 12:01 (UTC)
torstenchr commented on 2015-02-16 08:47 (UTC)
daimonion commented on 2015-02-09 20:41 (UTC)
skalkoto commented on 2015-02-09 19:38 (UTC)
ahjolinna commented on 2015-02-06 20:09 (UTC)
snoxu commented on 2015-02-06 01:08 (UTC)
stathisq commented on 2015-02-05 18:46 (UTC)
rezad commented on 2015-01-28 17:46 (UTC)
daimonion commented on 2015-01-07 12:48 (UTC)
ahjolinna commented on 2015-01-07 12:23 (UTC)
nomorsad commented on 2014-12-28 20:44 (UTC)
daimonion commented on 2014-12-21 13:30 (UTC)
neroburner commented on 2014-12-21 12:07 (UTC)
smirky commented on 2014-12-17 14:30 (UTC)
sarsanaee commented on 2014-12-16 19:18 (UTC)
cobalt commented on 2014-12-11 03:19 (UTC)
skalkoto commented on 2014-12-10 21:51 (UTC)
jifwin commented on 2014-12-07 14:10 (UTC)
daimonion commented on 2014-12-05 14:57 (UTC)
commented on 2014-12-04 08:18 (UTC)
kaptoxic commented on 2014-12-03 15:19 (UTC)
BBoy commented on 2014-12-03 15:10 (UTC)
kaptoxic commented on 2014-12-03 06:04 (UTC)
commented on 2014-11-25 19:00 (UTC)
artemklevtsov commented on 2014-11-24 19:09 (UTC)
commented on 2014-11-24 18:29 (UTC)
artemklevtsov commented on 2014-11-24 18:04 (UTC)
commented on 2014-11-24 17:29 (UTC)
artemklevtsov commented on 2014-11-23 14:51 (UTC)
commented on 2014-11-23 14:18 (UTC)
Jack_CM commented on 2014-11-16 22:49 (UTC)
artemklevtsov commented on 2014-11-14 16:40 (UTC)
amenzhinsky commented on 2014-11-13 14:07 (UTC)
cobalt commented on 2014-11-05 21:09 (UTC)
183.amir commented on 2014-10-26 06:09 (UTC)
Glinx commented on 2014-10-21 05:20 (UTC)
lybin commented on 2014-10-20 13:51 (UTC)
Glinx commented on 2014-10-20 08:05 (UTC)
artemklevtsov commented on 2014-10-14 10:53 (UTC)
stathisq commented on 2014-10-14 10:38 (UTC)
stathisq commented on 2014-10-13 13:09 (UTC)
lybin commented on 2014-10-13 11:41 (UTC)
stathisq commented on 2014-10-13 11:36 (UTC)
artemklevtsov commented on 2014-10-03 08:31 (UTC)
LeetShiva commented on 2014-09-28 17:22 (UTC)
Areimas commented on 2014-09-27 08:16 (UTC)
lybin commented on 2014-09-26 04:38 (UTC)
rafaelff commented on 2014-09-26 04:18 (UTC)
parovozik commented on 2014-09-14 23:29 (UTC)
daimonion commented on 2014-09-08 19:08 (UTC)
daimonion commented on 2014-09-08 15:19 (UTC)
lockheed commented on 2014-08-27 08:05 (UTC)
Nognir commented on 2014-08-24 23:25 (UTC)
dumphblooz commented on 2014-08-22 12:57 (UTC)
EasySly commented on 2014-08-22 08:30 (UTC)
EasySly commented on 2014-08-22 08:25 (UTC)
EasySly commented on 2014-08-19 10:47 (UTC)
ctsdownloads commented on 2014-08-18 05:36 (UTC)
dumphblooz commented on 2014-08-17 11:48 (UTC)
Nognir commented on 2014-08-16 16:44 (UTC)
stathisq commented on 2014-08-15 09:30 (UTC)
alarm commented on 2014-08-15 05:24 (UTC)
stathisq commented on 2014-08-14 14:29 (UTC)
alarm commented on 2014-08-14 09:21 (UTC)
alarm commented on 2014-08-14 08:08 (UTC)
tostaky80 commented on 2014-08-10 09:22 (UTC)
sorrat commented on 2014-08-07 21:21 (UTC)
smakki commented on 2014-08-07 12:59 (UTC)
Le_J commented on 2014-08-05 18:12 (UTC)
whitesun commented on 2014-06-12 12:57 (UTC)
wgnm commented on 2014-06-12 09:29 (UTC)
arch-nemesis commented on 2014-05-27 19:52 (UTC)
ilusi0n commented on 2014-05-22 21:56 (UTC)
weox.os commented on 2014-02-17 22:29 (UTC)
ozgursarier commented on 2014-01-13 15:09 (UTC)
Bersam commented on 2014-01-13 09:30 (UTC)
ozgursarier commented on 2014-01-12 08:46 (UTC)
kraxor commented on 2014-01-11 19:19 (UTC)
stecco commented on 2013-12-14 00:47 (UTC)
ozgursarier commented on 2013-12-14 00:37 (UTC)
stecco commented on 2013-12-14 00:07 (UTC)
ozgursarier commented on 2013-12-13 23:45 (UTC)
kostas213 commented on 2013-12-13 17:01 (UTC)
ozgursarier commented on 2013-11-30 12:43 (UTC)
lamiska commented on 2013-11-21 21:32 (UTC)
commented on 2013-11-21 08:52 (UTC)
MohammadR commented on 2013-09-02 08:46 (UTC)
knedlyk commented on 2013-09-02 08:42 (UTC)
MohammadR commented on 2013-08-26 13:56 (UTC)
Thaodan commented on 2013-08-26 07:17 (UTC)