How fixed this issue???
viber error status_custom_error
How fixed this issue???
viber error status_custom_error
What package makes this error?
Where do you get it?
How do you install it?
How do you start it?
from official site
start witk click on viber icon…
I do not find an package named viber.
Please answer not so short, post the Url of the rpm, open the Programm in a terminal and post the Errors from there.
viber provides the rpm (or deb)
I’ve noticed that the secondary viber devices need to ping your primary phone (as viber uses your phone number for authentication and login)
this sounds like an internal viber warning, check and see if your phone is on and connected to the internet and retry running viber
I think there is a limited time window viber can run from a pc/tablet between phone logons
https://www.viber.com/en/products/linux and choose a RPM…
I’ve been wanting to try viber on linux
I’ll install it and see if I have any issues
I have installed it on an android tablet that has no sim card or number and it needs access to your smart phone to be activated
more info latter
i have installed,but can’t activate desktop version…cannot communication beetwen computer and phone
how did you install it when viber wants an old library libcrypto.so.10 the current provided by opensuse is libcrypto.so.37
that’s the reason I didn’t install it
you can try and install libcrypto37 and then make a symlink
zypper in libcrypto37
I’ll try a symlink and report back
I got it working without installing the extra libcrypto37
just link /lib64/libcrypto.so.1.0.0 to /usr/lib64/libcrypto.so.10
ln -s /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.10
then install viber ignoring the missing dependency (I’m not sure why it showed up maybe because it was a symbolic link)
zypper in viber.rpm
start viber from the menu launcher or the terminal by doing
link the desktop app with your phone with the provided QR code and this is what you get
Nope, that is not the reason why rpm still complains about a missing dependency (and rightly does so). Even if you had copied libcrypto.so.1.0.0 to libcrypto.so.10 rpm would complain.
When installing a package, rpm will look in the system’s RPM database if all requirements are satisfied and your manual change will not show up there.
Consider your symlink a “software” which has been installed manually (like some program you installed via “./configure && make && make install”) which will also not show up in your package manager.
Looks like this RPM was built for RH/Fedora
“Compatibility version of the OpenSSL library”
If the “normal” libcrypto.so.1.0.0 is “compatible enough” for this program, the symlink will work, otherwise some strange behavior would be expected.
But as in most cases this “strange behavior” would be the program refusing to start with an error message “missing/wrong symbol $WHATEVER in $LIBRARY” it seems you were lucky this time.
I just had a quick look at the respective packages from Fedora to see what they really are.
So in a nutshell, these are the libraries for openSSL-1.0.x which have been renamed as Fedora already uses openSSL-1.1 and there are some programs not compatible with that newer version. That’s why your symlink worked (and why linking to libcrypto37 most likely will not work).
Just a little “nit-picking” here, if you are working around the problem by symlinking, please do not do it like this
ln -sf /lib64/libcrypto.so.1.0.0 /lib64/libcrypto.so.10
as you are creating a link in a directory which should only be used by files from RPM packages.
The moment openSUSE will implement something similar to what Fedora did this might be calling for trouble. If some day in the future there were a package containing “/lib64/libcrypto.so.10” installing via RPM (or zypper) might fail due to a symlink RPM does not know anything about.
As with all other software not being installed via package manager always use “/usr/local” for such files, so my first try would be
ln -sf /lib64/libcrypto.so.1.0.0 /usr/local/lib64/libcrypto.so.10 ldconfig
and if that does not work try
ln -sf /lib64/libcrypto.so.1.0.0 /usr/local/lib/libcrypto.so.10 ldconfig
paulparker@linux-6h2a:~> locate libcrypto.so.10 paulparker@linux-6h2a:~> sudo ln -sf /lib64/libcrypto.so.1.0.0 /usr/local/lib64/libcrypto.so.10 paulparker@linux-6h2a:~> sudo ldconfig paulparker@linux-6h2a:~>
paulparker@linux-6h2a:~> sudo ln -sf /lib64/libcrypto.so.1.0.0 /usr/local/lib/libcrypto.so.10 paulparker@linux-6h2a:~> sudo ldconfig paulparker@linux-6h2a:~>
paulparker@linux-6h2a:~> locate libcrypto.so /lib/libcrypto.so.1.0.0 /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.41 /usr/lib64/libcrypto.so.41.0.1 paulparker@linux-6h2a:~>
paulparker@linux-6h2a:~> sudo find / -name '.snapshots' -prune -o -print | grep -i 'libcrypto.so'/usr/local/lib/libcrypto.so.10 /usr/local/lib/libcrypto.so.1.0.0 **/usr/local/lib64/libcrypto.so.10** /usr/local/lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.41 /usr/lib64/libcrypto.so.41.0.1 find: ‘/run/user/1503/gvfs’: Permission denied /lib/libcrypto.so.1.0.0 /lib64/libcrypto.so.1.0.0 paulparker@linux-6h2a:~>
paulparker@linux-6h2a:~> sudo zypper in Downloads/viber.rpm Loading repository data... Reading installed packages... Resolving package dependencies... **Problem: nothing provides libcrypto.so.10()(64bit) needed by viber-220.127.116.111-2.x86_64** Solution 1: do not install viber-18.104.22.1681-2.x86_64 Solution 2: break viber-22.214.171.1241-2.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): c paulparker@linux-6h2a:~>
Puzzled, any ideas ?
did you link /lib64/libcrypto.so.1.0.0 to /usr/local/lib64/libcrypto.so.10?
ln -s /lib64/libcrypto.so.1.0.0 /usr/local/lib64/libcrypto.so.10 ldconfig
if so you can ignore the warning I didn’t link in /usr/local/lib64 but in /usr/lib64 and had no issues