From unknown Tue May 19 07:01:29 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1046: x2go session causes dbus conflicts with logged in desktop on Fedora 24 Reply-To: Andy Wang , 1046@bugs.x2go.org Resent-From: Andy Wang Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Sat, 25 Jun 2016 03:35:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: report 1046 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: Received: via spool by submit@bugs.x2go.org id=B.146682545224984 (code B); Sat, 25 Jun 2016 03:35:01 +0000 Received: (at submit) by bugs.x2go.org; 25 Jun 2016 03:30:52 +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=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 28EEE5DDD4 for ; Sat, 25 Jun 2016 05:30:51 +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 h94UN6BhUamP for ; Sat, 25 Jun 2016 05:30:44 +0200 (CEST) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 636515DA97 for ; Sat, 25 Jun 2016 05:30:44 +0200 (CEST) Received: by mail-io0-f179.google.com with SMTP id t74so114361730ioi.0 for ; Fri, 24 Jun 2016 20:30:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=moonteeth-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=O7C09qTWaLM80PeftIGfJvXf08rGcKsT8VHSQwXDDr8=; b=Ee7vH02hL/FZVS1W3RPtGCSd/rXITERXM4/Dki76VuW5zGEBaRrCshabkHSnDbo/+i r+1+SLb1l5oPIrrXtBYq3Y8DjDxVAb4OFurzGvMaByh2Enwo/VvH+fFUbmTj9B89lLec DCHZF3sOHfK1DzbkAoITwzAhAnXsu9D4jROuWsd63deOGPwXyW2cFbf2vWGPP+wMfd7k QUBwdrgGo52ofLdE5gE62yIPF2ea47ajg9J+OkYAbTnQJAxeJcvlbkOi5IBKIxR2npQf 4R8xD7nQZ7NVcoiISz2GGbTkFhbQOPApRoiJfI9HoVdhP8thCnNRV786b6y07n+6y3cW S9RQ== 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=O7C09qTWaLM80PeftIGfJvXf08rGcKsT8VHSQwXDDr8=; b=UD0MremsNwzShczJVifc7BrFL4UN5ffOuGxeoezKgv7wy8dfNdrll3hU13DB5qSAE+ R48JOLH1VtsDsUK2mRPmC8Zgdy7sB4JjQYLEZ3PBD+7jRMBKKBTNL4JkprS/QpRosOVF +OYxWcL6/1Xuf3BZAtlH6N0EqixUAh7vtHcZkGec/SBI838O7ywUkSrCPRlQTCnukzGm WyGUk4J2+E3m98C/clgwZ9rvyhGS+ZBaBONHR6aDxhXg+pDaJ5E0z+uTXLIJNMv39wnS 82CpxF5VBDHQCrvbXt3FYnEhMQOHAXfXhaRsWkExQoYVZ4X/Ld2Ev2vhlI0Hi+vNMu0N 6yiA== X-Gm-Message-State: ALyK8tKDUbWzLHx+qrJRLz4fvt6FIUip7ElFPeZgDc0Q+z81LG//QDOYnHkINnwh4BZKYfoxucDowppYjtPReQ== X-Received: by 10.107.36.198 with SMTP id k189mr8505270iok.176.1466825443107; Fri, 24 Jun 2016 20:30:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.67.74 with HTTP; Fri, 24 Jun 2016 20:30:42 -0700 (PDT) X-Originating-IP: [2602:43:4d0:9100:915c:b456:b330:7792] From: Andy Wang Date: Fri, 24 Jun 2016 22:30:42 -0500 Message-ID: To: submit@bugs.x2go.org Content-Type: multipart/alternative; boundary=001a1140ebaa7c17b1053611e984 --001a1140ebaa7c17b1053611e984 Content-Type: text/plain; charset=UTF-8 Package: x2goserver Version: 4.0.1.19-8.fc24 When attempting to login with a client desktop session that uses dbus while logged in as the same user on the console causes an error to appear in a pop up window: Could not acquire name on session bus You can dismiss the error but the desktop never full starts and attempts to logout triggers the logout on the console session. >From the error, I this appears to be resolved by using a custom session script in x2go and making sure to call: unset DBUS_SESSION_BUS_ADDRESS For example: #!/bin/sh unset DBUS_SESSION_BUS_ADDRESS # redirect to /dev/null due to x2go bug 914 /usr/bin/mate-session > /dev/null Doing some digging, it looks like the dbus socket (/usr/lib/systemd/user/dbus.socket) on fedora 24 (dbus-1.11.2-1.fc24.x86_64) does this: ExecStartPost=-/usr/bin/systemctl --user set-environment DBUS_SESSION_BUS_ADDRESS=unix:path=%t/bus And sets the DBUS_SESSION_BUS_ADDRESS for all logins for your user. This same workaround appears to be what tigervnc used as their permanent solution: https://github.com/TigerVNC/tigervnc/commit/c071e493a093d7ee9a568729dd2e151f5cd3d749 So I think this is the proper solution. FYI, a bug was filed against Fedora as well: https://bugzilla.redhat.com/show_bug.cgi?id=1350004 --001a1140ebaa7c17b1053611e984 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Package: x2goserver
Version: 4.0.1.19-8.fc24

When attempting to login with a client desktop session that= uses dbus while logged in as the same user on the console causes an error = to appear in a pop up window:
Could not acquire name on session b= us

You can dismiss the error but the desktop never= full starts and attempts to logout triggers the logout on the console sess= ion.

From the error, I this appears to be resolved= by using a custom session script in x2go and making sure to call: unset DB= US_SESSION_BUS_ADDRESS

For example:
#!/bin/sh
unset DBUS_SESSION_BUS_ADDRESS
# redirect to= /dev/null due to x2go bug 914
/usr/bin/mate-session > /dev/nu= ll

Doing some digging, it looks like the dbu= s socket (/usr/lib/systemd/user/dbus.socket) on fedora 24 (dbus-1.11.2-1.fc= 24.x86_64) does this:
ExecStartPost=3D-/usr/bin/systemctl --user = set-environment DBUS_SESSION_BUS_ADDRESS=3Dunix:path=3D%t/bus

And sets the DBUS_SESSION_BUS_ADDRESS for all logins for yo= ur user.

This same workaround appears to be what t= igervnc used as their permanent solution:

So I think this is the proper sol= ution.

FYI, a bug was filed against Fedora as well= :
 --001a1140ebaa7c17b1053611e984--