Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] x2goserver package is non-functional
Date: Mon, 10 May 2021 18:30:21 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30781@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4709 bytes --]

New issue by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/30781

Description:
The x2goserver package does not work as packaged and also contains some other issues that should be rectified:
1. It seems some references to a prefix of `/usr/local` still exist, leading to connection failures. (See Reference below.)
2. The package is missing a `perl-Try-Tiny` dependency that is required for `x2godbadmin` to run.
3. `makepasswd` should not be a dependency; the ChangeLog notes that `makepasswd` was replaced with `pwgen`, but this only seems to be used with a Postgres or MySQL backend. This makes `pwgen` optional, so it shouldn't be a dependency either.
4. The `post_extract` function in the template should be `post_patch` instead. Sometimes it is desirable to step through `xbps-src` stages manually to investigate the state of the build directory, and those patches should only be applied by `xbps-src patch x2goserver`, *not* `xbps-src extract x2goserver` as would happen now.
5. A runit server for `x2gocleansessions` should be provided. This has some caveats. Running `x2gocleansessions` without arguments causes the process to fork, which will cause runit's `runsv` to lose supervision over the process. Running `x2gocleansessions --debug` will prevent the fork, but will also spam the console with useless messages every second or so. The `x2gocleansessions` script should probably be patched to separate the no-fork flag from the debug flag, and that patch should be upstreamed. In the meantime, I am not sure how best to handle this. Maybe just manually drop the forking logic so `x2gocleansessions` always runs in the foreground?

## Test Procedure
1. Install `x2goclient`, `x2goserver` on two hosts (server.remote and client.local).
2. On server.remote, execute (as root) `x2godbadmin --create`. (This requires `perl-Try-Tiny` be installed.)
3. On server.remote, run `x2gocleansessions --debug`.
4. On client.local, launch `x2goclient` and create a new session to `server.remote`, selecting a "Single application" session type and trying to run `/usr/bin/xterm` (or some other X11 application installed on server.remote).
5. Attempt to start the session and observe a pop-up dialog showing the connection failure message in the Reference below.

## Reference:
Failure message when connecting to a Void server:
```
Connection failed. /usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':")
/usr/lib/x2go/x2gocheckport: line 131:
'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':: syntax error:
operand expected (error token is
"'/usr/local/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl':") Unable to find
free display port or insert new session into database; parameters: port (50),
hostname (my.remote.host.com) and session name ().
```
cc: @eoli3n

             reply	other threads:[~2021-05-10 16:30 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 16:30 ahesford [this message]
2021-05-10 16:48 ` ericonr
2021-05-10 20:23 ` eoli3n
2021-05-10 20:24 ` eoli3n
2021-05-10 20:34 ` eoli3n
2021-05-10 20:35 ` eoli3n
2021-05-10 20:38 ` eoli3n
2021-05-10 21:16 ` eoli3n
2021-05-10 21:16 ` eoli3n
2021-05-10 21:24 ` eoli3n
2021-05-10 21:27 ` eoli3n
2021-05-10 21:27 ` eoli3n
2021-05-10 22:01 ` eoli3n
2021-05-10 22:10 ` eoli3n
2021-05-10 22:10 ` eoli3n
2021-05-10 22:13 ` eoli3n
2021-05-10 22:16 ` eoli3n
2021-05-10 22:18 ` eoli3n
2021-05-10 22:20 ` eoli3n
2021-05-10 22:28 ` eoli3n
2021-05-10 22:28 ` eoli3n
2021-05-10 22:29 ` eoli3n
2021-05-10 22:30 ` eoli3n
2021-05-10 22:40 ` eoli3n
2021-05-10 22:40 ` eoli3n
2021-05-11  7:07 ` eoli3n
2021-05-11  7:07 ` eoli3n
2021-05-11  7:36 ` eoli3n
2021-05-11  7:36 ` eoli3n
2021-05-11  7:39 ` eoli3n
2021-05-11  7:44 ` eoli3n
2021-05-11  7:50 ` eoli3n
2021-05-11  7:50 ` eoli3n
2021-05-11  8:30 ` eoli3n
2021-05-11  8:56 ` eoli3n
2021-05-11  9:04 ` eoli3n
2021-05-11  9:04 ` eoli3n
2021-05-11  9:53 ` eoli3n
2021-05-11  9:54 ` eoli3n
2021-05-11 10:10 ` eoli3n
2021-05-11 10:45 ` eoli3n
2021-05-11 10:46 ` eoli3n
2021-05-11 10:47 ` eoli3n
2021-05-11 10:49 ` eoli3n
2021-05-11 10:50 ` eoli3n
2021-05-11 10:51 ` eoli3n
2021-05-11 11:47 ` eoli3n
2021-05-11 11:47 ` eoli3n
2021-05-11 11:57 ` eoli3n
2021-05-11 12:30 ` eoli3n
2021-05-11 17:29 ` eoli3n
2021-05-11 18:51 ` eoli3n
2021-07-15 11:53 ` [ISSUE] [CLOSED] " ahesford
2023-02-11 15:28 ` devmalick
2023-02-11 16:41 ` ahesford
2023-02-11 16:42 ` ahesford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30781@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).