From jrpique@baseinf.com Fri Dec 23 17:27:36 2016 Received: (at 1125) by bugs.x2go.org; 23 Dec 2016 16:27:38 +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=-1.9 required=3.0 tests=BAYES_00,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 19B285DAA3 for <1125@bugs.x2go.org>; Fri, 23 Dec 2016 17:27:36 +0100 (CET) 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 lKsCu2Zas-9T for <1125@bugs.x2go.org>; Fri, 23 Dec 2016 17:27:29 +0100 (CET) Received: from vz10.tacf.cat (vz10.tacf.cat [188.165.128.192]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 759BE5DA86 for <1125@bugs.x2go.org>; Fri, 23 Dec 2016 17:27:28 +0100 (CET) Received: (qmail 23745 invoked from network); 23 Dec 2016 16:27:28 +0000 Received: from 204.red-79-158-197.dynamicip.rima-tde.net (HELO xiket) (79.158.197.204) by vz10.tacf.cat with ESMTPA; 23 Dec 2016 16:27:28 +0000 Date: Fri, 23 Dec 2016 17:27:26 +0100 From: JR To: Chris , 1125@bugs.x2go.org, dpbasti@wp.pl Subject: Re: [X2Go-Dev] Bug#1125: Remote printing not working in Debian Jessie Message-Id: <20161223172726.e8ea0090d87618a3db54a6d3@baseinf.com> In-Reply-To: References: <20161216204146.f1bdcc0b625a16e446cca0f3@baseinf.com> <20161221120010.0529e0c60bb46f612cf6d87b@baseinf.com> <3455d80c-adac-38b0-edc3-037a6a675e1a@hemsing.eu> <10088227.bKZboZK6FI@laprus> Organization: Base =?UTF-8?B?aW5mb3Jtw6B0aWNhLA==?= SCP X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.23; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-PPP-Message-ID: <20161223162728.23743.14186@vz10.tacf.cat> X-PPP-Vhost: baseinf.com Chris, I've seen. This workaround about bug 694 allows print remotely from linux. Sebastian, really in my tests from Windows 10 and 8.1 I was suffering bug 1105. I've done some testing and it seems that the problem to print remotely from Windows is x2goclient version 4.0.5.2. With older versions I believe that I have not experienced this problem. With nightly version 4.0.5.3 remote printing from Windows (XP / 8.1) works perfectly for me. Thank you very much to all for your help. JR On Wed, 21 Dec 2016 19:17:49 +0100 Chris wrote: > In case it is a standard jessie cups installation without the workaround I > described in bug 694, then it just cannot work! > Cups remounts /tmp! > > BR > Chris > > > On 21/12/16 18:21, Sebastian T. wrote: > > or a lack of reverse tunnel can also cause printing issue as I reported here > > http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1105 > > > > fix is already committed but not yet in release. > > > > Dnia środa, 21 grudnia 2016 12:30:56 CET Chris pisze: > >> Hi JR, > >> > >> have you read: > >> http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=694 > >> > >> That buf has been there since 2014. Nobody cares. > >> It might be your problem. > >> > >> BR > >> Chris > >> > >> Am 21.12.2016 um 12:00 schrieb JR: > >>> Hi Stefan, > >>> > >>> I tried the options discussed without success. > >>> It is strange, perhaps this Windows XP has a problem. > >>> So I can I will test different scenarios and I will notify the results. > >>> > >>> Thank you very much. > >>> > >>> Kind Regards, > >>> > >>> JR > >>> > >>> On Mon, 19 Dec 2016 19:48:37 +0100 > >>> > >>> Stefan Baur wrote: > >>>> Am 16.12.2016 um 20:41 schrieb JR: > >>>>> Package: cups-x2go > >>>>> Version: 3.0.1.3-0x2go1+git20161129.135+8.main.1 > >>>>> > >>>>> I tried printing on the local PC from the x2goclient without success. > >>>>> x2goclient gives no message. > >>>>> > >>>>> I installed x2goserver-printing, cups, cups-x2go and I have installed > >>>>> x2go virtual printer. > >>>>> > >>>>> This happens to me only in Q4OS 1.18-Orion (Debian Jessie based). In > >>>>> Q4OS 2.2-Scorpion (Debian Stretch based) it works perfectly. > >>>>> > >>>>> For more details, please give a look at: > >>>>> > >>>>> http://www.q4os.org/forum/viewtopic.php?id=1261 > >>>> I followed that thread and the reason why you can't print at all is > >>>> SystemD-related, not X2Go-related. For various reasons, I don't think > >>>> too highly of SystemD, and I strongy doubt that we'll add a patch to > >>>> X2Go to fix something that is actually SystemD's fault. > >>>> > >>>> Now, why you still can't print from Windows XP after applying that > >>>> configuration change, that's another issue, and one that will have to be > >>>> investigated. > >>>> > >>>> Please check that the settings under Options/Settings/Printing match > >>>> between your Linux client (where remote printing works after applying > >>>> the fix) and your Windows client for your initial test. > >>>> > >>>> After that, please try changing the Windows client setting to "View as > >>>> PDF" instead of printing directly. If that doesn't work, either, then > >>>> you're either missing a default PDF viewing/printing application (you > >>>> can try SumatraPDF if you don't want something as bloated as Adobe > >>>> Reader) on the client, or there's something wrong in getting the data > >>>> processed. > >>>> > >>>> For that, I would suggest running the debug version of X2GoClient.exe > >>>> and logging its output to a file, then attaching that file to the bug > >>>> report by e-mailing it to: 1125@bugs.x2go.org > >>>> > >>>> Kind Regards, > >>>> Stefan Baur > >>> _______________________________________________ > >>> x2go-dev mailing list > >>> x2go-dev@lists.x2go.org > >>> http://lists.x2go.org/listinfo/x2go-dev > >> _______________________________________________ > >> x2go-dev mailing list > >> x2go-dev@lists.x2go.org > >> http://lists.x2go.org/listinfo/x2go-dev > _______________________________________________ > x2go-dev mailing list > x2go-dev@lists.x2go.org > http://lists.x2go.org/listinfo/x2go-dev