I wonder if you have really solved the problem. 
in my experience changing printing permissions will be a disaster. 
Peter 

Peter D Knight 
22 Westfort rd
Houtbay 
7806
0827407210

----- Reply message -----
From: "Mahmoud Ramadan" <[email protected]>
To: <[email protected]>
Subject: [Ltsp-discuss] LTSP CUPS is NOT Printing with “ Filter Failed ” Error 
Message.
Date: Sat, Jan 23, 2016 14:20
Thank u all...the issue has been solved by using #chmod -R 777 cups  it was a 
permission issue with the configuration files causes cups to trigger message 
filter errors...but again solved with fixing the cups folder 
permissions...thanks gain...
Best Regards,Mahmoud Ramadan AliNetwork and VOIP Specialist.





Mobil: (+2) 01276877112Blog | Website | LinkedIn

On Sat, Jan 23, 2016 at 5:06 AM, Truth <[email protected]> wrote:
On 23.01.2016 07:08, Alkis Georgopoulos wrote:

> On 22/01/2016 10:45 μμ, Mahmoud Ramadan wrote:

>> Hi dears,

>> I've migrated my CUPS working configuration to the Chroot image by

>> copying the /etc/cups directory to the target LTSP chroot image and the

>> printers appears in the LTSP clients GUI without any problem BUT

>> whenever i try to print a document i get an error message saying "

>> Filter Failed " and the job stops !

>>

>> I've verified that the " foomatic-filters " are installed and still get

>> the same error...any help to solve this issue please and thanks in advance.

>>

> 1) Set up all your printers on your server.

> Then go to the printers control panel (system-config-printer) and select

> Server => Settings => [v] Publish shared printers connected to this system.

>

> 2) The stock Ubuntu LTSP version is quite broken and old, it won't work.

> Use a very recent LTSP version, e.g. LTSP 5.5.5 from the Greek schools PPA:

> # add-apt-repository ppa:ts.sch.gr

> # apt-get update

> # apt-get dist-upgrade

> both in the server and in the chroot

>

> 3) Don't do anything in lts.conf nor in the chroot cups folder.

> Both thin and fat clients will automatically use

>     CUPS_SERVER=<server_ip>

> and will see all the server's printers without any other configuration,

> without having to add drivers etc.



I also had problems to print from a LTSP-PNP fat-client (version

5.5.5-1~bpo8+1).

It turns out that both server and client try to share the same printer ...



I've been able to solve this problem as follows:

1.) Make sure that you are able to use the printer form the server.

2.) On the server: Disable (within CUPS) sharing connected printers

3.) Update your image (or built your client and/or copy /etc/cups)

2.) On the server: Enable (within CUPS) sharing connected printers

5.) Boot and print from the client



Truth









------------------------------------------------------------------------------

Site24x7 APM Insight: Get Deep Visibility into Application Performance

APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month

Monitor end-to-end web transactions and take corrective actions now

Troubleshoot faster and improve end-user experience. Signup Now!

http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140

_____________________________________________________________________

Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:

      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss

For additional LTSP help,   try #ltsp channel on irc.freenode.net
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to