Thx, I did:
$ gpg --recv-keys 1AD23D1B8F087A35AB74BDE9F4A7678C9C6B0B2B
before building with yaourt and it worked.
Search Criteria
Package Details: x2godesktopsharing 3.1.1.3-1
| Git Clone URL: | https://aur.archlinux.org/x2godesktopsharing.git (read-only) |
|---|---|
| Package Base: | x2godesktopsharing |
| Description: | X2Go add-on tool that allows a user to grant other X2go users access to the current session (shadow session support). |
| Upstream URL: | http://www.x2go.org/ |
| Licenses: | |
| Groups: | |
| Submitter: | MilanKnizek |
| Maintainer: | grazzolini |
| Last Packager: | grazzolini |
| Votes: | 18 |
| Popularity: | 0.010504 |
| First Submitted: | 2012-02-13 20:51 |
| Last Updated: | 2017-03-22 04:11 |
Latest Comments
ant commented on 2017-09-11 19:22
grazzolini commented on 2017-09-11 18:14
@ant
Please make sure you have read and understood this:
https://wiki.archlinux.org/index.php/Makepkg#Signature_checking
ant commented on 2017-09-11 18:03
Build fails with:
==> Verifying source file signatures with gpg...
x2godesktopsharing-3.1.1.3.tar.gz ... FAILED (unknown public key F4A7678C9C6B0B2B)
MilanKnizek commented on 2016-06-06 14:56
I quit using X2Go due to more and more issues with newer X. The package is disowned now.
Sorry, guys.
shimi commented on 2016-06-06 14:40
Doesn't build on my system.
Log here: http://pastebin.com/QtNAMEAm
cousinm commented on 2015-05-27 08:04
What we would need would be a way to get debug traces. I couldn't find a way to get the cause of this error, as x2go uses several components mixed together, and each of these has its own way of logging :(
MilanKnizek commented on 2015-04-19 17:06
Then, guys, I do not know what's different with my computer. I can connect remotely to the server and the running sessions on the server (of a different user than the one I am connecting as) do list in x2goclient. All involved users (the user running the session and the user connecting remotely) must be members of x2godesktopsharing group.
Noctivivans commented on 2015-04-19 09:26
Nope, it doesn't help. Whet I try to connect, I still have a message "No usable screens found". I also tried to change group manually, before your update - without success.
MilanKnizek commented on 2015-04-17 12:51
It seems that despite the information in 'man groupadd', the max length limit on group name has been relaxed up to 32 from the original 16.
in 3.1.1.2-2, I have removed the Arch specific patch for 'x2godesktopsharing' to 'x2godesktopshare' group renaming, which was in place to comply with the old limit.
Please upgrade, retest and let me know if it does not work.
MilanKnizek commented on 2015-04-15 06:51
@Noctivivans: hm, it might be something related to the group authorisations.
As a first step, check that your /etc/group has a group name "x2godesktopshare" and you are member of it. If it does not resolve the problem, read further:
There is a difference between Debian and Arch in the maximal group name length, Arch has a shorter limit. Upstream considers this as Arch specifics, hence it is up to the Arch maintainer to resolve it.
See the sharetray.cpp.patch1, which replaces "x2godesktopsharing" with "x2godesktopshare" group name: it used to work in the past.
I have not tested the latest version of x2godesktopsharing and may have a look at the code in the near future to see if there is anything new related to the group name. I would not oppose any help, should anyone be willing to dig in the code.