Hi,

** Reply to message from Francesco Scaglioni on Tue, 23 Nov 2004 10:05:47 +0000 (GMT)

...

Have done exactly that and any attempt to print ( or even selecting page setup ) results in a hung firefox with process lpd using 20+ % of CPU. Am using windowmkaer from the 9.1 distro and using local filtering to a remote printer via lprng ( not cups as could never get cups to print to the remote )

I use cups. What is your printer? Is it a network printer, or hooked to another machine on the network?

Brother laser on a networked spooler ( gets printed to by a number of MS machines and a SCO machine ) lpstat -p ( as suggested ) shows Printer: lp@mossdog 'lpdfilter drv=upp method=auto color=yes' (dest lp@172.29.136.20) Other apps seem able to print to it fine. Cheers F

On Tue, 23 Nov 2004 21:05, Francesco Scaglioni wrote:

Have done exactly that and any attempt to print ( or even selecting page setup ) results in a hung firefox with process lpd using 20+ % of CPU. Am using windowmkaer from the 9.1 distro and using local filtering to a remote printer via lprng ( not cups as could never get cups to print to the remote )

Any suggestions most appreciated

I'm struggling with the same problem. On my machine (SuSE 9.2) here at home the printers are connected directly to it and firefox prints without any problems to both printers. This is using the SuSE RPM. Now at work I just installed SuSE 9.2 on one of the computers and for love or money can I get it to print from firefox. The only difference is that the printers run off another server. All other programs I have tried do print. Both setups are using cups. So the only difference appears to be that firefox will not print to a remote server. If I get a chance tonight I will see if I can duplicate the problem here at home and see if I can find a solution. -- Regards, Graham Smith ---------------------------------------------------------

On Tue, 23 Nov 2004 22:06, Johannes Meixner wrote:

Hello,

On Nov 23 21:39 Graham Smith wrote (shortened):

...

Both setups are using cups. So the only difference appears to be that firefox will not print to a remote server.

I don't know how firefox does its printing stuff internally.

Therefore I am only guessing:

Perhaps firefox reads /etc/printcap (-> /etc/cups/printcap) to determine the available queues. In this case it will recognize only local queues because the cupsd writes only the local queues to /etc/cups/printcap.

Perhaps firefox must be forced to contact a remote cupsd directly? This may be possible by setting the environment variable CUPS_SERVER like export CUPS_SERVER="server.domain" provided firefox cares about the CUPS_SERVER setting.

Perhaps firefox asks the local cupsd for its available queues. Then the remote cupsd must broadcast its queues to the local cupsd - this is called "Browsing" in CUPS, see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html In this case the remote queues must be shown on the client machine by "lpstat -p".

Thanks for the tips. The thing is the remote queues appear OK in firefox. When you print everything appears to work ( no error message if started from a terminal) but nothing is printed. If I get a chance later tonight/morning I will set it up on my laptop and watch the logs on cups to see what is going wrong. I ran out of time at the office looking into this problem yesterday. -- Regards, Graham Smith ---------------------------------------------------------

I dont know if this solution is what you are looking for. I have cups and firefox printing without problem. Open firefox -> print -> print properties -> Print Command Change what firefox offers with: kprinter -stdin So firefox will print through "kprinter".kprinter will offer you all availaible printers, inclusive remotes. I dont have problems with cups. Cups as client works perfectly with our remote server. The server itself works with cups also. Kind regards, Beatriz Johannes Meixner wrote:

Hello,

On Nov 23 21:39 Graham Smith wrote (shortened):

...

Both setups are using cups. So the only difference appears to be that firefox will not print to a remote server.

I don't know how firefox does its printing stuff internally.

Therefore I am only guessing:

Perhaps firefox reads /etc/printcap (-> /etc/cups/printcap) to determine the available queues. In this case it will recognize only local queues because the cupsd writes only the local queues to /etc/cups/printcap.

Perhaps firefox must be forced to contact a remote cupsd directly? This may be possible by setting the environment variable CUPS_SERVER like export CUPS_SERVER="server.domain" provided firefox cares about the CUPS_SERVER setting.

Perhaps firefox asks the local cupsd for its available queues. Then the remote cupsd must broadcast its queues to the local cupsd - this is called "Browsing" in CUPS, see http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html In this case the remote queues must be shown on the client machine by "lpstat -p".

Regards Johannes Meixner