X2Go Bug report logs - #1091
'Xset: Unable to open display' prevents connection

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: Sandro <redsandro@gmail.com>

Date: Mon, 19 Sep 2016 23:30:02 UTC

Severity: normal

Tags: not-a-bug

Found in version 4.0.1.19

Done: Mihai Moldovan <ionic@ionic.de>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1091; Package x2goserver. (Mon, 19 Sep 2016 23:30:02 GMT) (full text, mbox, link).


Acknowledgement sent to Sandro <redsandro@gmail.com>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Mon, 19 Sep 2016 23:30:03 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Sandro <redsandro@gmail.com>
To: submit@bugs.x2go.org
Subject: 'Xset: Unable to open display' prevents connection
Date: Mon, 19 Sep 2016 23:29:16 +0000
[Message part 1 (text/plain, inline)]
Package: x2goserver
Version: 4.0.1.19

I have a Linux Mint 18 x2go client and a Debian Testing x2go server. And I
update both at random intervals.
Things just worked for ages. I think I went from Linux Mint 15 to 18.
Debian is also really uptodate.

Then at one moment - I don't exactly know when because I don't use x2go
daily - I started getting this error message.

Connection failed. xset: unable to open display ""
http://i.imgur.com/Z6yQb4R.png

This sounds like one of those xorg errors you get when doing x stuff while
not logged into a virtual terminal, but in the case of x2go, I use the
magic but don't know how it works, so I have no idea where to start looking.

Client machine:
    Linux Mint 18 (AKA Ubuntu 16.04)
    x2goclient 4.0.5.1-1
    pyhoca-gui 0.5.0.4-1*
    pyhoca-cli 0.5.0.2-1*
Server:
    Debian Testing
    x2go-server 4.0.1.19-0x2go2+git20160621.1064+stretch.main.1
    x2goserver-xsession 4.0.1.19-0x2go2+git20160621.1064+stretch.main.1
    nxagent 2:3.5.0.32-0x2go1+git20160614.734+stretch.main.1

*) Never heard of there. I don't think I ever installed them. I figured I
didn't have them installed before so I installed them now. Didn't fix my
problem though.
[Message part 2 (text/html, inline)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1091; Package x2goserver. (Thu, 10 Nov 2016 15:00:01 GMT) (full text, mbox, link).


Acknowledgement sent to Mihai Moldovan <ionic@ionic.de>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Thu, 10 Nov 2016 15:00:02 GMT) (full text, mbox, link).


Message #10 received at 1091@bugs.x2go.org (full text, mbox, reply):

From: Mihai Moldovan <ionic@ionic.de>
To: Sandro <redsandro@gmail.com>, 1091@bugs.x2go.org
Subject: Re: [X2Go-Dev] 'Xset: Unable to open display' prevents connection
Date: Thu, 10 Nov 2016 15:55:23 +0100
[Message part 1 (text/plain, inline)]
Control: close -1
Control: tag -1 not-a-bug

On 20.09.2016 01:29 AM, Sandro wrote:
> Connection failed. xset: unable to open display "" 
> http://i.imgur.com/Z6yQb4R.png
> 
> This sounds like one of those xorg errors you get when doing x stuff while not
> logged into a virtual terminal, but in the case of x2go, I use the magic but
> don't know how it works, so I have no idea where to start looking.

You very likely call "xset" in your shell startup scripts. Newer X2Go Client
versions started calling bash as a login shell, which implies executing scripts
like ~/.profile, ~/.bash_profile, ~/.bashrc and the like. If you have anything
in there that outputs to stderr, X2Go Client will abort the connection.

Because the first connection logically won't have a valid DISPLAY variable set -
after all, the client has to spawn x2goagent first - the "xset" call will fail
and the session terminate abnormally.

Please fix your shell startup scripts.

Marking this bug as not-a-bug and closing.


> Client machine:
>     Linux Mint 18 (AKA Ubuntu 16.04)
>     x2goclient 4.0.5.1-1
>     pyhoca-gui 0.5.0.4-1*
>     pyhoca-cli 0.5.0.2-1*
> Server:
>     Debian Testing
>     x2go-server 4.0.1.19-0x2go2+git20160621.1064+stretch.main.1
>     x2goserver-xsession 4.0.1.19-0x2go2+git20160621.1064+stretch.main.1
>     nxagent 2:3.5.0.32-0x2go1+git20160614.734+stretch.main.1
> 
> *) Never heard of there. I don't think I ever installed them. I figured I didn't
> have them installed before so I installed them now. Didn't fix my problem though.

PyHoca is another client for X2Go, like X2Go Client. You don't need it, but
chances are you wouldn't have hit that problem with it because it connects and
executes commands differently than X2Go Client.



Mihai


[signature.asc (application/pgp-signature, attachment)]

Marked Bug as done Request was from Mihai Moldovan <ionic@ionic.de> to 1091-submit@bugs.x2go.org. (Thu, 10 Nov 2016 15:00:02 GMT) (full text, mbox, link).


Notification sent to Sandro <redsandro@gmail.com>:
Bug acknowledged by developer. (Thu, 10 Nov 2016 15:00:02 GMT) (full text, mbox, link).


Added tag(s) not-a-bug. Request was from Mihai Moldovan <ionic@ionic.de> to 1091-submit@bugs.x2go.org. (Thu, 10 Nov 2016 15:00:02 GMT) (full text, mbox, link).


Bug archived. Request was from Debbugs Internal Request <owner@bugs.x2go.org> to internal_control@bugs.x2go.org. (Fri, 09 Dec 2016 06:24:01 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Fri Sep 18 13:53:04 2020; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.