From unknown Sat May 16 11:06:43 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#139: [X2Go-Dev] Bug#139: Reply-To: "Gross, Christopher W. (Chris)" , 139@bugs.x2go.org Resent-From: "Gross, Christopher W. (Chris)" Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Mon, 16 Sep 2013 12:48:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 139 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 139-submit@bugs.x2go.org id=B139.13793352062292 (code B ref 139); Mon, 16 Sep 2013 12:48:02 +0000 Received: (at 139) by bugs.x2go.org; 16 Sep 2013 12:40:06 +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.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, T_FILL_THIS_FORM_SHORT,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by ymir (Postfix) with ESMTPS id A04A25DA79 for <139@bugs.x2go.org>; Mon, 16 Sep 2013 14:40:04 +0200 (CEST) Received: from mail221-va3-R.bigfish.com (10.7.14.254) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.22; Mon, 16 Sep 2013 12:40:03 +0000 Received: from mail221-va3 (localhost [127.0.0.1]) by mail221-va3-R.bigfish.com (Postfix) with ESMTP id 7A0F6C02FD; Mon, 16 Sep 2013 12:40:03 +0000 (UTC) X-Forefront-Antispam-Report: CIP:164.107.81.208;KIP:(null);UIP:(null);IPV:NLI;H:cio-krc-pf01;RD:none;EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(zz98dI9371Ic89bh936eIc85dhzz1f42h1d77h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h17326ah18c673h1de097h186068hz2fh2a8h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h20f0h1b1bi1155h) Received-SPF: pass (mail221-va3: domain of osu.edu designates 164.107.81.208 as permitted sender) client-ip=164.107.81.208; envelope-from=gross.364@osu.edu; helo=cio-krc-pf01 ;cio-krc-pf01 ; Received: from mail221-va3 (localhost.localdomain [127.0.0.1]) by mail221-va3 (MessageSwitch) id 1379335166390094_19374; Mon, 16 Sep 2013 12:39:26 +0000 (UTC) Received: from VA3EHSMHS026.bigfish.com (unknown [10.7.14.239]) by mail221-va3.bigfish.com (Postfix) with ESMTP id 51389440048; Mon, 16 Sep 2013 12:39:26 +0000 (UTC) Received: from cio-krc-pf01 (164.107.81.208) by VA3EHSMHS026.bigfish.com (10.7.99.36) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 16 Sep 2013 12:39:26 +0000 Received: from CIO-KRC-HT01.osuad.osu.edu (localhost [127.0.0.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by cio-krc-pf01 (Postfix) with ESMTPS id 824FBA0050; Mon, 16 Sep 2013 08:39:25 -0400 (EDT) Received: from CIO-KRC-D1MBX04.osuad.osu.edu ([fe80::d025:f47e:cbe9:18b]) by CIO-KRC-HT01.osuad.osu.edu ([fe80::6d8f:7dea:5691:1620%12]) with mapi id 14.03.0123.003; Mon, 16 Sep 2013 08:39:25 -0400 From: "Gross, Christopher W. (Chris)" To: Moritz Struebe CC: "<139@bugs.x2go.org>" <139@bugs.x2go.org>, "" Thread-Topic: [X2Go-Dev] Bug#139: Thread-Index: AQHOstE0HorZ5qU3rkWrZtQBE+ggnpnIjNuAgAAEHAA= Date: Mon, 16 Sep 2013 12:39:25 +0000 Message-ID: References: <5236F889.4090401@informatik.uni-erlangen.de> In-Reply-To: <5236F889.4090401@informatik.uni-erlangen.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.146.220.206] Content-Type: multipart/alternative; boundary="_000_C873205AEA1C844AA36A68A66637C180819C3D6FCIOKRCD1MBX04os_" MIME-Version: 1.0 X-CFilter-Loop: Forward X-OriginatorOrg: osu.edu X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% --_000_C873205AEA1C844AA36A68A66637C180819C3D6FCIOKRCD1MBX04os_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes, yes, we know. The software is free. Every time anyone expresses concer= n with something like the, this is the argument that comes forth, which sud= denly makes our concerns invalid if we don't suddenly know how to fix the p= roblem ourselves in a language we're not familiar with. I am grateful for t= he software, but as a developer myself, I find that programmers are way too= sensitive to criticism. Sometimes users get upset when glaring issues are = put on the back burner while other, much less severe bugs are added to new = releases. It's going to happen and it's a critical part of the feedback and= development cycle. Never is "why don't you fix it yourself?" a proper resp= onse. On Sep 16, 2013, at 8:24 AM, Moritz Struebe > wrote: On 2013-09-16 13:38, Gross, Christopher W. (Chris) wrote: This is very disappointing. It's been 6 months since this report was filed (and since the last release) and even though it was acknowledged in July, it still was not fixed in the current version. Will we be stuck with this bug for another six months? Filing and acknowledging bugs does not fix them. You get X2Go for free, thus I can see no justification for you to complain. Instead of whining you could give something back to those people who spent many hours working on X2Go for free(!). Either by providing a patch your self or by putting out a bounty. Morty -- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl f=FCr Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universit=E4t Erlangen-N=FCrnberg Martensstr. 1 91058 Erlangen Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty --_000_C873205AEA1C844AA36A68A66637C180819C3D6FCIOKRCD1MBX04os_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable Yes, yes, we know. The software is free. Every time anyone expresses concer= n with something like the, this is the argument that comes forth, which sud= denly makes our concerns invalid if we don't suddenly know how to fix the p= roblem ourselves in a language we're not familiar with. I am grateful for the software, but as a developer myse= lf, I find that programmers are way too sensitive to criticism. Sometimes u= sers get upset when glaring issues are put on the back burner while other, = much less severe bugs are added to new releases. It's going to happen and it's a critical part of the feed= back and development cycle. Never is "why don't you fix it yourself?&q= uot; a proper response.


On Sep 16, 2013, at 8:24 AM, Moritz Struebe <Moritz.Struebe@informatik.uni-erlang= en.de> wrote:

On 2013-09-16 13:38, Gross, Christopher W. (Chris= ) wrote:
This is very disappointing. It's been 6 months si= nce this report was
filed (and since the last release) and even though it was acknowledged
in July, it still was not fixed in the current version. Will we be
stuck with this bug for another six months?

Filing and acknowledging bugs does not fix them. You get X2Go for free,
thus I can see no justification for you to complain. Instead of whining
you could give something back to those people who spent many hours
working on X2Go for free(!). Either by providing a patch your self or by putting out a bounty.

Morty

--
Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter)
Lehrstuhl f=FCr Informatik 4 (Verteilte Systeme und Betriebssysteme)
Friedrich-Alexander-Universit=E4t Erlangen-N=FCrnberg
Martensstr. 1
91058 Erlangen

Tel   : +49 9131 85-25419
Fax   : +49 9131 85-28732
eMail : struebe@infor= matik.uni-erlangen.de
WWW   : http://www4.informatik.uni-erlangen.de/~morty




--_000_C873205AEA1C844AA36A68A66637C180819C3D6FCIOKRCD1MBX04os_--