From owner-freebsd-questions@freebsd.org Wed Dec 20 15:29:13 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90224E8FBCB for ; Wed, 20 Dec 2017 15:29:13 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC23A7397B for ; Wed, 20 Dec 2017 15:29:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from hermann ([141.89.176.204]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LvPgd-1f9MyU1LZT-010fh7 for ; Wed, 20 Dec 2017 16:29:09 +0100 Date: Wed, 20 Dec 2017 16:29:08 +0100 From: "Hartmann, O." To: freebsd-questions@freebsd.org Subject: printing problems: CUPS, claws-mail, firefox and xpdf-4 Message-ID: <20171220162908.445ef8c6@hermann> Organization: walstatt.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:fWZWnjz4F/Yw0uuMndNiwJzRTeh2KcnNH9Q+bV+NcvYfnyhE+cw 4SRyGsVGc1tUp8CgxORS8OVYfYLBKITqT7g8gHt9jV2fQxfdPhnR1BPVx7X7MzFw1Zu8735 sZ3Vg7rN0WlryNYx2jc28NKzZZ3AzToNRtiEr8uPijm21Ik0Que2Odp6fDzcv/hZbOdZBwp 9Dp4/3zjPaRv/at/PIJow== X-UI-Out-Filterresults: notjunk:1;V01:K0:Cp+GCOpVrTQ=:eE4Xw2/KJWmJXxvHsRLQYD nF1fh6bmETKxDw/3sOmL8ORHmO/vTzBiny15gAY/rFOUFXEg3WTq3zFt/HUIDJwN7MC+H1jWy 1K2yWja+ArGnceMjQsFS7WxfW8Q5bNrizbQJDB/Wa9rBSNBpoGBVjJMwa4LkOE15gBRCldgEx 1KvUfjKgCLeHQkEGPYwY0UK2ploJzVwI+HJNNY2CsUrqcZox/3dhapwtuNeeKANBnZAppgzFv f/15ab7WczWMbrJmJ3wy3I+2aN4q07Kr60AoKCjJzGdgUrXyUwM/tHpADV52fAyUrA4jmhFPG rLG/Q94KtFZ77B80KEJrESWdqg9YGLt7c//qPahyYr1kPUzca0EeE5EeLUYjAyk9L1Q1ro8r5 A5McHwLaA6N0SCYNoqQkLd45xCR9m9LyidAOkVYiR/9LbwpKsIzQKFcU4phLWBc1YbHPjSooX +wFIxnr8JCKeZsvRr5AtUNdz8dt1ZWLq2I1MZOnIfwWJEU30y0zssR0OxXEYmrI4JsCdX5Do8 8eZXduWk2e7aVZMMpSscLVdchy+aR7mnOsjGd9XkscMkqEvgIkiZvr7hUFg2Yv1oWLYqam/yx OIxexJNWL0xju4/CS1sQSViid+ap5QaHt6zTm5/Z+IOrUXqpDcF03gtjb8spoTge04AYZYCoD 6yIF3QKsPTcV57StRWYk0FYAYFf1LpbHivrHxBEUou+Vkby8nfR8/QQgqAkAkAjJ/mEWWzQGq YvHYn6D9zclOqWXoJgLXAbbAN1B6+T0486j1QDvg3RcnsfOxk8s5Fde0U1wEOaBKiY6ysoV4P tivQlMjzIKPCqsbI228qo5UlEw7t18JDiGWwraT3xukA6vhR/g= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 15:29:13 -0000 At first, please CC me in your response, I'm not subscribing to the list. I have problems printing on FreeBSD CURRENT (12.0-CURRENT #37 r327022: Wed Dec 20 15:07:55 CET 2017 amd64). print/cups, graphics/xpdf, mail/claws-mail and www/firefox are of most recent version as of usr/ports revvision r456793. The phenomenon is that I can not print via firefox' printing facility (printer symbol which should open a requester showing all the available printers), neither via xpdf or claws-mail. CUPS is up and running ans sockstat indicates, that cupsd is listening USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root cupsd 28838 5 tcp4 127.0.0.1:631 *:* root cupsd 28838 7 stream /var/run/cups.sock Connecting via firefox and https://localhost:631 works, also printing a testpage to any printer configured. The not-so-funny part is that either claws-mail, xpdf or firefox' printing facility seem to take a long time when selected from menu, showing then nothing but printing to file. In firefox, it takes ages to come up with this residual set of printing options, xpdf and claws-mail are a bit faster. =46rom the console, lpstat -a shows every configured printer and printing PS or PDF to a queue from a xterm or console works as expected. =46rom a Linux forum I gathered some pieces of information regarding the fact that possibly gtk3 problems may the reason but recompiling the usual suspicious ports didn't help, even recompiling firefox, xpdf or claws-mail or poppler/podofo didn't change the situation. I'm out of ideas. Maybe somebody faces the same problem and has some hints - I'd appreciate any tip. Thanks in advance, Oliver