X2Go Bug report logs - #616
x2goclient.exe 4.0.3.0 shows "arrow and hourglass" cursor for 5 seconds during startup

version graph

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

Affects: x2goclient

Reported by: Stefan Baur <newsgroups.mail2@stefanbaur.de>

Date: Sat, 28 Jun 2014 17:45:01 UTC

Severity: normal

Tags: pending

Found in version 4.0.3.0-2014.09.17-0e3aff0

Fixed in version 4.0.3.2

Done: X2Go Release Manager <git-admin@x2go.org>

Bug is archived. No further changes may be made.

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#616: Finally managed to record the issue "on tape"
Reply-To: Michael DePaulo <mikedep333@gmail.com>, 616@bugs.x2go.org
Resent-From: Michael DePaulo <mikedep333@gmail.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 09 Jan 2015 14:00:02 +0000
Resent-Message-ID: <handler.616.B616.142081184826011@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 616
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 616-submit@bugs.x2go.org id=B616.142081184826011
          (code B ref 616); Fri, 09 Jan 2015 14:00:02 +0000
Received: (at 616) by bugs.x2go.org; 9 Jan 2015 13:57:28 +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=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
	T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 14D375DEA9
	for <616@bugs.x2go.org>; Fri,  9 Jan 2015 14:57:27 +0100 (CET)
Received: by mail-we0-f180.google.com with SMTP id w62so8096836wes.11
        for <616@bugs.x2go.org>; Fri, 09 Jan 2015 05:57:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=ShwZZueojSCKLq42H9DBKwnL8jkzPMm4KSnQx9f8OFs=;
        b=oHwTQaxtpmHRs5UwA/PEQQwUfMEp2MelrU4KkM44L+5VWo5TPOMvt6HFTuvXO/PHUS
         jFlvV5/mj3wkR0dc1AUlbIhrT/53gGntID31AEdtcDyLvOGl/QxsIDHVJYU0YZNjYD+y
         Ksy6t+fgelz79OlMdvvlQ+wze/yVsYE669maQlmVVbDR/Kmp2YJDUJULWvlxU1KCCHgK
         M7mXSzF1F1/CqsYJE/LscoBsa9e/sL4J9WzlzYlTgrjYLJd9GiCU2XEpHJ8qRJje8eUE
         S0T2IzqhxmA6Cfm69Oy8g5nSuc30sEdwKVYoxgICkbFBCG1BR1QCvjhFCatU5pHVwuSn
         pWVQ==
MIME-Version: 1.0
X-Received: by 10.180.90.206 with SMTP id by14mr5238068wib.67.1420811846727;
 Fri, 09 Jan 2015 05:57:26 -0800 (PST)
Received: by 10.180.90.116 with HTTP; Fri, 9 Jan 2015 05:57:26 -0800 (PST)
In-Reply-To: <54AF9FA0.20307@phoca-gmbh.de>
References: <5447C574.2040801@baur-itcs.de>
	<54734302.1060802@phoca-gmbh.de>
	<54AEB57D.9050200@baur-itcs.de>
	<54AF9FA0.20307@phoca-gmbh.de>
Date: Fri, 9 Jan 2015 08:57:26 -0500
Message-ID: <CAMKht8jGyvO7NU49pqgf0RFs0Vzm2wokg3=ebneZnE8EKt4GJw@mail.gmail.com>
From: Michael DePaulo <mikedep333@gmail.com>
To: Oleksandr Shneyder <o.shneyder@phoca-gmbh.de>
Cc: Stefan Baur <X2Go-ML-1@baur-itcs.de>, 616@bugs.x2go.org, 
	Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Content-Type: text/plain; charset=UTF-8

The way I see it, there are 2 parts of the issue.

1. Something is happening for 5 seconds.
2. During those 5 seconds, X2Go Client is displaying the Hourglass-and-Pointer.

We should be able to fix the issue by solving either part.

Perhaps there is some Qt feature we need to adjust in order to fix part #2?

-Mike#2

On Fri, Jan 9, 2015 at 4:30 AM, Oleksandr Shneyder
<o.shneyder@phoca-gmbh.de> wrote:
> Hello Stefan,
>
> Actually, I don't see it as a problem at all, but I understand your
> point. I'll see, what I can do about it.
>
> regards,
> Alex
>
> Am 08.01.2015 um 17:51 schrieb Stefan Baur:
>> Am 24.11.2014 um 15:38 schrieb Oleksandr Shneyder:
>>
>>> I tried to launch newest client from nightly builds on Win7. I see
>>> a "waiting" pointer on the start of x2go client. But in this time I
>>> can use X2Go Client without problem and UI is responsible at that
>>> time. Did I understand you right? You have 5 sec. delay and during
>>> this delay you can't use a UI?
>>
>> Sorry for not replying sooner.  No, we're talking about the same
>> cursor.  "Hourglass-and-Pointer", not "Hourglass".
>>
>> So while yes, one can use the UI during these 5 seconds, it
>> nevertheless is confusing to the user.  The initial reaction of the
>> average user is "Oh, that thing's busy, I should wait".  A
>> non-technical user will not differentiate between
>> "Hourglass-and-Pointer" and "Hourglass".
>>
>> Since previous versions of X2GoClient did not exhibit this behavior, I
>> am expecting complaints about a sudden slow startup (from
>> non-technical users, that are not aware of the difference between
>> those two cursor types) when I roll this thing out.
>>
>> Is there no way we can avoid this? Maybe start the background
>> processes and the reaper only when a session is in the startup phase,
>> and not immediately when x2goclient.exe start?
>>
>> -Stefan
[...]

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 19:28:23 2024; 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.