I have found a bug and workaround in x2goclient on MacOS Sequoia. I am trying to raise report/this but where?
The official wiki advice <https://wiki.x2go.org/doku.php/wiki:bugs> suggests applying to join the GitLab org - I've applied but I have to wait for admin approval.
There's an IRC/Matrix channel <https://wiki.x2go.org/doku.php/contact:start>where it was suggested I also join the mailing list. The bugs mailing list <https://lists.x2go.org/listinfo/x2go-bugs> does not appear to have been active for a decade <https://lists.x2go.org/listinfo/x2go-bugs> although I have subscribed. A kind soul on IRC suggested also joining this mailing list but I am not sure that this is the right place to raise a bug report.
Without meaning to be rude about a great software project, the situation does seem a bit ridiculous. I run my own (much, much smaller) open source project onGitHub and if people want to raise an issue then they can just do that, ditto me for many of the other open source software projects I use. It's unfortunate that there isn't a clear and straightforward way here.
If anyone is able to comment on the correct route to raise an issue/bug then I should be grateful, thanks
Joshua
I have been asked to describe the bug here:
I am using x2goclient: 4.1.2.2 on Mac ARM installed via Homebrew, primarily to access an Ubuntu server via SSH. I have been doing this largely successfully for years. Last week I updated to MacOS Sequoia. When I go to connect to my server from the GUI 'New Session' I consistently get 'Failed to connect: No route to host'.
If instead of launching X2go in the normal mac way by clicking on the app icon, i do in terminal
/Applications/x2goclient.app/Contents/MacOS/x2goclient
The same operation for 'new session' is successful. I see this output in my shell:
x2go-INFO-1> "Starting X2Go Client 4.1.2.2..." x2go-WARNING-1> English language requested, not loading translator. x2go-WARNING-1> English language requested, not loading translator. x2go-INFO-3> "Started X2Go Client." 2024-09-30 14:36:11.522 x2goclient[58808:5273496] +[IMKClient subclass]: chose IMKClient_Legacy 2024-09-30 14:36:11.522 x2goclient[58808:5273496] +[IMKInputSession subclass]: chose IMKInputSession_Legacy x2go-INFO-8> "Starting connection to server: 192.168.1.101:22"
I recently had an issue with another app after updating to Sequoia with a workaround: https://github.com/zim-desktop-wiki/zim-desktop-wiki/issues/2665 I am wondering if the issue is cmoparable here - some sort of environment variable or locale being required but not otherwise being sourced correctly since Sequoia
On Mon, 30 Sept 2024 at 11:39, Joshua Kite <joshuamkite@gmail.com> wrote:
I have found a bug and workaround in x2goclient on MacOS Sequoia. I am trying to raise report/this but where?
The official wiki advice <https://wiki.x2go.org/doku.php/wiki:bugs> suggests applying to join the GitLab org - I've applied but I have to wait for admin approval.
There's an IRC/Matrix channel <https://wiki.x2go.org/doku.php/contact:start>where it was suggested I also join the mailing list. The bugs mailing list <https://lists.x2go.org/listinfo/x2go-bugs> does not appear to have been active for a decade <https://lists.x2go.org/listinfo/x2go-bugs> although I have subscribed. A kind soul on IRC suggested also joining this mailing list but I am not sure that this is the right place to raise a bug report.
Without meaning to be rude about a great software project, the situation does seem a bit ridiculous. I run my own (much, much smaller) open source project onGitHub and if people want to raise an issue then they can just do that, ditto me for many of the other open source software projects I use. It's unfortunate that there isn't a clear and straightforward way here.
If anyone is able to comment on the correct route to raise an issue/bug then I should be grateful, thanks
Joshua
Hi there,
I have this same bug/problem here. It seems that the application x2goclient needs some sort of database entry in Macos, to be able to appear in the list of 'Lokales Netzwerk', where I could enable network access for x2goclient. But it does not appear in this list. Did anybody find a solution for this problem? As a workaround, I can open an ssh tunnel to the remote machine, and then connect to a port on localhost. But this is a bit complicated for everyday use.
Best, Thomas
Workaround for x2goclient "No route to host" on macOS Sequoia / Tahoe
The root cause is that x2goclient has no bundle identifier (CFBundleIdentifier) and its Qt frameworks have a non-standard structure that can't be codesigned. This affects both the Homebrew and DMG installs. Because of this, macOS never prompts for Local Network permission and silently blocks connections. Codesigning the app doesn't work due to the malformed Qt framework bundles. The simplest fix is to create an Automator wrapper app:
Open Automator → New Document → Application Search for Run Shell Script and drag it into the workflow Set Shell to /bin/zsh and paste:
/Applications/x2goclient.app/Contents/MacOS/x2goclient &
File → Save as "X2Go" to your Applications folder Launch the new X2Go app — it inherits Terminal's local network permissions and connects without issue
Optionally, copy the original x2goclient icon onto the Automator app via Get Info (Cmd+C / Cmd+V on the icon). Tested on macOS Tahoe 26.x with x2goclient 4.1.2.2 (both Homebrew and DMG installs). The real fix needs to come from X2Go packaging the macOS app with a proper CFBundleIdentifier and correctly structured/signed frameworks.
-
78-yearly-dryness＠icloud.com -
Joshua Kite -
Thomas Stephan