requested length exceeded (code 4) Message-Id: <20180827152604.53712210c51522704b6ec5ce@lucassen.org> Reply-To: x2go-user@lists.x2go.org Organization: XAQ Systems X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
Maybe it has nothing to do with x2go, but on my server I get this when starting a few programs, e.g. VLC or sqlitebrowser:
$ vlc VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332) [000055dbab76c570] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-richard' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-richard' The X11 connection broke: Maximum allowed requested length exceeded (code 4) XIO: fatal IO error 2 (No such file or directory) on X server ":50" after 433 requests (433 known processed) with 0 events remaining. QMutex: destroying locked mutex
IIRC the program runs well on the local machine. Anyone a hint?
-- richard lucassen http://contact.xaq.nl/
On Mon, 27 Aug 2018 15:26:04 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
requested length exceeded (code 4) Message-Id: <20180827152604.53712210c51522704b6ec5ce@lucassen.org> Reply-To: x2go-user@lists.x2go.org Organization: XAQ Systems X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
Maybe it has nothing to do with x2go, but on my server I get this when starting a few programs, e.g. VLC or sqlitebrowser:
[..]
IIRC the program runs well on the local machine. Anyone a hint?
Hmmm, when setting x2go client to a fixed screensize instead of fullscreen (which I don't want) the problem has gone. Anyone an idea?
R.
-- richard lucassen http://contact.xaq.nl/
Might try using "Display 1" as opposed to full screen. You can set that
option using the pull down menu on the entry for that machine on the right side, it is not available from the setup dialogue anymore for reasons I am unfamiliar with.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 28 Aug 2018, richard lucassen wrote:
Date: Tue, 28 Aug 2018 11:38:38 +0200 From: richard lucassen <mailinglists@lucassen.org> Reply-To: x2go-user@lists.x2go.org To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Maximum allowed
On Mon, 27 Aug 2018 15:26:04 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
requested length exceeded (code 4) Message-Id: <20180827152604.53712210c51522704b6ec5ce@lucassen.org> Reply-To: x2go-user@lists.x2go.org Organization: XAQ Systems X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
Maybe it has nothing to do with x2go, but on my server I get this when starting a few programs, e.g. VLC or sqlitebrowser:
[..]
IIRC the program runs well on the local machine. Anyone a hint?
Hmmm, when setting x2go client to a fixed screensize instead of fullscreen (which I don't want) the problem has gone. Anyone an idea?
R.
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Tue, 28 Aug 2018 11:38:38 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
For future googlers:
I run a Debian version (testing) and on the server side there is a file called "/etc/x2go/x2goagent.options" and I needed to comment out the line with "X2GO_NXAGENT_DEFAULT_OPTIONS" (or remove "-extension BIG-REQUESTS" I suppose):
[..] # Disable BIG-REQUESTS, nx-libs does not implement this extension # correctly. Leads to all sorts of weird crashes if left enabled. ###X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension BIG-REQUESTS"
The problem has gone now. No need to restart the server, just start a new session.
Thanks to Ulrich Sibiller (again).
R.
-- richard lucassen http://contact.xaq.nl/