Description of problem: Since the update of x2goserver on Dec 25 (x2goserver.x86_64.4.0.1.18-4.fc20) I can no longer connect to my server with the "connect to local desktop" option. New sessions work fine. I back leveled my x2goserver to the base version (4.0.1.6-5.fc20) and it works fine. Version-Release number of selected component (if applicable): x2goserver.x86_64.4.0.1.18-4.fc20 How reproducible: always Steps to Reproduce: 1. Try to connect to local desktop with x2goserver.x86_64.4.0.1.18-4.fc20 installed on server 2. 3. Actual results: pop-up dialog states "no accessible desktop found" Expected results: my local session to be displayed Additional info:
Think I've found the problem.
x2goserver-4.0.1.18-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/x2goserver-4.0.1.18-5.fc20
Package x2goserver-4.0.1.18-5.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing x2goserver-4.0.1.18-5.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0473/x2goserver-4.0.1.18-5.fc20 then log in and leave karma (feedback).
Sorry, can't go to https://admin.fedoraproject.org/updates/FEDORA-2015-0473/x2goserver-4.0.1.18-5.fc20 and login and leave karma as the site won't allow me to create a user account. I left feedback as an anonymous user. It now works with the x2goserver-4.0.1.18-5.fc20 package from testing. Thanks.
*** Bug 1181628 has been marked as a duplicate of this bug. ***
Is there a date when this will be available in FC21? Thanks.
It's already in updates-testing for F21: https://admin.fedoraproject.org/updates/FEDORA-2015-0457/x2goserver-4.0.1.18-5.fc21 Should get push to stable in a couple of days. Faster if it gets enough positive feedback.
x2goserver-4.0.1.18-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Works, now. Thanks.
I'm running into this issue on CentOS 7 w/ EPEL. https://bugzilla.redhat.com/show_bug.cgi?id=1371690