http://www.viber.com/products/linux/ Viber for Android and desktop, native Linux client available. I don't know if it is possible to add .deb packages, but I would love to see this in portage! (It works pretty well with WINE, but of course the native client would be better).
just download it and decompress data.tar.gz in root. Works very well in Gentoo. waiting ebuild....
I will wait for an ebuild too. I really don't want to spam my system with manually installed packages. The wine version works though.
Created attachment 369392 [details] first alpha viber ebuild this is my very first ebuild. I don't know if it works for you
(In reply to b1254633 from comment #3) > Created attachment 369392 [details] > first alpha viber ebuild > > this is my very first ebuild. I don't know if it works for you please start all ebuilds from /usr/portage/skel.ebuild, then remove as necessary.
Created attachment 369396 [details] second alpha viber ebuild some unuseful corrections
Created attachment 369450 [details] viber ebuild updated to skel.ebuild scheme
Hm, weird. ebuild compiles just fine, but if I call the command, from KDE menu or via Konsole, simply nothing happens. No output. Does it work for you?
very weird.... For me it works fine. I can start Viber from kde menu and from Konsole without issues. try this command sh /usr/share/viber/Viber.sh
It works as root, not as user...
thus, it should be a permission issue Can you post output of this? ls -l /usr/share/viber/
Sure: ls -l /usr/share/viber/ insgesamt 102528 drwxr-xr-x 2 root root 4096 3. Feb 18:17 icons drwxr-xr-x 2 root root 4096 3. Feb 18:17 imageformats -rw-r--r-- 1 root root 5120 3. Feb 20:13 launcher.db -rw-r--r-- 1 root root 1029368 31. Okt 09:26 libbfd-2.22-system.so -rw-r--r-- 1 root root 18282384 31. Okt 09:26 libicudata.so.48 -rw-r--r-- 1 root root 1866528 31. Okt 09:26 libicui18n.so.48 -rw-r--r-- 1 root root 1465096 31. Okt 09:26 libicuuc.so.48 -rwxr-xr-x 1 root root 4334448 31. Okt 09:26 libQt5Core.so.5 -rwxr-xr-x 1 root root 489624 31. Okt 09:26 libQt5DBus.so.5 -rwxr-xr-x 1 root root 4190616 31. Okt 09:26 libQt5Gui.so.5 -rwxr-xr-x 1 root root 1390328 31. Okt 09:26 libQt5Network.so.5 -rwxr-xr-x 1 root root 432752 31. Okt 09:26 libQt5OpenGL.so.5 -rwxr-xr-x 1 root root 342400 31. Okt 09:26 libQt5PrintSupport.so.5 -rwxr-xr-x 1 root root 2359536 31. Okt 09:26 libQt5Qml.so.5 -rwxr-xr-x 1 root root 3553744 31. Okt 09:26 libQt5Quick.so.5 -rwxr-xr-x 1 root root 258240 31. Okt 09:26 libQt5Sql.so.5 -rwxr-xr-x 1 root root 333800 31. Okt 09:26 libQt5Svg.so.5 -rwxr-xr-x 1 root root 4483560 31. Okt 09:26 libQt5V8.so.5 -rwxr-xr-x 1 root root 32935424 31. Okt 09:26 libQt5WebKit.so.5 -rwxr-xr-x 1 root root 266304 31. Okt 09:26 libQt5WebKitWidgets.so.5 -rwxr-xr-x 1 root root 6418808 31. Okt 09:26 libQt5Widgets.so.5 -rwxr-xr-x 1 root root 19046376 3. Feb 18:17 libViber.so -rw-r--r-- 1 root root 14480 31. Okt 09:26 libXss.so.1 drwxr-xr-x 2 root root 4096 3. Feb 18:17 platforms drwxr-xr-x 5 root root 4096 3. Feb 18:17 Sound drwxr-xr-x 2 root root 4096 3. Feb 18:17 sqldrivers -rwxr-xr-x 1 root root 1386368 3. Feb 18:17 Viber -rw-r--r-- 1 root root 25391 31. Okt 09:26 viber.png -rwxr-xr-x 1 root root 228 31. Okt 09:26 Viber.sh
from root: chown <yourusername>:<yourusername> /usr/share/viber/launcher.db from user: sh /usr/share/viber/Viber.sh tell me if this fix it
No, doesn't work, even ls -la shows my user:group as owner of the file. Still nothing happens.
Created attachment 369466 [details] viber-1.0.ebuild fix permissions
try emerge -C viber rm -rf /usr/share/viber emerge viber using new ebuild
Comment on attachment 369466 [details] viber-1.0.ebuild ># Copyright 1999-2014 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header: $ > >EAPI="5" > >DESCRIPTION="Free calls, text and picture sharing with anyone, anywhere!" >HOMEPAGE="http://www.viber.com" >SRC_URI="http://download.cdn.viber.com/cdn/desktop/Linux/viber.deb" > >SLOT="0" >KEYWORDS="~amd64" >IUSE="" > >src_unpack() { > unpack ${A} > mkdir ${P} >} > >src_prepare(){ > tar -xf "${WORKDIR}/data.tar.gz" -C ${S} > chmod 777 ${S}/usr/share/viber/ >} > >src_install(){ > mv ${S}/* ${D} >}
Awesome! It works now :-D Thanks mate!! Let'S hope your ebuild makes it into portage.
chmod 777 evil very bad almost certainly insecure pretty sure there are builtin methods for extracting .deb see qgrep .deb
I know 777 is very bad. the problem is that viber needs to write launcher.db in /usr/share/viber/. It shoud be better if viber creates launcher.db in user home. In this way, chmod 777 is unnecessary.
Then patch it. We don't want another bug 125902.
My ebuild is public. If you are able patch it please.
Thank you for your bug and contribution. Some further suggestions for improvements for whomever picks this up: 1) Except in SRC_URI, you can use ${PN} instead of viber; this allows for easier package changes. 2) To catch failures, add || die "..." (fill in a reason to die) at the end of external commands like mkdir, tar, chmod, mv. 3) ${S} and ${D} are unquoted, use "${S}" and "${D}" to allow spaces instead. 4) `chmod 777 ${S}/usr/share/viber/` is indeed wrong, see the install functions in the dev manual as there are functions like fperms; but as pointed out, this might be something that upstream will want to fix such that the user can use a file in ~ instead. Or maybe upstream does this already; so, check first how the package works in this regard. On a side note, permission changes are to be done in the src_install phase function. 5) `mv ${S}/* ${D}` is avoided, there are ins* and do* functions in the same install functions section of the devmanual. For reference: http://devmanual.gentoo.org/function-reference/install-functions
Created attachment 369710 [details] viber-1.0.ebuild same changes
Thank you for your efforts!
Created attachment 369864 [details] viber-1.0.ebuild added pkg_postrm
Created attachment 369934 [details] viber-9999.ebuild
The 9999 ebuild will not start. Seems it doesn't install in /usr/share/viber anymore?
can you post output?
There's no output. There is simply no directory /usr/share/viber anymore.
it's weird emerge -C viber?
Very weird. If I unmerge version 1.0 and remerge the 9999-ebuild it works again :) Will this automatically fetch newer versions if called again?
It emerge the newer version only if you remove viber.deb from distfiles
Btw. /usr/share/viber is the wrong place for shared libraries und executable files. Better would be /usr/lib/viber. Or if that conflicts with existing libs, the right place would be /opt/viber as Google Earth does.
(In reply to Sven Müller from comment #34) > Btw. /usr/share/viber is the wrong place for shared libraries und executable > files. > > Better would be /usr/lib/viber. Or if that conflicts with existing libs, the > right place would be /opt/viber as Google Earth does. precompiled binaries _always_ go to /opt... at least in gentoo
Note, new version of Viber available for download on their site. It's named viber.deb (no versioning info per previous release, but has the following characteristics: Size: 57046082 MD5: 4dec3ade37a3738c6f084858a4554861 It's a big improvement as far as I can tell: - extracts into /opt/viber - no 0777 perms needed any more (modify ebuild to make the executable /opt/viber/Viber 0755) - no launcher.db requiring write perms - faster - shows delivered/seen/last online times The only thing they haven't fixed is if you run it from an nfs mounted homedir it'll cry about re-registration every time you switch computers. I fixed by symlinking ~/.ViberPC into /var/tmp/viber on both machines and registering twice. I raised it with them as a bug also, no response yet.
How do I modify the ebuild to work with this newer version?
Any idea when viber might arrive in portage? -- Regards, Mick
I also wish to have viber in portage. It could be a great replacement for skype. http://gpo.zugaina.org/net-im/viber/Dep
Guys, does anyone here has the newer versions of viber running successfully? I can install it from any overlay, but when I go through the registration process it tells me that I need an internet connection. I tried like 4 to 5 different ebuilds (all I could find) with no success. Any ideas?
viber need a =media-libs/gstreamer:0.10 >>$ /opt/viber/Viber >>/opt/viber/Viber: error while loading shared libraries: libgstreamer-0.10.so.0: cannot open shared object file: No such file or directory
Can it be added to tree now, or some additional feedback is required?
Created attachment 461658 [details] viber-bin-6.5.5.1481.ebuild
> Can it be added to tree now, or some additional feedback is required? There is no good way to support it in portage, at least until Viber will continue to provide package without version info in its name. Package is too big to be added to distfiles (from my point of view), so we can use distfiles to redistribute package. At the same time, we can't use upstream provided package since every its update will break ebuild.
Created attachment 511480 [details] viber-bin-7.0.0.1035.ebuild
Is it actually needs pulseaudio? Any chance it'll work with media-sound/apulse instead?
Created attachment 523570 [details] viber-bin-7.0.0.1035.ebuild viber-bin-7.0.0.1035.ebuild supports apulse. You could try it.
(In reply to Vladimir Pavljuchenkov (SpiderX) from comment #47) > viber-bin-7.0.0.1035.ebuild supports apulse. > You could try it. Thanks. It turns out viber require libpulse-mainloop-glib.so.0. It emulation was added to apulse just few weeks ago and not included in any tagged release yet. With apulse installed from current master viber was able to start, at least (I didn't had a chance to actually login and test is sound/microphone works with apulse). BTW, you probably need to mark required one of apulse/pulseaudio USE flags.
Created attachment 524072 [details] viber-bin-7.0.0.1035.ebuild It's great that you were able to use it. > BTW, you probably need to mark required one of apulse/pulseaudio USE flags. Added.
net-im/viber now requires: dev-libs/openssl-compat:1.0.0
This could be added to the list of packages failing with newer versions of openssl: https://bugs.gentoo.org/592438 https://bugs.gentoo.org/679194
Created attachment 595920 [details] ebuild I don't see that viber has dependencies on openssl
Conditions: You use dev-libs/openssl-1.1.1 or above. Symptoms: You cannot use Viber desktop to send or receive files. Solution, as I said, install: dev-libs/openssl-compat:1.0.0 So, it depends on your use of Viber. dev-libs/openssl-compat:1.0.0 is not a hard requirement, but if you care about receiving and sending files, then you need it. I spent the whole afternoon yesterday debugging Viber, figuring what was broken, why and how to fix it. The solution, it turns out, is very simple. I posted the previous comment to save you all a lot of time, if you start to wonder why you cannot send file attachments.
Created attachment 596622 [details] viber-10.3.0.37.ebuild > I posted the previous comment to save you all a lot of time, if you start to wonder why you cannot send file attachments And you succeed in time saving, thanks. I see what you meant. Modified ebuild attached.
How to check what is the latest version available for linux? The download page does not make it clear: https://www.viber.com/download/ only links to viber.rpm and viber.deb, without any version number mentioned.
Created attachment 613290 [details] updated viber ebuild, with proper permissions and accounting for moved files (In reply to augustin from comment #55) > How to check what is the latest version available for linux? To install it, then go to Help->About - that's the only way I know of unfortunately :). Anyway, I am glad to report that as of now (or some time ago, impossible to be sure because of a really sloppy versioning by upstream - as was pointed out many times above, and which is the main reason Viber is not in the official tree) Viber is working just fine with openssl:1.1. Installing/denending upon openssl-compat:1.0.0 is no longer necessary. Some extra info: The latest version (as of this date) is 12.0.0 one of the files that need fperms done to it has been moved into libexec/ from top dir. The updated ebuild for this latest version is attached..
Thanks a lot George for the answer and the update.
https://www.viber.com/blog/2020-02-10/remember-everything-thats-important-with-my-notes-see-whats-new-on-viber/ Is the feature above, "My Notes", supposed to be available on the Desktop 12.0.0 version? I just upgraded, thanks to George's newest ebuild, but I don't see it, so that I cannot share notes between the mobile and the desktop version.
(In reply to augustin from comment #58) > Is the feature above, "My Notes", supposed to be available on the Desktop > 12.0.0 version? Hm, not so sure. The active mobile version is 12.3.7, and I don't remember seeing My Notes until very recently. In fact I think I noticed them appearing like a week or two ago only, haven't even investigated what's that - was assuming its another spam channel that's popped up. So, thanks for a pointer in fact :). But back to this issue, I rather suspect that not in 12.0, not yet. I don't think I can even see it on Windows version yet either, but I haven't updated it in a few weeks.. Frankly, I think its really nice/lucky that we are on the same major version in Linux as on mobile - quite contrary to most other messaging apps (like Skype :) ) lagging behind severely or even being actively blocked by regular protocol changes.. I guess just try to reinstall viber on desktop once in a while (every few weeks or so), but don;t forget first to delete downloaded file. Unfortunately, due to totally absent versioning info by upstream, the only way to spot an update is to force redownload and see if portage complains about checksum failure.. If it does fail - bingo! Rename the downloaded file back to its proper name (portage adds .chechsum_failure_blah-blah part to it) and run ebuild viber-x.y.z.ebuild digest from its portage dir and then emerge away. You should have new version installed after that. If the build fails, likely due to some files having been moved around, then you are likely looking at major version change, then some ebuild adapting would be necessary, but usually simple..
Thanks a lot George for all the information. I'll post further updates as and when I find something new.
viber-13.3.1 for desktop linux is out. In includes the feature that I mentioned in #58.
Created attachment 651060 [details] viber-13.3.1.22.ebuild
(In reply to Vladimir Pavljuchenkov (SpiderX) from comment #62) > Created attachment 651060 [details] > viber-13.3.1.22.ebuild Your ebuild works fine here, but I have one issue. It core dumps when it tries to download a video. The same behaviour is with the viber AppImage, so it must be something wrong with the upstream binary.
You are probably missing one or more gstreamer packages. Upstream .deb depends on a bunch of them, namely: Depends: libpulse0, libasound2, libnss3, libgstreamer-plugins-base1.0-0, libgstreamer1.0-0, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gstreamer1.0-plugins-ugly, gstreamer1.0-pulseaudio, gstreamer1.0-libav The Gentoo equivalent would be something along the lines of: RDEPEND="media-libs/alsa-lib media-sound/pulseaudio dev-libs/nss media-libs/gstreamer:1.0 media-libs/gst-plugins-base:1.0 media-libs/gst-plugins-good:1.0 media-libs/gst-plugins-ugly:1.0 media-plugins/gst-plugins-pulse:1.0 media-plugins/gst-plugins-libav:1.0"
(In reply to Konstantinos Smanis from comment #64) > You are probably missing one or more gstreamer packages. Upstream .deb > depends on a bunch of them, namely: > > Depends: libpulse0, libasound2, libnss3, libgstreamer-plugins-base1.0-0, > libgstreamer1.0-0, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, > gstreamer1.0-plugins-ugly, gstreamer1.0-pulseaudio, gstreamer1.0-libav > > The Gentoo equivalent would be something along the lines of: > > RDEPEND="media-libs/alsa-lib > media-sound/pulseaudio > dev-libs/nss > media-libs/gstreamer:1.0 > media-libs/gst-plugins-base:1.0 > media-libs/gst-plugins-good:1.0 > media-libs/gst-plugins-ugly:1.0 > media-plugins/gst-plugins-pulse:1.0 > media-plugins/gst-plugins-libav:1.0" I have all these packages installed, I just checked. What else can I check?
Try to launch it from shell, maybe it will provide some meaningful output on crush.
Just to confirm that the last ebuild works fine so far (haven't tested all functionality yet though). Used mostly as is, with a minor modification of adding media-plugins/gst-plugins-libav[${MULTILIB_USEDEP}] to RDEPEND and adjusting conditional on pulsaidio (ibid) to: pulseaudio? ( media-sound/pulseaudio[${MULTILIB_USEDEP}] media-plugins/gst-plugins-pulse[${MULTILIB_USEDEP}] )
https://gpo.zugaina.org/Search?search=viber shows several overlays with viber. Guru could be a good overlay to collaborate on this one https://wiki.gentoo.org/wiki/Project:GURU
Created attachment 746598 [details] viber-16.1.0.37.ebuild
Created attachment 814015 [details] viber-18.2.0.2.ebuild
(In reply to Vdrag from comment #73) > Created attachment 814015 [details] > viber-18.2.0.2.ebuild $ Viber Viber: error while loading shared libraries: libgstphotography-1.0.so.0: cannot open shared object file: No such file or directory
(In reply to Uladzimir Bely from comment #74) > (In reply to Vdrag from comment #73) > > Created attachment 814015 [details] > > viber-18.2.0.2.ebuild > > $ Viber > Viber: error while loading shared libraries: libgstphotography-1.0.so.0: > cannot open shared object file: No such file or directory It seems, new ebuild should depend on `media-libs/gst-plugins-bad` that provides this library
Version 18.2.0.2 affected by Qt bug https://bugreports.qt.io/browse/QTBUG-101201 and fail to start in environment with multiple keyboard layouts: xkbcommon: ERROR: Couldn't process include statement for 'us(winkeys)' xkbcommon: ERROR: Abandoning symbols file "(unnamed)" xkbcommon: ERROR: Failed to compile xkb_symbols xkbcommon: ERROR: Failed to compile keymap [8530:8560:0928/190953.815645:FATAL:xkb_keyboard_layout_engine.cc(640)] Keymap file failed to load: us-winkeys For me fixed by simplest workaround ever: start Viber when non-us layout enabled. After startup it works fine.
We also need `app-arch/snappy`: ``` $ Viber Viber: error while loading shared libraries: libsnappy.so.1: cannot open shared object file: No such file or directory ```
Also, dependencies from Viber's .deb: ``` Depends: libpulse0, libasound2, libnss3, libgstreamer-plugins-base1.0-0, libgstreamer1.0-0, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gstreamer1.0-plugins-ugly, gstreamer1.0-pulseaudio, gstreamer1.0-libav, libxcb-xinput0, libstdc++6 ``` Note: they propose gstreamer1.0-plugins-{base,good,ugly}, we propose gstreamer1.0-plugins-{base,bad}. Uhm?
Oh, I'm sorry about a span... But I've found `qa-vdb` tool... So, let's sum up again: 1. Here is its output for this bug's .ebuild: ``` $ qa-vdb net-im/viber-18.2.0.2 VDB: detected possibly incorrect RDEPEND (net-im/viber-18.2.0.2) > app-arch/snappy > app-arch/zstd > app-crypt/mit-krb5 > dev-libs/libxml2 > dev-libs/libxslt dev-libs/openssl-compat < > media-libs/gst-plugins-bad:1.0 > media-libs/harfbuzz > media-libs/lcms:2 > media-libs/libglvnd > media-libs/libwebp > media-libs/opus > media-libs/tiff > sys-apps/systemd-utils > sys-libs/mtdev x11-libs/libXcomposite < x11-libs/libXcursor < x11-libs/libXdamage < > x11-libs/libxkbcommon > x11-libs/libxkbfile x11-libs/libXi < x11-libs/libXrender < > x11-libs/libxshmfence ``` 2. The dependencies from Viber's .deb: ``` Depends: libpulse0, libasound2, libnss3, libgstreamer-plugins-base1.0-0, libgstreamer1.0-0, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, gstreamer1.0-plugins-ugly, gstreamer1.0-pulseaudio, gstreamer1.0-libav, libxcb-xinput0, libstdc++6 ``` According to this, we may need `media-plugins/gst-plugins-libav`. Also, they request `gstreamer1.0-plugins-{base,good,ugly}`, we request `media-libs/gst-plugins-base` only (`-bad` was proposed above). 3. We request ``` pulseaudio? ( media-sound/pulseaudio[${MULTILIB_USEDEP}] ) ``` but according to PipeWire sound server migration [1], could it be replaced by: ``` pulseaudio? ( media-libs/libpulse[${MULTILIB_USEDEP}] ) ``` ? I'd appreciate a feedback very much. Thanks! --- [1] https://www.gentoo.org/support/news-items/2022-07-29-pipewire-sound-server.html
Created attachment 849169 [details] viber-18.2.0.2-r1.ebuild Found also `x11-libs/tslib` and `media-libs/libmng` dependencies. Created a patch based on my previous comments. Also, add more `fperms`, move binaries fixing to `src_prepare`, move EAPI to 8, use HTTPS.
Created attachment 849285 [details] viber-18.2.0.2-r1.ebuild Updates: 1. Point `amd64` architecture in `SRC_URI`. 2. Replace `QA_PREBUILT` by more concrete `QA_PRESTRIPPED` file list. 3. Move `pax-mark` and `fix-gnustack` back to `src-install`. 4. Replace back `media-libs/libpulse` by `media-sound/pulseaudio`. 5. Make `fperms +x` for really executable files only.
(In reply to Alexander Kurakin from comment #81) > Created attachment 849285 [details] > viber-18.2.0.2-r1.ebuild > > Updates: > > 1. Point `amd64` architecture in `SRC_URI`. > 2. Replace `QA_PREBUILT` by more concrete `QA_PRESTRIPPED` file list. > 3. Move `pax-mark` and `fix-gnustack` back to `src-install`. > 4. Replace back `media-libs/libpulse` by `media-sound/pulseaudio`. > 5. Make `fperms +x` for really executable files only. Tried it. In my systemd system, I had blocks. The line sys-apps/systemd-utils[${MULTILIB_USEDEP}] must probably be replaced by || ( sys-apps/systemd[${MULTILIB_USEDEP}] sys-apps/systemd-utils[${MULTILIB_USEDEP}] )
(In reply to Vasilis Lourdas from comment #82) > (In reply to Alexander Kurakin from comment #81) > Tried it. In my systemd system, I had blocks. The line > > sys-apps/systemd-utils[${MULTILIB_USEDEP}] > > must probably be replaced by > > || ( sys-apps/systemd[${MULTILIB_USEDEP}] > sys-apps/systemd-utils[${MULTILIB_USEDEP}] ) Vasilis, thank you very much! Will apply. Seems like we need `udev` for `sys-apps/systemd-utils`. BTW, could anybody help about required flags for all dependencies above? And one more question. Is Viber's `.deb` for amd64 only? Or we could use it for x86, too?
Created attachment 849868 [details] viber-18.2.0.2-r1.ebuild Well, a new version, then. Updates: 1. Fix LICENSE. 2. Move `sys-apps/fix-gnustack` from `IDEPEND` to `BDEPEND`. 3. `sys-apps/systemd-utils[${MULTILIB_USEDEP}]` was be replaced by ``` || ( sys-apps/systemd[${MULTILIB_USEDEP}] sys-apps/systemd-utils[udev,${MULTILIB_USEDEP}] ) ```
Today Viber failed to start (not die, but show nothing) with messages below. I have updated system yesterday (without --depclean). I see minor Gstereamer bump: 1.20.3 --> 1.20.4, kernel, and more. If I cleanup ~/.ViberPC it show login screen and otputs message before "QHighDpiScaling", but after scanning QR code I got "new auth detected" in smartphone, rotating progressbar and other part of the messgae in console. Appimage fail to start with same message. Not sure what direction to search. (Viber:20815): GStreamer-CRITICAL **: 11:42:05.987: gst_element_unlink: assertion 'GST_IS_ELEMENT (dest)' failed (Viber:20815): GStreamer-CRITICAL **: 11:42:05.987: gst_bin_remove: assertion 'GST_IS_ELEMENT (element)' failed (Viber:20815): GStreamer-CRITICAL **: 11:42:05.987: gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed 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 QHighDpiScaling::setFactor: Should only be called when no windows exist. (Viber:20815): GStreamer-CRITICAL **: 11:42:06.682: gst_bin_add_many: assertion 'GST_IS_ELEMENT (element_1)' failed (Viber:20815): GStreamer-CRITICAL **: 11:42:06.682: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (Viber:20815): GStreamer-CRITICAL **: 11:42:06.682: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (Viber:20815): GStreamer-CRITICAL **: 11:42:06.682: gst_pad_add_probe: assertion 'GST_IS_PAD (pad)' failed
Viber starts normally after installing media-libs/gst-plugins-good Audio-video calls also works fine.
Created attachment 862885 [details] viber-18.2.0.2-r1.ebuild (In reply to Vadim Efimov from comment #86) > Viber starts normally after installing media-libs/gst-plugins-good > Audio-video calls also works fine. Yes, thanks! Checked. Added the dependency.
Created attachment 874607 [details] Viber 21.0.0.1 Ebuild Updated to the 21.0.0.1 upstream version. Also according to * iwdevtools, * post-install QA warnings, * .deb package's Dependencies I: Fixed subslots for: * app-arch/brotli, * app-arch/snappy, * app-arch/zstd, * media-libs/harfbuzz, * media-libs/libmng, * media-libs/libwebp. Added: * dev-libs/libevent:=, * media-plugins/gst-plugins-libav:1.0, * media-libs/mesa, * x11-libs/gdk-pixbuf:2, * x11-libs/gtk+:3, * x11-libs/pango, * x11-libs/xcb-util-cursor, * pulseaudio? ( media-plugins/gst-plugins-pulse:1.0 ). Replaced media-libs/tiff with media-libs/tiff-compat:4. Removed x11-libs/libxshmfence.
(In reply to Alexander Kurakin from comment #88) > Created attachment 874607 [details] > Viber 21.0.0.1 Ebuild Hi, thank you for the update. Works fine here and crash on start depending on kbd layout finally gone.
Created attachment 887887 [details] viber-21.8.0.11.ebuild Viber 21.8.0.11 for Linux is out.
What changed above? * Upstream version 21.8.0.11. * x11-libs/xcb-util-cursor became an embedded .so. * media-video/ffmpeg:0/56.58.58[${MULTILIB_USEDEP}] became an RDEPEND but since it's an optional (`Warning: could not load multimedia backend "ffmpeg"`) and FFMPEG 4.4 is old, I made it as optfeature. Didn't check its installing. There are warnings: could not load multimedia backend "ffmpeg" QtMultimedia is not currently supported on this platform or compiler. Failed to initialize QMediaPlayer "Not available" Installing dev-qt/qtmultimedia:6/6.6.2 didn't seem to change anything.
(In reply to Alexander Kurakin from comment #91) > What changed above? > > * Upstream version 21.8.0.11. > * x11-libs/xcb-util-cursor became an embedded .so. > * media-video/ffmpeg:0/56.58.58[${MULTILIB_USEDEP}] became an RDEPEND > but since it's an optional (`Warning: could not load multimedia backend > "ffmpeg"`) > and FFMPEG 4.4 is old, I made it as optfeature. > Didn't check its installing. > > There are warnings: > > could not load multimedia backend "ffmpeg" > QtMultimedia is not currently supported on this platform or compiler. > Failed to initialize QMediaPlayer "Not available" > > Installing dev-qt/qtmultimedia:6/6.6.2 didn't seem to change anything. The nest overlay contains the latest Viber ebuild that depends on the media-video/ffmpeg-compat library with the old ffmpeg ABI. It works for me.
Created attachment 903647 [details] viber-23.2.0.3.ebuild * New upstream version: 23.2.0.3. * `QA_PRESTRIPPED` was updated. * Added dependencies per ``` * QA Notice: Unresolved soname dependencies: * * /opt/viber/lib/libavcodec.so.58: libgsm.so.1 libtwolame.so.0 libzvbi.so.0 * /opt/viber/lib/libavformat.so.58: libbluray.so.2 libopenmpt.so.0 * /opt/viber/lib/libx265.so.179: libnuma.so.1 * ``` * Added dependencies per `qa-vdb`. Unresolved: * it's unsuccessfully looking for `libvdpau_va_gl.so`, at stratup.
Thank you Alexander for the updated .ebuild. :) -- Much earlier versions of Viber had a very good file selection interface, I think based on standard linux libraries. viber-21 and viber-23 have almost unuseable file selection interface: we cannot bookmark oftently accessed folders, we cannot search files by name, we cannot order the files by last updated timestamp, (we have to scroll in alphabetical order over a potentially very long list of entries), we do not have file preview (pictures, etc.).... In many situations, it makes sending files via viber-desktop an unnecessary pain. Do you experience the same? Do you confirm it wasn't like this before? Does anyone here have the .deb of an earlier version of viber, which we could use to downgrade? Is there a fix (using wrong library?) or is that purely a viber upstream problem?
(In reply to augustin from comment #94) > Do you experience the same? > > Do you confirm it wasn't like this before? > > Does anyone here have the .deb of an earlier version of viber, which we > could use to downgrade? > > Is there a fix (using wrong library?) or is that purely a viber upstream > problem? I have the same experience with the file manager, but what I find most disturbing is the non receiving of messages some times. While I do get the messages from group or single chats in Viber in my phone, I don't get them in the application. While quitting and restarting the application causes the messages to finally arrive, at some point, the receiving just stops. I think this started with version 23, but I'm not really sure. In any case, this issue is serious.
(In reply to augustin from comment #94) > Does anyone here have the .deb of an earlier version of viber, which we > could use to downgrade? Hi, I put what I found in my distfiles here https://evadim.ru/files/viber/
(In reply to Vadim Efimov from comment #96) > I put what I found in my distfiles here https://evadim.ru/files/viber/ Thank you very much Vadim. The viber-18.2.0.2.deb installed fine with the corresponding original .ebuild. Unfortunately, launching from the command line, nothing happens, and there is no error output nor anything in the logs. I have upgraded back to viber-23.2.0.3 until I can investigate further. Thanks again Vadim for sharing.
(In reply to augustin from comment #97) > Unfortunately, launching from the command line, nothing happens, and there > is no error output nor anything in the logs. I have upgraded back to > viber-23.2.0.3 until I can investigate further. I have few ideas. 1) You can try to move your profile folder ~/.ViberPC to somewhere (for backup) and test on "fresh one" (you need to log in again). 2) I remember some version of Viber hang on start for me, so I upgraded. 3) If you have multiple keyboard layouts: this exact version (according to comments) failed to start for me if EN layout active, must switch to second and then start Viber. > > Thanks again Vadim for sharing. You are welcome. On the other side, looks like this new Viber works fine for me...
I'm stopping to publish new versions.
