See https://unix.stackexchange.com/questions/467507/x2go-unable-to-find-free-display-port-or-insert-new-session-into-database. Solved with `x2godbadmin --createdb`. Feels like this should be run automatically, but perhaps there is deeper issue. Reproducible: Always Steps to Reproduce: 1. Install x2goserver on machine. 2. Attempt to connect with x2goclient. Actual Results: Long error message, see SO link. Potentially related bug on another project: https://bugs.mageia.org/show_bug.cgi?id=6729. Expected Results: Connect to machine graphically.
Is the ebuild log warning not enough? Given there's different setups depending on USE and no cleanups, having the user do it and be aware of it may be preferable (not that it's up to me). > if use sqlite ; then > if [[ -f "${EROOT}"/var/lib/x2go/x2go_sessions ]] ; then > elog "To use sqlite and update your existing database, run:" > elog " # x2godbadmin --updatedb" > else > elog "To use sqlite and create the initial database, run:" > elog " # x2godbadmin --createdb" > fi > > fi > if use postgres ; then > elog "To use a PostgreSQL database, more information is availabe here:" > elog "http://www.x2go.org/doku.php/wiki:advanced:multi-node:x2goserver-pgsql" > fi
If it got spit out in warning I admit I missed it. Perhaps this bug should be taken as a suggestion to perform these actions automatically. I can't see a reason not to.