Package Details: vidyodesktop 3.6.3.017-7

Git Clone URL: https://aur.archlinux.org/vidyodesktop.git (read-only, click to copy)
Package Base: vidyodesktop
Description: VidyoDesktop(TM) video conferencing client
Upstream URL: http://www.vidyo.com
Keywords: client desktop proprietary videoconference
Licenses: custom
Conflicts: vidyo
Submitter: troyengel
Maintainer: seadanda
Last Packager: seadanda
Votes: 15
Popularity: 0.000000
First Submitted: 2014-09-05 20:19 (UTC)
Last Updated: 2018-10-26 09:42 (UTC)

Pinned Comments

seadanda commented on 2018-02-05 14:20 (UTC)

Hi @bunnybooboo, VidyoDesktop broke with an update to qt a few months ago. Unfortunately Vidyo stopped supporting Vidyo Desktop on Linux a long time ago and so I doubt we will see any attempts to fix this problem. The current version (3.6.3_017) was released back in March 2016. Since it is closed source the only way that we have found to run it succesfully is by using a systemtray application.

If you run trayer (which is installed as a dependency) before running Vidyo Desktop, Vidyo works without any issues. This is unfortunate but it is an upstream issue.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8

arch-nemesis commented on 2014-12-05 16:07 (UTC)

I'd been struggling to understand why, after installing on two machines with different desktop environments, one machine would refuse to run this package. $ VidyoDesktop CLIENT: socket_error removed server QTVD-IPC-SERVER IPC server fired successfully QPainter::begin: Widget painting can only begin as a result of a paintEvent It would seem that Vidyo really does want you be using Pulse Audio. The error given is not exactly obvious, but it's a problem connecting to pulse. Starting it this way works: VIDYO_AUDIO_FRAMEWORK=ALSA VidyoDesktop Hopefully this helps somebody else!

troyengel commented on 2014-09-09 23:40 (UTC)

As usual Carl I agree with everything. :) While I'm usually not a fan of changing what the vendor wants to do, I agree that shipping the XDG file that causes an autostart *for every user* is just a bad idea, and have used your changes to stop shipping it. Not sure about that weird extract problem either -- I've uploaded a new -4 release with the changes and just did a full 'yaourt -Syua' (woo, new kernel!) and the vidyodesktop package is upgrading cleanly without those errors. Give it a shot on your end and see if the errors went away... Thanks for the reports on problems!

<deleted-account> commented on 2014-09-09 13:45 (UTC)

I'm not sure what changed to cause this, but now I'm getting build errors od: /build/vidyodesktop/src/: read error: Is a directory expr: non-integer argument expr: non-integer argument expr: syntax error expr: non-integer argument od: invalid -j argument '-N' expr: non-integer argument expr: non-integer argument expr: syntax error expr: syntax error bsdtar: Error opening archive: Unrecognized archive format I removed the rpmextract stuff from the PKGBUILD so that makepkg can correctly use bsdtar to extract the rpm. Now it builds fine. package() { cp -dpr "${srcdir}/opt" "${pkgdir}" cp -dpr "${srcdir}/usr" "${pkgdir}" install -dm1777 "${pkgdir}/opt/vidyo/VidyoDesktop/lic" install -Dm0644 "${srcdir}/opt/vidyo/VidyoDesktop/license.txt" \ "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" } I intentionally left out /etc because the only file in there is a .desktop file that is causing the application to be autostarted (regardless of what the check box in the settings says). /etc/xdg/autostart/VidyoDesktop.desktop is just a duplicate of /usr/share/applications/VidyoDesktop.desktop, with an extra flag. The extra flag is parsed by /usr/bin/VidyoDesktop and just causes the application to wait 8 seconds before starting. I would just leave that file out to prevent the autostart.

<deleted-account> commented on 2014-09-09 13:41 (UTC)

The AUR can't parse custom variables in the source array, so the sources section here on the web interface is not displaying properly. I would change it to this instead. if [ "$CARCH" == "i686" ]; then source=("https://demo.vidyo.com/upload/VidyoDesktopInstaller-sl5-TAG_VD_3_3_0_027.rpm") md5sums=('02e44ed593066c6cca6dd69e165a864b') elif [ "$CARCH" == "x86_64" ]; then source=("https://demo.vidyo.com/upload/VidyoDesktopInstaller-sl564-TAG_VD_3_3_0_027.rpm") md5sums=('ce446bf9f222675891c2437394102d92') fi

troyengel commented on 2014-09-08 21:52 (UTC)

Thanks for the report -- I've updated the PKGBUILD (-3 release) to address both: 1) variable name is now preceded by _ as per guidelines, I copied/pasted that part and missed it. 2) The used of the name in the package was 100% intentional, as the phrase is a trademarked term. Since packaging guidelines indicate the name of the package must be all lowercase, the name VidyoDesktop is intentional in the desciption -- I have updated PKGBUILD to use the *proper* (oops) phrase, "VidyoDesktop(TM)" which I should have done - this is their trademark and must be represented as such according to the websites I was able to Google. (actually most say to use the non-ASCII ^TM symbol, but I won't do that). http://www.vidyo.com/products/use/#tab=Desktop Fixing it to add (TM) to satisfy the legal requirement has a side effect of namcap not calling it out as broken. We want to be careful with packaging commercial software to represent all trademarks, etc.

<deleted-account> commented on 2014-09-08 14:23 (UTC)

$ namcap PKGBUILD PKGBUILD (vidyodesktop) W: Non standard variable 'rpmfilename' doesn't start with an underscore PKGBUILD (vidyodesktop) W: Description should not contain the package name. https://wiki.archlinux.org/index.php/Arch_packaging_standards#Package_etiquette "Do not introduce new variables into PKGBUILD build scripts, unless the package cannot be built without doing so, as these could possibly conflict with variables used in makepkg itself. If a new variable is absolutely required, prefix the variable name with an underscore (_)..." "When creating a package description for a package, do not include the package name in a self-referencing way. For example, "Nedit is a text editor for X11" could be simplified to "A text editor for X11"."

troyengel commented on 2014-09-05 21:01 (UTC)

Roger that -- I've uploaded 3.3.0.027-2 changing the depends() for libgl, give it a shot now. Thanks for reporting!

<deleted-account> commented on 2014-09-05 20:58 (UTC)

Please require libgl instead of mesa-libgl. libgl can be provided by either mesa-libgl or nvidia-libgl, but you don't want to force users to either one. I'm sure there is some AMD/ATI equivalent as well.

« First ‹ Previous 1 .. 3 4 5 6 7 8