From unknown Mon Apr 27 18:54:51 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#694: Another workaround Reply-To: Chris , 694@bugs.x2go.org Resent-From: Chris Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Sun, 10 Jul 2016 10:50:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 694 X-X2Go-PR-Package: cups-x2go X-X2Go-PR-Keywords: Received: via spool by 694-submit@bugs.x2go.org id=B694.146814776015266 (code B ref 694); Sun, 10 Jul 2016 10:50:01 +0000 Received: (at 694) by bugs.x2go.org; 10 Jul 2016 10:49:20 +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 autolearn=ham version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 005F75DDF5 for <694@bugs.x2go.org>; Sun, 10 Jul 2016 12:49:18 +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 Sh9IfU6zv1jT for <694@bugs.x2go.org>; Sun, 10 Jul 2016 12:49:11 +0200 (CEST) Received: from s2.spam-free.eu (s2.spam-free.eu [195.5.121.125]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 781FA5DDD0 for <694@bugs.x2go.org>; Sun, 10 Jul 2016 12:49:11 +0200 (CEST) Received: from [192.168.129.190] (p54B451A7.dip0.t-ipconnect.de [84.180.81.167]) by s2.spam-free.eu (Postfix) with ESMTPSA id 2084F1AAFA2 for <694@bugs.x2go.org>; Sun, 10 Jul 2016 12:49:11 +0200 (CEST) To: 694@bugs.x2go.org From: Chris Message-ID: <57822826.3020604@hemsing.eu> Date: Sun, 10 Jul 2016 12:49:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit After years this important issue is still there... On debian jessie one can do: Change /etc/systemd/system/printer.target.wants/cups.service from PrivateTmp=true to PrivateTmp=false I don't really see a necessity for a private tmp anyway ... **** Apart from the workaround, I would say: why use /tmp for the spool area mount points on the server side in the first place? The directories are being owned by the respective user anyway. Why not use the user's home directory under ~/.x2go? Then this problem would be solved without touching x2goserver-printing nor cups-x2go nor the operating system (see the workaround). Chris P.S.: My lack of knowledge: why has the printing be divided in cups-x2go and x2goserver-printing? Why not one package?