Package Details: lgogdownloader 3.17-1

Git Clone URL: https://aur.archlinux.org/lgogdownloader.git (read-only, click to copy)
Package Base: lgogdownloader
Description: Open source downloader for GOG.com games, uses the GOG.com API
Upstream URL: https://sites.google.com/site/gogdownloader/
Keywords: games gaming gog gog.com
Licenses: WTFPL
Submitter: tea
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 76
Popularity: 0.183887
First Submitted: 2012-08-01 22:40 (UTC)
Last Updated: 2025-03-23 22:14 (UTC)

Pinned Comments

FabioLolix commented on 2023-10-03 22:03 (UTC)

  • every time you have error while loading shared libraries: libXXX.so.XXX: cannot open shared object file: No such file or directory for build from source programs you have to rebuild it

Latest Comments

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

fbis251 commented on 2018-02-11 08:14 (UTC)

Please add armv7h to the supported architectures

sosonok commented on 2018-02-10 23:25 (UTC)

With boost-libs 1.66, lgogdownloader is broken again.

florensie commented on 2017-12-17 14:26 (UTC) (edited on 2017-12-17 14:28 (UTC) by florensie)

Building says something about a deprecated json api.

nirnakinho commented on 2017-11-02 22:02 (UTC)

logdownloader requires a version bump, as boost has been updated to version 1.65. This makes the binary unable to run as the old boost libraries (v1.63) are gone. Regards,

hringriin commented on 2017-09-06 14:37 (UTC)

The lgogdownloader requires the a cookies.txt due to the captcha login. Ok, but it deletes the file ~/.config/lgogdownloader/cookies.txt when started with the --login option. beside what, it definitely wants to have full access permissions a) to the directory and b) to the file. why?

FabioLolix commented on 2017-06-08 18:50 (UTC)

lgogdownloader: error while loading shared libraries: libboost_system.so.1.63.0: cannot open shared object file: No such file or directory Got this error today, solved with rebuilding the package

tea commented on 2017-03-12 19:01 (UTC)

banzr, I would not recommend importing that .pem since a collection of root certificates is provided by Arch anyway in ca-certificates and other packages in [core]. You should check to see you have that installed, and remove the certificates from that file from your root store to prevent any issues in future when Arch updates its certificates.

<deleted-account> commented on 2017-03-12 16:08 (UTC)

If you cannot login... Download cacert.pem wget https://curl.haxx.se/ca/cacert.pem Then try login with lgogdownloader --cacert cacert.pem --login or CURL_CA_BUNDLE=cacert.pem lgogdownloader --login

<deleted-account> commented on 2017-03-12 16:08 (UTC)

If you cannot login... Download cacert.pem wget https://curl.haxx.se/ca/cacert.pem Then try login with lgogdownloader --cacert cacert.pem --login or CURL_CA_BUNDLE=cacert.pem lgogdownloader --login

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