Date: Fri, 11 Mar 2011 07:41:09 +0100 From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: xpdf can not print via cups if started from firefox Message-ID: <4D79C405.6030201@mail.zedat.fu-berlin.de> In-Reply-To: <20110311011336.51d0ce9a.freebsd@edvax.de> References: <4D75EB04.7090704@zedat.fu-berlin.de> <alpine.BSF.2.00.1103080850170.9758@wonkity.com> <4D78AA1B.3000000@zedat.fu-berlin.de> <20110311011336.51d0ce9a.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/11/11 01:13, Polytropon wrote: > On Thu, 10 Mar 2011 11:38:19 +0100, "O. Hartmann"<ohartman@zedat.fu-berlin.de> wrote: >> On 03/08/11 16:51, Warren Block wrote: >>> On Tue, 8 Mar 2011, O. Hartmann wrote: >>> >>>> 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. >>> >>> In your .xpdfrc, do you specify a full path to the CUPS lpr? >> >> I did now and it hasn't any effect. > > Maybe you're experiencing a caching problem? I would guess > that as you stated there is a temporary file, this should > not happen (in relation to Firefox) there should at least > be an error message. > > Did you try to enter the full command into xpdf's printing > dialog, e. g. "/usr/local/bin/lpr -P<printer>", just in case > the .xpdfrc setting hasn't been read upon program start? > > > Yes, I did, still the same problem. I have the strange feeling that a firefox-started xpdf doesn't know anything about CUPS and its printing queues. I try to figure out how to log this ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D79C405.6030201>