From unknown Mon Apr 06 09:03:48 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#139: x2goclient: No keyboard input at login on OSX Reply-To: "Matthew L. Dailey" , 139@bugs.x2go.org Resent-From: "Matthew L. Dailey" Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Mon, 20 May 2013 20:18: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.13690806492743 (code B ref 139); Mon, 20 May 2013 20:18:02 +0000 Received: (at 139) by bugs.x2go.org; 20 May 2013 20:10:49 +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.3 required=5.0 tests=RCVD_IN_DNSWL_MED autolearn=ham version=3.3.2 X-Greylist: delayed 1107 seconds by postgrey-1.34 at ymir; Mon, 20 May 2013 22:10:48 CEST Received: from mailhub2.dartmouth.edu (mailhub2.dartmouth.edu [129.170.17.107]) by ymir (Postfix) with ESMTPS id C01AC5DB13 for <139@bugs.x2go.org>; Mon, 20 May 2013 22:10:48 +0200 (CEST) Received: from schultz.kiewit.dartmouth.edu (Schultz.Kiewit.dartmouth.edu [129.170.70.6]) (authenticated bits=0) by mailhub2.dartmouth.edu (8.13.5/DND2.0/8.13.5) with ESMTP id r4KJq7FD004377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <139@bugs.x2go.org>; Mon, 20 May 2013 15:52:07 -0400 From: "Matthew L. Dailey" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Date: Mon, 20 May 2013 15:52:07 -0400 To: 139@bugs.x2go.org Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) X-MailScanner: Found to be clean by mailhub2.dartmouth.edu X-MailScanner-From: matthew.l.dailey@dartmouth.edu Greetings, I just wanted to report that we're seeing this identical behavior, but = in a slightly different way on our Mac OS X clients that are *not* = running in broker mode. When we run the client, everything works well and we are able to start a = session. However, if we either terminate or suspend the session, we are = no longer able to enter a password in the dialog. The cursor is blinking = in the password field, but no characters can be entered. All other = functionality seems to work, however - other sessions can be clicked on = the right side and settings of sessions can be edited. The workaround is = to quit and restart the client. I had a look at the x2goclient code, and this is a bit out of my league, = but something that looked suspicious to me on first glance was = passForm->setEnabled() in onmainwindow.cpp. I wonder if this is getting = set to false when then session runs and then not getting set back to = true when the session ends or is suspended. Just a thought... Please let me know if you need any other info to help track this down. --=20 Matthew L. Dailey Systems Administrator Thayer School of Engineering Dartmouth College=