From unknown Thu Apr 23 23:01:08 2026 MIME-Version: 1.0 X-Mailer: MIME-tools 5.502 (Entity 5.502) X-Loop: owner@bugs.x2go.org From: owner@bugs.x2go.org (X2Go Bug Tracking System) Subject: Bug#1091 closed by Mihai Moldovan (Re: [X2Go-Dev] 'Xset: Unable to open display' prevents connection) Message-ID: References: <14eb6c93-3d28-3f43-0d30-daa1e4f6f8fd@ionic.de> X-X2go-PR-Message: they-closed 1091 X-X2go-PR-Package: x2goserver X-X2go-PR-Source: x2goserver Date: Thu, 10 Nov 2016 15:00:02 +0000 Content-Type: multipart/mixed; boundary="----------=_1478790002-21462-0" This is a multi-part message in MIME format... ------------=_1478790002-21462-0 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 This is an automatic notification regarding your Bug report which was filed against the x2goserver package: #1091: 'Xset: Unable to open display' prevents connection It has been closed by Mihai Moldovan . Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Mihai Moldovan by replying to this email. --=20 1091: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=3D1091 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems ------------=_1478790002-21462-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 1091) by bugs.x2go.org; 10 Nov 2016 14:55:40 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS autolearn=ham version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 6F19E3CBB6 for <1091@bugs.x2go.org>; Thu, 10 Nov 2016 15:55:38 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnJxXXgA3Juq for <1091@bugs.x2go.org>; Thu, 10 Nov 2016 15:55:31 +0100 (CET) Received: from Root24.de (powered.by.root24.eu [5.135.3.88]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 606B73CBB5 for <1091@bugs.x2go.org>; Thu, 10 Nov 2016 15:55:30 +0100 (CET) Received: from nopileos.eduroam.hnu.uas (unknown [194.95.21.122]) by mail.ionic.de (Postfix) with ESMTPSA id D2B614F00066; Thu, 10 Nov 2016 15:55:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ionic.de; s=default; t=1478789730; bh=AJ2ZimNBE14u7Yr/6Ox8oG9aPGjj+d8AZ7niRve3O7g=; h=Subject:To:References:From:Date:In-Reply-To:From; b=FGunmn3HPmRK6RKSNoGncDQfv8cKI7/NSYLc4wlTM/B37wMEmWTNP/6BkBacT2mZu mIo26EnVZcRRQhUxc1hbZe/7Fq5V3rx5JkqKq5njXdoYZgOfa3FaactbU2jEe6gftU 1L+Rc1qy5lfFokWAalgC1gSoy7VB89VJM+qdB0x8= Subject: Re: [X2Go-Dev] 'Xset: Unable to open display' prevents connection To: Sandro , 1091@bugs.x2go.org References: From: Mihai Moldovan Message-ID: <14eb6c93-3d28-3f43-0d30-daa1e4f6f8fd@ionic.de> Date: Thu, 10 Nov 2016 15:55:23 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3JowdmV5G5vNEJQj5QXHRfL3Wh6ktfpxo" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3JowdmV5G5vNEJQj5QXHRfL3Wh6ktfpxo Content-Type: multipart/mixed; boundary="UiThHEP4I9Dqf3HGCv2PShwwOaL7Naw3Q"; protected-headers="v1" From: Mihai Moldovan To: Sandro , 1091@bugs.x2go.org Message-ID: <14eb6c93-3d28-3f43-0d30-daa1e4f6f8fd@ionic.de> Subject: Re: [X2Go-Dev] 'Xset: Unable to open display' prevents connection References: In-Reply-To: --UiThHEP4I9Dqf3HGCv2PShwwOaL7Naw3Q Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 ""=20 > http://i.imgur.com/Z6yQb4R.png >=20 > This sounds like one of those xorg errors you get when doing x stuff wh= ile not > logged into a virtual terminal, but in the case of x2go, I use the magi= c 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 Cli= ent versions started calling bash as a login shell, which implies executing s= cripts like ~/.profile, ~/.bash_profile, ~/.bashrc and the like. If you have any= thing in there that outputs to stderr, X2Go Client will abort the connection. Because the first connection logically won't have a valid DISPLAY variabl= e 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 >=20 > *) 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 probl= em though. PyHoca is another client for X2Go, like X2Go Client. You don't need it, b= ut chances are you wouldn't have hit that problem with it because it connect= s and executes commands differently than X2Go Client. Mihai --UiThHEP4I9Dqf3HGCv2PShwwOaL7Naw3Q-- --3JowdmV5G5vNEJQj5QXHRfL3Wh6ktfpxo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCgAGBQJYJIpgAAoJEB/WLtluJTqHe0QP/0Mr5wczi0E6n3tSKN6V7K02 eUAJvFPoWHv2C0yBUSbTo2oLP2qgD3bhEhOc0A2GhgjzXG//XJVKQWmLrhQhBVvh DgpIl6QG+d3Cug1UNB8BXKYGHKxkH9F+VsWmLtvuYpuNp55i9c3jOfoZzZmJN9Lm 4p2aAmacIyOnw6H9lA9T20Z8b3+aQj91zhX8XtzN0yXzZ/P4hGy6qfUcVZScevR/ 0Cnig9Mezxmk71zTu5yAYg697s0UutH3NJt8lKPOd5wE49oFU5oRBaEaPEbS3UhD ZODeY+AcFh6THWzzirQuf2MUb1PqImitYtQPU02XRN3rAjZEppARjJmqktA+fUGV +Bm3kLf2rlEhOu99lvWAt+qJs39LIHNPHv3aHwfIHu/UrDvaBDcwQ/9funzC6MF/ aazeJZZ+61v2D8vJLikZBDTUf5TCMGnN0kHZgh8wa2CfjZe+qc/KKeL1OSyr0c7E lf9QQ8yypoxT5WVsNt2AWYuBHYnR4Z6LJ6VL03VqLEGYB97zkIt9XabELn14WFxf Q4BEjVzgGsNdDEd204StJhj77LskkxYghA7V3cRdKbaPgyt4XazYEkl9amuTBA4C 5t4Y1aXQPR/GQjCXwQSY0UZkZ+i10PMfw8Hj9SKHKzb3CRd4/WudHx1bia74Vhtb ruFe7QFlXHR7CUEQstJi =A+dJ -----END PGP SIGNATURE----- --3JowdmV5G5vNEJQj5QXHRfL3Wh6ktfpxo-- ------------=_1478790002-21462-0 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by bugs.x2go.org; 19 Sep 2016 23:29:36 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: * X-Spam-Status: No, score=1.2 required=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_SORBS_SPAM, URIBL_BLOCKED autolearn=no version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 54AFD5DA94 for ; Tue, 20 Sep 2016 01:29:35 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSfXv2bCRG-Y for ; Tue, 20 Sep 2016 01:29:28 +0200 (CEST) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 5C8085DA8E for ; Tue, 20 Sep 2016 01:29:28 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id a25so6668199wmi.1 for ; Mon, 19 Sep 2016 16:29:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=excZmKHRlQ9ccSEQtwAhSppk4zJ9f55tt1Efb1ZYcGw=; b=bOVq87JPSDLSWmO9UEhjuUapRVW7lhftFGb5YqkCs16rw/nsArhCIPOn+Xh68MciCW lMegdVLs7BMCQUUeSOr74x43IFR1ab3Ai4L952nP8uGVflvM8Uc0vefS9arjZmRZEfy5 uTIfE2BjqxlaG2HHc1nMITpeJdYmNVq48YSB+FHCaBnX4YWsqGFvJ79ttX4/0sKYN9XV xgR1rwVIUbE8HBPqts99c/4Nld1qufNnIonX3KofzeBOfMXvFx0E8KoW45wlAFQRoQmK i27YcSisH7FWG5FEa+aJqPdIUJJyWSgvRx4wzQXJ/6sUxGV0bzag8RatrhIi1TOtFxbp OokA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=excZmKHRlQ9ccSEQtwAhSppk4zJ9f55tt1Efb1ZYcGw=; b=Vk8738i52MApfbBaP6X4wMpm4m6j9FvJXHLpOjFERRwr8Rod2lkHrGGfvFYLxRdjKg TRHs08/gHASLz7PqbAdLx+zCipgQBCSM7qjd4LHCFaSFDrEWqntBL8QDmoZ/KKXEE6GX 2Pccxwt3KR4exncGWL0WGA48pdo5Ot4/J1Q2FiyRIs1wlY0wEhsZQTwUq3+c5lc04iEV 2/AHAG9trTg/xPY+nKA/KhKXQ0cuASTNxTuKPTp8XZlfDhZGMqKB1NICD/DZUvXszdU+ VIi/9fXzpswQTg7bsV/mD8s9tZi4kZEvUFXg3DzVtTs1TRX+qjNjh1YyCmKU2nFkrqCc /kPA== X-Gm-Message-State: AE9vXwM8jAHwxDBjMptgFheGTRomUl+hUOC2wtAbWROXIxRVRLzXDtR6OXg3hBYTmrEpir8iaiuC32fSz20rBQ== X-Received: by 10.28.28.70 with SMTP id c67mr458270wmc.8.1474327767670; Mon, 19 Sep 2016 16:29:27 -0700 (PDT) MIME-Version: 1.0 From: Sandro Date: Mon, 19 Sep 2016 23:29:16 +0000 Message-ID: Subject: 'Xset: Unable to open display' prevents connection To: submit@bugs.x2go.org Content-Type: multipart/alternative; boundary=001a1144fb74dfe4ac053ce4ae0a --001a1144fb74dfe4ac053ce4ae0a Content-Type: text/plain; charset=UTF-8 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. --001a1144fb74dfe4ac053ce4ae0a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Package: x2goserver
Version: 4.0.1.19

I have a Linux Mint 18 x2go client and a Debian Tes= ting x2go server. And I update both at random intervals.
Thin= gs 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&= #39;t exactly know when because I don't use x2go daily - I started gett= ing this error message.

Connection failed. xset: u= nable to open display ""=C2=A0

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

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


<= /div>

--001a1144fb74dfe4ac053ce4ae0a-- ------------=_1478790002-21462-0--