Package Details: yakyak 1.5.4-0

Git Clone URL: (read-only)
Package Base: yakyak
Description: Desktop client for Google Hangouts
Upstream URL:
Licenses: MIT
Submitter: kuenx
Maintainer: mistachie777 (RobertFischer, vincedyne, snowiow)
Last Packager: mistachie777
Votes: 46
Popularity: 0.218168
First Submitted: 2015-06-23 17:25
Last Updated: 2018-12-11 01:10

Dependencies (4)

Required by (0)

Sources (3)

Pinned Comments

kuenx commented on 2016-12-02 14:03

Please don't flag this package as out-of-date if the new release is a pre-release. YakYak creates pre-releases for testing with the same release version as the final release will have, which would cause problems with the package SHA sums and break the package if I published them. The pre-releases have the "pre-release" badge on GitHub. Wait for the final release before flagging.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

kuenx commented on 2018-12-10 23:42

@mistachie777: Since I'm no longer using Hangouts and this has been working so well I have disowned the package and transferred the primary maintainer role to you. You can now manage co maintainers and all other things.
Thanks for taking over and the good work!

simona commented on 2018-12-10 23:41

=> Avvio di build() in corso... npm WARN tar ENOENT: no such file or directory, open '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/source-map-ff2adf18/dist/source-map.min.js' npm WARN tar ENOENT: no such file or directory, open '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/source-map-3d0ab21a/dist/source-map.js' npm WARN tar ENOENT: no such file or directory, open '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/bluebird-8d0882c5/js/browser/bluebird.min.js' npm WARN tar ENOENT: no such file or directory, open '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/fnuc-211d7587/' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/fsevents-006d9a36/node_modules/abbrev' -> '/home/simona/.cache/yay/yakyak/src/yakyak-1.5.3/node_modules/.staging/abbrev-a08f46a4'

npm ERR! code E404 npm ERR! 404 Not Found: event-stream@3.3.6

npm ERR! A complete log of this run can be found in: npm ERR! /home/simona/.npm/_logs/2018-12-10T23_40_33_550Z-debug.log ==> ERRORE: Si è verificato un errore in build(). L'operazione sta per essere interrotta... Error making: yakyak

mistachie777 commented on 2018-12-10 23:27

Now that electron 3.0 is available, v1.5.3 compiles and runs for me so I have updated the PKGBUILD.

jordanconway commented on 2018-12-10 16:21

Updating the pkgver to 1.5.3 and fixing the sha256sum in the PKGBUILD worked for me now that electron >= 3.0 is in the repos.

reefland commented on 2018-12-07 18:57

"Once electron 3.x is available in the repositories, the original, unmodified PKGBUILD should work fine."

$ pacman -Q yakyak
yakyak 1.5.1-0
$ pacman -Q electron
electron 3.0.10-1

resolved proxy DIRECT
resolved proxy DIRECT
connect_failed TypeError: Cannot read property 'length' of undefined
at /usr/share/yakyak/app/node_modules/hangupsjs/lib/init.js:125:21
at _fulfilled (/usr/share/yakyak/app/node_modules/q/q.js:854:54)
at /usr/share/yakyak/app/node_modules/q/q.js:883:30
at Promise.promise.promiseDispatch (/usr/share/yakyak/app/node_modules/q/q.js:816:13)
at /usr/share/yakyak/app/node_modules/q/q.js:570:49
at runSingle (/usr/share/yakyak/app/node_modules/q/q.js:137:13)
at flush (/usr/share/yakyak/app/node_modules/q/q.js:125:13)
at process._tickCallback (internal/process/next_tick.js:61:11)

Waited for the new electron 3.x and still unable to connect.

mistachie777 commented on 2018-11-16 05:06

There were some additional breakages in v1.5.2 and v1.5.3 but the v1.5.4 rolling beta currently works for me. To build, use this PKGBUILD: and the same as before:

It is still not possible to use the system electron to run yakyak as was previously done, because it has not been updated to 3.x. When this changes, I will update the official PKGBUILD.

mistachie777 commented on 2018-10-26 18:18

I've been informed by @vollekannehoschi that v1.5.2 has now fixed the connection errors, and that it now depends on electron 3.x, which not available in the repositories or on the AUR. I just tested the binary 1.5.2 Linux release from Github and it works with no issues. It seems like the best solution at the moment is to make a PKGBUILD that just extracts the binary release to /opt. The downside of this is that it will no longer use the system version of electron and the resulting package will be larger.

The PKGBUILD can be downloaded here: You will also have to use a modified

Once electron 3.x is available in the repositories, the original, unmodified PKGBUILD should work fine.

mistachie777 commented on 2018-10-25 17:12

I've encountered 2 separate issues that have left me unable to get any version of yakyak to work at the moment:

1) It is no longer necessary to remove the package-lock.json file and run 'npm update' to update the dependencies for Node 10. However, while the package can build successfully, it fails to launch because of the following error:

'TypeError: app.requestSingleInstanceLock is not a function'

I could not find this call in the yakyak codebase, so maybe it's in a dependency?

2) It seems that all versions of yakyak, including 1.5.2 are broken:,, There are some fixes proposed in those issues, but it sounds like they may need to update yakyak to a new release.

It looks like we're dealing with several upstream issues and may have to wait for those to be resolved before we can use the app again. But I'm open to any suggestions!

kuenx commented on 2018-10-23 19:43

I've published mistachie777's PKGBUILD and it works.

kuenx commented on 2018-10-23 19:30

RobertFischer, vincedyne, mistachie777: I've received orphan requests for this package and I'm happy to give it to someone else but I don't know how I can respond to the request to make it an actual orphan. If I disown the package the ownership will just go to snowiow, and I'm not sure if he/she even wants that.

Last time I tried to update I couldn't get YakYak to build on my machine anymore and I haven't gotten around investigating why.

So I've added you all as co-maintainers. You should be able to publish new versions. Please let me know who wants to be the new main maintainer so I that I can transfer ownership to the right person.

Thank you