From owner-freebsd-questions@FreeBSD.ORG Tue Mar 8 08:38:29 2011 Return-Path: Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D651106564A for ; Tue, 8 Mar 2011 08:38:29 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4AFBB8FC0A for ; Tue, 8 Mar 2011 08:38:29 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-questions@FreeBSD.ORG with esmtp (envelope-from ) id <1PwsR2-0002d4-DZ>; Tue, 08 Mar 2011 09:38:28 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-questions@FreeBSD.ORG with esmtpsa (envelope-from ) id <1PwsR2-0007wB-A2>; Tue, 08 Mar 2011 09:38:28 +0100 Message-ID: <4D75EB04.7090704@zedat.fu-berlin.de> Date: Tue, 08 Mar 2011 09:38:28 +0100 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: Subject: xpdf can not print via cups if started from firefox X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2011 08:38:29 -0000 Hello. I've got a weird problem here. Very often I download scientific papers as pdf from protals and they got opened via firefox3 with the configured propper utility, in this case xpdf. In such a case, printing is impossible. I hit the print button, a popup shows up with the configured CUPS printing queue, but hitting OK doesn't have any effect. The funny thing is: when opening the same PDF (it is stored in /tmp/) with xpdf by starting xpdf from a terminal, printing on the same queue works well. I realized that the change of this behaviour occured a long time ago when the cups printing system got an update. I never figured out what's the diffrence between starting xpdf via terminal and starting via firefox. My first guess was that my local ~/.xpdfrc does have effect, as the right configured CUPS printing queue showed up, but even the firefox-started xpdf client shows the right printing queue, so this implies that xpdf also reads my ~/.xpdfrc. I'm not sure what's going wrong. I have no clue what kind of paper information is passed to xpdf by being called via firefox. Any help appreciated. Thanks, Oliver