From mikedep333@gmail.com Sat May 27 18:05:43 2017 Received: (at submit) by bugs.x2go.org; 27 May 2017 16:05:44 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) 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_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RCVD_IN_SORBS_SPAM autolearn=no autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 989A75DAD3 for ; Sat, 27 May 2017 18:05:43 +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 Oq4r3SliebMx for ; Sat, 27 May 2017 18:05:36 +0200 (CEST) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 9553D5DA96 for ; Sat, 27 May 2017 18:05:36 +0200 (CEST) Received: by mail-lf0-f48.google.com with SMTP id m18so18204787lfj.0 for ; Sat, 27 May 2017 09:05:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=rH60RFFt4Nb7YqKgegLRUuLymPe+evrmYBPKrmucHHA=; b=qhUB7uMfxZaLmyGlznOVgyXiP6I/xzZdESHgyBgO8rU47BAzeBGNgzjKkjRJ3lRQU6 /nHbosfS7VdsgBDmVA+LlSNH9sXTyXFnbzJt8w+g9Tzkn7+79+HIcK+aOSBpooqdzI6k 2lDi6XOzgXUANVHCmOSC0ex67R7uLhu1cyDtB2DGcY0lVd0XRrnPLdA5d/hber27qNuW 8bysFlHRpxj+KxerqY5cnzLav3WM3w63Z7bSdLWfp0k+/513mm7ZCjT7WIYxpqSm4vxA vZh71/mqt+nVtD2W6xhaZlCIY6p03pk+01tTzo6nAxZ6N4jtgRvIHx8VqgLneI8AkB1m EElw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rH60RFFt4Nb7YqKgegLRUuLymPe+evrmYBPKrmucHHA=; b=EuEPp0hoJXFlFPLjDoEN/SQ5kki/ZdGtxPToSvBTFdy9XUv+tLLX2iQtDj0BeZxUwC lGxbCGmjDm+rT4/Fzk9kLEDB/+S/llXJvLXtanW64KlZBJnPE/HSHOD/raJmK+RB3Wgl mByJJroFBKLkiyXv5BRYFGXL/wwUYxrI05jtUNKHJHKUaOMdGypet4qlifgyWSOjfSmT BhlJDnPJaZ4ZfYQxY2FZZPsgV5ZKgYd7enmGKQdibnC0gT1EKFoPPCGtwTR1lGcBfCzQ pwCItM7XN06oixG0KPXm2WnKJvdbcsBkicUnM+p85plZu9/ejdLDOrjfrJ1RtF/PR7Uq 84bA== X-Gm-Message-State: AODbwcDhzA1sOoWdv1ZNDNCtVpkKb/KRzNDQzJGiVhH2p+qq2aCwJlhc n3LJG36ofNuOsrHO7RV7lSlSDz865EIkHsI= X-Received: by 10.25.23.104 with SMTP id n101mr1630311lfi.93.1495901135898; Sat, 27 May 2017 09:05:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.221.212 with HTTP; Sat, 27 May 2017 09:05:35 -0700 (PDT) From: Mike DePaulo Date: Sat, 27 May 2017 12:05:35 -0400 Message-ID: Subject: Unable to logout of KDE4 when a PolicyKit prompt is up To: "submit@bugs.x2go.org" Content-Type: multipart/alternative; boundary="001a114056acd31b7c0550839fca" --001a114056acd31b7c0550839fca Content-Type: text/plain; charset="UTF-8" Package: nx-libs Version: 3.5.0.32 Note: This bug might actually be in x2goserver instead. Steps: 1. You connect to a KDE4 server 2. You maximize the session 3. #2 This triggers a PolicyKit prompt "Authentication is required to create a color managed device" 4. You select to log out of KDE 5. The screen does not turn black. There is a log out dialog, but it is actually hidden behind the PolicyKit prompt. 6. You are unable to click the log out button in the log out dialog because it is not visible. Hitting escape does not help either. You are unable to move the PolicyKit prompt. Note: In the absence of the PolicyKit dialog, the screen still does not turn black. Note: #3. Is a nuisance in and of itself. It is related to the fact that PolicyKit applies different rules for physical logins (active) vs remote logins (inactive.) It is especially a nuisance because you have to click "cancel" repeatedly. However, it is not what I am reporting as a bug. If you have a local session, this bug does not occur: 3. Trigger a PolicyKit prompt by opening up a terminal and running `pkexec vi` for example. 5. The screen turns black, and the log out dialog appears. 6. You click the log out button and all is well. This can be worked around by moving the PolicyKit prompt before logging out, or by hitting "cancel" repeatedly. I am confident this can be worked around also by writing new PolicyKit rules that prevent the "color managed device" prompt. I will post how soon. However, other PolicyKit prompts can presumably still cause this issue. Server configuration 1: CentOS 7.3 with KDE4 & EPEL's x2goserver 4.0.1.20-1.el7 & nxagent 3.5.0.32-3.el7 Server configuration 2: CentOS 7.3 with KDE4 & nightly x2goserver 4.1.0.0 & nxagent 3.5.99.7 (from the copr repo mikedep333/nx-libs-3.6) Client 1: Fedora 25 x64 with Fedora's x2goclient 4.1.0.0-1.fc25 & nxproxy 3.5.0.32-4.fc24 Client 2: Windows 10 1703 x64 with X2Go Client 4.1.0.0-2017.03.11 --001a114056acd31b7c0550839fca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Package: nx-libs
Version: 3.5.0.32

Note: This bug might actually be in x2goserver instead.
Steps:
1. You connect to a KDE4 server
= 2. You maximize the session
3. #2 This triggers a PolicyKit promp= t "Authentication is required to create a color managed device"
4. You select to log out of KDE
5. The screen does not t= urn black. There is a log out dialog, but it is actually hidden behind the = PolicyKit prompt.
6. You are unable to click the log out button i= n the log out dialog because it is not visible. Hitting escape does not hel= p either. You are unable to move the PolicyKit prompt.

=
Note: In the absence of the PolicyKit dialog, the screen still does no= t turn black.

Note: #3. Is a nuisance in and of it= self. It is related to the fact that PolicyKit applies different rules for = physical logins (active) vs remote logins (inactive.) It is especially a nu= isance because you have to click "cancel" repeatedly. However, it= is not what I am reporting as a bug.

If you have = a local session, this bug does not occur:
3. Trigger a PolicyKit = prompt by opening up a terminal and running `pkexec vi` for example.
5. The screen turns black, and the log out dialog appears.
6. You click the log out button and all is well.

This can be worked around by moving the PolicyKit prompt before logging ou= t, or by hitting "cancel" repeatedly.

I = am confident this can be worked around also by writing new PolicyKit rules = that prevent the "color managed device" prompt. I will post how s= oon. However, other PolicyKit prompts can presumably still cause this issue= .

Server configuration 1: CentOS 7.3 with KDE4 &am= p; EPEL's=C2=A0x2goserver=C2=A04.0.1.2= 0-1.el7 & nxagent=C2=A03.5.0.32-3.el7
Server configuration 2:=C2=A0CentOS 7.3 with KDE4 &= amp; nightly x2goserver 4.1.0.0=C2=A0&= nxagent 3.5.99.7 (from the copr repo=C2=A0mikedep333/nx-libs-3.6)
Client 1: Fedora 25 x64 with Fedo= ra's x2goclient 4.1.0.0-1.fc25 & nxproxy 3.5.0.32-4.fc24
Client 2: Windows 10 1703 x64 with = X2Go Client 4.1.0.0-2017.03.11
--001a114056acd31b7c0550839fca--