Search Criteria
Package Details: x2goclient 4.1.2.3-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/x2goclient.git (read-only, click to copy) |
---|---|
Package Base: | x2goclient |
Description: | a graphical client (Qt5) for the X2Go system |
Upstream URL: | https://wiki.x2go.org/doku.php |
Licenses: | GPL2 |
Submitter: | arojas |
Maintainer: | envolution |
Last Packager: | envolution |
Votes: | 18 |
Popularity: | 1.28 |
First Submitted: | 2022-04-01 18:56 (UTC) |
Last Updated: | 2024-10-29 04:44 (UTC) |
Dependencies (13)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libldap
- libssh (libssh-gitAUR)
- libxpm (libxpm-gitAUR)
- nxproxyAUR
- qt5-svg (qt5-svg-gitAUR)
- qt5-x11extras
- man2html (vh-man2htmlAUR) (make)
- qt5-tools (make)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (make)
- xorg-xauth (make)
- xorg-xauth (optional) – may be required by X2goservers running a different linux distribution giving MIT-COOKIE errors
Latest Comments
1 2 Next › Last »
trumee commented on 2024-02-29 18:09 (UTC) (edited on 2024-02-29 18:10 (UTC) by trumee)
==> Verifying source file signatures with gpg...
gpg ==> ERROR: One or more PGP signatures could not be verified!
terryer commented on 2024-01-01 19:18 (UTC)
Seems to be broken. Using
yay
I'm getting ldap.h: No such file or directorypolygamma commented on 2023-08-07 12:52 (UTC) (edited on 2023-08-07 12:57 (UTC) by polygamma)
For the new 4.1.2.3 version another patch needs to be included, as far as I can see :(
In the PKGBUILD in
prepare()
:Otherwise we get:
jal666 commented on 2023-03-13 11:34 (UTC)
$ gpg --keyserver keyserver.ubuntu.com --recv-keys F4A7678C9C6B0B2B
varocho commented on 2022-10-24 09:25 (UTC)
no worries @reibax, its working now without any workaround thanks!
reibax commented on 2022-10-23 20:42 (UTC)
Sorry guys. I think I made a mistake. This was my very first contribution. I swear I saw that checksum on two different machines and I thought it was correct. I don´t know what happened there.
I think I fixed it now. I hope it works OK.
Thank you very much everyone for pointing it out, and thank you @jeroenhd for helping out while I was away by helping others with the correct answer.
gowa182 commented on 2022-10-19 10:45 (UTC)
Thanx, work!
jeroenhd commented on 2022-10-19 10:04 (UTC)
Workaround until the PKGBUILD gets fixed:
Then indicate to edit the PKGBUILD for the package and set the last sha256sum to: be636e911074b474d66016f7a5f0da5fb1693d59291d585cec73f81f54fd9981
1 2 Next › Last »